UCS Deployment Guide – Service Profiles Templates and Service Profiles Assignment – Part 4

In this post, which is the final part of these UCS deployment series, we will create our UCS Service Profiles and assign them to our servers to make them fully functional. Remember, I am using the term functional as a server with no Service Profile assigned to it is just a piece of hardware that cannot even be powered up.

Basically, here is how it works:

  1. You create a Service Profile Template, where you leverage all the resources, pools and templates that have been already created.The Service Profile Template is used as a model or a template for all downstream created Service Profiles.
  2. You create Service Profiles from the Service Profile Template. By doing so, the Service Profiles created will inherits all configuration from the Template.
  3. You assign the Service Profiles to your physical UCS servers. This is a one to one association. One Service Profile cannot be assigned to more than one server. Likely, one server cannot be assigned more than one Service Profile.

Notes:

In fact, It is not mandatory to create a Service Profile Template to create the Service Profile. We could avoid the first step and create directly the Service Profile.

4.1 Create a Service Profile Template

To create a Service Profile Template, go to to Servers tab > Service Profile Template > root > Sub-Organization > Right click your organization and Create a Service Profile Template

UCS-ServiceProfileTemplateCreation

You will be promoted with the Service Profile Window, where you have to insert all the inputs created previously, some examples are the UUID pools from where the serves need to get their IDs, the boot order policy, the local disk configuration policy, the management IPs pool associated to the service profiles, …etc.

Start by providing a name to your Service Profile Template and UUID pool to user for server ID assignment for each profile created from this template. Select if the Template is of type initial or updating. Initial Template means that the Service Profiles created from this template will not be updated in case the configuration is changed in the parent template. This is obviously more cautious than choosing Updating Template, especially in a live environment where hundreds of Service Profiles may be linked to one Service Profile Template.

 

Select the UUID pool from the servers get their IDs. This UUID has been created previously in Section 3 – UCS Configuration.

Once done, click on Next

The Storage Provisioning step allows to choose the storage policy to be used by the Service Profile. In our case, we have already created a RAID1 disk policy to be used in our environement.

 

Check your selection then click on Next

 

The Networking section allows to create the required vNIC (in UCS, vNIC means the physical adapter that will be seen by your OS). As we have already created our the vNIC templates in the previous part, we’ll go ahead and click on Expert to use them for the LAN connectivity configuration.

Then, click on Add to add your first vNIC

UCS-ServiceProfileTemplateCreation

Provide the name of the vNIC (Typicallt vNIC00 or vNIC01for the first vNIC) then check the Use vNIC Template

UCS-ServiceProfileTemplateCreation

Select one of the previously added vNIC template to be used used by your vNIC. Remember that a vNIC template contains all the network connectivity configuration needed (VLANs, MAC pools, QoS policy, …etc) by your vNIC. The actual benefit of using it is to avoid configuring each vNIC separately.

UCS-ServiceProfileTemplateCreation UCS-ServiceProfileTemplateCreation

Similarly, add all your vNICs and make them use the appropriate vNIC templates untill you have something similar to the screenshot below. In this example, we will have six vNICs in the Service Profile.

UCS-ServiceProfileTemplateCreation

Once done, click on Next to get SAN connectivity window.

UCS-ServiceProfileTemplateCreationSelect Expert to be able to add your vHBA templates, and select the WWNN pool from which the vHBAs will get their WWNN

UCS-ServiceProfileTemplateCreation

Click on Add to add the vHBAs that will be used by the Service Profile

Click on Use vNIC Template

Provide the vHBA names and choose the corresponding vHBA template to be used

 

Once done, click on Next

We are not configuring any zoning on the UCS level, so we’ll skip this step

 

The vNIC/vHBA Placement section allows to place the vNICs/vHBA order as required.

The vMedia policy section

The vMedia Policy allows you to map the remote server ISO image through scripting or programming. Normally you mount the ISO image during the installation of a server to boot from it; the same thing can be achieved through vMedia policy.

As we are configuring a basic Service Profile template, no vMedia Policy will be used for this template. So we’ll click on Next

In the the Server Boot Order section, we will user already created boot policy

The Server Assignment section allows to create the the service profiles and assign them to the physical servers on the fly. As we will do it late, we’ll skip this step.

The final step of the Service Profile Template creation is the Operational Policies, where you can define several settings such as BIOS Configuration, External IPMI Management Configuration, Management IP Address, Monitoring Configuration, ..etc.

We will the CIMC Out-of-Band management IP addresses pool to use in this step.

Once done. Click on Finish then OK to have a ready to use Service Profile Template.

4.2 Create Service Profiles from the Service Profile Template

 

OK. Now that we have our Service Profile Template, let’s create some Service Profiles from it.

Right Click on the Service Profile Template and choose Create Service Profile From Template. Make sure you select the one which is under your organization.

Provide a name suffix for the Service Profile and the number of instances to create.

Service Profiles created. Let’s assign to the physical servers to make them fully functional.

 

4.3 Assign the Service Profiles to the servers

 

We can see that we have two Service Profiles which are not assigned yet. Let’s assign the first one to the first server in Chassis 1 to make it operative.

Once done, you can go to you Service Profile and check that it is associated to a physical server. The server can be powered on from there and we can connect to its KVM.

4.4 Summary

In this final post, Services Profiles have been created and assigned to our UCS servers, which made them fully functional and operative.

Find this post interesting. Share it!

1 Comment

  1. Pingback: Cisco UCS Deployment Guide – vAdmin-Land

Leave a Comment

Your email address will not be published. Required fields are marked *