Cisco Cisco UCS C22 M3 Rack Server Guía Para Resolver Problemas
The example output provided in this document is either from /var/log/messages or OBFL as well as OS logs
for ESXi, RHEL, and Windows.
for ESXi, RHEL, and Windows.
Prerequisites
There are no specific requirements for this document.
Components Used
The information in this document is based on these software and hardware versions:
Cisco Unified Computing System (UCS) C200-M1 firmware version 1.4(3w)
•
Cisco UCS C210-M2 firmware version 1.4(3w)
•
Cisco UCS C220-M3 firmware version 2.0(3d)
•
Cisco UCS C220-M4 firmware version 2.0(3f)
•
ESXi 5.0 U2
•
RHEL 6.6
•
Windows 2008 R2
•
The information in this document was created from the devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If your network is live, make sure
that you understand the potential impact of any command.
devices used in this document started with a cleared (default) configuration. If your network is live, make sure
that you understand the potential impact of any command.
Background Information
A reboot can be either expected or unexpected. When a reboot is expected, it might be that not all interested
parties expect it. It is important to have a change control process in place for any reboot or shutdown
maintenance tasks in order to ensure everyone is aware of the action.
parties expect it. It is important to have a change control process in place for any reboot or shutdown
maintenance tasks in order to ensure everyone is aware of the action.
Expected Reboots
This is any reboot or shutdown event that was initiated by a person, process, or script intentionally. This can
be initiated in one of several ways. These log snippets can help identify which reboot scenario occurred, so
that you can track down who or what took the action:
be initiated in one of several ways. These log snippets can help identify which reboot scenario occurred, so
that you can track down who or what took the action:
Through the CIMC GUI
•
From the OS
•
When you press the front panel button on the front of the server
•
Unexpected Reboots
This is any reboot that is not planned or expected, but it can still be expected by the person or process that
initiated the action. Also, there might have been a hardware failure like a PSU failure or power loss in the
data center. These can be initiated in several ways.
initiated the action. Also, there might have been a hardware failure like a PSU failure or power loss in the
data center. These can be initiated in several ways.
If it is determined that the front panel button was pressed, you can track down who had physical access to the
data center at the time of the reboot. If it is a power issue, engage the Data Center team to see if there was a
power failure at the time.
data center at the time of the reboot. If it is a power issue, engage the Data Center team to see if there was a
power failure at the time.
Through the CIMC GUI
•
From the OS
•
When you press the front panel button on the front of the server
•