HP Virtual Connect for c-Class BladeSystem Setup and Install Guide Version 3.70 and 3.75
Installation 19
• Only install HP Virtual Connect Flex-10 Modules into bays horizontally adjacent to bays containing
another HP Virtual Connect Flex-10 Module.
If any other type of module is installed, the second one discovered is set to UNKNOWN, and no
connections are made to the server NICs attached to the interconnect bay. The module is set to
UNKNOWN because it is removed automatically from the VC domain when removed physically from
the interconnect bay.
• If an HP Virtual Connect Flex-10 Module is connected to a Flex-10 NIC that corresponds to an Ethernet
connection in a server profile, then replacing the module with any other type of Virtual Connect Ethernet
module requires that all network uplinks be removed from the module before replacement. For more
information on module removal, see "Interconnect module removal and replacement (on page 45)."
If the replacement module is not removed from the GUI, the module is marked as INCOMPATIBLE, and
no connections are made to the server NICs attached to the interconnect bay.
• An empty interconnect bay horizontally adjacent to a bay containing an HP Virtual Connect Flex-10
Module is treated as if it has a Flex-10-compatible Ethernet module for server configuration. If the
corresponding server NIC is Flex-10, it is partitioned according to the connections in the server profile.
Adding a module that does not support Flex-10 when the corresponding server is configured for Flex-10
results in the module being set to INCOMPATIBLE.
HP Virtual Connect Flex-10/10D Module guidelines
The following guidelines apply to the installation or replacement of HP Virtual Connect Flex-10/10D
Modules:
• Only install HP Virtual Connect Flex-10/10D Modules into bays horizontally adjacent to bays
containing another HP Virtual Connect Flex-10/10D Module.
If any other type of module is installed, the second one discovered is set to UNKNOWN, and no
connections are made to the server NICs attached to the interconnect bay. The module is set to
UNKNOWN because it is removed automatically from the VC domain when removed physically from
the interconnect bay.
• If an HP Virtual Connect Flex-10/10D Module is connected to a Flex-10 NIC that corresponds to an
Ethernet connection in a server profile, then replacing the module with any other type of Virtual Connect
Ethernet module requires that all network uplinks be removed from the module before replacement. For
more information on module removal, see "Interconnect module removal and replacement (on page
45)."
If the replacement module is not removed from the GUI, the module is marked as INCOMPATIBLE, and
no connections are made to the server NICs attached to the interconnect bay.
• An empty interconnect bay horizontally adjacent to a bay containing an HP Virtual Connect
Flex-10/10D Module is treated as if it has a Flex-10-compatible Ethernet module for server
configuration. If the corresponding server NIC is Flex-10, it is partitioned according to the connections
in the server profile. Adding a module that does not support Flex-10 when the corresponding server is
configured for Flex-10 results in the module being set to INCOMPATIBLE.
• An HP Virtual Connect Flex-10/10D Module can only be used in a domain running VC firmware v3.70
or higher, otherwise the module is marked as UNKNOWN.