Cisco Nexus 1000V VDP Configuration Guide, Release 4.2(1)SV2(2.2)
Configuring VDP
Downloads: This chapterpdf (PDF - 1.36MB) The complete bookPDF (PDF - 2.24MB) | The complete bookePub (ePub - 171.0KB) | Feedback

Configuring VDP

Configuring VDP

This chapter contains the following sections:

Information about VDP for Blade-Chassis Deployment

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

Unsupported Topology

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.


Note


  1. VDP is supported only on the Cisco Nexus 6000 Series switches in release 4.2(1)SV2(2.2).
  2. VDP supports connectivity to multiple bridges that are clustered to one bridge through a virtual port channel (vPC).

Prerequisites

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.

Guidelines and Limitations

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 is supported for only segmentation based port-profiles. VDP for VLAN based port-profiles is not supported in this release.
  • 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.

Default Settings

The following table lists the default settings for VDP parameters:

Parameter

Default

Feature Segmentation

Disabled

Enabling Edge Virtual Bridging

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.

Before You Begin
  • 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) and Virtual Ethernet Module (VEM) connectivity is functioning.
  • Log in to the CLI in EXEC mode.
Procedure
     Command or ActionPurpose
    Step 1switch # configure terminal   Enters global configuration mode.  
    Step 2switch(config)# feature evb  

    Enables EVB.

     
    Step 3switch(config)# show feature   (Optional)

    Displays the enabled status for the Cisco Nexus 1000V for features such as EVB.

     
    Step 4switch(config)# copy running-config startup-config   (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.  

    show feature

    This example shows how to display the features after evb is enabled.
    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

    Modifying a Port Profile

    You can the modify the Cisco Nexus 1000V port profile to configure the vEthernet interfaces or a port channel as VDP-capable links.

    Before You Begin
    • Log in to the CLI in EXEC mode.
    • Configure the interface must be configured as a trunk mode interface.
    • Enable the EVB feature.
    Procedure
       Command or ActionPurpose
      Step 1switch# configure terminal  

      Enters global configuration mode.

       
      Step 2switch(config)# port-profile type ether vdp-capable-uplink  

      Specify the port profile configuration mode for the VDP-capable uplink. If the port profile does not already exist, it is created using the following parameter:

      • name— Port profile name that can be up to 80 characters and must be unique for each port profile on the Cisco Nexus 1000V.
        Note   

        If a port profile is configured as an Ethernet type, it cannot be used to configure VMware virtual ports.

       
      Step 3switch(config-port-prof)# switchport mode trunk  

      Designates that the interfaces are to be used as a trunking ports.

      A trunk port transmits untagged packets for the native VLAN and transmits encapsulated, tagged packets for all other VLANs.

       
      Step 4switch(config-port-prof)# switchport trunk dynamic  

      Designates that the interfaces are to be used as dynamic trunking ports.

       
      Step 5switch(config-port-prof)# channel-group auto mode active   (Optional) Configures the port profile for a port channel.
      Note   

      If more than one physical uplink port or port channels inherit the port profile information from the original configuration, only one of them is chosen as the designated uplink port over which the VDP communication is enabled. The selected port functions in active mode and the other ports move to the standby mode.

       
      Step 6switch (config)# show running-config port-prof vdp-capable uplink  (Optional) Displays a list of interfaces that inherited a port profile.  
      Step 7switch (config)# show running interface port-channel   (Optional) Displays the port channel that has inherited a port profile. 
      Step 8switch(config)# copy running-config startup-config   (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.  

      show running-config port-prof

      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
      
      

      Configuring Global Mode

      At a global configuration level, you can set the transport mode to a native (VDP) state to employ the network-based overlays.

      Before You Begin

      • Log in to the CLI in EXEC mode.
      • You have previously enabled the EVB feature.
      Procedure
         Command or ActionPurpose
        Step 1switch # configure terminal   Enters global configuration mode.  
        Step 2switch (config)# feature segmentation   Enables the segmentation feature.  
        Step 3switch (config)# segment transport-mode native   Sets the default transport mode to VXLAN. Specify native to set it to VDP global configuration mode.  
        Step 4switch (config)# show running-config bridge-domain   (Optional) Displays the segmentation configuration for all bridge domains.  
        Step 5switch(config)# copy running-config startup-config   (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.  

        show run bridge-domain

        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
        
        

        Configuring a VDP Segment Bridge Domain

        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.

        Before You Begin
        • Log in to the CLI in EXEC mode.
        Procedure
           Command or ActionPurpose
          Step 1switch # configure terminal   Enters global configuration mode.  
          Step 2switch (config)# bridge-domain name-string   Creates a bridge domain and associates an identifying name to it.  
          Step 3switch (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 4switch (config-bd)# group name   Specifies the multicast group name for broadcasts and floods.

          Reserved multicast addresses are not allowed.

          Note   

          If you enable native encapsulation, the group name is not used in data packet forwarding or in the control plane associated with the VDP segments. The group name is used only for VXLAN segments.

           
          Step 5switch (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 6switch (config-bd)# show running-config bridge-domain   (Optional) Displays the segmentation configuration.  
          Step 7switch(config)# copy running-config startup-config   (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.  

          show running -config bridge-domain

          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
           
          

          Configuring a DMAC from the VDP Station

          To avoid any changes to the blade switches such as the Cisco UCS fabric interconnect and other network devices, you must manually configure the destination MAC address for ECP packets that originates from the VDP station, to enable forwarding data traffic upstream to the Cisco DFA leaf.

          Note


          You must ensure that the same MAC configuration is present at the upstream Cisco DFA leaf.
          Before You Begin
          • 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) and Virtual Ethernet Module (VEM) connectivity is functioning.
          • Log in to the CLI in EXEC mode.
          Procedure
             Command or ActionPurpose
            Step 1switch # configure terminal   Enters global configuration mode.  
            Step 2switch(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 3switch # show evb  Displays the configured MAC addresses.  
            Step 4switch(config)# copy running-config startup-config   (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.  

            show evb

            This example shows how to display the evb information:
             
            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) 

            Specifying EVB TLV Parameters

            Because the Cisco Nexus 1000V does not support the Link Layer Discovery Protocol (LLDP), VDP uses the EVB TLV communicated through the LLDP payloads to negotiate the VDP/ECP parameters. Use the following commands to configure the EVB TLV parameters:
            Before You Begin
            • Log in to the CLI in the EXEC mode.
            • Configure the EVB feature to enable VDP on the Cisco Nexus 1000V .
            Procedure
               Command or ActionPurpose
              Step 1switch configure terminal   Enters global configuration mode.  
              Step 2switch (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 3switch (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 4switch (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 5switch (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 6switch(config) # show evb   (Optional) Displays the configured VDP/ECP information.  
              Step 7switch(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)
              
              

              Verifying VDP Configuration

              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

              Example 1 - show evb

              This example shows how to display the EVB segmentation information.
              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)  
               

              Example 2 - show running-config evb

              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

              Example 3 - show evb vsi interface

              This example shows how to display the EVB vsi information from the Cisco Nexus 1000V VEMs:
              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
              

              Example 4 - show evb module

              This example shows how to display EVB information for a module.
              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# 
              

              Example 5 - show ecp

              This example shows how to display the configuration information for ECP.
              switch # show ecp 
              ECP Max ReTries : 3
              ECP Retransmition Timer Exp : 14(163840 micro seconds)

              Example 6 - show ecp module

              This example shows how to display the statistics and state information for a module.
              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
              

              Standards

              The following table lists the standards supported in this release:

              Standards

              Title

              IEEE 802.1Qbg

              Edge Virtual Bridging (EVB)

              http:/​/​www.ieee802.org/​1/​pages/​802.1bg.html

              Feature History for Configuring VDP

              Feature

              Release

              Feature information

              VSI Discovery and Configuration protocol

              4.2(1)SV2(2.2)

              This feature was introduced.