Deploying VXLAN on the Nexus 1000V and

CSR1000V VXLAN
LABDCN-3016
Alejandro Marino – Customer Support Engineer, Services

1|Page
Table of Contents
INTRODUCTION ................................................................................................................................................ 3
PREREQUISITES ................................................................................................................................................ 4
Requirements ......................................................................................................................... 4
Limitations ............................................................................................................................. 4
Components Used .................................................................................................................. 4
Definitions.............................................................................................................................. 4
DISCLAIMER ...................................................................................................................................................... 4
LAB ACCESS ....................................................................................................................................................... 5
Access Details and Login Credentials ................................................................................... 5
LAB TOPOLOGY AND ADDRESSING ........................................................................................................... 8
Pod and VLAN Assignment .................................................................................................. 8
IP Addressing ......................................................................................................................... 8
Network Diagram................................................................................................................... 8
Logging into vCenter and network devices ........................................................................... 8
vCenter ............................................................................................................................... 8
Network Devices ................................................................................................................ 9
TASK 1: INFRASTRUCTURE ROUTER ....................................................................................................... 10
TASK 2: SITE 1 INFRASTRUCTURE VIRTUAL SWITCH (NEXUS 1000V) .......................................... 11
Task 2.1: Site 1 Nexus 1000v Port-Profile Configuration ................................................... 11
TASK 3: SITE 1 CLOUD SERVICE ROUTER .............................................................................................. 13
Task 3.1: CSR Networking Configuration........................................................................... 14
Task 3.2: CSR Networking Configuration........................................................................... 17
TASK 4: SITE 2 NEXUS 1000V CONFIGURATION .................................................................................... 18
Task 4.1: VxLAN Configuration ......................................................................................... 18
TASK 5: VERIFICATION ................................................................................................................................ 24
Verify the backbone router IP PIM configuration: .......................................................... 25
Verify the backbone router sees the IGMP Group messages from the Site 2 Nexus
1000V hypervisor physical interfaces:............................................................................. 26
Verify the CSR1000 has a PIM adjacency to the backbone router and contains a route to
the 239.1.119.150 group .................................................................................................. 26
Verify the NVE is up and a peering to the Site 2 hypervisor host VMK (11.1.119.74) has
been formed: .................................................................................................................... 27
Verify the CSR1000 forwarding table: ............................................................................ 27
Verify the Site2 hypervisor host has been programmed correctly and the Mcast statistics
are incrementing............................................................................................................... 28

2|Page
Introduction
This document describes configuring VxLAN (Virtual eXtensible Local Area Network) between the
Cisco Nexus 1000V Virtual Switch and Cloud Services Router 1000V in multicast VTEP distribution
mode. VxLAN creates a Layer 2 overlay network allowing for network isolation though a
standardized protocol.

This feature enables the Cisco CSR 1000V to act as a Layer 2 VxLAN gateway to provide support to
bridge traffic across VxLAN segments in a hypervisor and on VLANs on physical servers. The
CSR1000V supplements the Cisco Nexus 1000V VxLAN Gateway feature with the ability to add Layer
3 and VPN services.

A VxLAN Layer 2 gateway performs the following functions:

 Provides support to bridge 802.1q traffic on a network to a VM residing in a VxLAN segment
behind a virtual switch.
 Implements a Virtual Tunnel Endpoint(VTEP) function acting as a VxLAN
encapsulation/decapsulation point.
 The VTEP removes the VxLAN header (VNI), identifies the bridge domain, and then bridges
the inner L2 packet to the 802.1q network. VTEPs also function in the reverse direction by
mapping an 802.1q vlan into a bridge domain followed by encapsulating the entire L2 frame
in a VxLAN header.

3|Page
Prerequisites

Requirements
 Cisco Nexus 1000V Virtual Switch Version 5.2(1)SV3(1.6) or later
 Cisco Cloud Service Router 1000V 3.17.00.S / 15.6(1)S
 A multicast enabled & aware network

Limitations
 The CSR 1000V only supports multicast VTEP learning. Unicast & BGP VTEP distributions are
not supported.
 Nexus 1000V versions prior to SV3(1.1) use UDP/8472 for VxLAN VTEP distribution. This is a
