HP Virtual Connect for c-Class BladeSystem Version 3.00 User Guide for Integrity BL8x0c i2 Server Blades

Hardware information screens 127
Causes for INCOMPATIBLE status
When a module status is INCOMPATIBLE, details can be viewed in the System log ("System Log screen"
on page 49). The system log provides information about why a module is marked incompatible so that
proper corrective action can be taken.
Following is a list of reasons why a module might be INCOMPATIBLE and the suggested corrective
action.
• Module adjacency
Typically, a module can only be in a bay next to a module of the same type. See the installation
guidelines in the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide.
If a module is next to another module that it is not compatible with, both modules will be labeled as
INCOMPATIBLE, since the rule applies to both modules.
Corrective action: Remove the adjacent incompatible modules and replace with modules that are
compatible next to each other.
• Module replacement
If an interconnect module is being used by the domain, is physically removed, and then another
module is put in the same bay, the new module must be the same type as the module previously 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 in interconnect bay 1 or bay 2 of the primary enclosure
VC-FC Modules In-Use by the Domain modules are considered in use by the domain if uplinks or
downlinks are being used by fabrics or profiles
Corrective action: Remove the incompatible module and replace with the same module that
previously existed. For more information, see "Module removal and replacement (on page 141)."
• 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.
• FC bay groups
In a multi-enclosure environment, all enclosures must have the same FC module configuration. For
more information, see the multiple enclosure guidelines in the HP Virtual Connect for c-Class
BladeSystem Setup and Installation Guide.
Corrective action: Remove the incompatible module and replace it with the correct module for the FC
bay group that already exists.
• In a c3000 enclosure, FC modules are not supported in bay 2.