Logical Server Management

For additional information not included in the online help and documentation for logical server management, see Insight Dynamics VSE 4.1 Update 1 Documentation Addendum.

Limitations

The following is a limitation for Logical Server Management.

For important information about requirements for logical server management, see Insight Dynamics VSE 4.1 Update 1 Documentation Addendum.

Performing Actions on a Virtual Connect Blade Logical Server Running as a Hypervisor

You can perform any actions on a Virtual Connect blade logical server running as a hypervisor as long as the hypervisor does not also contain any managed virtual machine logical servers.

Major Issues

The following are major issues for Logical Server Management.

Service Restart is Required if UUID of Virtual Machine Changes During Logical Server Reactivation

Occasionally when you are reactivating a virtual machine logical server, a timing issue in VMware VirtualCenter 2.5.0 or VMware Infrastructure Client 2.5.0 changes the UUID of the logical server when it registers the virtual machine.

The UUID is used to manage the logical server, so a changed UUID causes the activation job to run indefinitely. You cannot cancel a running job. If you notice an activation job that is running for an unusually long time, verify that this problem has occurred in VMware Infrastructure Client. Select the affected virtual machine, then the Tasks & Events tab. Click on the Events view and check for an error stating “Warning BIOS UUID was changed.”

Workaround Install VMware VirtualCenter 2.5 Update 4, which is available from http://www.vmware.com/download/vi/.

Oversubscribing The Number of Networks for a Virtual Connect Blade Logical Server

It is possible to "over subscribe" the number of networks for a Virtual Connect blade logical server. If the logical server requires more network connections than are supported by the NICs on a given blade, some of the networks specified in the logical server will not be available to the operating system.

Minor Issues

The following are minor issues for Logical Server Management.

Virtual Connect Blade Logical Servers Minor Issues

Logical Server Associations Not Displayed on HP SIM System Page Associations List The associations list for a logical server on the HP SIM ToolsSystem InformationSystem Page... does not show associations between the mxnode for an active logical server and the object on which the logical server is running (virtual machine or blade). These associations do appear in the HP SIM System table and in the perspectives of the Virtualization Manager Visualization tab.
Enclosure Bay 3 Must Contain VC-FC Module or Fabric Connection Before Bay 4 You cannot create, import, or activate a Virtual Connect blade logical server if the enclosure contains a VC-FC module in bay 4 that is connected to a SAN fabric and bay 3 either does not contain a module or is not connected to a SAN fabric.
Workaround Move the VC-FC module or fabric connection, or both, from bay 4 to bay 3.
Activating Logical Servers when there are Identically Named Enclosures in a Virtual Connect Domain When you activate a Virtual Connect blade logical server, the target selection screen does not display the VC domain of potential target hosts. Virtual Connect Enterprise Manager 1.30 allows more than one enclosure to have the same name in the same VC domain group.
Workaround Check the serial number of the enclosure and select the target blade in the appropriate enclosure.

Target Hosts Rejected with Incorrect Error When you move a Virtual Connect blade logical server, some blades may be rejected as possible target hosts with an incorrect hard error. This happens if the following conditions are met:

VCEM 1.30 is installed.
The logical server is active on a VC Domain with more than one enclosure.
The logical server is active on a blade with the same bay number, but different enclosure, as the rejected blade.
The rejected blade has another logical server active on it.

In this case, the target blade is rejected, which is correct behavior, but the error reported for the rejection incorrectly states that the logical server to be moved is active on the rejected blade.




	NOTE: The latest release of HP ProLiant Essentials Server Migration Pack (SMP) contains HP Portable Images Network Tool (PINT), which may be useful when moving a logical server to a target server blade with a warning on it. See the HP Insight Dynamics - VSE Suite Information Library for more information.

Configuring Storage Entry For A Virtual Connect Blade Logical Server When you are configuring the storage entry for a Virtual Connect blade logical server, note the following issues.
- When you specify a LUN identifier that corresponds to the server world wide name for each storage volume, LUN IDs can be in one of the following formats:
  Decimal number in the range of 0 to 255
  Hexadecimal number with 13 to 16 digits
  An example of defining a boot volume and data volume is to set one path to each volume as primary boot and (assuming redundancy) the other path to each volume (boot or data) as ** ** secondary boot. Do not select disabled from the drop-down menu.
  You can create, modify, import, and activate a logical server with LUN IDs in these formats. However, you can perform storage validation only on storage volumes with LUN IDs that are decimal numbers in the range of 0 to 255. Storage validation returns “not found” for storage volumes with LUN IDs not in decimal format.
- In the Volume Path Settings table, the Boot Path column title is misleading. The column should be named Path, because some of the volumes in the table may be data volumes. The path is a boot path only if the volume is the boot volume. The path is a data path for data volumes.
(ProLiant Only) After Upgrading, A Virtual Connect Blade Logical Server Displays A New Disabled HBA Port After an upgrade from ID-VSE 4.0 to 4.1, a Virtual Connect blade logical server may display a new disabled HBA port on the Create Logical Server storage screen that was not displayed on the corresponding 4.0 screen. In 4.1, the number of ports is determined by the number of active connection bays within the domain group. For example, if the enclosure has two active connection bays, and the 4.0 logical server had one port, then one extra disabled port is displayed. Similarly, a new unassigned network port may be displayed on the 4.1 active server network page that was not displayed on the corresponding 4.0 page.
These new ports were part of an activated logical server in 4.0, but were not displayed on the screens. This is expected behavior.

ESX and Hyper-V Virtual Machine Logical Servers Minor Issues

SAN Storage Names with Parentheses Can Cause VM Hosts to be Rejected Targets at Activation Do not use a SAN storage name that includes a parentheses when you specify the storage configuration for a virtual machine logical server. For example, MYSAN(1) is an invalid SAN storage name. Logical server management interprets the value inside the parentheses as a storage identifier. When the logical server is activated, the VM Hosts are shown as rejected target hosts with an incorrect storage error.
Workaround When you create SAN Storage, specify storage names that do not include parentheses.
Cannot Activate Logical Server if Operating System Variation is “Other Linux” or “Invalid Entry” (ESX 3i Only) If you create an ESX virtual machine logical server and specify Linux as the operating system and Other Linux as the OS Variation on the Create Logical Server Identity screen, you cannot activate the logical server on an ESX 3i VM host.
Similarly, if you import an ESX virtual machine logical server and the View Logical Server Details screen displays “Operating System: <Invalid Entry>”, you cannot activate the logical server on a VM host.
Workaround Modify the logical server identity and select another Operating System Variation, then retry the activation.
Free Disk Space on the VM Host Is Smaller Than The Amount of Memory Chosen For The Logical Server When you create a Hyper-V virtual machine logical server, if the amount of free disk space on the VM Host is smaller than the amount of memory chosen for the logical server, the logical server cannot be powered on. This occurs infrequently, because free disk space is usually larger than memory size.
Workaround Use HP SIM to power on the logical server. Select the VM node and click the power on button.
Activation Times Out If you attempt to activate a virtual machine logical server and the activation times out (after 10 minutes), retrying the activation may return the error:
VM already registered
Workaround Manually refresh logical servers by using the Tools -> Logical Servers -> Refresh... menu selection, or wait for the automatic refresh to occur (every 60 minutes).
Reactivating A Virtual Machine Logical Server May Fail If you attempt to reactivate a virtual machine logical server, the operation fails with an ID not specified error.
Workaround Delete the logical server (selecting Recoverable Logical Server Definition Deletion), then import the virtual machine.