Enet Module State Missing - HP ProLiant Gen9 Troubleshooting Manual

Action: Insert a module that is compatible with the adjacent module.
Observe the following guidelines when installing interconnect modules in horizontally adjacent bays:
•
Only like 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.
•
HP 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.
•
HP 1/10 Gb VC-Enet Modules and HP 1/10 Gb-F Ethernet Modules can reside in any bay. However,
only another HP 1/10 Gb VC-Enet Module or an HP 1/10 Gb-F Ethernet Module can reside in an
adjacent bay.
•
HP VC 8Gb 20-Port FC Modules can reside in any bay. However, only another HP VC 8Gb 20-Port FC
Module can reside in an adjacent bay.
•
HP 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 HP Virtual Connect 8Gb 24-Port FC Modules with HP 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.)

3019 - Enet Module state MISSING

Severity: CRITICAL
Description: A module that is configured in the domain is physically missing in the enclosure.
Possible cause: A module configured as "in-use" by the domain by a network, uplink set, or profile, and has
been physically removed from an enclosure. Modules that are configured and being use by the domain
cannot be removed from the domain (because of domain dependencies) and must be replaced by modules
of the same type.
Action: When removing modules, make sure that you replace the module with the same type. If you are not
planning to replace the module, then the domain should be modified prior to physical removal to eliminate
the dependencies on the module so that it can be cleanly removed from the domain. If you are planning to
replace the module with one of a different type, you must remove the dependencies on the module prior to
removal so that it can be cleanly removed from the domain prior to inserting the new module.
HP Virtual Connect errors 222