12-23-2015 07:59 PM - edited 03-01-2019 12:31 PM
Is there any standard procedure to power off the Fabric Interconnect ?
Solved! Go to Solution.
12-24-2015 05:10 AM
Hi Ajay,
If you are just trying to shut down the Fabric Interconnect the only way would be to unplug the power. However, there are some best practices that can be taken into considerations.
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.
Hope this helps.
Qiese Dides
12-23-2015 10:12 PM
There is no power switch !
Don't hesitate and just remove the power cable ! I assume of course, that status of HA is ready !
CLI: show cluster state
12-24-2015 05:10 AM
Hi Ajay,
If you are just trying to shut down the Fabric Interconnect the only way would be to unplug the power. However, there are some best practices that can be taken into considerations.
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.
Hope this helps.
Qiese Dides
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide