B DCNM 114 Vxlan Evpn v1

Cisco DCNM 11.
4 for VXLAN EVPN Multi-Site Deployments Lab v1

First Published: 2020-10-08
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
© 2020 Cisco Systems, Inc. All rights reserved.
CONTENTS
CHAPTER 1 About 1
About This Demonstration 1
Requirements 2
About This Solution 2
Use cases 3
Topology 4
Before Presenting 5
Get Started 6
CHAPTER 2 Scenarios 7
Import and Deploy Brownfield into DCNM 7

Review existing Brownfield Configuration 7
Create Fabric 10
Add Switches 13
Confirm Connectivity 17
Bulk Creation of Networks and VRFs (Optional) 17
Importing VRFs 19
Importing Networks 20
Import and Deploy VXLAN EVPN fabric on Greenfield 23
Create Fabric 24
Add Switches 24
Review and Switch Configuration by DCNM 27
Import and Deploy Core Fabric 28
Import Core Fabric 28
Create Fabric 29
Add Switches 30
Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

iii
Contents
Configure Multi-Site 32
Create Fabric 32
Move Fabrics 33
Confirm Connectivity 38
VMM integration 39
Enabling vCenter Compute Visualization 40
Configure Endpoint Locator 47
Network Deployment via REST API (Swagger) 53
DCNM Restful API Documentation 55
Data Center Network Manager 58
CHAPTER 3 Appendix 59
Appendix A. Troubleshooting 59

iv
CHAPTER 1
About
• About This Demonstration, on page 1
• Requirements, on page 2
• About This Solution, on page 2
• Use cases, on page 3
• Topology, on page 4
• Before Presenting, on page 5
• Get Started, on page 6
About This Demonstration

In this demonstration DCNM is used to in the following situations:
• Brownfield: This use case shows how to migrate an existing VXLAN BGP EVPN fabric to Cisco DCNM.
The transition involves migrating existing network configurations to DCNM. Typically, your fabric
would be created and managed through manual CLI configuration or custom automation scripts. Now,
you can manage the fabric through DCNM. After the migration, DCNM manages the fabric underlay
and overlay networks.
• Import and Deploy Brownfield into DCNM
• Bulk Creation of Networks and VRFs (Optional)
• Greenfield: This use case shows how to provision new VXLAN EVPN fabrics.
• Import and Deploy VXLAN EVPN fabric on Greenfield
• Import and Deploy Core Fabric
• Configure Multi-Site: A multi-fabric container created to manage multiple member fabrics. It is a
single point of control for a definition of overlay networks and Virtual Routing and Forwarding
(VRF) that are shared across member fabrics.
• VMM integration: The Virtual Machine Manager (VMM) plug-in stores all the computes and the virtual
machine information that connects to the fabric or the switch groups that are loaded into Cisco DCNM.
VMM gathers compute repository information and displays the VMs, VSwitches/DVS, and hosts in the
topology view.

1
About
Requirements
• Configure Endpoint Locator: The Endpoint Locator (EPL) feature allows real-time tracking of endpoints
within a data center. The tracking includes tracing the network life history of an endpoint and getting
insights into the trends associated with endpoint additions, removals, moves, etc. An endpoint is anything
with an IP and MAC address. In that sense, an endpoint can be a virtual machine (VM), container,
bare-metal server, service appliance etc.
• Network Deployment via REST API (Swagger): In addition to provisioning, monitoring, and
troubleshooting the data center network infrastructure, Cisco DCNM provides a comprehensive feature-set
that meets the routing, switching, and storage administration needs of the data center. It streamlines the
provisioning of the Programmable Fabric and the monitoring of the SAN and LAN components. The
Cisco Fabric Automation REST APIs for third party applications enables you to programmatically control
Cisco Fabric Automation. The REST API supports Power On Auto Provisioning (POAP), Auto Config
and, Cable plan features. All the REST API operations can also be performed using the DCNM GUI as
DCNM uses these REST APIs to render the GUI.
Requirements
The table below outlines the requirements for this preconfigured demonstration.
Required Optional
Laptop Cisco AnyConnect
About This Solution

Cisco Data Center Network Manager (DCNM) offers a network management system (NMS), support for
traditional or multiple-tenant LAN, and SAN fabrics on a single window. Cisco DCNM can:
• Work across all Cisco Nexus and MDS switching families
• Manage large numbers of devices while providing ready-to-use control, management, and automation
capabilities including Virtual Extensible LAN (VXLAN) control and automation for Cisco Nexus LAN
fabrics
• Support automatic configuration for multi-tenant automation
• Offer integrated storage visualization, provisioning, and troubleshooting
• Offer intuitive, multi-fabric topology views for LAN fabric and storage
• Integrate with Cisco UCS Director, vSphere, and OpenStack
Virtual Extensible LAN (VXLAN) is an overlay technology for network virtualization. It provides a Layer 2
extension over a shared Layer 3 underlay infrastructure network by using MAC address in IP User Datagram
Protocol (MAC in IP/UDP) tunneling encapsulation. The purpose of obtaining a Layer 2 extension in the
overlay network is to overcome the limitations of physical server racks and geographical location boundaries
to achieve flexibility for workload placement within a data center or between different data centers.
The initial IETF VXLAN standards (RFC 7348) defined a multicast-based flood-and-learn VXLAN without
a control plane. It relies on data-based flood-and-learn behavior for remote VXLAN tunnel endpoint (VTEP)
peer discovery and remote end-host learning. The overlay broadcast, unknown unicast, and multicast traffic