static setting which cannot be modified. If using one of these earlier versions, modify the
CSR1000V VxLAN port with the command "vxlan udp port 8472". Starting in version
SV3(1.1), the IANA assigned port of 4789 is the default.

Components Used
 All virtual components (CSR, N1000V, Virtual Machines) are hosted behind an infrastructure
Nexus 1000V Virtual Switch.
 A Nexus 5500 Series switch with L3 module connects all physical servers.

Definitions
 VTEP - VXLAN uses VXLAN tunnel endpoint (VTEP) devices to map tenants' end devices to
VXLAN segments and to perform VXLAN encapsulation and de-encapsulation.
 NVE - The Network Virtualization Endpoint to maps a VNI (VxLAN ID) to a multicast group
and a VTEP.
 VNI - VXLAN uses a 24-bit segment ID known as the VXLAN network identifier (VNID).

Disclaimer
This training document is to familiarize with the deployment of VXLAN on the Nexus 1000V and
CSR1000V VXLAN. Although the lab design and configuration examples could be used as a reference,
it’s not a real design, thus not all recommended features are used, or enabled optimally. For the
design related questions please contact your representative at Cisco, or a Cisco partner.

4|Page
Lab Access

Access Details and Login Credentials

1. Open a web browser and go to the link below
a. https://labops-out.cisco.com/labops/ilt
2. Login using your email and the class name provided by the instructor. For Cisco Live US 2017
it is: amarino2_v24088

a.
3. After entering you email and class name, fill out the registration information.

a.
4. Pick a Pod (Note that the instructor will let you know which pod to pick)

5|Page
 a.
5. If the pod is not available, wait to become available. Once the pod is available you should be
able to access it.

a.
6. Under the topology diagram, click on the Virtual Center box below to get connect to remote
session.

6|Page
 a.
b. The username and password for the remote session is Administrator/ Cisco123

If you have any questions or you are unable to log into the remote session, please reach out to the
instructors for assistance.

7|Page
Lab Topology and Addressing

Pod and VLAN Assignment

Pod and VLAN Assignment
Pod 1 2050,2060
Pod 2 2051,2061
Pod 3 2052,2062
Pod 4 2053,2063
Pod 5 2054,2064

IP Addressing
IP Addressing
Device IP Address Username password
ESXi vmk0 SITE_1 10.1.119.73 root Cisco123
ESXi vmk0 SITE_2 10.1.119.74 root Cisco123
Nexus 1000v Site 1 10.1.119.75 admin Cisco123
Nexus 1000v Site 2 10.1.119.76 admin Cisco123
CSR1000V Site 1 10.1.119.77 admin Cisco123
PC1 11.1.119.100 Administrator Cisco123
PC2 11.1.119.101 Administrator Cisco123

Network Diagram

Logging into vCenter and network devices

vCenter
To Access vCenter double click on the VMware vSphere Client icon ,and then login using Windows
session credentials

8|Page
Network Devices
For access to the Nexus 1000v on Site 1 and Site 2, Nexus 5500 and both ESXi host use the already
saved session in PuTTY.

9|Page
Task 1: Infrastructure Router
The infrastructure router/switch provides physical networking to all hypervisor hosts. Additional
multicast configuration may be required for multi-router topologies.

Refer to “Pod and VLAN Assignment” table for VLAN assignment to the respective pod.

