Operating Environment Software User Manual

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 Systems Insight Manager 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.
Unmanaging a logical server using a storage pool entry may result in an
inconsistent state
If a storage pool entry was associated with the unmanaged logical server, the WWNs that are
still being used by the profile remain in the logical server, but the storage pool entry is marked as
Inoperable, and the Ready check box is grayed out. These WWNs will not be assigned to a new
logical server while in this state.
To make the logical server Operable, perform one of the following methods:
Suggested action 1
Delete the VC Profile (freeing up the WWNs), then run Refresh Server Resources and select Virtual
Connect Resources. This allows you to re-use the existing WWNs.
Suggested action 2
Increment the Maximum Sharer count, adding new WWNs that are free to be used. This is useful
only if a new logical server will be able to share access to the disks with the current VC profile.
Oversubscribing the number of networks 85