2
About
Use cases
is encapsulated into multicast VXLAN packets and transported to remote VTEP switches through the underlay
multicast forwarding. Flooding in such a deployment can present a challenge for the scalability of the solution.
The requirement to enable multicast capabilities in the underlay network also presents a challenge because
some organizations do not want to enable multicast in their data centers or WAN networks.
To overcome the limitations of the flood-and-learn VXLAN as defined in RFC 7348, organizations can use
Multiprotocol Border Gateway Protocol (MP-BGP) Ethernet Virtual Private Network (EVPN) as the control
plane for VXLAN. MP-BGP EVPN has been defined by IETF as the standards-based control plane for VXLAN
overlays. The MP-BGP EVPN control plane provides protocol-based VTEP peer discovery and end-host
reachability information distribution that allows more scalable VXLAN overlay network designs suitable for
private and public clouds. The MP-BGP EVPN control plane introduces a set of features that reduces or
eliminates traffic flooding in the overlay network and enables optimal forwarding for both east-west and
north-south traffic.
The VXLAN EVPN Multi-Site feature is a solution to interconnect two or more BGP-based Ethernet VPN
(EVPN) site's fabrics in a scalable fashion over an IP-only network.
The Border Gateway (BG) is the node that interacts with nodes within a site and with nodes that are external
to the site. For example, in a leaf-spine data center fabric, it can be a leaf, a spine, or a separate device acting
as a gateway to interconnect the sites.
Use cases
VXLAN EVPN Multi-Site architecture is a design for VXLAN BGP EVPN–based overlay networks. It allows
interconnection of multiple distinct VXLAN BGP EVPN fabrics or overlay domains, and it allows new
approaches to fabric scaling, compartmentalization, and DCI.
When you build one large data center fabric per location, various challenges related to operation and failure
containment exist. By building smaller compartments of fabrics, you improve the individual failure and
operation domains. Nevertheless, the complexity of interconnecting these various compartments precludes
the pervasive rollout of such concepts, specifically when Layer 2 and Layer 3 extension is required.
Figure 1: Compartmentalization Example
VXLAN EVPN Multi-Site architecture provides integrated interconnectivity that doesn’t require additional
technology for Layer 2 and Layer 3 extension. It thus offers the possibility of seamless extension between
compartments and fabrics. It also allows you to control what can be extended. In addition to defining which
VLAN or Virtual Routing and Forwarding (VRF) instance is extended, within the Layer 2 extensions you can
also control broadcast, unknown unicast, and multicast (BUM) traffic to limit the ripple effect of a failure in
one data center fabric.
When you build networks using the scale-up model, one device or component typically reaches the scale limit
before the overall network does. The scale-out approach offers an improvement for data center fabrics.

3
About
Topology
Nevertheless, a single data center fabric also has scale limits, and thus the scale-out approach for a single
large data center fabric exists.
In addition to the option to scale out within a single fabric, with EVPN Multi-Site architecture you can scale
out in the next level of the hierarchy. Similarly, as you add more leaf nodes for capacity within a data center
fabric, in EVPN Multi-Site architecture you can add fabrics (sites) to horizontally scale the overall environment.
With this scale-out approach in EVPN Multi-Site architecture, in addition to increasing the scale, you can
contain the full-mesh adjacencies of VXLAN between the VXLAN tunnel endpoints (VTEPs) in a fabric.
Figure 2: Scale Example
EVPN Multi-Site architecture can also be used for DCI scenarios. As with the compartmentalization and
scale-out within a data center, EVPN Multi-Site architecture was built with DCI in mind. The overall
architecture allows single or multiple sites per data center to be positioned and interconnected with single or
multiple sites in a remote data center. With seamless and controlled Layer 2 and Layer 3 extension through
the use of VXLAN BGP EVPN within and between sites, the capabilities of VXLAN BGP EVPN itself have
been increased. The new functions related to network control, VTEP masking, and BUM traffic enforcement
are only some of the features that help make EVPN Multi-Site architecture the most efficient DCI technology.
Figure 3: Data Center Interconnect Example
Topology
This content includes preconfigured users and components to illustrate the scripted scenarios and features of
the solution. Most components are fully configurable with predefined administrative user accounts. You can

4
About
Before Presenting
see the IP address and user account credentials to use to access a component by clicking the component icon
in the Topology menu of your active session and in the scenario steps that require their use.
Figure 4: dCloud Topology
Figure 5: Physical Topology
Before Presenting
Cisco dCloud strongly recommends that you perform the tasks in this document before presenting in front of
a live audience. This will allow you to become familiar with the structure of the document and content.