a) Since the CSR1000V is a Layer3 device it will learn routes via PIM. Configure a PIM RP on the
routing device(s) for the backbone network.
b) The Nexus 5500 acts as both a L2 and L3 device therefore an IGMP querier for Site 2 Nexus
1000V must be configured.
c) In the next section a loopback for CSR<-->N1K communication will be provisioned. The
loopback address must be reachable by all VxLAN nodes and therefore advertised into the
routing protocol. Below we configured OSPF between the infrastructure router on
VLAN205X and the CSR1000V GigabitEthernet1 interface.
d) Interface Eth 1/1 will be configured as trunk and allow VLAN 205X, the link speed needs to
be 1G.
a. (where X = Pod# -1 -- see “Pod and VLAN Assignment” table)

From the putty session SSH into the N5K using username and password admin/Cisco123, and
configure it with the configuration below.

Commands:
# Cisco Nexus 5500 - Infrastructure

N5K# configure terminal

N5K(config)#feature ospf
N5K(config)#feature pim
N5K(config)#feature interface-vlan
!
N5K(config)#router ospf 1
!
N5K(config)#vlan 205X <-----(if pod assignment is 2 then X = 2 – 1)
!
N5K(config)#vlan configuration 205X
N5K(config -vlan-config)# ip igmp snooping querier 11.1.119.254
N5K(config -vlan-config)# ip igmp snooping version 3
!
N5K(config)# interface Vlan205X <-----(if pod assignment is 2 then X = 2 – 1)
N5K(config-if)# no shutdown
N5K(config-if)# mtu 9216
N5K(config-if)# ip address 11.1.119.254/24
N5K(config-if)# ip router ospf 1 area 0.0.0.0
N5K(config-if)# ip pim sparse-mode
N5K(config-if)# ip igmp version 3
N5K(config-if)# ip proxy-arp
!
N5K(config)# interface eth1/1
N5K(config-if)# no shutdown
N5K(config-if)# switchport mode trunk
N5K(config-if)# switchport trunk allowed vlan all
!
N5K(config)# ip pim rp-address 11.1.119.254 group-list 224.0.0.0/9 bidir

10 | P a g e
Task 2: Site 1 Infrastructure Virtual Switch (Nexus 1000V)
The CSR and Virtual Machine at Site1 reside behind a Nexus 1000V switch.

Task 2.1: Site 1 Nexus 1000v Port-Profile Configuration

1. From putty, SSH to the Nexus 1000V VM in Site 1 ---(N1K)
2. Create VLANs:
a. 1, 205X, and 206X
3. Create a Port-Profile to provide management and VxLAN VTEP networking to the CSR 1000V.
Port-Profile CSR-vlan205X will be attached to the CSR GigabitEthernet1 and
GigabitEthernet2(unused) interfaces.
4. Create a second Port-Profile to trunk 802.1q tagged VLANs into the CSR. Port-Profile CSR-
vTrunk will be attached to the CSR GigabitEthernet3 interface.
5. Create a Port-Profile for the virtual machine interface on VLAN 206X. This is an access Port-
Profile.

Commands:
# Site 1 Nexus 1000v

N1K # configure terminal

N1K(config)# vlan 1,205X,206X
!
N1K(config)# port-profile type vethernet CSR-vlan205X
N1K(config-port-prof)# vmware port-group
N1K(config-port-prof)# switchport mode access
N1K(config-port-prof)# switchport access vlan 205X
N1K(config-port-prof)# no shutdown
N1K(config-port-prof)# description Assigned to CSR1000 GigE1, GigE2
N1K(config-port-prof)# state enabled
!
N1K(config)# port-profile type vethernet CSR-vTrunk
N1K(config-port-prof)# vmware port-group
N1K(config-port-prof)# switchport mode trunk
N1K(config-port-prof)# switchport trunk allowed vlan 1,206X
N1K(config-port-prof)# no shutdown
N1K(config-port-prof)# description Assigned to CSR1000 GigE3
N1K(config-port-prof)# state enabled
!
N1K(config)# port-profile type vethernet vlan206X
N1K(config-port-prof)# vmware port-group
N1K(config-port-prof)# switchport mode access

11 | P a g e
N1K(config-port-prof)# switchport access vlan 206X
N1K(config-port-prof)# no shutdown
N1K(config-port-prof)# description Assigned to VMs in VLAN206X
N1K(config-port-prof)# state enabled

12 | P a g e
Task 3: Site 1 Cloud Service Router

13 | P a g e
Task 3.1: CSR Networking Configuration
1. From vSphere Client, access the settings on the CSR 1000V VM by doing a right click on the
“Site 1 Cloud Services Router” VM.

a.
2. Configure the CSR Network Adapters 1 & 2 with the CSR-vlan205X Port-Profile and Adapter
3 with CSR-vTrunk.

a.
3. Assign port-profile VLAN 206X to “Network adapter 1” of PC1

14 | P a g e
 a.

b.
4. Access CSR1000 VM via vSphere Client console and configure an IP address on the
GigabitEthernet1 interface, and create a Loopback0 interface. Here, loopback0’s network
should be advertised over OSPF to the backbone router.

15 | P a g e
 a.

Commands
# Site 1 CSR1000v

CSR-1K> enable
CSR-1K# configure terminal
!
CSR-1K(config)# ip multicast-routing distributed
!
CSR-1K(config)# interface Loopback0
CSR-1K(config-if)# ip address 11.119.119.1 255.255.255.0
CSR-1K(config-if)# ip pim sparse-mode
CSR-1K(config-if)# ip ospf network point-to-point
CSR-1K(config-if)# exit
!
CSR-1K(config)# interface GigabitEthernet1
CSR-1K(config-if)# mtu 9216
CSR-1K(config-if)# ip address 11.1.119.30 255.255.255.0
CSR-1K(config-if)# ip pim sparse-mode
CSR-1K(config-if)# ip igmp version 3
CSR-1K(config-if)# negotiation auto
CSR-1K(config-if)# no shutdown
CSR-1K(config-if)# exit
!
CSR-1K(config-router)# router ospf 1
CSR-1K(config-router)# network 11.119.119.0 0.0.0.255 area 0
CSR-1K(config-router)# network 11.1.119.0 0.0.0.255 area 0
CSR-1K(config-router)# exit
!
CSR-1K(config)# ip pim bidir-enable
CSR-1K(config)# ip pim rp-address 11.1.119.254 bidir
CSR-1K(config)# ip pim ssm default
CSR-1K(config)# ip route 0.0.0.0 0.0.0.0 GigabitEthernet1 11.1.119.254

16 | P a g e
Task 3.2: CSR Networking Configuration
In bridge domains the Virtual Network Identifier (VNI) designates the VxLAN Segment ID. This value
is encoded in the VXLAN frame header and must match the segment-id defined in Site2's Nexus
1000V.

The Network Virtualization Endpoint (NVE) maps the VNI (VxLAN ID) to a multicast group and
simultaneously creates a Virtual Tunnel Endpoint (VTEP) bound to the loopback. The VTEP is a
termination endpoint for VxLAN frame encapsulation / decapsulation.

GigabitEthernet3 acts as an 802.1q trunking interface to bridge non-VxLAN frames from virtual
machines into the CSR. As an alternative sub-interfaces could be utilized.

1. Create a bridge domain with VNI 6001. Bind the bridge-domain to GigabitEthernet3 with
service-instance 3.
2. Create a NVE interface mapping the VNI(6001) to the multicast group (239.1.119.150). Bind
nve1 to the loopback0 interface.
3. Add the service instance to GigabitEthernet3. Set the 802.1q VLAN to be encapsulated in
VxLAN. Set a symmetrical rewrite policy.

Commands:
# Site 1 CSR1000v

CSR-1K# config terminal

CSR-1K(config)# bridge-domain 1
CSR-1K(config-bdomain)# member vni 6001
CSR1K(config-bdomain)# member GigabitEthernet3 service-instance 3
CSR1K(config-bdomain)# exit
!
CSR-1K(config)# interface nve1
CSR-1K(config-if)# no ip address
CSR-1K(config-if)# member vni 6001 mcast-group 239.1.119.150
CSR-1K(config-if)# source-interface Loopback0
CSR-1K(config-if)# no shut
CSR-1K(config-if)# exit
!
CSR-1K(config)# interface GigabitEthernet3
CSR-1K(config-if)# no shutdown
CSR-1K(config-if)# no ip address
CSR-1K(config-if)# negotiation auto
CSR-1K(config-if)# service instance 3 ethernet
CSR-1K(config-if-srv)# encapsulation dot1q 206X
CSR-1K(config-if-srv)# rewrite ingress tag pop 1 symmetric
CSR-1K(config-if-srv)# exit

17 | P a g e
Task 4: Site 2 Nexus 1000v Configuration

Task 4.1: VxLAN Configuration

1. From the putty, SSH to Nexus 1000v VM in Site2 --- (N1K_2)
2. Enable VxLAN with the feature segmentation command.
3. Create a bridge-domain with a matching segment-id and multicast group as the CSR1K. In
previous step the segment-id is 6001 in multicast group 239.1.119.150.
4. Create a vethernet port-profile for the virtual machine. Instead of configuring an access
VLAN, set a bridge-domain with the csr segment-id.
5. Assign Port-Profile bd-6001 to network adapter 1 of PC2
6. Create vethernet Port-Profile VMK-VXLAN with capability VxLAN and allow vlan 205X
7. Create VMkernel interface on ESX host in Site 2, assign the VKM-VXLAN Port-Profile, and
configure IP address 11.1.119.74 to the VMK

Commands:
# Site 2 Nexus 1000v

N1K_2# config terminal

N1K_2(config)# feature segmentation
N1K_2(config)# vxlan udp port 4789
!
N1K_2(config)# bridge-domain csr
N1K_2(config-bdomain)# segment id 6001
N1K_2(config-bdomain)# group 239.1.119.150
N1K_2(config-bdomain)# no segment mode unicast-only
!
N1K_2(config)# port-profile type vethernet bd-6001
N1K_2(config-port-prof)# switchport mode access
N1K_2(config-port-prof)# switchport access bridge-domain csr
N1K_2(config-port-prof)# no shutdown
N1K_2(config-port-prof)# state enabled
N1K_2(config-port-prof)# vmware port-group
!
N1K_2(config)# port-profile type vethernet VMK-VXLAN

18 | P a g e
N1K_2(config-port-prof)#
N1K_2(config-port-prof)#
N1K_2(config-port-prof)#
N1K_2(config-port-prof)#
N1K_2(config-port-prof)#
N1K_2(config-port-prof)#
vmware port-group
switchport mode access
switchport access vlan 205X
capability vxlan
no shutdown
state enabled

Screenshots:
a) Assign Port-Profile bd-6001 to network adapter 1 of PC2

