Practical OTV
Practical OTV
————-
This post is all about OTV (Overlay Transport Virtualization) on the CSR1000v.
I wanted to create the post because there are alot of acronyms and terminology involved.
A secondary objective was to have a “real” multicast network in the middle, as the examples I have seen around the web, have used a direct P2P network for the DCI.
Instead, I wanted to have full multicast running in the SP core in order to gain a full understanding of the packet forwarding and encapsulation.
First off, lets talk about the topology I will be using:
Datacenters:
————
We have 2 Datacenters, one represented by Site 1 and the other by Site 2.
In the middle, we have what is in all respects a SP provider network. In your environment, this may or may not be your own transport network.
In site 1, CSR-1 is our “server”, basically all thats configured on it is an IP address (192.168.100.1/24) on its G1 interface.
SW-9 is our L2 switch, which is configured with 2 VLAN’s (Vlan 100 (SERVER-VLAN) and Vlan 900 (SITE-VLAN)). The port (e0/0) going to CSR-1 is configured as an access-port in Vlan 100.
The ports Continue reading

The platform uses the MEF 63 Optical Transport Services specification focused on Layer 1 orchestration but is not intended as an end-to-end orchestrator.
Employees recently posted a blog protesting the company's plans to bid on the $10 billion, 10-year contract to provide cloud services for all branches of the military.
The work is part of a wider drive to develop 5G in India, boosted by the Centre of Excellence and Innovation Lab for 5G at the Indian Institute of Technology, which Ericsson established in Delhi in July.