I’ve been in this situation a few times now, where I need to move a physical production UCS blade from one chassis to another. It can make you nervous, worried that your server won’t come back up properly after the relocation. What if the network configuration changes, what about storage, what about the OS?! Rest assured, this is quite an easy procedure. If you can bake a cake, you can relocate a UCS blade.
Whether you have local boot or SAN boot, this process will work as long as you’re moving the blade within the same UCS domain, under the same pair of Fabric Interconnects. (You can actually achieve this across domains, but in most cases you wouldn’t do that, so I won’t be covering that here.) Read carefully, and follow the steps during your maintenance window:
- Shut down the OS running on the blade (Or if running a hypervisor – enter maintenance mode)
- Shut down the server blade
- (Servers > Service Profile > General > Shutdown Server)
- Make sure the Service Profile does not have a disk scrub policy associated!!
- (Servers > Service Profile > Policies > Scrub Policy)
- Disassociate the Service Profile, wait for the disassociate to complete
- (Servers > Service Profile > General > Disassociate Service Profile)
- View status on the FSM tab of the blade
- Decommission the blade from the UCSM
- (Equipment > Chassis > Server > General > Server Maintenance)
- View status on the FSM tab for the process
- Remove the blade from the current slot
- Move the blade to the new slot
- Wait for the blade to fully discover again
- View status from the FSM tab of the blade
- You might be required to accept / acknowledge the slot to accept the blade and trigger the discovery.
- Once discovered, associate the service profile
- (Equipment > Chassis > Server > General > Associate Service Profile)
- Power on the blade
- Boot the OS / or take server out of maintenance mode
You should now be back in business, all configuration status quo just like you moved a rack-mount server from one rack to another.
Disclaimer: This is a personal blog and purely based on my experiences. Please proceed with care and caution in your own environments.