5
Initialize the Server Network Adapter. After you configure the vNICs on the server network
adapter, you might have to reboot the server and reset the server network adapter and reload the
drivers. See the documentation for your specific server network adapter for details. When the
configuration is complete, the server network adapter and the switch re-establishes a link and
performs the initial handshake and negotiation process. The server network adapter and the
switch also establish higher level control plane connectivity using the Virtual Interface
Configuration (VIC) protocol.
The VIC protocol allows you to provision and manage virtual interfaces on a remote
device.
When the VIC protocol connectivity is established, the server network adapter requests
that the switch create a vEthernet interface for each vNIC that is configured on the
server network adapter. The server network adapter also passes the following
attributes over the uplink in addition to the create vEthernet interface request:
—
Port-profile name
—
Channel number
—
Active/standby status
The switch responds by creating a vEthernet interface for each vNIC on the server network
adapter and associates the port-profile and channel number to the vEthernet interface. The
server boot process might be held at the BIOS configuration phase until the vEthernet creation
has completed. After the vEthernet is created, the boot process resumes and the operating
system is loaded. Refer to the documentation for your specific adapter for details.
The global configuration command,
no vethernet auto-create
, stops the vEthernet interfaces
from being automatically created. If the switch is not configured with the
vethernet auto-create
command, you must configure the vEthernet interfaces manually with the appropriate binding and
port-profile configurations.
vEthernet interfaces created by the switch are numbered automatically as they are created.
These vEthernet numbers start from 32769. The switch picks the lowest unused number when
creating a vEthernet interface. When you manually create vEthernet interfaces, you may select
any number for the vEthernet . However, as a best practice, you should choose a number that is
less than 32678.
Manually creating virtual Ethernet interfaces
When a server network adapter is connected to a VNTag-mode Ethernet interface on a switch, the
vEthernet interfaces are created. However, vEthernet interfaces can also be created manually
interface
vethernet veth-id
command.
When manually configuring vEthernet interfaces, use the
no vethernet auto-create
command to disable
the automatic creation of vEthernet interfaces.
When a server network adapter is connected and a request to create a vEthernet is received,
the switch checks for a manually configured vEthernet interface that matches the channel
number of the vEthernet creation request. If the manually configured vEthernet interface
already exists, it is used and a new vEthernet interface is not created.
The commands in the following example manually create a vEthernet interface:
Managing networking resources
|
48
