Once the connectivity
between upstream uplink switches and downstream IOMs is established, we can
connect vNICs from blade servers configuring vNICs. We recommended that you
create a vNIC template to provide ease of management .
vNICs can be created
within server profiles or by using a vNIC template. Using a vNIC template is
the recommended method for configuring the NIC settings once, for each
template, and then quickly creating new vNICs with the desired configuration.
The vNIC configuration settings can be optimized for various operating systems,
storage devices, and hypervisors.
A vNIC template can be
configured as either of the following:
template: This vNIC template will provide one-time configuration for the vNICs
created using this template. Any subsequent changes to the template are not
propagated to abstracted vNICs.
This vNIC template will provide initial configuration for the vNICs created
using this template. Any subsequent changes to the template will also be
propagated to abstracted vNICs. We recommend that you to create an updating
vNIC template for production environments.
vNIC MAC addresses can
be assigned manually or by configuring a MAC address pool. It is possible to
either use the burned-in MAC addresses or abstract MAC addresses from an
identity pool with system-defined prefixes. Stateless computing is the salient
feature of the Cisco UCS platform. Therefore we recommend to you abstract vNIC
MAC addresses for server profiles, and consequently use server vNIC MAC
addresses from MAC address identity pools instead of using burned-in NIC MAC
addresses. The benefit of abstracting the MAC identity is that in case of
physical server failure, the server profile can be easily associated with the
replacement server. The new server will acquire all the identities associated
with the old server including the vNIC MAC addresses. From the operating system
perspective, there is no change at all.
We recommend that you
create vNIC templates with different configurations and create individual vNICs
from vNIC templates as required. Also, define MAC address pools and assign MAC
addresses to individual vNICs using those MAC address pools.
A vNIC is typically
abstracted from the physical mezzanine card. Older Emulex, QLogic, and Intel
NIC cards have fixed ports. The Cisco mezzanine NIC card, also known as a Palo
card or Virtual Interface Card (VIC), provides dynamic server interfaces. Cisco
VIC cards provide up to 256 dynamic interfaces. vNICs can be created within
server profiles or by using a vNIC template. Using a vNIC template is the
recommended method for configuring the NIC settings, doing so once for each
template and then quickly creating additional vNICs with the desired
configurations. The vNIC configuration settings can be optimized for various
operating systems, storage devices, and hypervisors.
The vNIC creation for
servers is part of the server profile, or server profile template creation.
Create Service Profile Template or
Service Profile (Expert) is started for the blade
servers, creating the vNIC is the second step in the configuration wizard.