Feedback
Table Of Contents
Dynamic Interfaces or Dynamic VNICs
Dynamic Floating vEthernet Interfaces
Static Floating vEthernet Interfaces
Fixed vEthernet Interface Provisioning Model
Static Fixed vEthernet Interface Configuration
Dynamic Fixed vEthernet Interface Configuration
Hardware and Software Requirements
Dynamic Fixed vEthernet Interface Configuration
Static Fixed vEthernet Interface Configuration
Fixed vEthernet Interface Failback and Failover with a vPC System
Fixed Static vEthernet Interface Failback and Failover with a vPC System
Dynamic Floating vEthernet Interfaces Configuration Scenario
VM-to-VM-FEX Connection Scenario
VM-FEX Connectivity Verification Scenario
Using VM-FEX
This chapter describes how to use the Cisco Virtual Machine Fabric Extender (VM-FEX).
This chapter includes the following sections:
•
Hardware and Software Requirements
•
•
•
•
•
•
•
•
•
Information About VM-FEX
The Cisco Virtual Machine Fabric Extender (VM-FEX) works with a Cisco virtual interface card (VIC) adapter to replace software-based switching on the server with external hardware-based switching. VM-FEX introduces many new components and concepts. It is important to understand these components and concepts in order to successfully deploy VM-FEX in your network.
VN-Link
A virtual network link (VN-Link) is a virtual network interface card (vNIC) that connects to a virtual Ethernet (vEthernet) interface or virtual host bus adapter (VHBA) that connects to a virtual Fibre Channel (vFC) interface using a Fibre Channel over Ethernet (FCoE) tunnel.Static Interfaces
A static interface is an interface with parameters that are configured manually by you as the administrator. A static interface can be a vEthernet or Fibre Channel interface.For statically created fixed and floating vEthernet interfaces, you as the device administrator can associate the configuration to the vEthernet interface before bringing the interface up. Follow these rules to resolve conflicts:•
•
•
Static Virtual Adapters
A Static Virtual Adapter is a virtual network interface card (VNIC) or a virtual host bus adapter (vHBA).Dynamic Interfaces or Dynamic VNICs
A dynamic interface or dynamic VNIC is a vEthernet interface that gets configured automatically when the adapter and device communicate. The dynamic VNIC inherits the parameters of the virtual network interface card (VNIC) port group on the virtual machine (VM).A dynamic virtual adapter can be a virtual NIC but not a Virtual HBA. A dynamic virtual interface can be a vEthernet interface. Dynamic interfaces support hardware-based failovers in the, Unified Computing System (UCS), UCS VIC card.Because dynamic fixed and floating vEthernet interfaces are created dynamically on the device, you cannot have a configuration that is associated with it. As a result, the device can only associate a configuration to this type of vEthernet using the specified port profile in either the VIF_CREATE or Virtual Ethernet Module (VEM) attach message.Floating Virtual Interfaces
In a Cisco network interface virtualization (NIV) environment with a virtual computing, networking, server, and storage architecture, a VM migrates from one physical server to the other with the virtual network link and vEthernet interface on the physical device. A floating virtual interface is a virtual interface that migrates with its profile characteristics and parameters with the VM and virtual network.For floating (static or dynamic) vEthernet interfaces, configuration changes (including shut or no shut) are allowed at anytime regardless of the attached (hypervisor requested for a vNIC) state except for the binding configuration, which cannot be changed while a vEthernet interface is attached. The binding configuration can be changed only if a vEthernet interfaced is not attached. To see the attachment state of a vEthernet interface, use the show interface veth command.
Fixed vEthernet Interfaces
A fixed vEthernet interface is a virtual interface that does not support migration across physical interfaces.You can change the configuration of a fixed vEthernet interface (static or dynamic), including using the shut or no shut commands or the create or delete commands anytime. The vEthernet number to channel number binding is persistent unless you change it.Dynamic Floating vEthernet Interfaces
The vEthernet interfaces are dynamically created when new VMs are brought up on the hypervisor. A dynamic floating vEthernet interface can move from one VEM to another as VMs are migrated using vMotion. Additionally, the statistics and policies of a dynamic vEthernet interfaces are retained when a VM moves from one host to another.
The following process shows how VMs and their associated vEthernet interfaces are brought up:
1.
2.
3.
4.
5.
a.
b.
6.
7.
a.
b.
Static Floating vEthernet Interfaces
You can create and configure floating vEthernet interfaces.
You can use the following command to select a vEthernet interface number that has been given a distributed virtual port and distributed virtual switch (DVS):
int veth10vmware dvport <dvport-number> dvsswitch uuid <uuid>You can use the following command to select a vEthernet interface number for a MAC address of a VM:
int veth11vsi mac <mac-address>The creation model is the same between static and dynamic floating vEthernet interfaces. When a VEM or NIV adapter signals the device to create vEthernet interface, the device first attempts to match for a configured static vEthernet interface. If a match is found, the specific vEthernet interface number is used. If there is a configuration specified for the static vEthernet interface, this configuration overrides the same coniguration specified, in the port profile.
Fixed vEthernet Interface Provisioning Model
A fixed vEthernet interface is not associated with VMs. Fixed vEthernet interfaces can be created and exposed to host operating systems (OSs) as regular NICs. The host OS can use these vEthernet interfaces and normal Ethernet interfaces as boot devices. If the server is VM-enabled, these fixed vEthernet interfaces present themselves as physical adapters because vCenter cannot migrate this type of vEthernet interface using vMotion.
The desired provisioning model for a fixed vEthernet interface is the dynamic model. In this provisioning model, there is no configuration on the device that represents the vEthernet interface. This model depends on the port profile information that is provided to the device through the VIC protocol.
The device advertises the list of port profile names that are configured on the device using the VIC control channel (VIF_SET of 0). The NIV adapter allows a way for you as the server administrator to choose from a list of port profiles to be attached to each fixed vEthernet interface.
This process describes how to bring up a fixed vEthernet interface:
1.
2.
a.
b.
3.
4.
5.
This example shows vEthernet interface 10 being created and bound to Ethernet interface 1/10, channel 4:
int veth10bind interface ethernet 1/10 channel 4inherit port profile xxxA unique channel number given to each physical interface is required. You can remove the binding by using the no bind interface ethernet command, even after the vEthernet interface is attached to the VNIC in the host (that is, even after the device receives the vif-create command). This behavior is different from creating a floating vEthernet interface. With fixed vEthernet interfaces, the adapter internally maps the channel number to the OS-visible NIC interfaces and displays the mapping information in the adapter tool.
In a FEX Active-to-Active topology, there are at least two VIFs for each vEthernet interface and multiple bind interface commands are allowed under a vEthernet interface. For example, if an adapter has two uplinks and each uplink is connected to FEX port 100/1/10 and 100/1/11, then both bound interfaces must be configured as static fixed vEthernet interfaces.
int veth10bind interface ethernet 100/1/10 channel 4bind interface ethernet 101/1/11 channel 4Static Fixed vEthernet Interface Configuration
In the Cisco Integrated Management Controller (CIMC), the port profile is not specified for the VNIC, and on the device, the static fixed vEthernet interface is manually configured in the running configuration.
interface veth 1bind int e 100/1/1 channel 1no shutDynamic Fixed vEthernet Interface Configuration
An alternative to creating a static, fixed vEthernet interface is to configure the device with the dynamic_vnic_profile port profile and configure a bound physical interface in the VNTag mode. The device pushes the dynamic_vnic_profile port profile to the Unified Computing System (UCS) VIC adapter.
You must go to CIMC and add or edit the fixed vNIC properties by changing the port profile to dynamic_vnic_profile. You can either manually type the string "dynamic_vnic_profile" or use the drop-down menu, because the device has pushed all port profiles to the adapter.
Then, you must reboot the server to make the changes take effect with the early firmware release. As a result, the dynamic fixed vEthernet interfaces are entered automatically in the device's running configuration.
interface veth 1inherit port-profile xyzbind int e 100/1/1 channel 1NIV Host Discovery
Before NIV vEthernet interfaces can be created, the physical interface connected to the host must be configured with VNTag mode, and Data Center Bridging Exchange (DCBX) communication between the switchport and the host uplink must be converged with VNTag mode.
int e1/1 or e100/1/1switchport mode vntag
Note
Note
The host that runs softPTS can operate in classical Ethernet mode before transitioning to VNTag mode. The transition to VNTag mode is made when the host starts to include the NIV capability (that is, TLV) in its DCBX advertisement. Until then, the host runs softPTS operates in the classical Ethernet mode. While it operates in the classical Ethernet mode, the host has full connectivity to the network through the physical interface connected the device that is configured with VNTag mode. Because the port can be configured in access or trunk mode, you can use the following commands to configure the switchport behavior when the port is configured in VNTag mode:
switchport trunk allowed vlan [add|all|except|none|remove] <vlan-list>switchport trunk native vlan <vlan>switchport access vlan <vlan>You can use switchport trunk allowed vlan and switchport trunk native vlan vlan commands only when the port is configured to be a VNTag trunk device port that is operating in the classical Ethernet mode. The command configures the allowed VLAN list for the switchport and default VLAN for the trunk port.
You can use switchport access vlan only when the port is configured as a VNTag access device port that is operating in the classical Ethernet mode. This command allows you to configures the access VLAN for the device port.
Port Profile Inheritance
Because dynamic fixed and floating vEthernet interfaces are created dynamically on the device, there cannot be a configuration associated with it. As a result, the device can only configure this type of vEthernet interface using the port profile specified in either the VIF_CREATE or VEM attach message.
For statically created fixed and floating vEthernet interfaces, it is possible for you as the device administrator, to associate the configuration with the vEthernet interface before it is brought up. These rules are necessary to resolve conflicts:
•
•
vEthernet interface configurations or port profile configurations can be specified in a synchronization profile if configuration synchronization between two Cisco Nexus 5000 Series devices is enabled.
Distributed Virtual Switches
The DVS or virtual distributed switch (VDS) spans multiple VMware vSphere (vSphere) hosts and aggregating the network management of the virtual switching environment into a centralized management interface. Prior to DVS, each server needed to have a device configured and if VMware vMotion (vMotion) was desired, the configuration of these devices needed to be manually verified as consistent across the entire cluster. With DVS, a single device is created that spans all of the servers in the cluster. The port groups only need to be configured once, and they are automatically applied on all servers in the cluster.
The VEM for ESX systems always contains both the Local Switching module and the PTS module. The PTS module covers both the Soft-PTS and Hard-PTS mode of functions that can flexibly enable both VEM and NIV functionalities. This software package is also commonly known as VIB, where VIB is the format used by VMware.
Hardware and Software Requirements
Table 1 explains the VM-FEX hardware and software requirements.
Table 2-1 VM-FEX Hardware and Software Requirements
Dynamic Fixed vEthernet Interface Configuration
The two possible configuration models for fixed vEthernet interfaces are static and dynamic. The preferred configuration model on the device is the dynamic fixed vEthernet interface because of the ease of configuration and the minimal interaction required between the device and the server administrator to set up the vEthernet configuration.
First, the device administrator configures several port profiles on the device. Each port profile defines a set of device port configurations that are applied to a vEthernet interface. The configuration is based on the various roles that a host could have in the network and is a template from which a server administrator can choose the configuration that is needed for the server port.
When a VIC session is established between the adapter and the device, as part of the protocol handshake, the device passes a list of port profiles that are relevant to the host. You can display this list of port profiles using a BIOS or adapter tool and choose a specific port profile from the list for a vNIC that is presented on the PCI bus. After choosing the port profile, the port profile ID is sent back to the device though the VIC protocol as part of this VIF bringup. The device creates a dynamic vEthernet interface during this VIF bringup and applies the port profile that it receives from the adapter.
The dynamic fixed vEthernet interfaces are entered automatically in the device running-configuration.
interface veth 1inherit port-profile xyzbind int e 100/1/1 channel 1When the vEthernet handshake is complete and the interface is brought up, all the interface configuration that was part of the port profile is applied to the interface and the interface becomes operational.
If the physical link between the server and the device flaps or there is a disruption in the VIC session between the device and the server, the port profile list on the server is cleared so that there is no stale information that is retained on the host. When the VIC session is reestablished, a new port profile list is sent to the server.
Figure 2-1 shows a dynamic vEthernet configuration on a device.
Figure 2-1 Dynamic vEthernet Configured on a Device
Static Fixed vEthernet Interface Configuration
In CIMC, the port profile is not specified for the VNIC. On the device, the static fixed vEthernet is manually entered in the running configuration such as:
interface vEthernet 1bind int e 1/18 channel 1no shut
Note
Some packets might get lost due to the time needed for the reconvergence of the return traffic to take place.
The Cisco Nexus 5548 Series device sends the gratuitous ARP reply for the static MAC and IGMP join messages of the active vEthernet interface that has failed over or failed back for the reconvergence to take place. This action enables the return traffic path immediately in the direction from the network to the host.
In the FEX straight-through topology, the active Cisco Nexus 5000 Series device synchronizes continuously all unicast MAC addresses learned on the active vEthernet interface to the Cisco Nexus 5000 Series device with the standby vEthernet interface. The destination for these unicast MAC addresses point to them Multichassis EtherChannel Trunk (MCT) on the standby Cisco Nexus 5000 Series device. Unicast MAC addresses are synchronized using Cisco Fabric Services over Ethernet (CFSoE) as a transport. IGMP groups are not synchronized.
A future Cisco NX-OS version sends for all MAC dynamic addresses in addition to the static one earned behind the failed over/failed back vEthernet port and for all IGMP join messages collected for the active vEthernet interface, the IGMP join requests, and the Gratuitous ARP reply to the external network.
Fixed vEthernet Interface Failback and Failover with a vPC System
The fixed vEthernet interface failback and failover with a vPC system process is as follows:
1.
2.
3.
4.
5.
6.
As a result of any of these events occurring, the NIV adapter activates the standby link to become the new forwarding path for the VIF. The NIV adapter sends the VIF_ACTIVATE message to the standby Cisco Nexus 5000 Series device.
7.
a.
b.
c.
d.
8.
Fixed Static vEthernet Interface Failback and Failover with a vPC System
The process for a fixed static vEthernet interface fails back or fails over to a vPC system is as follows:
1.
2.
3.
4.
a.
b.
c.
d.
5.
VM-FEX Configuration Scenario
This scenario takes you through the steps to configure VM-FEX in a sample network.
The following are the high-level steps for configuring FM-FEX:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
The port profile should propagate to the vds-nx5k VDS as a vmware port group.
12.
13.
14.
Static VNIC Configuration
The static VNIC configuration is as follows:
Note
Step 1
Step 2
Step 3
Figure 2-2 Verifying the NIV Mode
Note
•
•
•
Step 4
Step 5
Figure 2-3 VNIC's Properties
Step 6
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The parameters for the static VNICs on the UCS VIC for ESX Host 1 are shown in Figure 2-4.
Figure 2-4 VNICs on the UCS VIC for ESX Host 1
The vNIC properties for stateht1 is shown in Figure 2-5.
Figure 2-5 VNICs on the UCS VIC for ESX Host 2
Step 7
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The parameters for the static VNICs on the UCS VIC for ESX Host 1 are shown in Figure 2-6.
Figure 2-6 vNIC Properties for ESX Host 2
Adding vNIC for stateht1 is shown in Figure 2-7.
Figure 2-7 Adding vNIC
Step 8
Step 9
Note
Figure 2-8 shows the screen after the reboot.
Figure 2-8 Cisco Integrated Management Controller
Step 10
a.
–
–
–
–
–
–
–
–
–
–
b.
interface Ethernet1/17switchport mode vntag shutinterface Ethernet1/18switchport mode vntagshutc.
On the Cisco Nexus 5548-1 device enter these commands:
pod1-5548-1(config)# interface vethernet1pod1-5548-1(config-if)# bind interface eth 1/17 channel 10pod1-5548-1(config-if)# no shutpod1-5548-1(config-if)# interface vethernet 3pod1-5548-1(config-if)# bind interface eth 1/17 channel 11pod1-5548-1(config-if)# no shutpod1-5548-1(config-if)# interface vethernet 2pod1-5548-1(config-if)# bind interface eth 1/18 channel 10pod1-5548-1(config-if)# no shutpod1-5548-1(config-if)# interface vethernet 4pod1-5548-1(config-if)# bind interface eth 1/18 channel 11pod1-5548-1(config-if)# no shutOn the Cisco Nexus 5548-2 device enter these commands:
pod1-5548-2(config)# interface vethernet 1pod1-5548-2(config-if)# bind interface eth 1/17 channel 10pod1-5548-2(config-if)# no shutpod1-5548-2(config-if)# interface vethernet 3pod1-5548-2(config-if)# bind interface eth 1/17 channel 11pod1-5548-2(config-if)# no shutpod1-5548-2(config-if)# interface vethernet 2pod1-5548-2(config-if)# bind interface eth 1/18 channel 10pod1-5548-2(config-if)# no shutpod1-5548-2(config-if)# interface vethernet 4pod1-5548-2(config-if)# bind interface eth 1/18 channel 11pod1-5548-2(config-if)# no shutd.
interface Ethernet1/17no shutdownnterface Ethernet1/18no shutdowne.
On the Cisco Nexus 5548-1 device enter these commands:
pod1-5548-1# show interface vethernet 1Vethernet1 is upBound Interface is Ethernet1/17Hardware is Virtual, address is 0005.73fc.24a0Port mode is accessSpeed is auto-speedDuplex mode is auto300 seconds input rate 0 bits/sec, 0 packets/sec300 seconds output rate 0 bits/sec, 0 packets/secRx0 unicast packets 0 multicast packets 0 broadcast packets0 input packets 0 bytes0 input packet dropsTx0 unicast packets 0 multicast packets 0 broadcast packets0 output packets 0 bytes0 flood packets0 output packet dropsPOD1-5548-1# show interface vethernet 1 detailvif_index: 20--------------------------veth is bound to interface Ethernet1/17 (0x1a010000)priority: 0vntag: 16status: activechannel id: 10registered mac info:vlan 0 - mac 00:00:00:00:00:00vlan 0 - mac 58:8d:09:0f:0b:3cvlan 0 - mac ff:ff:ff:ff:ff:ffOn the Cisco Nexus 5548-2 device enter these commands:
POD1-5548-2# show interface vethernet 1 detailvif_index: 20--------------------------veth is bound to interface Ethernet1/17 (0x1a010000)priority: 0vntag: 16status: standbychannel id: 10registered mac info:vlan 0 - mac 00:00:00:00:00:00vlan 0 - mac 58:8d:09:0f:0b:3cvlan 0 - mac ff:ff:ff:ff:ff:ffPOD1-5548-1# show mac addressLegend:* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MACage - seconds since last seen,+ - primary entry using vPC Peer-LinkVLAN MAC Address Type age Secure NTFY Ports---------+-----------------+--------+---------+------+----+------------------* 1 588d.090f.0970 static 0 F F Veth2* 1 588d.090f.0971 static 0 F F Veth4* 1 588d.090f.0b3c static 0 F F Veth1* 1 588d.090f.0b3d static 0 F F Veth3* 4040 0005.73fc.1fbc static 0 F F Router
Note
f.
POD1-5548-1(config-if-range)# inerface ethernet 1/17-18POD1-5548-1(config-if-range)# no shutPOD1-5548-2# show interface vethernet 1 detailvif_index: 20--------------------------veth is bound to interface Ethernet1/17 (0x1a010000)priority: 0vntag: 16status: activechannel id: 10registered mac info:vlan 0 - mac 00:00:00:00:00:00vlan 0 - mac 58:8d:09:0f:0b:3cvlan 0 - mac ff:ff:ff:ff:ffPOD1-5548-2# show mac addressLegend:* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MACage - seconds since last seen,+ - primary entry using vPC Peer-LinkVLAN MAC Address Type age Secure NTFY Ports---------+-----------------+--------+---------+------+----+------------------* 1 588d.090f.0970 static 0 F F Veth2* 1 588d.090f.0971 static 0 F F Veth4* 1 588d.090f.0b3c static 0 F F Veth1* 1 588d.090f.0b3d static 0 F F Veth3POD1-5548-1(config-if-range)# show interface veth 1 detailveth is not boundpriority: n/avlan: n/avntag: n/aregistered mac info:POD1-5548-1(config-if-range)# show mac addressLegend:* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MACage - seconds since last seen,+ - primary entry using vPC Peer-LinkVLAN MAC Address Type age Secure NTFY Ports---------+-----------------+--------+---------+------+----+------------------* 4040 0005.73fc.1fbc static 0 F F RouterPOD1-5548-1(config-if-range)#g.
POD1-5548-1# show interface vethernet 1 detailvif_index: 20--------------------------veth is bound to interface Ethernet1/17 (0x1a010000)priority: 0vntag: 16status: activechannel id: 10registered mac info:vlan 0 - mac 00:00:00:00:00:00vlan 0 - mac 58:8d:09:0f:0b:3cvlan 0 - mac ff:ff:ff:ff:ff:ffPOD1-5548-1# show mac addressLegend:* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MACage - seconds since last seen,+ - primary entry using vPC Peer-LinkVLAN MAC Address Type age Secure NTFY Ports---------+-----------------+--------+---------+------+----+------------------* 4040 0005.73fc.1fbc static 0 F F Router* 1 588d.090f.0970 static 0 F F Veth2* 1 588d.090f.0971 static 0 F F Veth4* 1 588d.090f.0b3c static 0 F F Veth1* 1 588d.090f.0b3d static 0 F F Veth3POD1-5548-1#POD1-5548-2# show interface vethernet 1 detailvif_index: 20--------------------------veth is bound to interface Ethernet1/17 (0x1a010000)priority: 0vntag: 16status: standbychannel id: 10registered mac info:vlan 0 - mac 00:00:00:00:00:00vlan 0 - mac 58:8d:09:0f:0b:3cvlan 0 - mac ff:ff:ff:ff:ff:ffPOD1-5548-2# show mac addressPOD1-5548-2#
Dynamic Floating vEthernet Interfaces Configuration Scenario
The Dynamic Floating vEthernet Interfaces Configuration Scenario is as follows:
Step 1
Step 2
Step 3
Step 4
Step 5
Modifying Adapter Properties is shown in Figure 2-9.
Figure 2-9 Modifying Adapter Properties
Step 6
The dynamic vEthernet interfaces should be entered into the running configuration and connected to the dynamic vNICs automatically when the VM connects to the dynamic port group in PTS mode as shown in Figure 2-10.
Figure 2-10 Virtual FEXs
Step 7
Step 8
port-profile type vethernet VLAN61switchport mode accessswitchport access vlan 61dvs-name allport-bindindg dynamicstate enabledvlan 61The dvs-name all command defines the dvs device in vCenter that this port profile is exported to as a port group as shown in Figure 2-11. Using the all option, the port group is exported to all DVSes in the data center.
These keywords are the vEthernet port binding types:
•
•
•
Step 9
Step 10
Step 11
Step 12
Figure 2-11 vSphere Client
Step 13
Figure 2-12 SVS connection between the vCenter server and the vPC system
Note
Each DVS is created with an extension key and a certificate. In the case where two Cisco Nexus 5000 Series devices are configured in a vPC topology, the primary vPC device pushes the DVS and extension key pair to a particular datacenter that is supported on a vCenter and port profiles. Both primary and secondary devices independently poll the vCenter to perform garbage collection by retrieving the list of DV port IDs in use. Any vEthernet interface that maps to an unused DV port ID is deleted. The vCenter never initiates communication to the devices.
Step 14
a.
b.
Figure 2-13 Index of Downloads
Step 15
a.
b.
Figure 2-14 Plug-in Manager
c.
Figure 2-15 Register plug-in
d.
Note
e.
Figure 2-16 Status of Plug-ins
Step 16
On the Cisco Nexus 5548-2 Series device enter the following commands:
pod1-5548-2(config)# feature vpcpod1-5548-2(config)# feature lacppod1-5548-2(config)# vpc domain 1pod1-5548-2(config-vpc-domain)# role priority 100 /no priority the other switchpod1-5548-2(config-vpc-domain)# peer-keepalive destination 10.29.186.195 vrf managementpod1-5548-2(config)# int eth 1/27-30pod1-5548-1(config-if-range)# channel-group 10pod1-5548-1(config-if-range)# exitpod1-5548-2(config)# int po10pod1-5548-2(config-if)# vpc peer-linkpod1-5548-2(config-if)# spanning-tree port type networkpod 1-5548-2(config-if)# // permit all vlans but but not FCOE VLAN 200!pod 1-5548-2(config-if)# sw trunk allowed vlan 1-199, 201-3967, 4048-4093pod1-5548-2(config-if)# no shutOn the Cisco Nexus 5548-1 Series device:
pod1-5548-1(config)# feature vpcpod1-5548-1(config)# feature lacppod1-5548-1(config)# vpc domain 1pod1-5548-1(config-vpc-domain)# role priority 90pod1-5548-1(config-vpc-domain)# peer-keepalive destination 10.29.186.196 vrf managementpod1-5548-1(config)# int eth 1/27-30pod1-5548-1(config-if-range)# channel-group 10pod1-5548-1(config-if-range)# exitpod1-5548-1(config)# int po10pod1-5548-1(config-if)# vpc peer-linkpod1-5548-1(config-if)# spanning-tree port type network // permit all vlans but but not FCOE VLAN 200!pod1-5548-1(config-if)#) sw trunk allowed vlan 1-199, 201-3967, 4048-4093 //no fcoe vlanpod1-5548-1(config-if)#no shutStep 17
pod1-5548-2# show vpcLegend:(*) - local vPC is down, forwarding via vPC peer-linkvPC domain id : 1Peer status : peer adjacency formed okvPC keep-alive status : peer is aliveConfiguration consistency status: successPer-vlan consistency status : successvPC role : secondaryNumber of vPCs configured : 0Peer Gateway : DisabledDual-active excluded VLANs : -Graceful Consistency Check : EnabledvPC Peer-link status---------------------------------------------------------------------id Port Status Active vlans-- ---- ------ --------------------------------------------------1 Po10 up 1,61POD1-5548-1# show vpcLegend:(*) - local vPC is down, forwarding via vPC peer-linkvPC domain id : 1Peer status : peer adjacency formed okvPC keep-alive status : peer is aliveConfiguration consistency status: successPer-vlan consistency status : successvPC role : primaryNumber of vPCs configured : 0Peer Gateway : DisabledDual-active excluded VLANs : -Graceful Consistency Check : EnabledvPC Peer-link status---------------------------------------------------------------------id Port Status Active vlans-- ---- ------ --------------------------------------------------1 Po10 up 1,61OD1-5548-2(config-if)# show vpc rolevPC Role status----------------------------------------------------vPC role : secondaryDual Active Detection Status : 0vPC system-mac : 00:23:04:ee:be:01vPC system-priority : 32667vPC local system-mac : 00:05:73:fc:24:fcvPC local role-priority : 110----------------------------------------------------- ---------------------------------------------------------------POD1-5548-1# show vpc rolevPC Role status----------------------------------------------------vPC role : primaryDual Active Detection Status : 0vPC system-mac : 00:23:04:ee:be:01vPC system-priority : 32667vPC local system-mac : 00:05:73:fc:1f:bcvPC local role-priority : 90POD1-5548-1#Step 18
Note
pod1-5548-1(config)# svs connection 2VCpod1-5548-1(config-svs-conn)# protocol vmware-vimpod1-5548-1(config-svs-conn)# vmware dvs datacenter-name DC1pod1-5548-1(config-svs-conn)# dvs-name Pod1PTSpod1-5548-1(config-svs-conn)# remote ip address 10.29.186.125 port 80 vrf managementpod1-5548-1(config-svs-conn)# install certificate defaultpod1-5548-1(config-svs-conn)# extension-key: Cisco_Nexus_1000V_1543569268 // only on the primary vpc member
Note
Figure 2-17 Available Plug-ins
Note
Step 19
pod1-5548-1(config)# svs connection 2VCpod1-5548-1(config-svs-conn)# connectNote: Command execution in progress..please waitpod1-5548-1(config-svs-conn)#One of the results of the connect action is that the dvs-pts folder is created under your datacenter as shown in Figure 2-18.
Figure 2-18 vSphere - DCVMFEX1
Step 20
Note
pod1-5548-2(config)# svs connection 2VCpod1-5548-2(config-svs-conn)# protocol vmware-vimpod1-5548-2(config-svs-conn)# vmware dvs datacenter-name DC1pod1-5548-2(config-svs-conn)# dvs-name Pod1PTSpod1-5548-2(config-svs-conn)# remote ip address 10.29.186.125 port 80 vrf managementpod1-5548-2(config-svs-conn)# install certificate defaultpod1-5548-2(config-svs-conn)#
Note
The extension key is synchronized by the primary vPC member to the secondary vPC member. You can verify that the extension key is the same on both peers by using the show svs connection command. If the two Cisco Nexus 5548 devices were not vPC peers, the extension key would be different for each device, and each device would have to establish its own connection to the vCenter.
Step 21
POD1-5548-1(config)# show svs connectionconnection 2VC:ip address: 10.29.186.125remote port: 80vrf: amangprotocol: vmware-vim httpscertificate: defaultdatacenter name: DC1extension key: Cisco_Nexus_1000V_1543569268dvs name: Pod1PTSDVS uuid: 44 f1 04 50 47 cc 42 d6-ba ea 53 f9 f9 32 4b fb // This is pushed by VCenter to switchconfig status: Enabledoperational status: Connected // Only Primary connects to VCentersync status: in progressversion: VMware vCenter Server 4.1.0 build-258902Peer Info:----------connection 2VC:ip address: 10.29.186.125remote port: 80vrf: managementprotocol: vmware-vim httpsextension key: Cisco_Nexus_1000V_1543569268 //This extension key is result of synccertificate: default //status of the VPC primary to second.certificate match: TRUEdatacenter name: DC1dvs name: Pod1PTSDVS uuid: -config status: Disabledoperational status: DisconnectedStep 22
Figure 2-19 vPC system in vCenter
POD1-5548-2# show svs connectionconnection 2VC:ip address: 10.29.186.125remote port: 80vrf: managementprotocol: vmware-vim httpscertificate: defaultdatacenter name: DC1extension key: Cisco_Nexus_1000V_1543569268 // Received from the VPC Primarydvs name: pod1PTSDVS uuid: -config status: Enabledoperational status: Disconnectedsync status: -version: -Peer Info:----------connection 2VC:ip address: 10.29.186.125remote port: 80vrf: amangprotocol: vmware-vim httpsextension key: Cisco_Nexus_1000V_1543569268certificate: defaultcertificate match: TRUEdatacenter name: DC1dvs name: Pod1PTSDVS uuid: 44 f1 04 50 47 cc 42 d6-ba ea 53 f9 f9 32 4b fb //Received from VCenterconfig status: Enabledoperational status: ConnectedStep 23
Caution
ESX Host1:
10.29.186.197Username= rootPassword= Not4u2use!Use the Enterprise License Plus enteredSelect the shared datastore visible across the Qlogic VHBA and the datastore1 which is local.ESX Host 2:
10.29.186.198Username= rootPassword= Not4u2use!se the Enterprise License Plus entered.Select the shared datastore visible across the Qlogic VHBA and the datastore1 which is local.While adding the host, the wizard should show a screen for each host as shown in Figure 2-20.
Figure 2-20 Adding the Host Wizard Screen
The summary before finishing the wizard is shown in Figure 2-21.
Figure 2-21 Reviewing the Summary
The New Virtual Machines on vSphere Client is shown in Figure 2-22.
Figure 2-22 New Virtual Machines on vSphere Client
Step 24
Figure 2-23 Adding Hosts to the PodYPTS VDS
Note
Step 25
Step 26
Step 27
Figure 2-24 Viewing details of each VMNIC
Note
Figure 2-25 Physical Adapter Details - vEthenet1
The Physical Adapter Details for the Port ID vEthenet3 is shown in Figure 2-26.
Figure 2-26 Physical Adapter Details - vEthenet3
The Physical Adapter Details for the Port ID vEthenet2 is shown Figure 2-27.
Figure 2-27 Physical Adapter Details - vEthenet2
The Physical Adapter Details for the Port ID vEthenet4 is Figure 2-28.
Figure 2-28 Physical Adapter Details - vEthenet4
Step 28
Step 29
The results of this process are as follows:
•
•
•
•
•
All four VMNICs have to be up and running. Notice the red x next to VMNIC, which indicates that the VMNIC is not connected, and the two static VNICs that have been mapped to the VMNICs to the Pod1PTS VDS on each host as shown in Figure 2-29.
Figure 2-29 Pod1PTS VDS on each host
The adapter is first being brought up.
If this interface is a fixed vEthernet interface, the NIV adapter also creates one vEthernet interface on the active Cisco Nexus 5000 Series device and one vEthernet interface on the standby Cisco Nexus 5000 Series device. The NIV adapter uses the same channel number in both the VIF_CREATE messages to the two Cisco Nexus 5000 Series devices. For static fixed vEthernet interface, you must create the vEthernet interface on the two Cisco Nexus 5000 Series devices with the same vEthernet interface number and channel number. For dynamically created fixed vEthernet interface, the two Cisco Nexus 5000 Series devices coordinate to ensure the same channel number on the two Cisco Nexus 5000 Series device are mapped to the same vEthernet interface number.
If this is a floating (static or dynamic) vEthernet interface, the NIV adapter creates one vEthernet interface on the active Cisco Nexus 5000 Series device and one vEthernet interface on the standby Cisco Nexus 5000 Series device. Each Cisco Nexus 5000 Series device runs its own VIC protocol session to the NIV adapter. The NIV adapter uses the same dvport-id in both VIF_CREATE messages to the two Cisco Nexus 5000 Series devices. The two Cisco Nexus 5000 Series devices coordinate to ensure the same vEthernet number is allocated to the two vEthernet interfaces that are mapped to the same dvport_id.
VM-to-VM-FEX Connection Scenario
The VM-to-VM-FEX Connection Scenario is as follows:
Step 1
Step 2
Step 3
Figure 2-30 Adding the new Virtual Machine
Step 4
Step 5
Figure 2-31 Creating a new Virtual Machine
Step 6
Figure 2-32 Shared Datastore
The Ready to Complete Screen is shown in Figure 2-33.
Figure 2-33 Ready to Complete Screen
Step 7
Figure 2-34 Virtual Machine Properties
Step 8
Figure 2-35 Mapping the RedHat ISO image as a new virtual CD/DVD drive
Step 9
Figure 2-36 Powering on the Virtual Machine
Step 10
Figure 2-37 Red Hat Linux 5 Loaded Screen
VM-FEX Connectivity Verification Scenario
The VM-FEX Connectivity Verification Scenario is as follows:
Step 1
The Cisco UCS VIC in NIV mode enables the dynamic VNIC when the VM is associated to port group VLAN61 and configures it with the parameters inherited from the port group. The Cisco UCS VIC sends a DCBX VIC message to the Cisco Nexus 5548 device vPC system. The vPC system enables a dynamic vEthernet interface in active/standby mode on the vPC members and connects the VNIC to the vPC system using a VN-Link in the hardware with PTS. The dynamic VNIC is one of the 20 provisioned dynamic VNICs on the UCS VIC with the in-hardware-based failover enabled.
POD1-5548-2# show running // this interface was not manually configured but automatically that is why it is called dynamicinterface Vethernet5inherit port-profile VLAN61vsi mac 0050.5684.0000...output omitted...OD1-5548-1# show interface vethernet 5Vethernet5 is upBound Interface is Ethernet1/17Hardware is Virtual, address is 0023.04ee.be01Port mode is accessSpeed is auto-speedDuplex mode is auto300 seconds input rate 0 bits/sec, 0 packets/sec300 seconds output rate 0 bits/sec, 0 packets/secRx0 unicast packets 0 multicast packets 0 broadcast packets0 input packets 0 bytes0 input packet dropsTx0 unicast packets 5 multicast packets 0 broadcast packets5 output packets 1420 bytes0 flood packets0 output packet dropsPOD1-5548-1#POD1-5548-1# show running // this interface was not manually configured but automatically that is why it is called dynamicinterface Vethernet5inherit port-profile VLAN61vsi mac 0050.5684.0000...output omitted...POD1-5548-2# show interface vethernet 5Vethernet5 is upBound Interface is Ethernet1/17Hardware is Virtual, address is 0023.04ee.be01Port mode is accessSpeed is auto-speedDuplex mode is auto300 seconds input rate 0 bits/sec, 0 packets/sec300 seconds output rate 0 bits/sec, 0 packets/secRx0 unicast packets 0 multicast packets 0 broadcast packetsPOD1-5548-2# show interface veth 5 detail // veth 5 is standby on switch NX5548-2vif_index: 25--------------------------veth is bound to interface Ethernet1/17 (0x1a010000) // veth 5 is maped to phy. Interf. eth 1/17priority: 0vntag: 6status: standbyregistered mac info:POD1-5548-2#Step 2
POD1-5548-2# show mac addressLegend:* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MACage - seconds since last seen,+ - primary entry using vPC Peer-LinkVLAN MAC Address Type age Secure NTFY Ports---------+-----------------+--------+---------+------+----+------------------+ 61 0050.5684.0000 dynamic 0 F F Po10 // VM connects in VLAN 61+ 1 588d.090f.0970 dynamic 0 F F Po10+ 1 588d.090f.0971 dynamic 0 F F Po10+ 1 588d.090f.0b3c dynamic 0 F F Po10+ 1 588d.090f.0b3d dynamic 0 F F Po10POD1-5548-2#These interfaces are reported by vCenter Server and are available to the Pod1PTS VDS. Port 32 is in VLAN61 and is a dynamic VMNIC interface that is up and connected to the VM VNIC is shown in Figure 2-38.
Figure 2-38 Dynamic VMNIC Interface
You can list them using the ESX CIMC by opening a KVM session to the host. Alternatively, you can enter the following ESX console command to list the 20 dynamic VMNICs that are available to be activated once the VM connects to port group VLAN61:
ifconfig-a | moreThe names of dynamic VNICs in the output of the command are vm_vmnic0 through vf_vmnic19 is show in Figure 2-39.
Figure 2-39 Names of Dynamic VNICs in the Output
Step 3
POD1-5548-2# show interface vethernet 5The interface is no longer in the running configuration (even though port 32, the dynamic VNIC that was the VMNIC interface in the vCenter server in VLAN61, is also down.)
Step 4
Configuration Summary
The VM is powered on and resides on the ESX Host 1 with all the information stored on the shared storage.
The VM was connected to the PODy (where y is the number of your POD) PTS VDS by associating it to port group VLAN61 that was created on the Cisco Nexus 5548 device. The VM has been connected to the vPC system automatically using a VN-Link in the hardware in PTS mode or in VM-FEX mode.
The VEM bits are used in PTS mode to connect the VM VNIC to the VMNIC interface.
In this case, the VMNIC interface is not a real VMNIC but a dynamic VNIC that is presented as an interface to the ESX OS. The dynamic VNIC is enabled when the Cisco UCS VIC creates and configures the VNIC parameters inherited from port group VLAN61.
Sample Configuration
!Command: show running-config!Time: Thu Sep 1 09:29:07 2011version 5.1(3)N1(1)feature fcoeinstall feature-set virtualizationfeature-set virtualizationhostname POD1-5548-1feature telnetcfs eth distributefeature interface-vlanfeature lacpfeature vmfexfeature vpcfeature lldpfeature fexusername adminbackup password 5 ! role network-operatorusername admin password 5 $1$W40UpSMJ$RP8cRyIJjLhVYlwls9lcq1 role network-adminno password strength-checkbanner motd #Nexus 5000 Switch#ip domain-lookupclass-map type qos class-fcoeclass-map type queuing class-fcoematch qos-group 1class-map type queuing class-all-floodmatch qos-group 2class-map type queuing class-ip-multicastmatch qos-group 2class-map type network-qos class-fcoematch qos-group 1class-map type network-qos class-all-floodmatch qos-group 2class-map type network-qos class-ip-multicastmatch qos-group 2system qosservice-policy type qos input fcoe-default-in-policyservice-policy type queuing input fcoe-default-in-policyservice-policy type queuing output fcoe-default-out-policyservice-policy type network-qos fcoe-default-nq-policypolicy-map type control-plane copp-system-policycontrol-planeservice-policy input copp-system-policysnmp-server user admin network-admin auth md5 0xb2ee7c583c00370672f6605f06113332priv 0xb2ee7c583c00370672f6605f06113332 localizedkeysnmp-server enable traps entity fruvrf context managementip route 0.0.0.0/0 10.29.184.1vlan 1,61vlan 200fcoe vsan 200vethernet auto-createvpc domain 1role priority 90peer-keepalive destination 10.29.186.196port-profile type vethernet VLAN61switchport access vlan 61state enabledport-profile type ethernet Unused_Or_Quarantine_Uplinkshutdowndescription Port-group created for Nexus1000V internal usage. Do not use.state enabledport-profile type vethernet Unused_Or_Quarantine_Vethshutdowndescription Port-group created for Nexus1000V internal usage. Do not use.state enabledport-profile type vethernet statfloatsw access vlan 1state enabledvsan databasevsan 200fcdomain fcid databasevsan 200 wwn 20:00:58:8d:09:0f:09:6e fcid 0x730000 dynamicvsan 200 wwn 21:00:00:c0:dd:15:21:7f fcid 0x730001 dynamicvsan 200 wwn 21:00:00:c0:dd:12:14:03 fcid 0x730002 dynamicinterface Vlan1interface Vlan61no shutdownip address 10.10.10.1/24interface port-channel10switchport mode trunkspanning-tree port type networkvpc peer-linkinterface vfc300bind interface Ethernet1/26switchport mode Eswitchport trunk allowed vsan 1switchport trunk allowed vsan add 200no shutdowninterface vfc100bind interface Vethernet100interface vfc400bind interface Ethernet1/5no shutdowninterface vfc200bind interface Vethernet200interface vfc500bind interface Ethernet1/6no shutdownvsan databasevsan 200 interface vfc300vsan 200 interface vfc100vsan 200 interface vfc400vsan 200 interface vfc200vsan 200 interface vfc500interface Ethernet1/1interface Ethernet1/2interface Ethernet1/3interface Ethernet1/4interface Ethernet1/5switchport mode trunkinterface Ethernet1/6switchport mode trunkinterface Ethernet1/7interface Ethernet1/8interface Ethernet1/9interface Ethernet1/10interface Ethernet1/11interface Ethernet1/12interface Ethernet1/13interface Ethernet1/14interface Ethernet1/15interface Ethernet1/16interface Ethernet1/17switchport mode vntaginterface Ethernet1/18switchport mode vntaginterface Ethernet1/19interface Ethernet1/20interface Ethernet1/21interface Ethernet1/22interface Ethernet1/23interface Ethernet1/24shutdowninterface Ethernet1/25interface Ethernet1/26switchport mode trunkinterface Ethernet1/27switchport mode trunkspanning-tree port type networkchannel-group 10interface Ethernet1/28switchport mode trunkspanning-tree port type networkchannel-group 10interface Ethernet1/29switchport mode trunkspanning-tree port type networkchannel-group 10interface Ethernet1/30switchport mode trunkspanning-tree port type networkchannel-group 10interface Ethernet1/31interface Ethernet1/32interface mgmt0ip address 10.29.186.195/22interface Vethernet1bind interface Ethernet1/17 channel 10interface Vethernet2bind interface Ethernet1/18 channel 10interface Vethernet3bind interface Ethernet1/17 channel 11interface Vethernet4bind interface Ethernet1/18 channel 11interface Vethernet5inherit port-profile VLAN61vsi mac 0050.5684.0004interface Vethernet100shutdownswitchport mode trunkbind interface Ethernet1/17 channel 3interface Vethernet145inherit port-profile statfloatvsi mac 0050.5601.0144interface Vethernet200shutdownswitchport mode trunkbind interface Ethernet1/18 channel 3line consoleline vtyboot kickstart bootflash:/n5000-uk9-kickstart.5.1.3.N1.0.223.gbinboot system bootflash:/n5000-uk9.5.1.3.N1.0.223.gbinsvs connection 2VCprotocol vmware-vimremote ip address 10.29.186.125 port 80 vrf managmentvmware dvs uuid "8e c7 04 50 cb 46 d1 71-d1 98 68 74 a3 26 6d ff" datacenter-name DC1connectlogging monitor 4zone default-zone permit vsan 1zone default-zone permit vsan 200!Command: show running-config!Time: Thu Sep 1 09:36:47 2011version 5.1(3)N1(1)feature fcoeinstall feature-set virtualizationfeature-set virtualizationhostname POD1-5548-2feature telnetcfs eth distributefeature interface-vlanfeature lacpfeature vmfexfeature vpcfeature lldpfeature fexusername adminbackup password 5 ! role network-operatorusername admin password 5 $1$2/VZLE3/$esbYsWazKUXTc/G3xDXd3/ role network-adminno password strength-checkbanner motd #Nexus 5000 Switch#ip domain-lookupclass-map type qos class-fcoeclass-map type queuing class-fcoematch qos-group 1class-map type queuing class-all-floodmatch qos-group 2class-map type queuing class-ip-multicastmatch qos-group 2class-map type network-qos class-fcoematch qos-group 1class-map type network-qos class-all-floodmatch qos-group 2class-map type network-qos class-ip-multicastmatch qos-group 2system qosservice-policy type qos input fcoe-default-in-policyservice-policy type queuing input fcoe-default-in-policyservice-policy type queuing output fcoe-default-out-policyservice-policy type network-qos fcoe-default-nq-policypolicy-map type control-plane copp-system-policycontrol-planeservice-policy input copp-system-policysnmp-server user admin network-admin auth md5 0x659dc61aafac579799b0801bb80a7435priv 0x659dc61aafac579799b0801bb80a7435 localizedkeysnmp-server enable traps entity fruvrf context managementip route 0.0.0.0/0 10.29.184.1vlan 1,61vlan 200fcoe vsan 200vethernet auto-createvpc domain 1role priority 100peer-keepalive destination 10.29.186.195port-profile type vethernet VLAN61switchport access vlan 61state enabledport-profile type ethernet Unused_Or_Quarantine_Uplinkshutdowndescription Port-group created for Nexus1000V internal usage. Do not use.state enabledport-profile type vethernet Unused_Or_Quarantine_Vethshutdowndescription Port-group created for Nexus1000V internal usage. Do not use.state enabledport-profile type vethernet statfloatswitchport access vlan 1state enabledvlan 200fcoe vsan 200vethernet auto-createvpc domain 1role priority 100peer-keepalive destination 10.29.186.195vsan databasevsan 200fcdomain fcid databasevsan 200 wwn 21:00:00:c0:dd:15:21:7d fcid 0x080000 dynamicvsan 200 wwn 21:00:00:c0:dd:12:14:01 fcid 0x080001 dynamicvsan 200 wwn 20:00:58:8d:09:0f:09:6f fcid 0x080002 dynamicinterface port-channel10switchport mode trunkspanning-tree port type networkvpc peer-linkinterface vfc300bind interface Ethernet1/26switchport mode Eswitchport trunk allowed vsan 1switchport trunk allowed vsan add 200no shutdowninterface vfc100bind interface Vethernet100interface vfc400bind interface Ethernet1/5no shutdowninterface vfc200bind interface Vethernet200interface vfc500bind interface Ethernet1/6no shutdownvsan databasevsan 200 interface vfc100vsan 200 interface vfc400vsan 200 interface vfc200vsan 200 interface vfc500interface Ethernet1/1interface Ethernet1/2interface Ethernet1/3interface Ethernet1/4interface Ethernet1/5switchport mode trunkinterface Ethernet1/6switchport mode trunkinterface Ethernet1/7interface Ethernet1/8interface Ethernet1/9interface Ethernet1/10interface Ethernet1/11interface Ethernet1/12interface Ethernet1/13interface Ethernet1/14interface Ethernet1/15interface Ethernet1/16interface Ethernet1/17switchport mode vntaginterface Ethernet1/18switchport mode vntaginterface Ethernet1/19shutdowninterface Ethernet1/20shutdowninterface Ethernet1/21shutdowninterface Ethernet1/22shutdowninterface Ethernet1/23shutdowninterface Ethernet1/24shutdowninterface Ethernet1/25shutdowninterface Ethernet1/26switchport mode trunkinterface Ethernet1/27switchport mode trunkchannel-group 10interface Ethernet1/28switchport mode trunkchannel-group 10interface Ethernet1/29switchport mode trunkchannel-group 10interface Ethernet1/30switchport mode trunkchannel-group 10interface Ethernet1/31interface Ethernet1/32interface Ethernet2/1interface Ethernet2/2interface Ethernet2/3interface Ethernet2/4interface Ethernet2/5interface Ethernet2/6interface Ethernet2/7interface Ethernet2/8interface mgmt0ip address 10.29.186.196/22interface Vethernet1bind interface Ethernet1/17 channel 10interface Vethernet2bind interface Ethernet1/18 channel 10interface Vethernet3bind interface Ethernet1/17 channel 11interface Vethernet4bind interface Ethernet1/18 channel 11interface Vethernet5inherit port-profile VLAN61vsi mac 0050.5684.0004interface Vethernet100shutdownswitchport mode trunkbind interface Ethernet1/17 channel 4interface Vethernet145inherit port-profile statfloatvsi mac 0050.5601.0144interface Vethernet200shutdownswitchport mode trunkbind interface Ethernet1/18 channel 4line consoleline vtyboot kickstart bootflash:/n5000-uk9-kickstart.5.1.3.N1.0.223.gbinboot system bootflash:/n5000-uk9.5.1.3.N1.0.223.gbinsvs connection 2VCprotocol vmware-vimremote ip address 10.29.186.125 port 80 vrf managementzone default-zone permit vsan 1zone default-zone permit vsan 200pod1-5596-2# sh run!Command: show running-config!Time: Thu Sep 1 12:54:08 2011version 5.1(3)N1(1)feature fcoeinstall feature-set virtualizationfeature-set virtualizationswitchname pod1-5596-2feature telnetfeature lacpfeature vmfexfeature lldpfeature fexusername admin password 5 $1$sdMFwb78$3J2cgv7YbedIzxXlrm66H0 role network-adminno password strength-checkbanner motd #Nexus 5000 Switch#ip domain-lookupclass-map type qos class-fcoeclass-map type queuing class-fcoematch qos-group 1class-map type queuing class-all-floodmatch qos-group 2class-map type queuing class-ip-multicastmatch qos-group 2class-map type network-qos class-fcoematch qos-group 1class-map type network-qos class-all-floodmatch qos-group 2class-map type network-qos class-ip-multicastmatch qos-group 2system qosservice-policy type qos input fcoe-default-in-policyservice-policy type network-qos fcoe-default-nq-policyservice-policy type queuing input fcoe-default-in-policyservice-policy type queuing output fcoe-default-out-policyclass-map type control-plane match-any copp-system-class-arpmatch protocol arpclass-map type control-plane match-any copp-system-class-bgpmatch protocol bgpclass-map type control-plane match-any copp-system-class-bridgingmatch protocol bridgingclass-map type control-plane match-any copp-system-class-cdpmatch protocol cdpclass-map type control-plane match-any copp-system-class-defaultmatch protocol defaultclass-map type control-plane match-any copp-system-class-dhcpmatch protocol dhcpclass-map type control-plane match-any copp-system-class-eigrpmatch protocol eigrpclass-map type control-plane match-any copp-system-class-exceptionmatch protocol exceptionclass-map type control-plane match-any copp-system-class-gleanmatch protocol gleanclass-map type control-plane match-any copp-system-class-hsrp-vrrpmatch protocol hsrp_vrrpclass-map type control-plane match-any copp-system-class-icmp-echomatch protocol icmp_echoclass-map type control-plane match-any copp-system-class-igmpmatch protocol igmpclass-map type control-plane match-any copp-system-class-ip-fragmatch protocol ip_fragclass-map type control-plane match-any copp-system-class-isis-dcematch protocol isis_dceclass-map type control-plane match-any copp-system-class-lacpmatch protocol lacpclass-map type control-plane match-any copp-system-class-lldpmatch protocol lldp_dcbxclass-map type control-plane match-any copp-system-class-mgmtmatch protocol mgmtclass-map type control-plane match-any copp-system-class-msdpmatch protocol msdpclass-map type control-plane match-any copp-system-class-multicastmatch protocol multicastclass-map type control-plane match-any copp-system-class-ospfmatch protocol ospfclass-map type control-plane match-any copp-system-class-pimmatch protocol pimclass-map type control-plane match-any copp-system-class-regmatch protocol regclass-map type control-plane match-any copp-system-class-ripmatch protocol ripclass-map type control-plane match-any copp-system-class-same-ifmatch protocol same_ifclass-map type control-plane match-any copp-system-class-ttlmatch protocol ttlcontrol-planeservice-policy input copp-system-policy-defaultslot 1port 39-48 type fcsnmp-server user admin network-admin auth md5 0x338f7b1376b2f1548acf1f8295c0e734priv 0x338f7b1376b2f1548acf1f8295c0e734 localizedkeysnmp-server enable traps entity frusnmp-server community labpublic group network-operatorvrf context managementip route 0.0.0.0/0 10.29.184.1vlan 1vlan 200fcoe vsan 200vsan databasevsan 200fcdomain fcid databasevsan 1 wwn 26:02:00:01:55:35:0c:d3 fcid 0xc90000 dynamicvsan 1 wwn 21:00:00:c0:dd:15:21:7f fcid 0xc90001 dynamicvsan 1 wwn 21:00:00:c0:dd:12:14:01 fcid 0xc90002 dynamicvsan 1 wwn 21:00:00:c0:dd:15:21:7d fcid 0xc90003 dynamicvsan 200 wwn 26:02:00:01:55:35:0c:d3 fcid 0x340000 dynamicinterface vfc300bind interface Ethernet1/32switchport mode Eswitchport trunk allowed vsan 1switchport trunk allowed vsan add 200no shutdownvsan databasevsan 200 interface vfc300vsan 200 interface fc1/48interface fc1/39interface fc1/40no shutdowninterface fc1/41interface fc1/42interface fc1/43interface fc1/44interface fc1/45interface fc1/46interface fc1/47interface fc1/48no shutdowninterface Ethernet1/1switchport trunk allowed vlan nonespanning-tree port type edge trunkinterface Ethernet1/2switchport mode trunkswitchport trunk allowed vlan 1,1000interface Ethernet1/3interface Ethernet1/4interface Ethernet1/5interface Ethernet1/6interface Ethernet1/7interface Ethernet1/8interface Ethernet1/9interface Ethernet1/10interface fc1/41interface fc1/42interface fc1/43interface fc1/44interface fc1/45interface fc1/46interface fc1/47interface fc1/48no shutdowninterface Ethernet1/1switchport trunk allowed vlan nonespanning-tree port type edge trunkinterface Ethernet1/2switchport mode trunkswitchport trunk allowed vlan 1,1000interface Ethernet1/3interface Ethernet1/4interface Ethernet1/5interface Ethernet1/6interface Ethernet1/7interface Ethernet1/8interface Ethernet1/9interface Ethernet1/10interface Ethernet1/11interface Ethernet1/12interface Ethernet1/13interface Ethernet1/14interface Ethernet1/15interface Ethernet1/16interface Ethernet1/17interface Ethernet1/18interface Ethernet1/19interface Ethernet1/20interface Ethernet1/21interface Ethernet1/22interface Ethernet1/23interface Ethernet1/24interface Ethernet1/25interface Ethernet1/26shutdowninterface Ethernet1/27interface Ethernet1/28interface Ethernet1/29interface Ethernet1/30interface Ethernet1/31interface Ethernet1/32switchport mode trunkinterface Ethernet1/33interface Ethernet1/34interface Ethernet1/35interface Ethernet1/36interface Ethernet1/37interface Ethernet1/38interface mgmt0ip address 10.29.186.193/22line consoleline vtyboot kickstart bootflash:/n5000-uk9-kickstart.5.1.3.N1.0.212.binboot system bootflash:/n5000-uk9.5.1.3.N1.0.212.bininterface fc1/39interface fc1/40interface fc1/41interface fc1/42interface fc1/43interface fc1/44interface fc1/45interface fc1/46interface fc1/47interface fc1/48switchport mode Flogging monitor 6zone default-zone permit vsan 1zone default-zone permit vsan 200!Command: show running-config!Time: Thu Sep 1 09:42:50 2011version 5.1(3)N1(1)feature fcoeinstall feature-set virtualizationfeature-set virtualizationhostname pod1-5596-1feature telnetfeature vmfexfeature lldpfeature fexusername admin password 5 $1$aFZpnyOJ$kKzqLw8Ftu2I.T8mS.w1O0 role network-adminno password strength-checkbanner motd #Nexus 5000 Switch#ip domain-lookupclass-map type qos class-fcoeclass-map type queuing class-fcoematch qos-group 1class-map type queuing class-all-floodmatch qos-group 2class-map type queuing class-ip-multicastmatch qos-group 2class-map type network-qos class-fcoematch qos-group 1class-map type network-qos class-all-floodmatch qos-group 2class-map type network-qos class-ip-multicastmatch qos-group 2system qosservice-policy type qos input fcoe-default-in-policyservice-policy type network-qos fcoe-default-nq-policyservice-policy type queuing input fcoe-default-in-policyservice-policy type queuing output fcoe-default-out-policyclass-map type control-plane match-any copp-system-class-arpmatch protocol arpclass-map type control-plane match-any copp-system-class-bgpmatch protocol bgpclass-map type control-plane match-any copp-system-class-bridgingmatch protocol bridgingpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-icmp-echopolice cir 640 kbps bc 3600000 bytesclass copp-system-class-ospfpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-regpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-rippolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-unicastpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-multicastpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-ip-fragpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-same-ifpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-ttlpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-defaultpolice cir 2048 kbps bc 6400000 bytespolicy-map type control-plane copp-system-policy-scaled-l3class copp-system-class-igmppolice cir 1200 kbps bc 65535 bytesclass copp-system-class-pimpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-bridgingpolice cir 20000 kbps bc 4800000 bytesclass copp-system-class-arppolice cir 4000 kbps bc 3600000 bytesclass copp-system-class-dhcppolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-mgmtpolice cir 12000 kbps bc 4800000 bytesclass copp-system-class-lacppolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-lldppolice cir 2048 kbps bc 4800000 bytesclass copp-system-class-udldpolice cir 2048 kbps bc 4800000 bytesclass copp-system-class-msdppolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-vicpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-cdppolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-bgppolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-eigrppolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-exceptionpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-gleanpolice cir 4000 kbps bc 4800000 bytesclass copp-system-class-hsrp-vrrppolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-icmp-echopolice cir 4000 kbps bc 3600000 bytesclass copp-system-class-ospfpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-regpolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-rippolice cir 1024 kbps bc 4800000 bytesclass copp-system-class-unicastpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-multicastpolice cir 4000 kbps bc 3200000 bytesclass copp-system-class-ip-fragpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-same-ifpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-ttlpolice cir 1024 kbps bc 3200000 bytesclass copp-system-class-defaultpolice cir 2048 kbps bc 6400000 bytescontrol-planeservice-policy input copp-system-policy-defaultslot 1port 39-48 type fcsnmp-server user admin network-admin auth md5 0x512632220ce767d7bf7aed2f7af4b8e9priv 0x512632220ce767d7bf7aed2f7af4b8e9 localizedkeysnmp-server enable traps entity frusnmp-server community labpublic group network-operatorvrf context managementip route 0.0.0.0/0 10.29.184.1vlan 1vlan 200fcoe vsan 200port-profile type ethernet Unused_Or_Quarantine_Uplinkshutdowndescription Port-group created for Nexus1000V internal usage. Do not use.state enabledport-profile type vethernet Unused_Or_Quarantine_Vethshutdowndescription Port-group created for Nexus1000V internal usage. Do not use.state enabledvsan databasevsan 200fcdomain fcid databasevsan 1 wwn 26:01:00:01:55:35:0c:d3 fcid 0x9a0000 dynamicvsan 1 wwn 21:00:00:c0:dd:14:57:4d fcid 0x9a0001 dynamicvsan 1 wwn 21:00:00:c0:dd:12:14:03 fcid 0x9a0002 dynamicvsan 1 wwn 21:00:00:c0:dd:15:21:7f fcid 0x9a0003 dynamicvsan 200 wwn 26:01:00:01:55:35:0c:d3 fcid 0xe50000 dynamicinterface vfc300bind interface Ethernet1/32switchport mode Eswitchport trunk allowed vsan 1switchport trunk allowed vsan add 200no shutdownvsan databasevsan 200 interface vfc300vsan 200 interface fc1/48interface fc1/39interface fc1/40no shutdowninterface fc1/41interface fc1/42interface fc1/43interface fc1/44interface fc1/45interface fc1/46interface fc1/47interface fc1/48no shutdowninterface Ethernet1/1switchport mode trunkswitchport trunk allowed vlan 1,1000spanning-tree port type edge trunkinterface Ethernet1/2interface Ethernet1/3interface Ethernet1/4interface Ethernet1/5interface Ethernet1/6interface Ethernet1/7interface Ethernet1/8interface Ethernet1/9interface Ethernet1/10interface Ethernet1/11interface Ethernet1/12interface Ethernet1/13interface Ethernet1/14interface Ethernet1/15interface Ethernet1/16interface Ethernet1/17interface Ethernet1/18interface Ethernet1/19interface Ethernet1/20interface Ethernet1/21interface Ethernet1/22interface Ethernet1/23interface Ethernet1/24interface Ethernet1/25interface Ethernet1/26interface Ethernet1/27interface Ethernet1/28interface Ethernet1/29interface Ethernet1/30interface Ethernet1/31interface Ethernet1/32switchport mode trunkinterface Ethernet1/33interface Ethernet1/34interface Ethernet1/35interface Ethernet1/36interface Ethernet1/37interface Ethernet1/38interface mgmt0ip address 10.29.186.194/22line consoleline vtyboot kickstart bootflash:/n5000-uk9-kickstart.5.1.3.N1.0.212.binboot system bootflash:/n5000-uk9.5.1.3.N1.0.212.bininterface fc1/39interface fc1/40interface fc1/41interface fc1/42interface fc1/43interface fc1/44interface fc1/45interface fc1/46interface fc1/47interface fc1/48zone default-zone permit vsan 1zone default-zone permit vsan 200
