HP 1.10GB Virtual Connect Ethernet Module for c-Class BladeSystem - Manual (Page 175)

Hardware information screens 175
Column Description
Profile Server Profiles with connections to this port
HBA Port HBA port number
HBA Port Speed Speed setting of the HBA port
HBA Port Status Status of the HBA port
HBA WWPN Either the World Wide Port Name assigned to the port or the Server Factory
Default, if not assigning WWNs
Special notes on interconnect module removal and replacement
In VC releases prior to 3.00, when a module was removed from an enclosure and was no longer in use by
the domain, it had to be removed from the domain using the "Remove from Domain" feature available in the
GUI and VCM CLI.
Starting with VCM firmware version 3.00, it is no longer necessary to remove the module from the domain
if the module is not in use. In that scenario, the module is removed automatically from the domain without user
intervention.
Replacing a primary or backup VC module with a different VC module type is not allowed without first
deleting the domain.
If a module is in-use and configured by the domain at the time it is physically removed from an enclosure, then
the module is marked as MISSING, and can only be replaced by a module of the same model and type. If
an in-use module is replaced by a module of a different type, then it is marked as INCOMPATIBLE by the
domain.
If a module being physically removed is the primary module of a primary bay pair, then it is marked as
MISSING and can only be replaced by a module of the same type.
A VC-Enet module is in use if any the following conditions exist:
• The module physically exists in an interconnect bay.
• The uplink and downlink ports of the module are being used by one or more networks, uplink sets, or
profiles.
• Port monitoring is enabled for the interconnect module.
A VC-FC capable module is in use if any the following conditions exist:
• The module physically exists in an interconnect bay.
• The uplink ports of the module are being used by a fabric that is being used by a profile.
• The module is part of a FC bay group in a multi-enclosure configuration where other FC modules exist
in the bay group.
If a VC-FC module is replaced with a spare VC-FC module without powering down the servers, and if the
server has profiles assigned to it with FC connections, servers are allowed to log in for a brief period through
an uplink of the new module, provided that the uplink is connected to the fabric. Approximately 8 seconds
after discovering the new VC-FC module, VCM configures it with the correct information, mapping downlinks
to the correct uplinks. To work around this problem, power down the servers in the enclosure before
replacing or swapping FC modules. Alternatively, do not connect the VC-FC uplinks to the fabric until VCM
recognizes and configures the VC-FC module.