EasyManua.ls Logo

HPE ProLiant Gen9 - Enet Uplinkset Events (17000-17999)

HPE ProLiant Gen9
460 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Re-insert a module of the same type back into the bay that is marked as missing.
Make modifications to the domain to eliminate the dependencies on the missing module. Once the
dependencies have been removed, resetting VCM should clear the missing module indication.
9014 - Unknown Module state INCOMPATIBLE
Severity: MAJOR
Description: An unknown module is incompatible with the current domain configuration.
Possible causes:
An unknown module is adjacent to a module that is not unknown (a VC module).
An unknown module is not supported in the bay where it is physically located. For example, primary or
standby bays, or in a FC bay group bay.
Action:
Remove either the unknown module, or the module adjacent to it.
Remove the unknown module from the interconnect bay.
Try re-seating or rebooting the module to see if it can recover.
Physically remove and replace the module.
Analyze the Onboard Administrator logs for possible details regarding the failure.
9019 - Unknown Module state NO_COMM
Severity: MAJOR
Description: VCM cannot properly communicate with the module.
Possible cause 1: The module is powered off.
Action: Power the module back on through the OA interface.
Possible cause 2: Unable to communicate with the module through management interfaces.
Action: Reseat, reboot, or replace the module with one of the same type.
Possible cause 3: If a module reset occurred recently, it might be in this state for a period of time until VCM
can properly communicate with it. If this is the case, then waiting for a few minutes will usually clear the state.
Action: Wait for up to 5 minutes to see if the module recovers from this state.
Possible cause 4: Module reset occurred, but module never recovered from this state because VCM did not
receive an event notification from the OA. This can be caused by a problem with the OA firmware, or a
problem with the module.
Action: Reseat, reboot, or replace module with one of the same type.
Enet uplinkset events (17000-17999)
17012 - Enet uplinkset state FAILED
Severity: CRITICAL
Description: The VC Enet network lost uplink connectivity in the uplink set due to lack of configured ports,
all configured ports are in a bad state, or a bad or incompatible transceiver was inserted.
298 9014 - Unknown Module state INCOMPATIBLE

Table of Contents

Other manuals for HPE ProLiant Gen9

Related product manuals