HP ProLiant Gen8 Troubleshooting Guide Volume II: Error Messages

HP Virtual Connect errors 216
Enclosure events (2000-2999)
2003 - Enclosure import failed
Severity: CRITICAL
Description: An import or recovery of an enclosure failed. Imports are triggered by a user request to add an
enclosure to the domain. Recoveries may be triggered by a VCM reset, VCM failover, Configuration restore,
firmware upgrade, user re-authentication request, or the reconnection of an enclosure that was previously in
a NO-COMM state.
Possible causes:
• The primary OA IP, username, or password is not valid. This would include having insufficient
permissions. Administrator privileges, with full IOBAY and Device Bay access is required.
• The FW version of the primary OA of the enclosure is not >= 3.11.
Action: Do not attempt any configuration changes to the Virtual Connect Domain. Recommended corrective
actions:
• Provide valid OA credentials (IP/user/password) if requested by VC.
• Make sure that the user has interconnect bay access privileges.
• Verify OA and VC have been assigned IP addresses and that the IP addresses do not conflict with other
assignments on the network.
• Verify that OA management network is not being used for substantial data traffic.
• Verify that management network topology is correct.
• Verify end-to-end connectivity (for example, the ping command).
• Make sure the OA has appropriate firmware version and update if necessary.
• If all workarounds fail:
a. Export a support package from VC for HP analysis.
b. Capture the output of the OA show all command for HP analysis.
c. Contact HP customer support with the previously gathered information.
2011 - Enclosure state NO_COMM
Severity: CRITICAL
Description: The VC management application is unable to communicate with an enclosure.
Possible cause: The VC management application has determined that the serial number of the enclosure does
not match the stored configuration. This event might occur when an OA has been moved from one enclosure
to another or when the enclosure backplane has been replaced.
Action:
• If the OA has been moved to a different enclosure, provide VC with the OA credentials
(IP/user/password) of the OA in the enclosure that VC should import.
• If the enclosure backplane has been replaced, follow the backplane replacement recovery procedure.