3014 - Enet Module state INCOMPATIBLE

Severity: MAJOR

Description: A module that exists in an enclosure is not compatible with the VC domain configuration.

Possible cause 1: A newly inserted module is not compatible with a module that is adjacent to it.

Action: Insert a module that is compatible with the adjacent module.

Observe the following guidelines when installing interconnect modules in horizontally adjacent bays:

  • Only similar VC modules can reside in adjacent horizontal bays.
  • If a VC-Enet module is installed in an interconnect bay, the only module that can be installed in the horizontally adjacent bay is another VC-Enet module of the same type.
  • Virtual Connect Flex-10 10Gb Ethernet Modules can reside in any bay. However, only another Flex-10 10Gb Ethernet Module can reside in an adjacent bay.
  • 1/10 Gb VC-Enet Modules and 1/10 Gb-F Ethernet Modules can reside in any bay. However, only another 1/10 Gb VC-Enet Module or an 1/10 Gb-F Ethernet Module can reside in an adjacent bay.
  • VC 8Gb 20-Port FC Modules can reside in any bay. However, only another VC 8Gb 20-Port FC Module can reside in an adjacent bay.
  • Virtual Connect 8Gb 24-Port Fibre Channel Modules can reside in any bay. However, only another 8Gb 24-Port Fibre Channel Module can reside in an adjacent bay.
  • Do not mix Virtual Connect 8Gb 24-Port FC Modules with Virtual Connect 4Gb or 8Gb 20-Port FC Modules in the horizontally adjacent interconnect bays connected to the same server blade mezzanine card.
  • For c3000 enclosures, VC-FC modules are not supported in interconnect bay 2.

Possible cause 2: A newly inserted module is not the same type as the previously configured module that was in the interconnect bay.

Action:

  • Insert a module of the same type as the one that was previously configured.
  • Before removing the previous module, make domain modifications so that the module that was removed is no longer used by the domain configuration (profiles, networks, and fabrics). When the module is removed, it should not exist in the domain configuration and can be replaced by a module of a different type.

Possible cause 3: The firmware version on a module is not supported by the current VC domain version.

Action: Update the firmware on the module to a version that is supported by the domain. (A version supported by the running primary module.)