Column

Description

 

 

Firmware Rev

Firmware revision of the interconnect module installed in this bay

 

 

Causes for INCOMPATIBLE status

When an interconnect module status is INCOMPATIBLE, details can be viewed in the System log ("System Log (System Log) screen" on page 48). The system log provides information about why an interconnect module is marked incompatible so that proper corrective action can be taken.

The following list provides reasons why an interconnect module might be INCOMPATIBLE and the suggested corrective actions:

•Module adjacency

Typically, interconnect modules installed in adjacent bays must be of the same type. For more information, see the installation guidelines in the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide on the HP website (http://www.hp.com/go/vc/manuals).

If two adjacent modules are incompatible, both modules are labeled as INCOMPATIBLE, since the rule applies to both modules.

Corrective action: Remove the adjacent incompatible modules and replace with modules that are compatible.

•Module replacement

If an interconnect module is being used by the domain and is physically removed, and then another module is installed in the same bay, the new module must be the same type as the module previously installed in the bay.

If the physically removed module was not being used by the domain, the module can be replaced with a module of a different type.

VC-Enet modules are considered in use by the domain under the following conditions: o Uplinks or downlinks are being used by networks/profiles.

o The module is the primary or standby module.

VC-FC Modules are considered in use by the domain under the following conditions: o Uplink ports on the module are being used by a fabric.

o The fabric is being used by a profile connection.

Corrective action: Remove the incompatible module and replace with the previously existing module. For more information, see "Interconnect module removal and replacement (on page 275)."

•Firmware version

Only modules with firmware versions supported by the firmware running on the primary module are compatible. All other versions of firmware modules cause the module to be marked as INCOMPATIBLE.

Corrective action: Use VCSU to update incompatible modules to the appropriate firmware versions for the domain. For more information on updating the firmware, see the HP BladeSystem c-Class Virtual Connect Support Utility documentation on the HP website (http://www.hp.com/go/vc/manuals).

•FIPS mode

When the domain is in FIPS mode, all VC-Enet and FlexFabric modules in the domain must be configured for FIPS mode.

Virtual Connect modules 239