5
About
Get Started
PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION.
Get Started
Follow the steps to schedule a session of the content and configure your presentation environment.
Procedure
Step 1 Initiate your dCloud session. [Show Me How]

Note It may take up to 10 minutes for your session to become active.
Step 2 For best performance, connect to the workstation with Cisco AnyConnect VPN [Show Me How] and the local
RDP client on your laptop [Show Me How].
Workstation 1: 198.18.133.36, Username: dcloud\demouser, Password: C1sco12345
Note When the dCloud demo is first marked as available in the dCloud UI, scripts may continue to run
in the background on the demo Workstation configuring the demo components. This is indicated
by the presence of the Demo Initializing icon on the desktop. Allow these scripts to complete
before using the session.
Alternately, you can use the Search Catalog box to search for the Instant Demo name.

6
CHAPTER 2
Scenarios
• Import and Deploy Brownfield into DCNM, on page 7
• Bulk Creation of Networks and VRFs (Optional), on page 17
• Import and Deploy VXLAN EVPN fabric on Greenfield, on page 23
• Import and Deploy Core Fabric, on page 28
• Configure Multi-Site, on page 32
• VMM integration, on page 39
• Configure Endpoint Locator, on page 47
• Network Deployment via REST API (Swagger), on page 53
Import and Deploy Brownfield into DCNM

In this section we verify VXLAN BGP EVPN fabric in site-2 with a few show commands. The fabric can be
configured with CLI before importing into DCNM.
Also, we issue a verify ping between the servers working as expected before and after the fabric was imported
to confirm the fabric is functioning as expected.
Review existing Brownfield Configuration

Procedure
Step 1 Double-click the MTPuTTY desktop shortcut.

Step 2 Expand Site-2 then, double-click Leaf-2 and then, sign-in with these credentials.
• Username = admin
• Password = C1sco12345
Example:

7
Scenarios
Step 3 Enter show run | i bgp.

Example:
Step 4 Double-click server-2 then, enter ifconfig and then, note the IP Address.
Example:
Step 5 Double-click server-3 then, enter ifconfig and then, note the IP Address.
Example:

8
Scenarios
Step 6 Verify the operation of the fabric.

a) Return to server-2.
b) Ping the IP Address of server-3 (10.10.11.11).
Example:
Step 7 Get the addresses for the local server and the remote server.
a) Return to Leaf-2.
b) Enter show bgp l2vpn evpn.
Example:

9
Scenarios
Create Fabric
c) Enter show nve vni.

Example:
d) Enter show nve peers.

Example:
Create Fabric
Procedure
Step 1 Double-click the Data Center Network Manager desktop shortcut and sign-in with these credentials.

10
Scenarios
Create Fabric
Example:
Step 2 Click Fabric Builder and then, Create Fabric.

Example:
Step 3 In the Fabric Name field, enter VXLAN-EVPN-Brownfield-Site-2 and then, in the Fabric Template
drop-down, select Easy_Fabric_11_1.
Step 4 In the General tab, in the BGP ASN field, enter 65002.
Example:

11
Scenarios
Create Fabric
Step 5 In the Advanced tab, notice that Site ID field is 65002.

Step 6 In the Resources tab, change the first quad of all Underlay IP address fields from 10 to 20.
Example:
Step 7 In the Resources tab. scroll down and change the first quad of the VRF Lite Subnet IP Range field from 10
to 20.
Example:

12
Scenarios
Add Switches
Step 8 In the Configuration Backup tab, check the Hourly Fabric Backup checkbox and then, click Save.
Example:
Add Switches
Procedure
Step 1 In the Actions panel, click + Add switches.

Step 2 In the Discover Existing Switches tab, in the Seed IP field, enter 198.18.4.201.
a) In the Username field, enter admin.
b) In the Password field, enter C1sco12345.
c) Make sure the Preserve Config toggle is set to yes and then, click Start discovery.
Example:

13
Scenarios
Add Switches
Note If fabric discovery is not successful for all switches, going back and re-adding the Seed IP and
credentials seems to fix it.
Step 3 Check the select all checkbox and then, click Import into fabric.
Example:
Step 4 When the import completes, click Close.

Example:

14
Scenarios
Add Switches
Step 5 Right-click BGW-2 and then, select Set role > Border Gateway.
Example:
Step 6 Right-click Spine-2 and then, select Set role > Spine.
Example:
Step 7 Click Save and Deploy.

Step 8 When the deployments complete, click the link in the Preview Config column for Leaf-2.
Example:

15
Scenarios
Add Switches
The Pending Config is shown.

Step 9 Click Side-by-side Comparison to see the difference between the current and expected configurations.
Step 10 Close the Preview Config window.
Step 11 Click Deploy Config.
Step 12 When deployment completes, click Close.
Note If the Status returns FAILED with the following error interface nve1 Failed with
following reason:^ Invalid interface format.., the switch failed to enable the
vxlan feature when it was started.
Open MTPuTTY and then, open a session to the FAILED switch, authenticating with admin/
C1sco12345. Type following commands.
conf t
feature bash
run bash
sudo pkill ppm
exit
Another option is to reboot the switch by running the reload command. The switch will take 5
minutes or so to restart, it can be monitored via the MTPuTTY session.
Leaf-2 and Leaf-3 are now deployed.

