The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This part contains the following chapters:
Modular servers, which are introduced in Cisco UCS M-Series, are contained in compute cartridges.
Note | You cannot remove servers from their cartridges. |
Associate a service profile with a modular server or server pool.
1. UCS-A# scope org org-name
2. UCS-A /org # scope service-profile profile-name
3. UCS-A /org/service-profile # power up
4. UCS-A /org/service-profile # commit-buffer
The following example boots the modular server associated with the service profile named ServProf34 and commits the transaction:
UCS-A# scope org / UCS-A /org* # scope service-profile ServProf34 UCS-A /org/service-profile* # power up UCS-A /org/service-profile* # commit-buffer UCS-A /org/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.
Associate a service profile with a modular server or server pool.
1. UCS-A# scope org org-name
2. UCS-A /org # scope service-profile profile-name
3. UCS-A /org/service-profile # power down
4. UCS-A /org/service-profile # commit-buffer
The following example shuts down the modular server associated with the service profile named ServProf34 and commits the transaction:
UCS-A# scope org / UCS-A /org # scope service-profile ServProf34 UCS-A /org/service-profile # power down UCS-A /org/service-profile* # commit-buffer UCS-A /org/service-profile #
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # cycle {cycle-immediate | cycle-wait}
3. UCS-A /chassis/cartridge/server # commit-buffer
The following example immediately power cycles modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# scope server 2/2/2 UCS-A /chassis/cartridge/server # cycle cycle-immediate UCS-A /chassis/cartridge/server # commit-buffer UCS-A /chassis/cartridge/server #
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 shut down, the server is power cycled. The option to have Cisco UCS Manager complete all management operations before it resets the server does not guarantee that these operations will be completed 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 will become out of sync with the actual power state and the servers may 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. |
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # reset {hard-reset-immediate | hard-reset-wait}
3. UCS-A /chassis/cartridge/server # commit-buffer
The following example performs an immediate hard reset of modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# scope server 2/2/2 UCS-A /chassis/cartridge/server # reset hard-reset-immediate UCS-A /chassis/cartridge/server* # commit-buffer UCS-A /chassis/cartridge/server #
Perform the following procedure if you need to have Cisco UCS Manager 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.
1. UCS-A# acknowledge server chassis-id / cartridge-id / server-id
2. UCS-A /chassis/cartridge/server # commit-buffer
Command or Action | Purpose |
---|
The following example acknowledges modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# acknowledge server 2/2/2 UCS-A /chassis/cartridge/server* # commit-buffer UCS-A #
Decommissioning of a server is performed to temporarily remove the server from the UCSM configuration.
1. UCS-A# decommission server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # commit-buffer
Command or Action | Purpose |
---|
The following example decommissions modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# decommission server 2/2/2 UCS-A /chassis/cartridge/server* # commit-buffer UCS-A #
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # show status
Command or Action | Purpose |
---|
The following example shows the status for modular server 1 in cartridge 3 of chassis 1:
UCS-A# scope server 1/3/1 UCS-A /chassis/cartridge/server # show status Server Slot Status Availability Overall Status Discovery ------- --------------------------------- ------------ --------------------- --------- 1/3/1 Equipped Available Unassociated Complete
The locator LED is shared by all servers in a cartridge. Hence, you can turn the locator LED on from any server in a cartridge.
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # enable locator-led
3. UCS-A /chassis/cartridge/server # commit-buffer
The following example turns on the locator LED for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# scope server 2/2/2 UCS-A /chassis/cartridge/server # enable locator-led UCS-A /chassis/cartridge/server* # commit-buffer UCS-A /chassis/cartridge/server #
The locator LED is shared by all servers in a cartridge. Hence, to turn off a locator LED of a cartridge, you must turn it off from all servers in the cartridge.
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # disable locator-led
3. UCS-A /chassis/cartridge/server # commit-buffer
The following example turns off the locator LED for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# scope chassis 2/2/2 UCS-A /chassis/cartridge/server # disable locator-led UCS-A /chassis/cartridge/server* # commit-buffer UCS-A /chassis/cartridge/server #
On rare occasions, troubleshooting a server may require you to reset the CMOS. This procedure is not part of the normal maintenance of a server.
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # reset-cmos
3. UCS-A /chassis/cartridge/server # commit-buffer
The following example resets the CMOS for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# scope server 2/2/2 UCS-A /chassis/cartridge/server # reset-cmos UCS-A /chassis/cartridge/server* # commit-buffer UCS-A /chassis/cartridge/server #
On rare occasions, such as an issue with the current running firmware, troubleshooting a server may require you to reset the CIMC. This procedure 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 for as long as it takes for the CIMC to reboot. While this usually only takes 20 seconds, there is a possibility that the peak power cap could be exceeded during that time. To avoid exceeding the configured power cap in a very low power-capped environment, consider staggering the rebooting or activation of CIMCs.
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # scope CIMC
3. UCS-A /chassis/cartridge/server/CIMC # reset
4. UCS-A /chassis/cartridge/server/CIMC # commit-buffer
The following example resets the CIMC for modular server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# scope server 2/2/2 UCS-A /chassis/cartridge/server # scope CIMC UCS-A /chassis/cartridge/server/cimc # reset UCS-A /chassis/cartridge/server/cimc* # commit-buffer UCS-A /chassis/cartridge/server/cimc #
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.
1. UCS-A # scope server chassis-id / cartridge-id / server-id
2. UCS-A /chassis/cartridge/server # diagnostic-interrupt
3. UCS-A /chassis/cartridge/server # commit-buffer
Command or Action | Purpose |
---|
The following example sends an NMI from server 2 in cartridge 2 of chassis 2 and commits the transaction:
UCS-A# scope server 2/2/2 UCS-A /chassis/cartridge/server # diagnostic-interrupt UCS-A /chassis/cartridge/server* # commit-buffer UCS-A /chassis/cartridge/server #
The server health LED is located on the front of each Cisco UCS M-Series server. Cisco UCS Manager allows you to view the sensor faults that cause the server health LED to change color from green to amber or blinking amber.
The health LED alarms display the following information:
1. UCS-A# scope server chassis-id / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # show health-led expand
Command or Action | Purpose |
---|
The following example shows how to display the health LED status and sensor alarms for chassis 1 cartridge 2 server 1:
UCS-A# scope server 1/2/1 UCS-A /chassis/cartridge/server # show health-led Health LED: Severity: Minor Reason:: P0V75_STBY:Voltage Threshold Crossed;TEMP_SENS_FRONT:Temperature Threshold Crossed; Color: Amber Oper State:: On Sensor Alarm: Severity: Minor Sensor ID: 7 Sensor Name: P0V75_STBY Alarm Desc: Voltage Threshold Crossed Severity: Minor Sensor ID: 76 Sensor Name: TEMP_SENS_FRONT Alarm Desc: Temperature Threshold Crossed Severity: Minor Sensor ID: 91 Sensor Name: DDR3_P1_D2_TMP Alarm Desc: Temperature Threshold Crossed UCS-A /chassis/cartridge/server #