Domain State Failed; Domain State Profile_Failed; Domain State No_Comm - HP ProLiant Gen9 Troubleshooting Manual

•
Make sure OA version is appropriate.
•
Export a support package from VC for HP analysis.
•
Capture the output of the OA show all command for HP analysis.

1022 - Domain state FAILED

Severity: CRITICAL
Description: The VC domain is suffering an outage that does not allow VC to talk to any enclosure or device.
While this outage does not affect current network traffic, no domain configuration or monitoring can occur.
Possible cause: There are no enclosures in an OK or DEGRADED state due to physical enclosure faults or VC
lack of OA communication to the enclosures.
Action: Do not attempt any configuration changes to the Virtual Connect Domain. If this error is persistent or
frequently repeated, the cause should be investigated. Recommended corrective actions:
•
Provide appropriate OA credentials (IP/user/password) if requested by VC.
•
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:
Export a support package from VC for HP analysis.
a.
Capture the output of the OA show all command for HP analysis.
b.
Contact HP customer support with the previously gathered information.
c.

1023 - Domain state PROFILE_FAILED

Severity: MAJOR
Description: This event is occurs when at least one profile is not in an OK state.
Possible cause: A profile transitions from an OK state to a state that is not OK.
Action: Verify the status of each profile and find any that are in a state other than OK. Resolve the state of
each profile.

1026 - Domain state NO_COMM

Severity: CRITICAL
Description: This condition indicates that the Ethernet modules stacking links are not fully connected, causing
the effected modules to be isolated.
Possible cause: Stacking Links are not fully connected. This condition causes some Ethernet modules to be
isolated, which causes critical issues with network configuration and server profile mobility/accessibility to
servers.
Action: Connect stacking link cables correctly.
HP Virtual Connect errors 218