HPE ProLiant Gen9

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
Description: A profile was changed or assigned and some configuration required that the server be powered
off to make the change. For example, if the number of Ethernet connections is changed for a profile that is
assigned to a server with Flex-10 NICs, then the server must be powered off.
Possible causes:
• A user action results in a profile that requires the server be powered off to make the change or initially
assign or remove the profile.
• VCM restarts and detects a powered on server that has a profile assigned to the bay and the profile needs
to make a change on the server that requires it to be powered off.
Action: Power down the server and retry the change.
Ethernet Network events (7000-7999)
7012 - Enet Network state FAILED
Severity: CRITICAL
Description: The VC Enet Network lost all uplink connectivity because of lack of configured ports or all
configured ports are in a bad state or because a bad or incompatible transceiver was inserted.
Possible causes:
296 6023 - Profile is assigned to a multi-blade server that has data missing