Corrective action: Configure FIPS mode on the module. To configure FIPS mode, see "Enabling FIPS mode (on page 316)."

FC bay groups

In a multi-enclosure environment, all enclosures must have the same FC module configuration. For more information, see "Multiple enclosure requirements (on page 62)."

Corrective action: Remove the incompatible module and replace it with the correct module for the existing FC bay group.

In a c3000 enclosure, VC-FC modules are not supported in bay 2.

FC modules in multi-enclosure double dense domains

When using VC-FC modules, multi-enclosure double dense domains require similar and compatible VC-FC modules in bays 5, 6, 7, and 8 in all enclosures. If a multi-enclosure double dense configuration contains incompatible VC-FC modules in bays 5, 6, 7, or 8 in either the local or remote enclosures, some or all of the compatible VC-FC modules in the remote enclosures might be designated INCOMPATIBLE after import.

Corrective action:

a.Replace incompatible VC-FC modules with similar and compatible VC-FC modules in bays 5, 6, 7, and 8 in all enclosures.

b.Power cycle any VC-FC module that still remains in an INCOMPATIBLE state.

Ethernet Bay Summary (General Information) screen

This screen provides a summary of the interconnect module status and general information. To remove a module, see "Interconnect module removal and replacement (on page 275)."

The following table describes the rows within the Interconnect Bay Status table.

Row

Description

 

 

 

 

Overall Status

Represents the worst condition of OA Reported Status, VC Status, and OA

 

 

Communication Status

 

 

 

 

Hardware Status

Component health status from the Onboard Administrator

 

VC Status

Component health status from the Virtual Connect Manager

 

 

Virtual Connect modules 240