a.

b.

19 | P a g e
b) Create VMkernel interface on ESX host in Site 2, assign the VKM-VXLAN Port-Profile and
configure IP address 11.1.119.74 to the VMK.
a. Select host with N1K_2, under Configuration > Networking > vDVS and click “Manage
Virtual Adapters”

i.
b. Click “Add”

i.
c. Click “New Virtual Adapter” then “Next >”

20 | P a g e
 i.
d. Click “VMkernel” then “Next >”

i.
e. Select port group “VMK-VXLAN” then “Next >”

21 | P a g e
 i.
f. Select “Use the following IP settings” and assign IP address and subnet 11.1.119.74 /
255.255.255.0 then “Next >”, “Finish” and close the “Manage Virtual Adapters”
window.

i.
g. Verify that VMKernel interface was created.

22 | P a g e
i.

23 | P a g e
Task 5: Verification
Access PC1 VM via vSphere Client console, open Window’s Command Prompt, and start a ping to
PC2’s IP 11.1.119.101. (Note: If configuration is correct ping should work.)

24 | P a g e
Commands:

Verify the backbone router IP PIM configuration:

N5K# show ip mroute 239.1.119.150
IP Multicast Routing Table for VRF "default"

(*, 239.1.119.150/32), uptime: 00:28:34, igmp ip pim

