04-07-2018 02:39 AM - edited 03-01-2019 01:30 PM
I've create a service profile and want to associate it to blade 3-8 of chassis 1. but somehow failed to do so. To do so i've create server pool as well but it's not working. Can we associate a single service profile to multiple servers?
04-07-2018 04:57 AM
I would not recommend server pools. Just use an updating or initial service profile template and spawn service profiles from it.
04-07-2018 05:39 AM
Do we need to create Service profile for each server?
What if in case, i need to apply Service Profile in 100s of server?
04-07-2018 05:43 AM
Every service profile will have its own unique profile, yes. If you manage them using updating service profile templates, you make a change to the template (modify boot order, add VLAN, etc) and the changes are pushed down to all service profiles using that template.
You can use server pools, they just add a layer of complexity if you are in a situation where you want a certain blade to be named a certain way or run a certain application, etc.
04-07-2018 06:16 AM
04-07-2018 06:48 AM
In your case you would create a service profile template, a vNIC template for A and B side, and vHBA template for A and B side.
When you create the service profile template (we will name it "ESXi"), you would reference the vNIC and vHBA templates. These templates contain properties like VLAN, VSAN, etc. You also select other values in the template that you want to be the same across all blades, such as boot order, BIOS policy, firmware package.
Once the template is complete, you would create 8 service profiles from that template and assign them to each blade. For Example ESXi-1, ESXi-2. Now if you created an initial template, you can make individual changes to the service profiles without impacting other servers. Lets say one day you decide that blade 8 is going to boot from flexflash instead of local disk. You would just create a new boot policy and apply it to ESXi-8.
If you used an updating template, all changes made will reflect on all service profiles spawned from that template. This is the same for vNIC templates as well. So lets say you needed to add a new vNIC and apply a new VLAN globally to all existing vNIC on those 8 blades. You would just add a new vNIC to the template and add the new VLAN to the vNIC template, and these changes are pushed to all 8 blades at once.
I hope this helps.
04-07-2018 06:07 PM
04-08-2018 06:31 AM
Please check the configuration Limits of a UCS Domain:
Since day 1, a UCS 6200 / 6332 Domain is limited to 20 Chassis, resp. 160 combined rack and blade servers per Domain.
04-08-2018 06:48 AM - edited 04-08-2018 07:20 AM
Greetings.
For the environment scale you are describing, it sounds like you would need UCS central (and eventually Intersite).
If you are truly wanting to do stateless computing, don't want to individually associate service profiles, and want the service profiles to auto deploy as soon as they are created, then yes, Server pools are the mechanism to use.
This does add a layer of complexity, as Wes has already pointed out.
One of the common TAC cases we get, involving server pools, is trying to manually assign a specific service profile to a specific blade. Also server hardware maintenance such as RMA, or moving the server out of the server pool for some reason, is typically forgotten about, and will result in the service profile erroring out with 'insufficient resources' type error.
Thanks,
Kirk...
04-11-2018 12:13 AM
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