HP ProLiant Gen8 Troubleshooting Guide Volume II: Error Messages

HP Virtual Connect errors 222
Action: Verify that communication between VC and Onboard Administrator for the affected server is
operational. Verify that the server is in a good state (not failed or faulted).
5014 - Server state INCOMPATIBLE
Severity: MAJOR
Description: The VC management application has determined that the server BIOS version does not support
the minimum capabilities required for Virtual Connect.
Possible cause: The server has a down-rev BIOS version.
Action: Update the BIOS on the server to latest version.
5055 - The server BIOS needs to be updated to at least the version dated
Severity: MAJOR
Description: The VC management application has determined that the server BIOS version does not support
the minimum capabilities required for Virtual Connect.
Possible cause: The server has a down-rev BIOS version.
Action: Update the BIOS on the server to latest version.
Profile events (6000-6999)
6012 - Profile state FAILED
Severity: CRITICAL
Description: The profile is in a failed state because none of the connections is functioning correctly.
Possible cause: All the connections in a profile are failed. This is probably due to the networks and fabrics for
all the connections being in a failed state.
Action: Check the status of the individual connections and correct any problems. For example, if all the uplink
ports in a network are disconnected, that network will be in a failed state. Any Ethernet connection in a
profile that has this network assigned will be failed. Reconnecting the uplink ports will clear the failed state
for the network and this will be forwarded up to the Ethernet connection and the profile.
6020 - Profile has the same network on two Flex-10 NICs on the same physical port
Severity: CRITICAL
Description: This occurs whenever a profile is applied to a server with Flex-10 NICs and the same Ethernet
Network is on more than one Ethernet connection that is mapped to a Flex-10 physical function on the same
physical port. All physical functions after the first one with the duplicate network will be disabled, and no
traffic will flow on the connection.
Possible cause: A profile is applied to a server and the mapping results in duplicate Ethernet networks on the
same Flex-10 physical port.
Action: Remove the duplicate network from one or more of the Ethernet Connections. The GUI profile editor
will indicate which connections have duplicates.