16
Scenarios
Confirm Connectivity
Note If the switches are still blue, refresh the page until they are all green. If the layout is different from
above, drag the switch to match the layout and click Save layout.
Procedure
Step 1 Return to MTPuTTY.

Step 2 On server-2, ping server-3 (198.18.134.150).
Bulk Creation of Networks and VRFs (Optional)

The purpose of this scenario is to demonstrate bulk creation of Networks and VRFs.
Procedure
Step 1 Click Control > Interfaces.

Step 2 In the SCOPE drop-down, ensure that VXLAN-EVPN-Brownfield-Site-2 is selected.
Step 3 In the Device Name field, enter Leaf.
Step 4 In the Name field, enter Ethernet1/6.
Step 5 Click the first-column checkbox where Device Name = Leaf-2 and Name = Ethernet1/6.
Step 6 Click the first-column checkbox where Device Name = Leaf-3 and Name = Ethernet1/6 and then, click
Edit.
Example:

17
Scenarios
Bulk Creation of Networks and VRFs (Optional)
Step 7 In the Policy drop-down, select int_trunk_host_11_1 then click Save and then, click Deploy.
Example:
Step 8 In the configuration dialog, click OK.

Example:
Step 9 Verify that the Mode of Leaf-2 and Leaf-3 is now trunk.
a) In the Device Name field, enter Leaf.
b) In the Name field, enter Ethernet1/6.
c) In the Mode field, enter trunk.

18
Scenarios
Importing VRFs
Importing VRFs
Procedure
Step 1 Click Control > VRFs.

Click OK if Unsupported Fabric Data Center selected warning displays.
Step 2 In the SCOPE drop-down, ensure that VXLAN-EVPN-Brownfield-Site-2 is selected and then, click Import.
Example:
Step 3 Double-click the VRF file.

Example:

19
Scenarios
Importing Networks
Importing Networks
Procedure
Step 1 Click Network View.

Example:
Step 2 Click Import.

Step 3 Double-click the Network file.
Example:
Step 4 Select the imported Networks and then, click Continue.

Example:

20
Scenarios
Importing Networks
Step 5 Click the multi-select checkbox and the, click-and-drag a rectangle around Leaf-2, and Leaf-3.
Example:

21
Scenarios
Importing Networks
Step 6 Click the Select all checkbox.

Example:
Step 7 Configure Leaf-2.

a) Change VLAN value to 450.
b) Click the … (ellipses) button associated with Leaf-2.
c) Check the Ethernet1/6 checkbox and then, click Save.
Example:

a) Change VLAN value to 450.
b) Click the … (ellipses) button associated with Leaf-3.
c) Check the Ethernet1/6 checkbox and then, click Save.
Example:

22
Scenarios
Import and Deploy VXLAN EVPN fabric on Greenfield
Step 9 Click Deploy.

Example:
Import and Deploy VXLAN EVPN fabric on Greenfield

In this section we import a clean fabric and configure VXLAN BGP EVPN in site-1 using DCNM. DCNM
clears all configs on the switches except management before pushing VXLAN EVPN configs on the switches.

23
Scenarios
Create Fabric
Create Fabric
Procedure
Step 1 Return to Data Center Network Manager > Control > Fabric Builder and then, click Create Fabric.
Step 2 In the Fabric Name field, enter VXLAN-EVPN-Greenfield-Site-1 and then, in the Fabric Template
drop-down, select Easy_Fabric_11_1.
Step 3 In the General tab, in the BGP ASN field, enter 65001.
Example:
Step 4 In the Advanced tab, Notice that Site ID field is 65001.

Step 5 Scroll up and in the Greenfield Cleanup Option drop-down, select Enable.
Example:
Step 6 In the Configuration Backup tab, check the Hourly Fabric Backup checkbox and then, click Save.
Example:
Add Switches
Procedure

Step 2 In the Discover Existing Switches tab, in the Seed IP field, enter 198.18.4.101.
a) In the Username field, enter admin.
b) In the Password field, enter C1sco12345.
c) Set the Preserve Config toggle to no and then, click Start discovery.

24
Scenarios
Add Switches
Step 3 Click the select all checkbox and then, click Import into fabric.
Example:
Step 4 Click OK.
Step 5 When the import completes, click Close.
Step 6 Right-click BGW-1 and then, select Set role > Border Gateway.
Example:

25
Scenarios
Add Switches
Step 7 Right-click Spine-1 and then, select Set role > Spine.
Example:
Step 8 Click Save and Deploy.

Step 9 When the deployments complete, click the link in the Preview Config column for Leaf-1.
Example:
The Pending Configuration displays.

