CloudPacket.
net OTV
OTV 2.5 Encapsulation OTV 2.5 Encapsulation(Detail)
Overlay 0 bit 16 bit 31 bit
802.1Q
ID Version IHL TOS Total Length
Identification Flags Fragment Offset
Underlay (50 Bytes of Overhead)
Outer Outer CRC
UDP OTV DMAC SMAC Etype Payload
MAC IP (new)
Time to Live Protocol = 17 Header Checksum
14 bytes 20 bytes 8 bytes 8 bytes 4 bytes
Source-site OTV Edge Device IP Address
OTV (2.5) Frame Encapsulation
Destination-site OTV Edge Device(or multicast) Address
DMAC SMAC 802.1Q Etype Payload CRC
6 bytes 6 bytes 4 bytes 2 bytes 46~9000 bytes 4 bytes Source Port = (random) Dest Port = 8472
Classical Ethernet Frame (Original L2 Frame) UDP Length UDP Checksum = 0
* 4 bytes of 802.1Q header have already been removed
R|R|R|R|I|R|R|R Overlay ID
Terminology
Instance ID Reserved
OTV Control Group Multicast address used to build adjacency with
Overlay
remote sites in the control plane. Frame in Ethernet or 802.1Q Format
OTV Data Group Used to encapsulate L2 multicast traffic across overlay.
IGMP V3 Needed to send (S,G) IGMP Report messages towards the DCI
network on the Join Interface. OTV Interfaces & Device Role
Extend VLANs VLANs that are explicitly allowed to be extended across Internal Interface Site facing interfaces of the
the overlay between sites. edge devices, carry VLANs extended through
OTV. Regular layer 2 interfaces, no OTV
Site VLAN used for communication between local OTV edge devices configuration required.
within a site to facilitate role election of Authoritative Edge Devices (AED).
Join Interface Uplink of the edge device,
Site Identifier a number which define the site, must be unique for each
point-to-point routed interface. Used to physically
site, any number between 0000.0000.0001 and ffff.ffff.ffff in MAC format.
“join” the overlay network. No OTV specific
Edge Device Performs all OTV functionality, Usually located at the configuration required.
Aggregation or Core Layer,
Overlay Interface Virtual/Tunnel interface with
Authoritative Edge Device OTV supports multiple edge devices per most of the OTV configuration, encapsulates
site, only single OTV device is elected as AED on a per-vlan bassis. layer 2 frames in IP unicast or multicast.
Layer 2 Extension Methods
Loop Multicast Fault
Data-Plane Control-Plane Multi-Homing
Prevention Optimisation Containment
Stop Unknown Unicast
EoMPLSoGRE IS-IS Native Block BPDU Selective Unicast Flooding
OTV(1.0) IGMP Snooping
STP Integration ARP Suppression
Block BPDU Stop Unknown Unicast
OTV(2.5) UDP, “VXLAN” IS-IS Native IGMP Snooping Selective Unicast Flooding
STP Integration ARP Suppression
VXLAN VXLAN Flood & Learn MC-LAG/VPC Block BPDU Flood none
VXLAN VXLAN BGP EVPN MC-LAG/VPC Block BPDU Flood Minimised Unknown Unicast
ARP Suppression
VPLS MPLS/GRE Flood & Learn MC-LAG/VPC Block BPDU none none
OTV Over Multicast Transport OTV Over Unicast Transport
Multicast transport require the configuration of a control-group OTV can run across a unicast only transport, a primary and
and data-group. This addresses should not overlap. secondary server can be configured for redundancy.
Control-Group required to build adjacencies and exchange Adjacency Servers unicast transport require one or more
MAC reachability information. adjacency servers. OTV devices register with the adjacency
Data-Group is a SSM delivery group for extending multicast servers which in turn provides each with an OTV neighbor
traffic across overlay. Any subnet within transport SSM range. list (oNL).
This study source was downloaded by 100000843231488 from CourseHero.com on 08-17-2022 11:28:25 GMT -05:00
last update May 12, 2016 (version 1.00) Page 1/2 Prepared By Shakib Shaygan
https://www.coursehero.com/file/88346749/OTV-Cheatsheet-V100pdf/
CloudPacket.net OTV
OTV Control Plane (Multicast Transport) OTV Neighnor Discovery (Multicast Transport)
Neighbor Discovery 1- OTV edge device sends IGMP report OTV Hello 2 OTV OTV 5 OTV Hello
Control Plane ASM Group Control Plane OTV
to join ASM group (edge use IGMP not PIM). 2- OTV hello OTV
OTV Hello IP A Mcast G 4
packets are generated for other OTV to build control plane
IP A IP B
adjacencies.3- Hello packet are encapsulated by adding extra OTV
ip header, source ip is from joined interface, destination is IGMP Report 1 1 IGMP Report
ASM multicast group. 4- with multicast transport network, West East
IGMP Report
every multicast frame will be replicated for each OTV device. OTV Hello IP A Mcast G OTV Hello IP A Mcast G
5- Receiver OTV will decapsulate the IP header. 6-hello are 3 1 5
pass it to control plane for processing.
IP C
OTV Hello IP A Mcast G 5
MAC Address Advertisement 1- Each OTV will learn local lan
MAC using internal interface, via traditional data plane learning. South
2. OTV will send all of its MAC table using OTV updated
OTV Replication
messages to ASM multicast group. 3- frames are replicated for Control Plane OTV OTV Hello 6 Encap/Decap
each OTV device that joined the group. 4- MAC reachability
information are imported into CAM table of OTV edge device. OTV Adjacencies (Unicast Transport)
OTV Control Plane (Unicast Transport) OTV Hello 1 OTV 2 OTV 5 OTV Hello
OTV Hello IP A IP B Control Plane OTV
OTV Control Plane
Adjacencies 1- Edge device generate hello packet, to build OTV Hello IP A IP C
adjacencies. 2- OTV device will replcate the hello packet for IP A IP B
OTV
each remote neighbor, each of this frame will be encapsulated,
adding external IP header.unicast frame then sent out the join
interface to L3 network. 3- Unicast frame are routed to West East
OTV Hello IP A IP B OTV Hello IP A IP B
destination. 4- reciving OTV will decapsulate the packet.
OTV Hello IP A IP C 4
5- hellos are passed to the control plane process. 2
IP C
MAC Address Advertisement 1- OTV edge learn MAC from OTV Hello IP A IP C
internal interfaces. 2- OTV update message contain MAC info
is created for each remote OTV neighbor & will OTV encapsulate South
3- OTV updates are routed in unicast transport to destination. OTV Replication
4- MAC info will be added to CAM table of remote OTV. Control Plane OTV OTV Hello 6 Encap/Decap
OTV Data Plane (Unicast Traffic) Data Plane Inter Site Layer 2 (Unicast Traffic)
Inter Site Layer 2 unicast traffic 1- L2 frame is recived from OTV OTV
client destined other sites, OTV mac address point to IP add Control Plane Control Plane
OTV MAC 1 MAC 3 IP A IP B 4 OTV
of remote OTV device instead of local interface. 2- OTV will 2 MAC 1 MAC 3 IP A IP B
encapsulate the original L2 frame. 3- OTV encapsulated frame
IP A IP B
is carried across the transport infrastructure and deliverd to OTV
remote OTV device. 4- Remote OTV will decapsulates the frame. 3
5- Edge device will perform another L2 lookup to find the MAC West VLAN MAC IF VLAN MAC IF East
6- The frame is delivered to the destination. 100 MAC 1 Eth1 100 MAC 1 IP A
100 MAC 2 Eth2 100 MAC 2 IP B
100 MAC 3 IP B 5 100 MAC 3 Eth3
OTV Configuration
100 MAC 4 IP B 1 100 MAC 4 Eth4
# Enable feature # Internal Interfaces MAC 1 MAC 3 MAC 1 MAC 3
feature otv interface ethernet 2/3
switchport mode trunk PC1 PC3
# OTV VLANs
vlan 99 # Local OTV Identifier
Troubleshooting & Debugging
name OTV-SITE-VLAN otv site-identifier 0x1
# Show command
vlan 10-15 otv site-vlan 99
Show otv [overlay x | adjacency | vlan | route | site]
name DATA-VLAN
Show otv isis [ traffic | adjacency | site]
# Overlay Interfaces
Show ip [mroute | igmp groups]
# Join Interfaces interface Overlay 1
interface ethernet 2/1 otv join-interface eth2/1
# Debug command
no switchport otv control-group 239.1.1.1
Debug otv isis adjacency
ip igmp version 3 otv data-group 232.1.1.0/28
Debug ip igmp group
ip address 1.1.1.1/24 otv extend-vlan 10-15
no shut
This study source was downloaded by 100000843231488 from CourseHero.com on 08-17-2022 11:28:25 GMT -05:00
last update May 12, 2016 (version 1.00) Page 2/2 Prepared By Shakib Shaygan
https://www.coursehero.com/file/88346749/OTV-Cheatsheet-V100pdf/
Powered by TCPDF (www.tcpdf.org)