Incoming interface: Null, RPF nbr: 0.0.0.0
Outgoing interface list: (count: 1)
Vlan205X, uptime: 00:28:34, igmp

(11.1.119.74/32, 239.1.119.150/32), uptime: 00:28:34, ip pim mrib

Incoming interface: Vlan205X, RPF nbr: 11.1.119.74
Outgoing interface list: (count: 1)
Vlan2050, uptime: 00:28:34, mrib, (RPF)

(11.119.119.1/32, 239.1.119.150/32), uptime: 00:02:39, ip mrib pim

Incoming interface: Vlan205X, RPF nbr: 11.1.119.30
Outgoing interface list: (count: 1)
Vlan205X, uptime: 00:02:39, mrib, (RPF)

25 | P a g e
Verify the backbone router sees the IGMP Group messages from the Site 2 Nexus 1000V hypervisor
physical interfaces:
N5K# show ip igmp snooping groups 239.1.119.150
Type: S - Static, D - Dynamic, R - Router port, F - Fabricpath core port

Vlan Group Address Ver Type Port list

205X 239.1.119.150 v3 D Eth1/1

N5K# show ip igmp snooping groups 239.1.119.150 detail

IGMP snooping group membership for vlan 205X
Group addr: 239.1.119.150
Group ver: v3 [old-host-timer: 00:03:31]
report-timer: not-running
Last reporter: 11.1.119.74