26
Scenarios
Review and Switch Configuration by DCNM
Step 10 Click Side-by-side Comparison to see the difference between the Running and Expected configurations.
Step 11 Close the Preview Config window and then, click Deploy Config.
Step 12 When the deployment completes, click Close.
Review and Switch Configuration by DCNM

Procedure

Step 2 Double-click Spine-1 and then, sign-in with these credentials.
Step 3 Enter show run to review the configuration that has been pushed via DCNM.
Example:
Step 4 Return to Data Center Network Manager.

When all the switches are green, they are synchronized.

27
Scenarios
Import and Deploy Core Fabric
Import and Deploy Core Fabric

In this section we import a Core router connecting Site-1 and Site-2 into DCNM. We use an external template
to import the fabric.
Import Core Fabric

Procedure
Step 1 Return to Data Center Network Manager and then, click Control > Interfaces.
Example:

a) In the Device Name field, enter Leaf-1.
b) In the Name field, enter 1/2.
c) Click the checkbox of the row where Device Name = Leaf-1 and Name = Ethernet 1/2 and then, click
Edit.
Example:

28
Scenarios
Create Fabric
Step 3 In the Policy drop-down, select int_access_host_11_1 then, click Save and then, click Preview.
Step 4 Click Expected Config and then, when done viewing, close the Preview Configuration dialog.
Step 5 Click Deploy and then, click OK.
Example:
Create Fabric
Procedure
Step 1 Click Control > Fabric Builder.

Example:

29
Scenarios
Add Switches
Step 2 Click Create Fabric.

Step 3 In the Fabric Name field. enter Core-1.
Step 4 In the Fabric Template drop-down, select External_Fabric_11_1.
Step 5 In the General tab, in the BGP AS # field, enter 65003.
Step 6 Deselect the Fabric Monitor Mode checkbox and then, click Save.
Example:
Add Switches
Procedure

a) In the Seed IP field, enter 198.18.4.205.
b) In the Username field, enter admin.
c) In the Password field, enter C1sco12345.
d) Click Start discovery.
e) Check the checkbox of the row where Name = DCI-Router and then, click Import into Fabric.
Example:

30
Scenarios
Add Switches
Step 2 When deployment completes, click Close.

Step 3 In the topology diagram, right-click DCI-Router and then, select Set role > Core Router.
Example:
Step 4 Click Save and Deploy and then, on completion, click the Preview Config link.
Example:
Step 5 When done viewing, close the Preview Configuration dialog.

Step 6 Click Deploy Config and then, on completion, click Close.

31
Scenarios
Configure Multi-Site
The topology screen shows that Site-1, Site-2, and DCI-Router are deployed.
Configure Multi-Site
In this section we create a multi-site fabric using the multi-site template in DCNM and then, import all 3 fabric
with easy to use DCNM GUI. Ping between servers in two different sites confirms that multi-site is configured
successfully.
Create Fabric
Procedure
Step 1 Return to Data Center Network Manager and then, click Fabric Builder > Create Fabric.
a) In the Fabric Name field, enter MSD-1.
b) In the Fabric Template drop-down, select MSD_Fabric_11_1.
Step 2 Configure DCI.
a) In the DCI tab, in the Multi-Site Overlay IFC Deployment Method drop-down, select
Centralized_To_Route_Server.
b) In the Multi-Site Route Server List field, enter 100.100.100.100
c) In the Multi-Site Route Server BGN ASN List field, enter 65003.
d) Click the Multi-Site Underlay IFC Auto Deployment Flag checkbox and then, click Save.
Example:

32
Scenarios
Move Fabrics
Move Fabrics
Procedure
Step 1 In the Actions panel, click Move Fabrics.

Step 2 In the Move Fabric dialog, select VXLAN-EXPN-Brownfield_Site_2.
a) Click Add and then, click Close.
Example:

33
Scenarios
Move Fabrics
Step 3 In the Actions panel, click Move Fabrics.

Step 4 In the Move Fabric dialog, select VXLAN-EXPN-Greenfield_Site_1.
b) In the Actions panel, click Move Fabrics.
Step 5 In the Move Fabric dialog, select Core-1.
Zooming in on the topology shows the fabrics just added.

34
Scenarios
Move Fabrics
Step 6 Click Save and Deploy and then, on completion, click the Preview Config link for BGW-1.
Example:
Step 7 Click Side-by-side Comparison to see the difference between the configurations and then, when done viewing,
close the Preview Configuration dialog.
Step 8 Click Deploy Config and then, when complete, click Close.
Step 9 Click Control > Networks.
Example:

35
Scenarios
Move Fabrics
Step 10 In the SCOPE drop-down, make sure that MSD-1 is selected.

Example:
Step 11 Click the Auto_Net_VNI300001_VLAN250 checkbox and then, click Continue.

In the topology diagram, Leaf-2 is deployed (displaying in green). We are going to deploy it on Leaf-1.
Step 12 Click the Multi-select switches checkbox.

Example:
Step 13 Select Leaf-1 by clicking-and-dragging over it.

