- Introduction
- Getting Started with Cisco Virtual Topology System
- Managing Local Users and Groups
- Managing Inventory
- Managing Resources
- Creating and Managing Admin Domains
- Managing Templates
- Managing Tenants
- Provisioning Overlay Networks
- Viewing Overlay Details
- Administering Cisco VTS
- Service Extension Templates-Supported Configuration
- Supported Underlay Configuration
- Provisioning Overlay Networks Using Cisco Virtual Topology System
- Creating Overlays
- Creating Network using VMware
- Creating Subnetwork using VMware
- Creating Routers using VMware
- Attaching Network to Router
- Attaching a Virtual Machine to Network
- Creating a Network using Cisco VTS GUI
- Creating Router using Cisco VTS GUI
- Assigning BVI Interface IP Address
- Extending Layer 2 Network Across Data Centers
- Enabling Global Route Leaking Service
Provisioning Overlay
Networks
This chapter has the following sections:
- Provisioning Overlay Networks Using Cisco Virtual Topology System
- Creating Overlays
- Creating Network using VMware
- Creating Subnetwork using VMware
- Creating Routers using VMware
- Attaching Network to Router
- Attaching a Virtual Machine to Network
- Creating a Network using Cisco VTS GUI
- Creating Router using Cisco VTS GUI
- Assigning BVI Interface IP Address
- Extending Layer 2 Network Across Data Centers
- Enabling Global Route Leaking Service
Provisioning Overlay Networks Using Cisco Virtual Topology System
Virtual Topology System enables overlay connectivity orchestrated through an SDN-based control plane. This ensures instant availability of computing and application workloads in the virtualized data center, and removes network provisioning challenges.
Cisco VTS uses VXLAN to overcome scale limits in the data center and to segment the network better. VXLAN is designed to provide the same Ethernet Layer 2 network services as VLAN does, but with greater extensibility and flexibility. The dependence on a Layer 3 underlay network allows VXLAN to take complete advantage of Layer 3 routing, equal-cost multipath (ECMP) routing, and link aggregation protocols. Virtual Topology System supports hardware and software VTEPs to segment the data center network.
Virtual Topology System supports both VXLAN overlays using the BGP EVPN control plane and VXLAN overlays using IP Multicast-based techniques.
Implementing VXLANs using MP-BGP EVPN based control plane to manage the VXLAN overlay provides a distributed network database, which enables federation and scaling. The BGP EVPN solution is the preferred option, and it can be flexibly implemented using the infrastructure policy constructs within the Virtual Topology System environment.
Virtual Topology System implements the highly scalable MP-BGP with the standards-based EVPN address family as the overlay control plane to:
-
Distribute attached host MAC and IP addresses and avoid the need for unknown unicast, and multicast traffic
-
Support multidestination traffic by either using the multicast capabilities of the underlay or using unicast ingress replication over a unicast network core (without multicast) for forwarding Layer 2 multicast and broadcast packets
-
Terminate Address Resolution Protocol (ARP) requests early
Control-plane separation is also maintained among the interconnected VXLAN networks. Capabilities such as route filtering and route reflection can be used to provide flexibility and scalability in deployment.
High-level Workflow for Establishing a VXLAN Overlay Network with Hardware and Software VTEPs using BGP EVPN
The following steps provide a high-level workflow for establishing a simple VXLAN overlay network with hardware and software VTEPs using a BGP EVPN control plane:
-
Prepare the physical environment to be managed by Cisco VTS to build virtual overlays. See the Prerequisites section in the Cisco VTS Installation Guide for details.
- Discover the network topology in the data center. See the Managing Inventory chapter of the Cisco VTS User Guide for details.
- Define Admin Domains. See Creating and Managing Admin Domains chapter of the Cisco VTS User Guide for details.
After you commit the changes to the network group, Virtual Topology System automatically pushes all the relevant configuration information to the respective leafs, Cisco IOS XRv route reflectors, and DCI gateways. At this point, the Admin Domain is ready to build overlay networks based on the intent defined by the service policy or through a Virtual Machine Manager (VMM) or orchestration environment.
For a detailed, illustrated example, see Cisco Virtual Topology System: Data Center Automation for Next-Generation Cloud Architectures White Paper.
Creating Overlays
As part of overlay provisioning, you may need to:
This can be done using the VMM or Cisco VTS GUI.
Using OpenStack
![]() Note | When you use a VMM such as OpenStack or VMware, the plugin will provide integration between the VMM and Cisco VTS. Once Tenant/ Network/ Subnets are created on the VMM, required overlay network(s) will automatically be created by Cisco VTS. |
Using VMware
For information about performing these tasks using VMWare, see the following sections:
Using Cisco VTS GUI
For information about creating Network and Router using Cisco VTS GUI, see the following sections:
Creating Network using VMware
To create a network:
Creating Subnetwork using VMware
Before you create the subnetwork, you need to create the network in which the subnetwork has to be created.
To create subnetworks:
Creating Routers using VMware
Attaching Network to Router
To attach a network and subnetwork to a router:
Attaching a Virtual Machine to Network
To create VMs:
Creating a Network using Cisco VTS GUI
To create a network from the Cisco VTS GUI:
| Step 1 | Go to . The Overlay / Network window appears. |
| Step 2 | Select the Tenant for which you to create the network. |
| Step 3 | Click Add (+) icon. |
| Step 4 | Enter the network name. This is mandatory. |
| Step 5 | Specify whether you want this to be an external network using the External Network toggle switch. |
| Step 6 | From the
Extend
Network drop down, select L2 or L3, depending on your requirement. If you
select L2, VPN Service becomes available for use.
For the L2 Extended Network, click the L2VPN tab and enter the EVI number. This can be an integer between1 and 65534. See Extending Layer 2 Network Across Data Centers. To extend an L3 network, choose L3 from the drop-down. |
| Step 7 | Select the Zone. |
| Step 8 | If the network is not external, enter the Static VNI. This can be an integer between 4096 and 65535. |
| Step 9 | Click
Save.
You can also add a subnet, and add port. |
Creating a Subnetwork
To create a subnetwork:
Attaching a Port
To do a port attach:
Creating Router using Cisco VTS GUI
To create a router using Cisco VTS GUI:
| Step 1 | Go to . The Overlay / Router window appears. |
| Step 2 | Click the Add (+) icon. The Add Router window appears. |
| Step 3 | Select the tenant from the Select Tenant drop-down list. |
| Step 4 | Select the Zone from the Select Zone drop-down list. |
| Step 5 | Enter the Static VNI. This can be an integer number between 4096 and 65535 |
| Step 6 | Enter the Router Name. |
| Step 7 | Select a template that you might want to associate with the router, using the find icon in the Template field. See Attaching Templates while Adding Routers for details. |
| Step 8 | Enter a VRF
name. This is optional. If this is left empty, when the Save button is clicked,
a default VRF name will be automatically generated.
|
| Step 9 | Select the router gateway from the Router Gateway drop-down list. When you select External GW from dropdown, two additional fields for Router Gateway IPv4 and Router Gateway IPv6 get displayed. These are optional. |
| Step 10 | Click Add (+) icon. The Add Interface popup appears. |
| Step 11 | Select the subnet from the drop down list, and click OK. |
| Step 12 | Click Save in the Add Router window to save the router and its interface. |
Assigning BVI Interface IP Address
To assign a Bridge Group Virtual Interface (BVI) IP address:
| Step 1 | Go to Overlay > Network. The Overlay /Network page appears. |
| Step 2 | Click the + icon. The Add Network page appears. |
| Step 3 | Enter the Network name. |
| Step 4 | Check the External Network check box. |
| Step 5 | Click the + icon to assign a Subnet to the network created. |
| Step 6 | Go to Overlay > Router. The Overlay /Router page appears. |
| Step 7 | Click the + icon. The Add Router page appears. |
| Step 8 | Click the + icon to assign an Interface to the Subnet created. Note: This subnet belongs to the Internal network, and excludes the External network. |
| Step 9 | Select an external network from the Router Gateway drop-down list. Router Gateway IP address field appears. |
| Step 10 | Assign the Router Gateway IP address for the selected external network for BVI interface and click Save. |
| Step 11 | Verify whether the configuration is pushed to DCI and the IP address is assigned to BVI interface. |
Extending Layer 2 Network Across Data Centers
If there are multiple data center PODs managed separately, (one instance of Cisco VTS managing only one POD) and connected over the WAN/core using a BGP-EVPN MPLS cloud, the L2VNI routes can be distributed from within the BGP-EVPN VXLAN fabric by stitching them to BGP-EVPN MPLS routes over the WAN/core side. On the other side (POD) the BGP-EVPN MPLS routes can be stitched onto BGP-EVPN VXLAN routes.
To complete the L2VNI extension workflow:
![]() Note |
|
| Step 1 | Complete the Day Zero configuration with route policies/filters and DCI redundancy group. |
| Step 2 | Go to Admin Domain > DCI Interconnect profile, and create an MPLS L2 VPN profile. |
| Step 3 | Create the admin domain, add the MPLS L2 VPN profile. Extend L2 GW to DC GW. After you save, the neighbor details are pushed under BGP. |
| Step 4 | In Overlay > Network screen, on the External Network toggle switch. |
| Step 5 | Select L2 from the drop-down. |
| Step 6 | Select L2VPN tab, enter the EVI number. |
| Step 7 | Specify the subnets, then do a port attach. |
Enabling Global Route Leaking Service
The global route leaking feature enables you to provide internet/external connectivity to the host inside the Data Center. This feature allows associating/dissociating of Global Route Leaking (also known as Global Routing Table [GRT]) Service to/from the Overlay Router. Once the Overlay Router gets realized (that is, when port attach happens on interface), VTS pushes the policies configured as part of GRT associated to a router. Route policies for core facing/external facing routes and route policies for fabric facing/internal routes will be pushed.
![]() Note | Global Route Leaking feature is available only when an external router gateway is selected. |
Router cannot get deleted if the GRT is still attached. Admin needs to disassociate the GRT profile before deleting the router.
You can add create and enable global route leaking service while you create a router, or at any other point in time.
| Step 1 | Configure the
import and export route policy on DCI and perform a sync from. For
example:
route-policy data-center-vrf-export-policy
if destination in (101.1.1.0/24 eq 32, 102.1.1.0/24 eq 32, 103.1.1.0/24 eq 32, 104.1.1.0/24 eq 32, 105.1.1.0/24 eq 32) then
pass
endif
end-policy
!
route-policy data-center-vrf-import-policy
if destination in (60.0.0.0/24) then
pass
endif
end-policy
See Synchronizing Configuration for details about performing a sync from operation. | ||
| Step 2 | Create Fabric
and Core Facing Route Policy (underlay policy for Internet connectivity). This
is not mandatory. For example:
route-policy vts-route-policy
pass
end-policy
| ||
| Step 3 | Create Profile for Internet from Admin Domains > DCI Interconnect Profiles. See Creating DCI Interconnect Profiles. | ||
| Step 4 | Attach the
internet profile to DCI in the admin domain. Configuration is pushed by VTS on
saving the admin domain. For example, the below configuration, which has the
neighbor details, will be pushed under router BGP on the DCI.
router bgp 200
bgp router-id 18.18.18.18
.
.
.
neighbor 5.1.1.1
remote-as 400
ebgp-multihop 255
update-source Loopback2
address-family ipv4 unicast
route-policy vts-route-policy in
route-policy vts-route-policy out
| ||
| Step 5 | Go to . The Overlay / Router window appears. | ||
| Step 6 | Click Add (+). The Add Router page is displayed. | ||
| Step 7 | Click Global
Route Leaking tab.
| ||
| Step 8 | Click Add (+). The New Global Route Leaking popup window appears. | ||
| Step 9 | Enter a name (this is mandatory), and description. | ||
| Step 10 | In the Policies
pane, enter at least one policy for the address family.
| ||
| Step 11 | Click Add. The Global Route Leaking service gets added. You can click on the name to get a summary of the global route leaking service you created. | ||
| Step 12 | Click Save. Once the service is attached to the router, all the networks for the router will be leaked outside. To disassociate the service you need to select the Detach button and save the edit. |

Feedback