- Preface
- New and Changed Information
- Overview
- Equipment Policies
- Chassis Management
- I/O Module Management
- SIOC Management
- Power Management in Cisco UCS
- Blade Server Hardware Management
- Rack-Mount Server Hardware Management
- S3260 Server Node Hardware Management
- Virtual Interface Management
- Troubleshoot Infrastructure
- Cisco UCS S3260 Server Node Management
- Booting a Cisco UCS S3260 Server Node
- Booting a Cisco UCS S3260 Server Node from the Service Profile
- Determining the Boot Order of a Cisco UCS S3260 Server Node
- Shutting Down a Cisco UCS S3260 Server Node
- Shutting Down a Cisco UCS S3260 Server Node from the Service Profile
- Resetting a Cisco UCS S3260 Server Node
- Resetting a Cisco UCS S3260 Server Node to Factory Default Settings
- Reacknowledging a Cisco UCS S3260 Server Node
- Removing a Cisco UCS S3260 Server Node from a Chassis
- Deleting the Inband Configuration from a Cisco UCS S3260 Server Node
- Decommissioning a Cisco UCS S3260 Server Node
- Recommissioning a Cisco UCS S3260 Server Node
- Reacknowledging a Server Slot in a S3260 Chassis
- Removing a Non-Existent Cisco UCS S3260 Server Node from the Configuration Database
- Turning the Locator LED for a Cisco UCS S3260 Server Node On and Off
- Turning the Local Disk Locator LED on a Cisco UCS S3260 Server Node On and Off
- Resetting the CIMC for a Cisco UCS S3260 Server Node
- Resetting the CMOS for a Cisco UCS S3260 Server Node
- Issuing an NMI from a Cisco UCS S3260 Server Node
- Viewing the POST Results for a Cisco UCS S3260 Server Node
- Viewing Health Events for a Cisco UCS S3260 Server Node
- Health LED Alarms
S3260 Server Node
Hardware Management
Cisco UCS S3260 Server Node Management
You can manage and monitor all Cisco UCS S3260 server nodes in a Cisco UCS domain through Cisco UCS Manager. You can perform some server management tasks, such as changes to the power state, from the server and service profile.
The remaining management tasks can only be performed on the server.
If a server slot in a chassis is empty, Cisco UCS Manager provides information, errors, and faults for that slot. You can also re-acknowledge the slot to resolve server mismatch errors and rediscover the server in the slot.
Booting a Cisco UCS S3260 Server Node
If the Boot Server link is dimmed in the Actions area, you must shut down the server first.
After the server boots, the Overall Status field on the General tab displays an OK status.
Booting a Cisco UCS S3260 Server Node from the Service Profile
Determining the Boot Order of a Cisco UCS S3260 Server Node
![]() Tip | You can also view the boot order tabs from the General tab of the service profile associated with a server. |
Shutting Down a Cisco UCS S3260 Server Node
When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence.
If the Shutdown Server link is dimmed in the Actions area, the server is not running.
After the server has been successfully shut down, the Overall Status field on the General tab displays a power-off status.
Shutting Down a Cisco UCS S3260 Server Node from the Service Profile
When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence.
If the Shutdown Server link is dimmed in the Actions area, the server is not running.
After the server successfully shuts down, the Overall Status field on the General tab displays a down status or a power-off status.
Resetting a Cisco UCS S3260 Server Node
When you reset a server, Cisco UCS Manager sends a pulse on the reset line. You can choose to gracefully shut down the operating system. If the operating system does not support a graceful shutdown, the server is power cycled. The option to have Cisco UCS Manager complete all management operations before it resets the server does not guarantee the completion of these operations before the server is reset.
![]() Note | If you are trying to boot a server from a power-down state, you should not use Reset. If you continue the power-up with this process, the desired power state of the servers become out of sync with the actual power state and the servers might unexpectedly shut down at a later time. To safely reboot the selected servers from a power-down state, click Cancel, then select the Boot Server action. |
The reset may take several minutes to complete. After the server has been reset, the Overall Status field on the General tab displays an ok status.
Resetting a Cisco UCS S3260 Server Node to Factory Default Settings
You can now reset a Cisco UCS S3260 Server Node to its factory settings. By default, the factory reset operation does not affect storage drives. This is to prevent any loss of data. However, you can choose to reset these devices to a known state as well.
The following guidelines apply to Cisco UCS S3260 Server Nodes when using scrub policies:
-
For Cisco UCS S3260 Server Nodes, you cannot delete storage by using the scrub policy.
-
Cisco UCS S3260 Server Nodes do not support FlexFlash drives.
-
For Cisco UCS S3260 Server Nodes, you can only reset the BIOS by using the scrub policy.
Resetting storage devices will result in loss of data.
Perform the following procedure to reset the server to factory default settings.
Reacknowledging a Cisco UCS S3260 Server Node
Perform the following procedure to rediscover the server and all endpoints in the server. For example, you can use this procedure if a server is stuck in an unexpected state, such as the discovery state.
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server that you want to acknowledge. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the Actions area, click Server Maintenance. |
| Step 6 | In the
Maintenance dialog box, click
Re-acknowledge, then click
OK.
Cisco UCS Manager disconnects the server and then builds the connections between the server and the fabric interconnect or fabric interconnects in the system. The acknowledgment may take several minutes to complete. After the server has been acknowledged, the Overall Status field on the General tab displays an OK status. |
Removing a Cisco UCS S3260 Server Node from a Chassis
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server that you want to remove from the chassis. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the Actions area, click Server Maintenance. |
| Step 6 | In the
Maintenance dialog box, click
Decommission, then click
OK.
The server is removed from the Cisco UCS configuration. |
| Step 7 | Go to the
physical location of the chassis and remove the server hardware from the slot.
For instructions on how to remove the server hardware, see the Cisco UCS Hardware Installation Guide for your chassis. |
What to Do Next
If you physically reinstall the server, you must re-acknowledge the slot for Cisco UCS Manager to re-discover the server.
Deleting the Inband Configuration from a Cisco UCS S3260 Server Node
This procedure removes the inband management IP address configuration from a blade server. If this action is grayed out, no inband configuration was completed.
| Step 1 | In the Navigation pane, click Servers. | ||
| Step 2 | Expand . | ||
| Step 3 | In the Work area, click the Inventory tab. | ||
| Step 4 | Click the CIMC subtab. | ||
| Step 5 | In the Actions area, click Delete Inband Configuration. | ||
| Step 6 | Click
Yes in the
Delete confirmation dialog box.
The inband configuration for the server is deleted.
|
Decommissioning a Cisco UCS S3260 Server Node
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server that you want to decommission. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the Actions area, click Server Maintenance. |
| Step 6 | In the
Maintenance dialog box, do the following:
The server is removed from the Cisco UCS configuration. |
What to Do Next
If you physically reinstall the server, you must re-acknowledge the slot for Cisco UCS Manager to rediscover the server.
Recommissioning a Cisco UCS S3260 Server Node
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Click the Chassis node. |
| Step 3 | In the Work pane, click the Decommissioned tab. |
| Step 4 | On the row for each server that you want to recommission, check the check box in the Recommission column, then click Save Changes. |
| Step 5 | If a confirmation dialog box displays, click Yes. |
| Step 6 | (Optional)Monitor the progress of the server recommission and discovery on the FSM tab for the server. |
Reacknowledging a Server Slot in a S3260 Chassis
Perform the following procedure if you decommissioned a server without removing the physical hardware from the chassis, and you want Cisco UCS Manager to rediscover and reacknowledge the server.
| Step 1 | In the Navigation pane, click Equipment. | ||||||
| Step 2 | Expand . | ||||||
| Step 3 | Choose the server whose slot you want to reacknowledge. | ||||||
| Step 4 | If
Cisco UCS Manager displays a
Resolve
Slot Issue dialog box, do one of the following:
|
Removing a Non-Existent Cisco UCS S3260 Server Node from the Configuration Database
Perform the following procedure if you physically removed the server hardware without first decommissioning the server. You cannot perform this procedure if the server is physically present.
If you want to physically remove a server, see Removing a Cisco UCS S3260 Server Node from a Chassis.
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server that you want to remove from the configuration database. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the Actions area, click Server Maintenance. |
| Step 6 | In the
Maintenance dialog box, click
Remove, then click
OK.
Cisco UCS Manager removes all data about the server from its configuration database. The server slot is now available for you to insert new server hardware. |
Turning the Locator LED for a Cisco UCS S3260 Server Node On and Off
Turning the Local Disk Locator LED on a Cisco UCS S3260 Server Node On and Off
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server for which you want to turn the local disk locator LED on or off. |
| Step 4 | In the
Work pane, click the
tabs.
The Storage Controller inventory appears. |
| Step 5 | Click a disk. The disk details appear. |
| Step 6 | In the Details area, click Toggle Locator LED. If the Locator LED state is On, it will turn Off. If the Locator LED state is Off, it will turn On. |
| Step 7 | Click Save Changes. |
Resetting the CIMC for a Cisco UCS S3260 Server Node
Sometimes, with the firmware, troubleshooting a server might require you to reset the CIMC. Resetting the CIMC is not part of the normal maintenance of a server. After you reset the CIMC, the server boots with the running version of the firmware for that server.
If the CIMC is reset, the power monitoring functions of Cisco UCS become briefly unavailable until the CIMC reboots. Typically, the reset only takes 20 seconds; however, it is possible that the peak power cap can exceed during that time. To avoid exceeding the configured power cap in a low power-capped environment, consider staggering the rebooting or activation of CIMCs.
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server for which you want to reset the CIMC. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the Actions area, click Recover Server. |
| Step 6 | In the Recover Server dialog box, click Reset CIMC (Server Controller), then click OK. |
Resetting the CMOS for a Cisco UCS S3260 Server Node
Sometimes, troubleshooting a server might require you to reset the CMOS. Resetting the CMOS is not part of the normal maintenance of a server.
Issuing an NMI from a Cisco UCS S3260 Server Node
Perform the following procedure if the system remains unresponsive and you need Cisco UCS Manager to issue a Non-Maskable Interrupt (NMI) to the BIOS or operating system from the CIMC. This action creates a core dump or stack trace, depending on the operating system installed on the server.
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server that you want to issue the NMI. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the Actions area, click Server Maintenance. |
| Step 6 | In the
Maintenance dialog box, do the following:
Cisco UCS Manager sends an NMI to the BIOS or operating system. |
Viewing the POST Results for a Cisco UCS S3260 Server Node
You can view any errors collected during the Power On Self-Test process for a server and its adapters.
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Choose the server for which you want to view the POST results. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the
Actions area, click
View
POST Results.
The POST Results dialog box lists the POST results for the server and its adapters. |
| Step 6 | (Optional)Click the link in the Affected Object column to view the properties of that adapter. |
| Step 7 | Click OK to close the POST Results dialog box. |
Viewing Health Events for a Cisco UCS S3260 Server Node
| Step 1 | In the Navigation pane, click Equipment. | ||||||||||||||||||||||||
| Step 2 | Expand . | ||||||||||||||||||||||||
| Step 3 | Choose the server for which you want to view health events. | ||||||||||||||||||||||||
| Step 4 | In the
Work pane, click the
Health tab
The health events triggered for this server appear. The fields in this tab are:
| ||||||||||||||||||||||||
Health LED Alarms
The server health LED is located on the front of each server. Cisco UCS Manager allows you to view the sensor faults that cause the blade health LED to change color from green to amber or blinking amber.
|
Name |
Description |
|---|---|
|
Severity column |
The severity of the alarm. This can be one of the following: |
|
Description column |
A brief description of the alarm. |
|
Sensor ID column |
The ID of the sensor that triggered the alarm. |
|
Sensor Name column |
The name of the sensor that triggered the alarm. |
Viewing Health LED Alarms
| Step 1 | In the Navigation pane, click Equipment. |
| Step 2 | Expand . |
| Step 3 | Click the server for which you want to view health LED alarms. |
| Step 4 | In the Work pane, click the General tab. |
| Step 5 | In the
Actions area, click
View
Health LED Alarms.
The View Health LED Alarms dialog box lists the health LED alarms for the selected server. |
| Step 6 | Click OK to close the View Health LED Alarms dialog box. |


Feedback