Cisco Nexus 1000V Dağıtım Kılavuzu - Sayfa 28
Ağ Yönlendiricisi Cisco Nexus 1000V için çevrimiçi göz atın veya pdf Dağıtım Kılavuzu indirin. Cisco Nexus 1000V 49 sayfaları. For microsoft hyper-v
Ayrıca Cisco Nexus 1000V için: Veri Sayfası (8 sayfalar), Dağıtım Kılavuzu (25 sayfalar), Manuel (6 sayfalar), Kurulum Kılavuzu (27 sayfalar)
Sayfayı Yazdır
forwarding state. PortFast is configured per interface and should be enabled on interfaces connected to a VEM,
along with BPDU guard and BPDU filtering. Filtering BPDUs at the physical switch port will enhance VEM
performance by avoiding unnecessary processing at the VEM uplink interfaces.
Switch Port Interfaces
The Cisco Nexus 1000V supports multiple switch-port types for internal and external connectivity: virtual Ethernet
(vEth), Ethernet (Eth), and PortChannel (Po). The most common port type in a Cisco Nexus 1000V environment is
the vEth interface, which is a new concept. This interface type represents the switch port connected to a virtual
machine's vNIC or management or live migration vNIC.
A vEth interface has several characteristics that differentiate it from other interface types. Besides the obvious fact
that vEth interfaces are virtual and therefore have no associated physical components, the interface naming
convention is unique. Unlike a traditional Cisco interface, a vEth interface's name does not indicate the module
with which the port is associated. Whereas a traditional physical switch port may be notated as GigX/Y, where X is
the module number and Y is the port number on the module, a vEth interface is notated like this: vEthY. This
unique notation is designed to work transparently with Live Migration, keeping the interface name the same
regardless of the location of the associated virtual machine.
The second characteristic that makes a vEth interface unique is its transient nature. A given vEth interface
appears or disappears based on the status of the virtual machine connected to it. The mapping of a virtual
machine's vNIC to a vEth interface is static. When a new virtual machine is created, a vEth interface is also
created for each of the virtual machine's vNICs. The vEth interfaces will persist as long as the virtual machine
exists. If the virtual machine is temporarily down (the guest OS is shut down), the vEth interfaces will remain
inactive but still bound to that specific virtual machine. If the virtual machine is deleted, the vEth interfaces will
become available for connection to newly provisioned virtual machines.
The Cisco Nexus 1000V contains two interface types related to the Physical Ethernet interfaces (pNICs) on a
Microsoft Hyper-V host. An Ethernet, or Eth, interface is represented in standard Cisco interface notation (EthX/Y)
using the Cisco NX-OS naming convention "Eth" rather than a speed such as "Gig" or "Fast," as is the custom in
Cisco IOS Software. These Eth interfaces are module specific and are designed to be fairly static within the
environment.
PortChannels are the third interface type supported by the Cisco Nexus 1000V. A PortChannel is an aggregation
of multiple Eth interfaces on the same VEM.
Note:
Opaque Data
Opaque data is a collection of Cisco Nexus 1000V configuration parameters maintained by the VSM and Microsoft
SCVMM server when the link between the two is established. The opaque data contains configuration details that
each VEM needs to establish connectivity to the VSM during VEM installation.
Among other content, the opaque data contains:
Switch domain ID
●
Switch name
●
Control and packet VLAN IDs
●
System port profiles
●
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
PortChannels are not created by default and must be explicitly defined.
Page 28 of 48