HP ProLiant Gen8 Troubleshooting Guide Volume II: Error Messages

HP Virtual Connect errors 217
2013 - Enclosure state failed
Severity: CRITICAL
Description: The enclosure is non-functional due to total Ethernet module or total server hardware failures. VC
cannot configure or monitor this enclosure.
Possible causes:
• All Ethernet modules are not OK or DEGRADED. All Ethernet modules are suffering from some kind of
hardware failure that prevents them from accepting configuration and passing network traffic.
• All servers are not OK or DEGRADED. All servers are suffering from some kind of hardware failure that
prevents them from accepting configuration and passing network traffic.
Action: Do not attempt any configuration changes to the Virtual Connect Domain. Recommended corrective
actions:
• Check all Ethernet modules that are in not OK or Degraded state. Replace if necessary.
• Check all Servers that are in not OK or Degraded state. Replace if necessary.
• If hardware replacement does not correct the issue:
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.
2016 - Enclosure Find failed
Severity: MAJOR
Description: An add, import, or recovery of an enclosure failed while attempting to perform a connection or
reconnection with the enclosure. Find operations are cause by a user request to add an enclosure to the
domain. Reconnections may be caused 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.
• The FW version of the primary OA of the enclosure is not >= 3.11.
• During the connection or reconnection operation a call to the OA fails. This might be because of a failed
portion of OA/Enclosure hardware or the OA has not recovered sufficiently after a previous failure.
• Communications with the OA is not available due to networking issues.
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.