A customer deploying Cisco UCS blade servers must centrally manage VLANs carried by the server...

vNIC templates are the precise Cisco UCS mechanism for centrally defining how server vNICs connect to the LAN. A template can specify the fabric, VLAN or VLAN-group membership, MTU, QoS policy, network control policy, adapter policy, MAC-address pool, and related interface properties. Service profiles or service profile templates reference the vNIC template rather than duplicating those settings on every server. Cisco UCS Manager then applies the template-defined values to each bound vNIC. Cisco also documents that if an existing bound vNIC does not match its template, UCS Manager reconfigures it, and future changes to that vNIC must be made through the associated template. An updating vNIC template is therefore appropriate when modifications must propagate to interfaces on already deployed servers, subject to normal UCS change and reboot implications. A service profile template controls the broader server identity and policy composition, but it is not the most specific object for shared VLAN-tagging and vNIC properties. A usNIC connection policy allocates user-space NIC resources for supported applications and does not define general VLAN membership. A network control policy governs behaviors such as CDP, LLDP, MAC registration, uplink-failure handling, and related controls; it does not serve as the reusable VLAN configuration object. Consequently, vNIC templates provide the requested single point of administration and consistent post-deployment propagation across multiple UCS blade-server interfaces. Cisco UCS Central vNIC template guide

================