Showing results for 
Search instead for 
Did you mean: 

What are quick steps in moving a service profile to a different blade




A service profile represents a logical server and stores the server personality and server connectivity requirements. The main purpose of a service profile is to support server mobility. Once a service profile is associated with a server, the server is ready to have an operating system and applications installed. Remember that when a service profile is disassociated from a server, the identity and connectivity information for the server is reset to factory defaults. A service profile can be associated with only one blade at a time, but the association can be changed if there is a problem with the particular blade. The “replacement blade” for the profile will inherit the WWN/VSAN information and boot specifications from the profile just like the original blade.


Service profile Overview

A service profile typically includes four types of information:

a) Server definition: It defines the resources (e.g. a specific server or a blade inserted to a specific chassis) that are required to apply to the profile.

b) Identity information: Identity information includes the UUID, MAC address for each virtual NIC (vNIC), and WWN specifications for each HBA.

c) Firmware revision specifications: These are used when a certain tested firmware revision is required to be installed or for some other reason a specific firmware is used.

d) Connectivity definition: It is used to configure network adapters, fabric extenders, and parent interconnects, however this information is abstract as it does not include the details of how each network component is configured.


Service Profile Templates

With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools.


Move a service profile

To move a service profile which is associated to a particular blade to a different blade; the service profile needs to be first disassociated with the blade to which it is assigned and then it can be associated to the other blade. However to quickly do this, login to UCS manager and navigate to Server tab > Service Profiles and select the service profile that you want to move. Click Change Service Profile Association from the work pane.



In the Associate Service Profile window select the Server Assignment as Select Existing Server and then select the blade server from the available servers.




Related Information

What is a Service profile in UCS and what are its types
Cisco UCS Manager GUI Configuration Guide




Thank you for the quick write up. Can we perform the same operation for different blade type as well? (for example: B200M2 to B200M3 for example) 


My servers are SAN booted (iSCSI) Win2008R2. I have tried re-associating B200M2 SP to B200M3, it ended up BSOD. Before I dig into this more, I am just curious is there any existing doc/article from Cisco to perform this type of migration?





Hi Vanakkam,

No. you cannot do this unless if you change Blade BIOS ver in firmware policy to B200M3 versions> for this U need select Sp- Policies- hostfirmware policies- create new firmware policy-  minimum requirement u have to select B200M3 appropriate BIOS version

Whether you are looking for transportation services, a rental storage unit, or additional help with packing, a long-distance moving company denver is there to help you.