UCS system has lots of components in it, i.e Blade server, Rack server, Fabric Extender, Fabric Interconnect. All these are managed by the UCS manager. This document provides the steps to gracefully shutdown and power up the UCS system.
In an event when you need to shutdown the entire system for some activity follow the steps mentioned below to gracefully shut the UCS system. It is recommended to backup the UCS configuration before doing this activity as mentioned here. This document is applicable to all hardware and software version of UCS. Note that the information in this document was created from the devices in a specific lab environment. If your network is live, make sure that you understand the potential impact of any command.
Follow the steps to gracefully shutdown UCS system:
a) Graceful shutdown of servers: To shutdown the OS running in the server, UCSM sends ACPI signal to the server OS. The OS generally responds by gracefully shutting down; however this may not happen in certain cases. It is advisable to manually check if the OS has shutdown. Disassociating service profile from the servers will also shutdown the severs; however this is not advisable and is not graceful.
b) Disable management services: This step is optional and is intended only to lower the admin burden because of UCS system going down. Disable services like “Smart call Home” to stop UCS system from sending logs and information.
c) Decomission and Remove power to Chassis:Decomissoning is required only in case if you need to change the chassis. In other cases you can directly remove the power to chassis. This is done to stop the power to blade/rack server and Fabric Extender. There is nothing to be configured or saved from chassis end point.
d) Remove power to Secondary FI: This step is optional and is required only if you have two FI in failover. Removing power first from secondary FI prevents the system from doing failover, which is unnecessary here.
e) Remove power to Primary FI: As the last step remove the power to the primary FI. Note that there is no graceful shutdown method in case of FI, since it is not required.
The UCS system is now properly down and you can proceed with the maintenance activity. To bring the system back up follow the above steps in reverse order; i.e starting from the FI and going up to the servers.
The UCS system should reboot without any issue. However after rebooting if you find that the configuration is corrupt, follow the method to restore the configuration as described here. If after rebooting the UCS system gets stuck in boot prompt then follow the method to recover it as described here.
Hi Guys We migrating from NXOS STP classic network to ACI. We have different Tenants that need to utilize the same VLAN. However when statically pathing ports in an EPG using port encap of vlan 811 ACI complains about it being used in another Tenant&...
Hello,I've the following scenario: Tenant common: concrete FW used as L4-L4 Device, exported to various tenants facing toward SharedPrivateNetwork;Tenant One: one firewall instance with one SG to SharedPrivateNetwork;Tenant Two: one firewall in...
According to https://www.cisco.com/c/en/us/products/switches/nexus-3000-series-switches/models-comparison.html#~tab-nexus3400 , the Nexus 3432D-S supports NX-OS Release X and later . However, as far as I can tell NX-OS Release X either...
Hello,We have couple Nexus9K with configured IP SLA udp-jitter. For monitoring we are using PRTG tool.We have an issue with monitoring udp-jitter sensors. I have contacted to PRTG support team and they told me - This sensor requires the hardwar...
Hello, Having a hard time upgrading the code on this N3K-C3232C, i'd appreciate any advice on this. I am not sure if I am using the incorrect file or if there is a pre-upgrade step I am missing. below are the details from an upgrade attempt.&nbs...