×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

How to move UCS blade with OS on local disks between chassis

Answered Question
Aug 25th, 2014
User Badges:

Hi,

I've to move blade between chassis - blade have OS installed on local disks and associated profile.

Can I simply:

shutdown

enter maintenance

remove it from chassis

swap with other blade from second chassis

power on

Will blade be properly recognized and profile will go with it ?

I've found advise here that is is better to decommission blade and associate profile back after move:

https://supportforums.cisco.com/discussion/11230671/physically-move-blad...

but it seems too complex for me - can somebody who tired this exercise share some experience ?

 

Cheers

Correct Answer by Keny Perez about 2 years 11 months ago

Hi,

Assuming that the chassis belong to the same domain (same pair of Fabric Interconnect) and that you are using ESXi, you may try the following:

1-Enter the host in maintenance mode (this might include moving the VMs to other server/power them off/make them enter maintenance mode as well)

2-Turn off the blade

3-Make sure that the Service Profile does not have a disk scrub policy so that data is not deleted when the Service Profile (SP) is disassociated

4-Disassociate the SP

5-Decommission the blade

6-Take out the blade and insert the new blade

7-Move the original blade to the second chassis

8-Reacknowledge the blade and associate the same/original SP

9-Power on the blade

10-Take the server out of maintenance mode. as well as the VMs

 

Note: For the blade inserted in the slot we took our blade out from, you may create a new SP and associate it to it or you can actually have any SP (including the one assigned to the blade recently taken out) and assign it to the new blade. 

Only one SP per sever and only one server per SP.

SPs are independent from the hardware (as long as the hardware is compatible with the features configured in the SP)

 

Let me know if this info was of help, otherwise let me know and I wil expand or try to make this easier.

 

Please rate ALL helpful answers

-Kenny

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Keny Perez Mon, 08/25/2014 - 21:41
User Badges:
  • Blue, 1500 points or more

Hi,

Assuming that the chassis belong to the same domain (same pair of Fabric Interconnect) and that you are using ESXi, you may try the following:

1-Enter the host in maintenance mode (this might include moving the VMs to other server/power them off/make them enter maintenance mode as well)

2-Turn off the blade

3-Make sure that the Service Profile does not have a disk scrub policy so that data is not deleted when the Service Profile (SP) is disassociated

4-Disassociate the SP

5-Decommission the blade

6-Take out the blade and insert the new blade

7-Move the original blade to the second chassis

8-Reacknowledge the blade and associate the same/original SP

9-Power on the blade

10-Take the server out of maintenance mode. as well as the VMs

 

Note: For the blade inserted in the slot we took our blade out from, you may create a new SP and associate it to it or you can actually have any SP (including the one assigned to the blade recently taken out) and assign it to the new blade. 

Only one SP per sever and only one server per SP.

SPs are independent from the hardware (as long as the hardware is compatible with the features configured in the SP)

 

Let me know if this info was of help, otherwise let me know and I wil expand or try to make this easier.

 

Please rate ALL helpful answers

-Kenny

jakub.dwornicza... Wed, 08/27/2014 - 16:53
User Badges:

Followed this procedure, host was moved successfully without data lost on local disks.

Cheers!

Keny Perez Thu, 08/28/2014 - 06:47
User Badges:
  • Blue, 1500 points or more

Glad to help!   ;)

-Kenny

 

Actions

This Discussion