Example:
Step 14 In the Network Attachment – Attach networks for given switch(es) dialog, click the Leaf-1 checkbox.
a) In the Interfaces column, for Leaf-1, click
then, select Ethernet1/2 and then, click Save.

Step 15 Select BGW-2 by clicking-and-dragging over it.
Example:
Step 16 Clivk the BGW-2 checkbox and then, click Save.

Step 17 Select BGW-1 by clicking-and-dragging over it.
Example:

36
Scenarios
Move Fabrics
Step 18 Click the BGW-1 checkbox and then click Save.

Example:
Step 19 Preview the configuration of the switches.

a) Click Preview configuration.
Example:
b) In the Select a Switch drop-down. select BGW-1.

Example:

37
Scenarios
Step 20 Close the Preview Configuration dialog and then, click Deploy.
When the topology chart items turn green, the configuration is deployed.
Procedure

38
Scenarios
VMM integration

Example:
A successful ping confirms that the multi-site configuration is working.
VMM integration
In virtualized environments, any kind of troubleshooting starts with identifying the network attachment point
for the virtual machines. This means that a quick determination of the server, virtual switch, port group,
VLAN, associated network switch, and physical port is critical. This requires multiple touch points and
interactions between the server and the network administrator as well as reference to multiple tools (compute
orchestrator, compute manager, network manager, network controller, etc.).
In this scenario we will configure VMM integration within DCNM.
This allows you to visualize the vCenter-managed hosts and their leaf switch connections on the Topology
window. The visualization options include viewing only the attached physical hosts, only the VMs, or both.
When you select both, the topology all the way from the leaf switches to the VMs, including the virtual
switches are displayed.
Cisco DCNM Supports hosts running on UCS type B (chassis UCS) that are behind the Fabric interconnect.
You must enable CDP of the vNIC on Cisco UCSM to use this feature.
Procedure
Step 1 Return to DCNM.

Step 2 Click Topology and then, check out how it looks.
We will do a comparison after done the VMM integration

39
Scenarios
Enabling vCenter Compute Visualization

To enable the vCenter Compute Visualization feature from the Cisco DCNM Web UI, perform the following
steps.
Procedure
Step 1 Click Control > Management > Virtual Machine Manager.

Example:

40
Scenarios
The Control > Management > Virtual Machine Manager window displays.
Step 2 Click the + icon to add a new VMware vSphere vCenter.
a) Enter Virtual Center Server: 198.18.133.30 with these credentials.
Username: administrator@vsphere.local
Password: C1sco12345!
b) Click Add.
Example:
After initial discovery, the information that is received from the vCenter is appropriately organized and
displayed in the main Topology window.

41
Scenarios
Step 3 Click Topology again.

An extra menu item labeled Compute appears on the Show pane.
Step 4 In the Show list, select Compute to enable the compute visibility.
By default, the Host checkbox is selected. This implies that the topology shows the VMWare vSphere ESXi
hosts (servers) that are attached to the network switches.
The following options are available in the Compute Visualization feature.
• Host
• All
• VM Only
Step 5 Click an ESXi host to view additional information.

The layout might be different from the following image, but you can drag the ESXI host to match that. Click
+ to enlarge the topology.
Example:

42
Scenarios
Step 6 Hover the mouse over the connection line between Leaf-1, Leaf-2, Leaf-3 and the ESXI host.
You can see the port interface to which the leafs have connected and the ESXI host information.
Example:
Step 7 Double-click the ESXI host.

The expanded topology displayed in the following figure, shows the virtual switches (both vSwitch and
Distributed Virtual Switch) that are configured on the specific ESXi host.

43
Scenarios
When changing from the Host suboption to the All suboption, all the compute resources are expanded.
When All is selected, an expanded view of all the hosts, virtual switches, and virtual machines that are part
of the topology are displayed. If a VM is powered off, it is shown in red, otherwise it is shown in green.
Step 8 Hover your mouse over ESXI host, vSwitch, and virtual machine to see more information.
Example:

44
Scenarios
Instead of browsing through the large set of available information, to focus on the VM only, you can change
the All suboption to VM Only. Server-2 is connected with Leaf-2, Server-3 is connected with Leaf-3, and
Server-1 is connected with Leaf-1.
Step 9 Hover over the VM to see network adaptor and Mac address information.
Example:

45
Scenarios
The Virtual Machine List allows you to view the complete list of virtual machines.
Step 10 Change the VM Only suboption back to Host and then, click VM List at the bottom.
Example:
Step 11 In the list of the VMs, click on the name of a VM to view additional information about that virtual machine.
You can also see the VLAN, vSwitch, Physical NIC, and Switch Interface information in the list.
Example:

46
Scenarios
Configure Endpoint Locator

In this section we enable the endpoint locator feature in DCNM which helps us locate the endpoints connected
to Leafs. This would be very useful when have to troubleshoot or locate one from 100’s of endpoints inside
you data center.
The Endpoint Locator (EPL) feature allows real-time tracking of endpoints within a data center. This includes
tracing the life history of an endpoint as well as providing insights into the trends associated with endpoint
additions, removals, moves, etc.
A third interface is required when Inband management is used for a fabric via the eth1 interface. This ensures
that the management interface, used by Cisco DCNM for managing the devices, should not have any dependency
on the interface through which EPL BGP peering occurs.

