The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
VDP on a Cisco DFA network architecture runs the Edge Control Protocol (ECP) to forward packets upstream to the DFA leaf switch. ECP is a Layer 2 protocol that uses the nearest bridge MAC address 01:80:C2:00:00:01 as the destination MAC address to forward data traffic. In a blade-chassis deployment, blade switches such as the Cisco UCS Fabric Interconnect (UCS FI) that interface with the Cisco Nexus 1000V VEMs and the leaf switches terminate packets with the specified MAC address, because they are the same packets used for the bridge protocol data unit (BPDU) frames. Consequently, the VDP exchange between the Cisco Nexus 1000V VEMs and upstream leafs fail. To enable the VDP packets to get transported upstream to the DFA leaf, the destination MAC address for the ECP packets must be allowed to pass through the blade switches to forward the packets upstream to the Cisco DFA leaf.
To enable VDP communication and to avoid changes in the functioning of the blade switches such as the Cisco UCS fabric interconnect and their compatibility with other network devices, you can configure the destination MAC address that originates from the VDP station. See Configuring a DMAC from the VDP Station.
For more information about blade-chassis deployment, see http://www.cisco.com/en/US/products/ps10279/index.html
In this release, VDP on the Cisco Nexus 1000Vdoes not support an un-clustered topology where an upstream Leaf or bridge nodes are not configured as a VPC/VPC+pair, independent of the devices such as the UCS Fabric InterConnect (UCS FI) interfacing between the Cisco Nexus 1000V VEM and the Cisco DFA Leaf.
Configuring VDP for the Cisco Nexus 1000V has the following prerequisites:
You have installed and configured the Cisco Nexus 1000V for VMware vSphere software using the Cisco Nexus 1000V Installation and Upgrade Guide.
Ensure that the Virtual Supervisor Module (VSM) has an active SVS connection.
Ensure that the Virtual Supervisor Module (VSM) and Virtual Ethernet Module (VEM) connectivity is functioning.
You have added hosts to the Cisco Nexus 1000V.
You have disabled the segmentation feature.
Implementing VDP on the Cisco Nexus 1000V has the following guidelines and limitations:
The Cisco Nexus 1000V supports the Cisco DFA capable VDP based on the IEEE Standard 802.1 Qbg, Draft 2.2, and does not support the Link Layer Discovery Protocol (LLDP). Therefore, the EVB TLVs will not be originated or processed by the Cisco Nexus 1000V.
The VDP implementation in the current release supports a matching LLDP-less implementation on the bridge side, which is delivered as part of the Cisco DFA solution. For more information on the Cisco DFA, see Cisco DFA Solutions Guide.
Timer-related parameters are individually configurable in the station and in the leaf.
Connectivity to multiple unclustered bridges is not supported in this release. For more information about unsupported topologies, see Unsupported Topology
IPv6 addresses in filter format are not supported in this release.
VDP for access VLAN port profiles is supported in this release. VDP for trunk VLAN port profiles is not supported.
The dynamic VLANs allocated by VDP are local to the VEM, and they should not be configured on the Cisco Nexus 1000V VSM.
VDP is supported on VMware ESX releases 5.0. 5.1, and 5.5 in the current release.
Parameter |
Default |
---|---|
Feature Segmentation |
Disabled |
Configuring VDP
Edge Virtual Bridging (EVB) is an IEEE 802.1Qbg standard that enables coordinated configuration and management of bridge services for virtual stations in a network. VDP is a part of the EVB standard that is used to detect the presence of end hosts and exchange VDP capability with an adjacent VDP bridge. For more information about the EVB Standard, see Standards.
To configure VDP on the Cisco Nexus 1000V, you must enable the EVB feature.
switch # show feature Feature Name Instance State -------------------- -------- -------- cts 1 disabled dhcp-snooping 1 disabled evb 1 enabled http-server 1 enabled lacp 1 disabled netflow 1 disabled network-segmentation 1 disabled port-profile-roles 1 disabled private-vlan 1 disabled segmentation 1 enabled sshServer 1 enabled tacacs 1 disabled telnetServer 1 enabled vff 1 enabled vtracker 1 disabled vxlan-gateway 1 disabled
You can the modify the Cisco Nexus 1000V port profile to configure the vEthernet interfaces or a port channel as VDP-capable links.
This example shows how to display the port-profile configuration of a VDP capable uplink.
switch # show running-config port-prof vdp-capable uplink port-profile type ethernet uplink-vdp-capable uplink vmware port-group switchport mode trunk switchport trunk allowed vlan 2-3967,4048-4093 switchport trunk dynamic no shutdown state enabled
At a global configuration level, you can set the transport mode to a native (VDP) state to employ the network-based overlays.
Command or Action | Purpose | |
---|---|---|
Step 1 | switch # configure terminal | Enters global configuration mode. |
Step 2 | switch (config)# feature segmentation | Enables the segmentation feature. |
Step 3 | switch (config)# segment transport-mode native | Sets the default transport mode to VXLAN. Specify native to set it to VDP global configuration mode. |
Step 4 | switch (config)# show running-config bridge-domain | (Optional) Displays the segmentation configuration for all bridge domains. |
Step 5 | switch(config)# copy running-config startup-config | (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to display the segmentation configuration for all bridge domains.
switch # show running-config bridge-domain bridge-domain seg22222 segment id 22222 group 239.1.1.1 segment transport-mode native fabric forwarding mode proxy-gateway
The transport mode that you configure under a bridge domain always overrides the segment transport mode that you can set globally. Use this procedure to configure a VDP segment bridge domain.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | switch # configure terminal | Enters global configuration mode. | ||
Step 2 | switch (config)# bridge-domain name-string | Creates a bridge domain and associates an identifying name to it. | ||
Step 3 | switch (config-bd)# segment id number | Specifies the
bridge domain segment ID. Only one bridge domain can use a particular segment
ID value.
Valid values are from 4096 to 16000000. (1 to 4095 are reserved for VLANs.) | ||
Step 4 | switch (config-bd)# group name | Specifies the
multicast group name for broadcasts and floods.
Reserved multicast addresses are not allowed.
| ||
Step 5 | switch (config-bd)# segment transport-mode {native | vxlan} | Specifies the default transport mode. The default transport mode is set to VXLAN. If you specify native, sets it to VDP global configuration mode. | ||
Step 6 | switch (config-bd)# show running-config bridge-domain | (Optional) Displays the segmentation configuration. | ||
Step 7 | switch(config)# copy running-config startup-config | (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to display the segmentation configuration.
switch # show running-config bridge-domain version 4.2(1)SV2(2.2) feature segmentation no segment mode unicast-only bridge-domain seg22222 segment id 22222 group 239.1.1.1 segment transport-mode native fabric forwarding mode proxy-gateway
Note | You must ensure that the same MAC configuration is present at the upstream Cisco DFA leaf. |
Command or Action | Purpose | |
---|---|---|
Step 1 | switch # configure terminal | Enters global configuration mode. |
Step 2 | switch(config)# [no] evb mac |
Adds the destination MAC address information for the ECP packets originating from the VDP station to blade switches such as the Cisco UCS fabric interconnect and other similar network devices. |
Step 3 | switch # show evb | Displays the configured MAC addresses. |
Step 4 | switch(config)# copy running-config startup-config | (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
switch # show evb Edge Virtual Bridging Role : VDP Station VDP Mac Address : 0180.0000.0000 VDP Resource Wait Delay : 22(66 secs) VDP Reinit Keep Alive : 21(20 secs)
You can configure VDP on one or more VLANs.
You must enable Fabric Forwarding on your switch. For information, see the Cisco Nexus 1000V DFA Configuration Guide.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | switch# configure terminal |
Enters global configuration mode. | ||
Step 2 | switch(config)# system fabric vdp-vlan range range |
| ||
Step 3 | Verify that VDP is configured on the VLANs. |
show system fabric vdp-vlan | ||
Step 4 | switch(config)# copy running-config startup-config | (Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to configure VDP on the specified VLANs.
switch# configure terminal switch(config)# feature fabric forwarding switch(config-port-prof)# port-profile type vethernet vlan222 switch(config-port-prof)# switchport mode access switch(config-port-prof)# switchport access vlan 222 switch(config-port-prof)# no shutdown switch(config-port-prof)# state enabled switch(config-port-prof)# vmware port-group switch(config-port-prof)# exit switch(config)# system fabric vdp-vlan range 220-230, 330-340 switch(config)# copy running-config startup-config switch(config)# exit switch# show system fabric vdp-vlan VDP Vlans Range: 220-230 330-340 switch#
Command or Action | Purpose | |
---|---|---|
Step 1 | switch configure terminal | Enters global configuration mode. |
Step 2 | switch (config)# [no] ecp max-retries <1-7> | (Optional) Configures the number of times ECP retries to send an upper layer protocol message. This parameter corresponds to the R value in the EVB TLV. If you specify a value of zero, the standard default value is used. |
Step 3 | switch (config)# [no] ecp retransmission-timer-exponent <10-20> | (Optional) Configures the exponential value of the interval for which ECP waits before trying to retransmit the packet. This parameter corresponds to the RTE value in the EVB TLV. |
Step 4 | switch (config)# [no] evb resource-wait-delay <20-31> | Configures the resource wait delay used by VDP to calculate the time it waits before concluding that a request has timed out. VDP will retry its request after the timeout. |
Step 5 | switch (config)# [no] evb reinit-keep-alive <20-31> | Configures the interval at which VDP refreshes the VSI state in the bridge by sending a VDP associate refresh. |
Step 6 | switch(config) # show evb | (Optional) Displays the configured VDP/ECP information. |
Step 7 | switch(config)# copy running-config startup-config | (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to display details of the configured EVB TLV parameters on the Cisco Nexus 1000V:
switch # show evb Edge Virtual Bridging Role : VDP Station VDP Mac Address : 0000.1111.2222 VDP Resource Wait Delay : 20(17 secs) VDP Reinit Keep Alive : 20(10 secs)
To display the VDP configuration information, use the following commands:
Command |
Purpose |
---|---|
show evb |
Displays the EVB segmentation information. See Example Example 1 - show evb |
show run evb |
Displays the running configuration for the EVB segmentation. See Example Example 2 - show running-config evb |
show evb vsi interface veth |
Displays the VDP VSI information from the Cisco Nexus 1000V VEMs. See Example Example 3 - show evb vsi interface |
show evb module |
Displays EVB information for a module. See Example Example 4 - show evb module |
show ecp |
Displays the ECP information. See Example Example 5 - show ecp |
show ecp [module modid] |
Displays the state information and statistics for ECP. See Example Example 6 - show ecp module |
switch # show evb Edge Virtual Bridging Role : VDP Station VDP Mac Address : 0180.0000.0000 VDP Resource Wait Delay : 22(66 secs) VDP Reinit Keep Alive : 21(20 secs)
This example shows how to display the EVB segmentation configuration:
switch #: show running-config evb evb resource-wait-delay 24 evb reinit-keep-alive 25 ecp retransmission-timer-exponent 15 ecp max-retries 6
switch# show evb vsi interface vethernet 15 LTL : 50 [module: 4] Segment : 33333 MAC : 0050.5693.7D25 IP : 222.222.221.100 VSI State : 3 State Machine State : 7 Rwd Expiry Count : 37 Last CMD Time : 24 Last RSP Time : 21
switch # show evb module 4 Edge Virtual Bridging Role : VDP Station VDP Mac Address : 0180.C200.0000 VDP Resource Wait Delay : 20(22 secs) VDP Reinit Keep Alive : 25(335 secs) n1kv-vsm#
switch # show ecp ECP Max ReTries : 3 ECP Retransmition Timer Exp : 14(163840 micro seconds)
switch # show ecp mod 4 ECP Max ReTries : 3 ECP Retransmition Timer Exp : 14(163840 micro seconds) TX Sequence No : 127 Retry Count : 0 TX Count : 0 TX Count Errors : 0 In TX Queue : 0 RX Count : 0 RX Sequence : 42634
The following table lists the standards supported in this release:
Standards |
Title |
---|---|
IEEE 802.1Qbg |
Edge Virtual Bridging (EVB) |
Feature |
Release |
Feature information |
---|---|---|
VDP on access VLAN port profiles |
5.2(1)SV3(1.2) |
This enhancement was introduced. |
VSI Discovery and Configuration protocol |
4.2(1)SV2(2.2) |
This feature was introduced. |