Verify the CSR1000 has a PIM adjacency to the backbone router and contains a route to the
239.1.119.150 group
Notice the 'x' flag designating this is a VxLAN multicast group.

CSR-1K#show ip pim neighbor

PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.1.119.254 GigabitEthernet1 5d22h/00:01:43 v2 1 / DR B
G

CSR1K #show ip mroute 239.1.119.150

IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM
Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.1.119.150), 5d22h/stopped, RP 11.1.119.254, flags: BCx
Bidir-Upstream: GigabitEthernet1, RPF nbr 10.1.119.254
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 5d22h/00:01:02
GigabitEthernet1, Bidir-Upstream/Sparse, 5d22h/stopped

26 | P a g e
Verify the NVE is up and a peering to the Site 2 hypervisor host VMK (11.1.119.74) has been formed:
Once traffic is flowing between VTEPs the packet counters will increment.

CSR-1K #show nve vni

Interface VNI mcast VNI state
nve1 6001 239.1.119.150 Up

CSR-1K #show nve peers

Interface Peer-IP VNI Up Time
nve1 11.1.119.74 6001 -

CSR-1K#show nve interface nve 1 detail

Interface: nve1, State: Admin Up, Oper Up Encapsulation: Vxlan
source-interface: Loopback0 (primary:10.119.119.1 vrf:0)
Pkts In Bytes In Pkts Out Bytes Out
196382 16070982 198330 16343138

Verify the CSR1000 forwarding table:

Entries pointing at GigabitEthernet3 are virtual machines on the 802.1q network while nve1.VNI6001
will be VxLAN encapsulated toward Site 2.

CSR-1K #show bridge-domain

Bridge-domain 1 (2 ports in all)
State: UP Mac learning: Enabled
Aging-Timer: 300 second(s)
GigabitEthernet3 service instance 3
vni 6001
MAC address Policy Tag Age Pseudoport
(PC2 MAC)--> 0050.56BC.38AB forward dynamic 300 nve1.VNI6001 VxLAN
[src:11.119.119.1 dst:11.1.119.74]
(PC1 MAC)--> 0050.56BC.3688 forward dynamic 300 GigabitEthernet3.EFP3

CSR-1K #show l2fib bridge-domain 1 vxlan encap

VxLAN Encap:
VNI : Intf nve: nv1, Vni: 6001
Bridge Domain : 1
Multicast Group : 239.1.119.150
Encap String : 0x0800000000177100
Reference Count : 2
Tunnel Handle : 0xC
Tunnel Adjacency : 0x7FE241CFB760

CSR-1K #show l2fib bridge-domain 1 vxlan decap

VxLAN Decap :
Bridge Domain : 1
VNI : Intf nve: nv1, Vni: 6001
Reference Count : 1
Flags : UDPoIP Encap
Multicast Group : 239.1.119.150

27 | P a g e
Verify the Site2 hypervisor host has been programmed correctly and the Mcast statistics are
incrementing.
1) From the putty, SSH to ESXi 2

~ # vemcmd show vxlan interfaces

LTL VSM Port IP Seconds since Last Vem Port
Netmask IGMP Query Received
Gateway
(* = IGMP Join Interface/Designated VTEP)
-----------------------------------------------------------
49 Veth1 11.1.119.74 29 vmk1 *
0.0.0.0
0.0.0.0

~ # vemcmd show vxlan-stats

LTL Ucast Mcast/Repl Ucast Mcast Total
Encaps Encaps Decaps Decaps Drops
49 214551 11877 210817 17478 3590
50 213663 7291 209928 15365 210

28 | P a g e
Appendix

References
CSR1K Configuration Guide:
http://www.cisco.com/c/en/us/td/docs/routers/csr1000/software/configuration/csr1000Vswcfg.ht
ml

29 | P a g e