47
Scenarios
After physical connectivity is established between Cisco DCNM and the fabric through a switch’s front-panel
interface, the configurations should be performed on the respective switches and Cisco DCNM.
After the BGP connectivity to the fabric is established via the BGP RR, DCNM receives BGP updates. These
are fed into a BigData DB.
For a VXLAN BGP EVPN based data center fabric, Endpoint Locator provides near real-time tracking of
every endpoint. Events such as an endpoint coming up, an endpoint going down, or an endpoint move are
now visible with a few simple clicks.
Note DCNM should still be open from previous scenarios. If it is not, double-click the DCNM shortcut on the
remote desktop and login with username admin and password C1sco12345.
Procedure
Step 1 Configure the Leaf-2 Eth1/3 interface which is connected to eth2 of DCNM (DCNM Inband connection with
fabric).
a) Click Control > Interfaces.
b) In the SCOPE drop-down, make sure that VXLAN-EVPN-Brownfield-Site-2 is selected.
c) In the Device Name field, enter Leaf-2.
d) Click the Leaf-2 checkbox where Name = Ethernet1/3 and then, click Edit.
Example:

48
Scenarios
e) In the Policy drop-down, select epl_routed_intf.

f) In the Interface IP field, enter 192.168.55.1.
g) In the IP Netmark Length field, enter 24 then, click Save and then, click Deploy.
Example:

49
Scenarios
h) Click OK.
Example:
Step 2 Under Endpoint Locator, click Control > Configure.

a) In the SCOPE drop-down, make sure that VXLAN-EVPN-Browfield-Site-2 is selected.
b) In the Spine/Route Reflector (RR1) drop-down, select Spine-2.
c) For Collect additional information (port, VLAN, etc), select Yes and then, click Submit.
Example:

50
Scenarios
Note After a couple of minutes, the Endpoint Activity screen is populated by the recently configured
Endpoint Locator. The two endpoints are server-1 and server-2, which are located on leaf-2 and
leaf-3. If you do not see both the endpoints, ping from server 1 and server 2 to gateway
10.10.10.1. The reason you might see one endpoint is because two hosts are in the same subnet,
and one of them will do ARP. You can enable suppress-arp or ping the gateway for an ARP
request from both endpoints.
Step 3 Click Endpoint Life.

Example:

51
Scenarios
a) In the IP or MAC field, enter 10.10.11.11 (the IP Address of server-3).

b) In the VNI drop-down, select Auto_Net_VNI30000 and then, click Submit.
Example:
This shows that the Endpoint IP 10.10.11.11 is on Leaf-3.

52
Scenarios
Network Deployment via REST API (Swagger)

The purpose of this section is to use the swagger APIs to:
• Create a VRF.
• Create a network.
• Attach a network to an interface of a Leaf.
• Preview a config.
• Deploy a network and VRFs.
Note If you have done the Scenario: Bulk Creation of Networks and VRFs, skip the following steps and continue
with the DCNM Restful API Documentation section.
Procedure
Step 1 Click Control > Interfaces.

Step 2 In the SCOPE drop-down, make sure that VXLAN-EVPN-Brownfield-Site-2 is selected.
Step 3 In the Device Name field, enter Leaf.
Step 4 In the Name field, enter Ethernet1/6.
Step 5 Click the first column checkbox where Device Name = Leaf-2 and Name = Ethernet1/6.
Step 6 Click the first column checkbox where Device Name = Leaf-3 and Name = Ethernet1/6 and then, click Edit.
Example:

53
Scenarios
Step 7 In the Policy drop-down, select int_trunk_host_11_1 then, click Save and then, click Deploy.
Example:
Step 8 In the configuration dialog, click OK.

Example:
Step 9 Verify that the Mode of Leaf-2 and Leaf-3 is now trunk.
a) In the Device Name field, enter Leaf.

54
Scenarios
DCNM Restful API Documentation
b) In the Name field, enter Ethernet1/6.

c) In the Mode field, enter trunk.
Example:

Procedure
Step 1 On the desktop of the workstation, right-click the DCNM APIs.txt file and then, select Edit with Notepad++.
Example:
Note This file contains the JSON configuration key-value pairs that you copy and paste in the following
steps.
Step 2 In Google Chrome, open https://dcnm.dcloud.cisco.com/api-docs/.

Example:

55
Scenarios
Step 3 Copy the VRF configuration.

