HP Virtualization Manager with Logical Server Manager 6.2 User Guide

using the name of an existing system in HP SIM, if a host with that name is discovered after you
create or import the logical server, the logical server information is overwritten and Virtualization
Manager no longer displays the logical server.
Suggested actions
1. Restart the Logical Server Automation Service. This modifies the HP SIM system so that the
host named object is once again a logical server.
2. If the logical server is activated, deactivate it using Tools→Logical Servers→Deactivate....
3. Rename the logical server using Modify→Modify Logical Server.... On the Identity tab,
change the name of the logical server to a new, unique name.
4. Delete the HP SIM node for the original logical server. To delete the node, click All Servers,
select the system with the new name from step 3, and click Delete.
5. Restart the Logical Server Automation Service. This recreates the logical server with the new
name.
6. If the logical server was previously activated, then deactivated, reactivate it using
Tools→Logical Servers→Activate....
7. Use the HP SIM Option→Discovery... menu selection to rediscover the host.
Oversubscribing the number of networks
It is possible to "over subscribe" the number of networks for a Virtual Connect 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.
Insufficient NICs error when activating or moving logical servers (Virtual
Connect Flex-10 support)
Virtual Connect Flex-10 Ethernet Module for c-Class BladeSystem is supported in this release.
Flex-10 technology increases the number of NICs per connection. If you activate or move a Virtual
Connect logical server and you have a large number of networks configured, the blades with
Flex-10 are shown in the list of available targets with a soft error icon indicating insufficient
NICs.
Suggested action If you know that the target enclosure and blade support Flex-10, check that
the error message concerns insufficient NICs. In these cases, you can ignore the message and
select the target.
Use caution when renaming or moving a Virtual Connect domain group
Use caution when renaming or moving a Virtual Connect domain group, which is accomplished
by checking Change Logical Server Associations using the Tools→Logical Servers→Refresh...
menu selection. Do not use this functionality to merge Virtual Connect domain groups. This
functionality must only be used to reassociate logical servers to a new domain group name. Do
not specify an existing domain group for the New Domain Group Name, otherwise your logical
servers may become unusable.
Deactivate or move logical servers before replacing blade
Before you replace a blade in an enclosure that is currently hosting a logical server, move or
deactivate any logical servers that are active on the blade. After the new blade has been installed,
discovered, and licensed, perform the Tools→Logical Servers→Refresh... menu selection for
Virtual Connect server resources. Then reactivate the logical servers on the blade or move them
back from the location to which they have been moved.
110 Troubleshooting