Troubleshooting server hardware

For information on specific server hardware issues, see the HPE OneView Release Notes.

Server add or remove is unsuccessful

If the add server action is not successful, a notification panel provides the reason why the action failed and provides a solution to the problem. Often, the resolution is to click the add link embedded in the message; the add action rediscovers all components and updates its knowledge of the server.

Symptom Possible cause and recommendation
Cannot remove a server

Lack of connectivity with the server hardware can prevent the remove action from being successful 

The server is not removed from the appliance. The likely cause is an internal problem on the appliance and the best resolution is to follow the instructions in the notification panel.

The server is removed but due to communication failure, the configuration requires manual intervention to correct.

To forcibly remove a server due to connectivity failure, see Forcibly remove a server if a remove action fails.

In the case where manual configuration is needed, investigate the following:

  • The management URL might still point to the appliance, leave it alone. To manually clean up after removal, use the Force option to add the server back under a new appliance manager.

  • Remove _HPEOneViewAdmin administrative user, from the list of iLO users through the iLO.

  • Remove the SNMP trap destination, which is the IP address of the appliance, from the list of trap targets.

  • Navigate to the HPE OneView page in the iLO web interface, and then click the Delete button in the Delete this remote manager configuration from this iLO dialog.

Cannot control power on server blade

Server hardware power control depends on both the HPE Integrated Lights-Out (iLO) on the target server hardware, and in the case of ProLiant servers, the Onboard Administrator module in the host enclosure.

If you have difficulty with server power control, examine recent configuration and security changes which might affect this feature. Often the iLO event log can be a useful starting point to see these changes.

Another area to examine for ProLiant servers are the power management policies of the enclosure. Verify the Onboard Administrator to ensure sufficient power is available and the power operations policy is appropriate.

Hardware could have failed as well. Use the Integrated Management Log (IML) on the iLO for Power On Self Test (POST) errors to determine if a hardware failure has occurred.

If a power on or power off action fails, follow the instructions in the notification message.

Lost connectivity to server hardware after appliance restarts

When the appliance restarts after a crash, the server inventory is evaluated for any long-running activity that failed, such as applying server profile settings, that might have been in progress when the crash occurred. You can recover by performing the same action again, such as reapplying the server profile settings.

The appliance resynchronizes the servers. During resynchronization, each server hardware enters the resyncPending state. A full resynchronization of individual server hardware includes rediscovering the server hardware, verifying the server hardware power state and updating the resource state accordingly, and updating the health status. The appliance creates a task queue for each task during a resynchronization operation.

Replace a server with an assigned server profile

Symptom Possible cause and recommendation
Server Hardware failure

Server hardware failed and must be replaced

  1. Gracefully shut down the server hardware.

  2. Remove the original server and install the replacement server.

  3. If the server hardware type of the replacement server matches the server hardware type of the original server then:

    1. If the Affinity defined in the profile is set to Device bay, the server profile will be automatically re-assigned to the new server. Proceed to step 5.

    2. If the Affinity is set to Device bay + server hardware, the server profile must be edited and re-saved to allow the appliance to reconfigure the profile for the new server. No changes to the server profile are required. Proceed to step 5.

  4. If the server hardware type of the replacement server does not match the server hardware type of the original server a new profile must be created that matches the server hardware type of the replacement server. The original profile assigned to the server must be unassigned or deleted and the new profile assigned to the replacement server. Or, the server hardware type must be updated to match the inserted hardware.

  5. If the iLO firmware version is greater than or equal to the minimum required firmware version, proceed to Step 6. The minimum iLO firmware version is available in the HPE OneView Support Matrix. If the replacement server has an iLO firmware version less than the minimum required firmware version, an alert on the Server Hardware screen is displayed and the server status is Unmanaged/Unsupported Firmware.

    1. Select ActionsUpdate iLO firmware.

    2. Click OK.

  6. If the iLO firmware version is different from the baseline and the server profile is assigned to a Gen8 server or later, the iLO server firmware can be updated automatically with the re-assignment of the server profile.

    1. From the main menu, select Server Profiles, and then select the server profile to edit.

    2. Select ActionsEdit. If needed, select the proper server hardware.

    3. To manage the firmware update manually, from the Firmware baseline list, select managed manually.

    4. To automatically update the firmware, select the appropriate firmware baseline. To force install the firmware, select Force installation.

    5. Click OK.

    If the firmware version is different from the baseline and the server profile is assigned to a G7 server, you must update the firmware outside of the appliance.

Replace a server adapter on server hardware with an assigned server profile


[IMPORTANT: ]

IMPORTANT: The replacement adapter must match the old adapter. If the replacement adapter does not match the old adapter, the server hardware type will change. If a server profile was assigned to that server hardware, a new server profile must be created to support the changed server hardware type.


Symptom Possible cause and recommendation
Server adapter failure

Server adapter failed and must be replaced

  1. Gracefully shut down the server.

  2. Replace the adapter on the server.

  3. If the corresponding server profile is configured with virtual identifiers (MAC & WWN addresses) proceed to step 4. If the profile is configured with physical identifiers (MAC & WWN), consider the following:

    1. Due to change in the identifiers, any Ethernet network configurations may be lost on the OS and may require a reconfiguration.

    2. The server host WWN may need to be updated in your storage network zone and on the storage array.

  4. Check the firmware version of the new adapter.

    1. From the main menu, select Server Hardware or Server Profiles, and then select the server hardware or server profile that contains the replaced adapter.

    2. From the Server Hardware screen or Server Profile screen, select ActionsLaunch console. The iLO Remote Console is launched.

    3. Power on the server and check the firmware version of the new adapter during boot.


      [NOTE: ]

      NOTE: To check that the firmware version matches your firmware baseline, from the main menu, select Firmware Bundles, and select your firmware baseline. Scroll through the list of firmware to find what is offered in your baseline and compare it to your adapter firmware.


  5. If the firmware version is different from the baseline and the server profile is assigned to a Gen8 server or later, the server firmware can be updated automatically with the re-assignment of the server profile.

    1. From the main menu, select Server Profiles, and then select the server profile to edit.

    2. Select ActionsEdit. If needed, select the proper server hardware.

    3. To manage the firmware update manually, from the Firmware baseline list, select managed manually.

    4. To automatically update the firmware, select the appropriate firmware baseline. To force install all of the firmware, even if it is the same or newer, select Force installation.

    5. Click OK.


      [NOTE: ]

      NOTE: If the firmware version is different from the baseline and the server profile is assigned to a G7 server, you must update the firmware outside of the appliance.


See also