• 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:
1. Export a support package from VC for Hewlett Packard Enterprise analysis.
2. Capture the output of the OA show all command for Hewlett Packard Enterprise analysis.
3. Contact Hewlett Packard Enterprise 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.
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 are 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 are 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:
2011 - Enclosure state NO_COMM 287