For information on specific server hardware issues, see the HPE OneView Release Notes.
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:
|
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.
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.
| Symptom | Possible cause and recommendation |
|---|---|
| Server Hardware failure |
Server hardware failed and must be replaced
|
|
|
|
![]() |
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
|
![[IMPORTANT: ]](images/important.gif)
![[NOTE: ]](images/note.gif)