HP Virtual Connect errors 230
• The VC fabric has no configured ports. The user removed all the uplink ports from the fabric.
• ALL VC fabric ports are in one of the following states:
o FAILED (hardware error), UNAVAILABLE (not logged in), DISABLED, UNKNOWN (FC module
NO-COMM).
o There is no uplink that is in DEGRADED or OK state.
Action: Configure the uplink ports.
Unknown Module events (9000-9999)
9012 - Unknown Module state FAILED
Severity: CRITICAL
Description: An unknown module has been labeled with a FAILED status. This status is usually indicated by the
OA after a module hot-plug insert operation or when VCM is starting up. This condition is usually fatal.
Possible cause: A hardware failure or corrupted firmware.
Action:
• 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.
To Next Page
Loading...
Need help?
General
