I have to add a vNIC to a blade template. However, I heard that doing that will power cycle all blades that are bound to that template. Is that corect? I only have 1 template (for all VMware server blades). This would power cycle the whole farm. Can I add a vNIC to individual servers? even though they are bound to a template.
There are 2 types of templates: initial and updating. If you create Service Profiles from a initial template, SP and template are not connected; eg. making changes to template, will not update the SP's. This is different for updating template, where changes to template will update all derived SP's.
Adding or removing vnic's from a VIC I/O adaptor is disruptive, and requires a reboot of the blade. (adding / removing Vlan's is not disruptive, however).
In any case, you should implement a "maintenance policy", adding it to all SP's, and set it to ACK; in case of a change which requires a reboot, you get a pending activity, where you have to ACK every server that has to be rebooted.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...