10-27-2011 01:30 AM - edited 03-01-2019 10:07 AM
I have service profiles and blades running off of that service profile. Each blade has two vNIC's and I need to add two more vNIC's to them. I want to add the additional vNIC's to templates and let the service profiles get "updated" with the new vNIC's. This will happen automatically if the templates are "updating" but all my templates currently are "initial" so they wont push the new vNIC config to the blades.
To get the blades to recognize the new vNIC's should I re-bind the templates with the new vNIC's to the service profile or is there any "push" that I can trigger from the template somewhere that I am missing?
The blades are currently running ESX and i dont want a unplanned reboot.
thanks!!!
Gak
Solved! Go to Solution.
10-27-2011 06:04 AM
Greetings Ganesh,
When using Static (Initial) templates, the only way to apply your changes would be to unbind/re-bind the SP with the updated template. As this is an "initial" template, you can make changes without them being "pushed" immediately.
As a safe bet the best option for you would be to:
1. Unbind your SP's from the SP Template
2. Add the new vNICs to the SP Template (currently has nothing attached/bound to it)
3. Put your first ESX host into maintenance mode & shut it down.
4. Re-bind the Service Profile of that ESX host to the template (This will cause a re-association event)
5. Power up your ESX host & verify the changes
6. Repeat Steps 3-5 for your remaining ESX hosts.
Let me know if you have any further questions.
Regards,
Robert
**Note: I much prefer initial templates for the reason they do not PUSH config changes which can potentially cause a reboot. Updating templates are good if you're making profile changes that don't require a reboot to apply - ie. Adding or Removing VLANs. Other than this, your Initial Template will keep your changes "locked" without risking any accidental config push/reboots.
10-27-2011 06:04 AM
Greetings Ganesh,
When using Static (Initial) templates, the only way to apply your changes would be to unbind/re-bind the SP with the updated template. As this is an "initial" template, you can make changes without them being "pushed" immediately.
As a safe bet the best option for you would be to:
1. Unbind your SP's from the SP Template
2. Add the new vNICs to the SP Template (currently has nothing attached/bound to it)
3. Put your first ESX host into maintenance mode & shut it down.
4. Re-bind the Service Profile of that ESX host to the template (This will cause a re-association event)
5. Power up your ESX host & verify the changes
6. Repeat Steps 3-5 for your remaining ESX hosts.
Let me know if you have any further questions.
Regards,
Robert
**Note: I much prefer initial templates for the reason they do not PUSH config changes which can potentially cause a reboot. Updating templates are good if you're making profile changes that don't require a reboot to apply - ie. Adding or Removing VLANs. Other than this, your Initial Template will keep your changes "locked" without risking any accidental config push/reboots.
10-27-2011 06:10 AM
Thanks!!!. This is exactly what i did but i wasnt sure if this was the right way since i couldnt find any documentation for it. Yes, as you note, i prefer initial templates as well and thats the way i am deploying the UCS environment.
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