a) Expand Top Down LAN VRF Operations.
b) Click -POST- /top-down/fabrics/{fabric-name}/vrfs and then, click Try it out.
c) From DCNM APIs.txt, copy the Step 1: JSON text and then, paste it into the body field.
d) In the fabric-name field, enter MSD-1.
e) Click Execute.
f) Ensure that the Response Code is 200.
Step 4 Copy the LAN configuration.
a) Expand Top Down LAN Network Operations.
b) Click -POST- /top-down/fabrics/{fabric-name}/networks and then, click Try it out.
d) In the fabric-name field, enter MSD-1.
e) Click Execute.
f) Ensure that the Response Code is 200.
Step 5 Get serial number information.
b) Click -GET- /top-down/fabrics/{fabric-name}/networks/attachments and then, click Try it out.
c) In the fabric-name field, enter MSD-1.
d) In the network-names field, enter SEVT-NETWORK.
e) Click Execute.
f) Scroll the Response Body page up to show SEVT-NETWORK.
g) For Leaf-2, take a note of the value of switchSerialNo.

56
Scenarios
Example:
h) Ensure that the Response Code is 200.

Step 6 Configure Leaf-2 switch.
b) Click -POST- /top-down/fabrics/{fabric-name}/networks/attachments and then, click Try it out.
d) Change the serialNumber value with the switchSerialNo value from the previous -GET-.
e) In the fabric-name field, enter MSD-1.
f) Click Execute.
g) Ensure that the Response Code is 200.
Step 7 Preview the configuration before deployment.
a) Expand -GET- /top-down/fabrics/{fabric-name}/networks/preview and then, click Try it out.
b) In the fabric-name field, enter MSD-1.
c) In the network-names field, enter SEVT-NETWORK.
d) Click Execute.
e) Ensure that the Response Code is 200.
Step 8 Deploy the configuration.
a) Expand -POST- /top-down/fabrics/{fabric-name}/networks/deployments and then, click Try it out.
b) In the fabric-name field, enter MSD-1.
d) Click Execute.
e) Ensure that the Response Code is 200.

57
Scenarios
Data Center Network Manager
Data Center Network Manager

Procedure
Step 1 Click Control > Networks.

Step 2 In the SCOPE drop-down, ensure that VXLAN-EVPN-Brownfield-Site-2 is selected.
Step 3 Click the checkbox associated with SEVT-NETWORK, then click Continue and then, click Deploy.

58
CHAPTER 3
Appendix
• Appendix A. Troubleshooting, on page 59
Appendix A. Troubleshooting
Perform the procedure below if the steps in Import and Deploy Brownfield into DCNM fail (particularly the
ping between server-2 and server-3), indicating that the switches are either not responding or powered off.
Procedure
Step 1 On the demonstration workstation desktop, open a Chrome browser and a new tab.
Step 2 In the address bar, type in the IP address 198.18.133.33.
Step 3 Login as root with a password of C1sco12345.
Example:
Step 4 Click the Virtual Machines branch to display the VMs.

Example:

59
Appendix
Step 5 You can restart any of the VMs manually if you find any issue with that VM, or use the following below to
restart all VMs.
a) On the workstation desktop, double-click FixMyDemo .

b) Enter 1 to Restart all switches and servers at the prompt.
Example:
Step 6 Monitor server status in vCenter until all of the switches and servers are back online.
Example:

60
Appendix
Note In this demo we use virtual switches (not physical hardware). After the Fix My Demo process has
finished, it will take approximately 10 minutes more to load the virtual switch operating systems.
You can monitor progress by opening an MTPuTTY session to Leaf-2 and watching the load process.

61
Appendix

62

B DCNM 114 Vxlan Evpn v1

Uploaded by

Copyright:

Available Formats

You might also like

B DCNM 114 Vxlan Evpn v1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B DCNM 114 Vxlan Evpn v1

Uploaded by

Copyright:

Available Formats

Cisco DCNM 11.

4 for VXLAN EVPN Multi-Site Deployments Lab v1

Import and Deploy Brownfield into DCNM 7

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

About This Demonstration

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

About This Solution

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Figure 5: Physical Topology

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION.

Step 1 Initiate your dCloud session. [Show Me How]

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Import and Deploy Brownfield into DCNM

Review existing Brownfield Configuration

Step 1 Double-click the MTPuTTY desktop shortcut.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 3 Enter show run | i bgp.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 6 Verify the operation of the fabric.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

c) Enter show nve vni.

d) Enter show nve peers.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 2 Click Fabric Builder and then, Create Fabric.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 5 In the Advanced tab, notice that Site ID field is 65002.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 1 In the Actions panel, click + Add switches.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 4 When the import completes, click Close.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 7 Click Save and Deploy.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

The Pending Config is shown.

Leaf-2 and Leaf-3 are now deployed.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 1 Return to MTPuTTY.

Bulk Creation of Networks and VRFs (Optional)

Step 1 Click Control > Interfaces.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 8 In the configuration dialog, click OK.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 1 Click Control > VRFs.

Step 3 Double-click the VRF file.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 1 Click Network View.

Step 2 Click Import.

Step 4 Select the imported Networks and then, click Continue.

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Cisco DCNM 11.4 for VXLAN EVPN Multi-Site Deployments Lab v1

Step 6 Click the Select all checkbox.

Step 7 Configure Leaf-2.

Step 8 Configure Leaf-3.