HP ProLiant Gen9 Troubleshooting Manual page 228

Action: Remove the duplicate network from one or more of the Ethernet Connections. The GUI profile editor
will indicate which connections have duplicates.
6021 - Profile has PXE enabled on a non-primary Flex-10 NIC
Severity: MAJOR
Description: PXE is enabled on an Ethernet connection in a profile that is mapped to a non-primary physical
function on a Flex-10 NIC. The current Flex-10 implementation does not allow PXE booting on any but the first
physical function on a Flex-10 NIC port.
Possible cause: PXE is enabled on an Ethernet connection that is mapped to the second, third, or fourth
physical function on a Flex-10 NIC.
Action: Use the GUI to edit the profile and disable PXE on any connections that show PXE is not supported on
them.
6022 - Profile has iSCSI boot enabled on an unsupported Flex-10 NIC
Severity: MAJOR
Description: A profile has iSCSI boot enabled on an unsupported Flex-10 NIC.
Possible cause: An administrator has incorrectly configured the boot settings for the profile.
Actions:
•
Correct the specified profile settings to enable the iSCSI boot on a supported NIC.
•
Remove the iSCSI configuration from profile.
•
Insert a supported NIC card to configure iSCSI boot.
6023 - Profile is assigned to a multi-blade server that has data missing
Severity: MAJOR
Description: VCM does not have information about all of the bays in multi-blade server. The GUI should show
the appropriate state.
Possible cause: All the blades of the server could not complete initialization successfully; therefore, some
blades in the multi-blade server are not yet discovered.
Actions:
•
Check the status of the bays for an indication of the problem.
•
Remove and install the server into the bays that are indicating an error.
•
Reboot the server and check to see if it is discovered.
•
Physically remove and replace the server.
•
Analyze the Onboard Administrator logs for possible details regarding the failure.
6030 - Profile could not be assigned to powered up server
Severity: MAJOR
HP Virtual Connect errors 228