OTV PPT by NETWORKERS HOME
-
Upload
networkershome -
Category
Education
-
view
432 -
download
10
Transcript of OTV PPT by NETWORKERS HOME
![Page 1: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/1.jpg)
OTV
![Page 2: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/2.jpg)
Simplify DCI
![Page 3: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/3.jpg)
Agenda
• Distributed Data Centers: Goals and Challenges
• OTV Architecture Principles
• OTV Design Considerations & New Features
![Page 4: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/4.jpg)
Distributed Data Centers Goals
• Ensure business continuity
• Distributed applications
• Seamless workload mobility
• Maximize compute resources
![Page 5: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/5.jpg)
Traditional Layer 2 Extension
EoMPLS
VPLSDark Fiber
![Page 6: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/6.jpg)
Challenges in Traditional Method
![Page 7: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/7.jpg)
Technology Pillars
![Page 8: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/8.jpg)
Technology Pillars
![Page 9: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/9.jpg)
Simplify DCI
•Nexus 7000 First platform to support OTV (since 5.0 NXOS Release)
•ASR 1000 Now also supporting OTV (since 3.5 XE Release)
![Page 10: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/10.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation–New Feature –Multi-homing –L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 11: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/11.jpg)
Terminology
OTV Devices and Interfaces Edge Device –Performs all OTV functionality –Usually located at the Aggregation
Layer or at the Core Layer –Support for multiple OTV Edge
Devices (multi-homing) in the same site
Internal Interface –Site facing Interfaces of the Edge
Devices –Carry VLANs extended through OTV –Regular Layer 2 interfaces –No OTV configuration required –Supports IPv4 & IPv6
![Page 12: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/12.jpg)
Terminology
OTV Devices and Interfaces Join Interface –One of the uplink of the Edge Device –Point-to-point routed interface (physical
interface, sub-interface or port-channel supported)
–Used to physically “join” the Overlay network
–No OTV specific configuration required –IPv4 only
Overlay Interface –Virtual interface with most of the OTV
configuration –Logical multi-access multicast-capable
interface –Encapsulates Layer 2 frames in IP unicast
or multicast
![Page 13: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/13.jpg)
OTV Control Plane
Building the MAC Tables
• No unknown unicast flooding (selective unicast flooding in 6.2)
• Control Plane Learning with proactive MAC advertisement
• Background process with no specific configuration
• IS-IS used between OTV Edge Devices
![Page 14: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/14.jpg)
OTV Control Plane
Neighbor Discovery and Adjacency Formation Before any MAC address can be advertised the
OTV Edge Devices must: ‒Discover each other ‒Build a neighbor relationship with each other
Neighbor Relationship built over a transport infrastructure:
‒Multicast-enabled (all shipping releases) ‒Unicast-only (from NX-OS release 5.2 & IOS-XE 3.9)
![Page 15: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/15.jpg)
OTV Control Plane
• Neighbor Discovery (over Multicast Transport)
![Page 16: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/16.jpg)
OTV Control Plane (Multicast Transport)
![Page 17: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/17.jpg)
OTV Control Plane (Multicast Transport)
![Page 18: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/18.jpg)
OTV Control PlaneMAC Address Advertisements (Multicast-Enabled Transport)
• Every time an Edge Device learns a new MAC address, the OTV control plane will advertise it together with its associated VLAN IDs and IP next hop.
• The IP next hops are the addresses of the Edge Devices through which these MACsaddresses are reachable in the core.
• A single OTV update can contain multiple MAC addresses for different VLANs.
• A single update reaches all neighbors, as it is encapsulated in the same ASM multicastgroup used for the neighbor discovery.
Core
IP A
West
East
3 New MACs are learned on VLAN 100
Vlan 100 MAC A
Vlan 100 MAC B
Vlan 100 MAC C
South-East
VLAN MAC IF
100 MAC A IP A
100 MAC B IP A
100 MAC C IP A
4
OTV update is replicated by the core
3
3
2
VLAN MAC IF
100 MAC A IP A
100 MAC B IP A
100 MAC C IP A
4
3 New MACs are learned on VLAN 100
1
![Page 19: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/19.jpg)
Multicast Transport
OTV Control and Data Plane over Multicast Transport
Use a High-Available Multicast Rendez-Vous Point (RP) configuration
‒PIM Anycast (RFC4610) or MSDP (Multicast Source Discovery Protocol)
•Requirements to Control Plane ‒PIM Any-Source-Multicast (ASM) Sparse-
Mode
•Requirements to Data Plane ‒PIM Source-Specific-Multicast (SSM) or BiDir
![Page 20: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/20.jpg)
OTV Control PlaneNeighbor Discovery (Unicast-only Transport)
• Ideal for connecting a small number of sites
• With a higher number of sites a multicast transport is the best choice
![Page 21: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/21.jpg)
OTV Control Plane
CLI Verification Establishment of control plane adjacencies between OTV Edge Devices
(multicast or unicast transport):
Unicast MAC reachability information:
![Page 22: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/22.jpg)
TransportInfrastructure
OTV Data Plane: Inter-Site Packet Flow
OTV OTV OTV OTV
MAC TABLE
VLAN MAC IF
100 MAC 1 Eth 2
100 MAC 2 Eth 1
100 MAC 3 IP B
100 MAC 4 IP B
MAC 1 MAC 3
IP A IP BMAC 1 MAC 3
MAC TABLE
VLAN MAC IF
100 MAC 1 IP A
100 MAC 2 IP A
100 MAC 3 Eth 3
100 MAC 4 Eth 4
Layer 2Lookup
5
IP A IP BMAC 1 MAC 3MAC 1 MAC 3Layer 2Lookup
1 Encap
2
Decap
4
MAC 1 MAC 3West Site
MAC 1MAC 3
EastSite
1. Layer 2 lookup on the destination MAC. MAC 3 is reachable through IP B.
2. The Edge Device encapsulates the frame.3. The transport delivers the packet to the Edge
Device on site East.
4. The Edge Device on site East receives and decapsulates the packet.
5. Layer 2 lookup on the original frame. MAC 3 is a local MAC.
6. The frame is delivered to the destination.
3
6
IP A IP B
![Page 23: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/23.jpg)
Source
OTV
OTV Data Plane: Multicast DataMulticast State Creation
Receiver
OTV
IP A
IP B
West East
OIL-List
Group IF
Gs Gd Overlay
Client IGMP snoop
2
Client IGMPreport to join
Gs
1
IGMPv3 report to join (IP A, Gd) , the SSM group in the
Core.
3.2
Receive GM-Update Update OIL
4
SSM Tree for Gd
From Right to Left
1. The multicast receivers for the multicast group “Gs” on the East site send IGMP reports to join the multicast group.
2. The Edge Device (ED) snoops these IGMP reports, but it doesn’t forward them.
3. Upon snooping the IGMP reports, the ED does two things:
1. Announces the receivers in a Group-Membership Update (GM-Update) to all EDs.
2. Sends an IGMPv3 report to join the (IP A, Gd) group in the core.
4. On reception of the GM-Update, the source ED will add the overlay interface to the appropriate multicast Outbound Interface List (OIL).
It is important to clarify that the edge devices join the core multicast groups as hosts, not as routers!
GM-Update3.1
Multicast-enabled Transport
![Page 24: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/24.jpg)
Source
OTV
OTV Data Plane: Multicast DataMulticast Packet Flow
Receiver
OTV
IP A
IP B
West EastIP C
Receiver
South
OTV
OIF-List
Group IF
Gs Gd Overlay
Encap2
Lookup
1
IPs Gs
IP A GdIPs Gs
TransportReplication
3
IP A GdIPs Gs IP A GdIPs Gs
4
4
IP A GdIP s Gs
IPs Gs
IPs Gs
Decap 5
Decap 5
Multicast-enabled Transport
![Page 25: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/25.jpg)
OTV Data Plane Encapsulation
•42 Bytes overhead to the packet IP MTU size (IPv4 packet)
•Outer IP + OTV Shim - Original L2 Header (w/out the .1Q header)
•802.1Q header is removed and the VLAN field copied over to the OTV shim header
•Outer OTV shim header contains VLAN, overlay number, etc.
•Consider Jumbo MTU Sizing
![Page 26: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/26.jpg)
Configuration
Overlay Transport Virtualization (OTV) in a Nutshell
•OTV is a MAC-in-IP method that extends Layer 2
connectivity across a transport network infrastructure
•OTV supports both multicast and unicast-only transport networks
•OTV uses ISIS as the control protocol
•OTV on Nexus7000 does not encrypt encapsulated payload
![Page 27: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/27.jpg)
Edge Device
• Performs OTV functions
• Multiple OTV Edge Devices can exists at each site
• OTV requires the Transport Services (TRS) license
• Creating non default VDC’s requires Advanced Services license
![Page 28: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/28.jpg)
Internal Interfaces
• Regular layer 2 interfaces facing the site
• No OTV configuration required
• Supported on M-series modules
• Support for F1 and F2e starting in 6.2
• Support for F3 in 6.2(6)
![Page 29: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/29.jpg)
Join Interface
• Uplink on Edge device that joins the Overlay
• Forwards OTV control and data traffic
• Layer 3 interface • Supported on M-
series modules • Supported on F3
modules in 6.2(6)
![Page 30: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/30.jpg)
Overlay Interface
• Virtual Interface where the OTV configurations are applied
• Multi-access multicast-capable interface
• Encapsulates Layer 2 frames
![Page 31: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/31.jpg)
AED
• OTV supports multiple edge devices per site
• A single OTV device is elected as AED on a per-vlan basis
• The AED is responsible for advertising MAC reachability and forwarding traffic into and out of the site for its VLANs
![Page 32: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/32.jpg)
OTV Overview
![Page 33: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/33.jpg)
Site VLAN and Site Identifier
•Site VLAN needs to be configured and active even if you do not have multiple OTV devices in the same site. The site VLAN should not be extended across overlay
•Site Identifier can be any number between 0000.0000.0001 and ffff.ffff.ffff. Value will always be displayed in MAC format
•Site Identifier must be unique for each site
![Page 34: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/34.jpg)
Site VLAN and Site Identifier
![Page 35: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/35.jpg)
Multicast Transport: Overlay
•Multicast Transport requires the configuration of a control-group and data-group
•Adjacencies are built and MAC reachability information is exchanged over the control-group
•The data-group is a source specific multicast (SSM) delivery group for extending multicast traffic across the overlay. It can be configured as any subnet within the transport’s SSM range.
•The data-group range should not overlap with the control-group
![Page 36: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/36.jpg)
Multicast Transport
![Page 37: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/37.jpg)
Multicast Enabled Core
![Page 38: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/38.jpg)
Multicast Transport
![Page 39: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/39.jpg)
Multicast Transport Full Picture
![Page 40: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/40.jpg)
Unicast Transport: Overlay•OTV can run across a unicast only transport
•Unicast Transport requires the configuration of one or more adjacency servers. OTV devices register with the adjacency server which in turn provides each with an OTV Neighbor List (oNL).
•Think of the adjacency server as a special process running on a generic OTV edge device
•A primary and secondary adjacency server can be configured for redundancy
![Page 41: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/41.jpg)
Adjacency Server•Primary and Secondary Adjacency servers are stateless;
every OTV client must register with both servers
•OTV client will not process the oNL from the secondary server while the primary server is still active
•OTV uses graceful exit of Adjacency Servers. If the primary server is rebooted or reconfigured, it can notify the OTV clients allowing them to immediately use the secondary
![Page 42: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/42.jpg)
Primary Adjacency Server Overlay
![Page 43: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/43.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation –New Feature–Multi-homing –L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 44: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/44.jpg)
Spanning-Tree and OTV
Site Independence • Site transparency: no changes to the
STP topology
• Total isolation of the STP domain
• Default behavior: no configuration is required
• BPDUs sent and received ONLY on Internal Interfaces
![Page 45: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/45.jpg)
Unknown Unicast and OTV No Longer Unknown Unicast
Storms Across the DCI
• No requirements to forward
unknown unicast frames
• Assumption: end-host are not silent or uni-directional
• Default behavior: no configuration is required
![Page 46: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/46.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation –New Feature–Multi-homing –L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 47: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/47.jpg)
New Features
•F1/F2E used as Internal Interfaces
•Selective Unicast Flooding
•Dedicated Data Broadcast Group
•OTV VLAN Translation
•OTV Fast Convergence
•Tunnel Depolarization with Secondary IP
•Loopback Join-Interface
![Page 48: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/48.jpg)
New Feature
6.2(2) and above
•F1 or F2E can be mixed with M-series VDC and used as OTV internal interface
•Unicast MAC address can be statically configured to flood across OTV
•Dedicated Broadcast Group
–Allows separation and prioritization of control traffic vs. data plane broadcast traffic
![Page 49: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/49.jpg)
OTVSupported Line Card Topologies :: NX-OS 6.1 and Prior Releases
• OTV VDC must use only M-Series ports for both Internal and Join Interfaces[M1-48, M1-32, M1-08, M2-Series]
• OTV VDC Types (M-only)• Aggregation VDC Types (M-only, M1-F1 or F2/F2E)
Aggregation VDC
![Page 50: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/50.jpg)
OTVSupported Line Card Topologies :: NX-OS 6.2 and Later Releases
• OTV VDC Join Interfaces must use only M-Series ports[M1-48, M1-32, M1-08, M2-Series]
• OTV VDC Internal Interfaces can use M-Series, F1 and F2E ports (F1 and F2E must be in Layer 2 proxy mode)• OTV VDC Types (M-only, M1-F1, M1-F2E)• Aggregation VDC Types (M-only, M1-F1, M1-F2E, F2, F2E, F2F2E)
Aggregation VDC
![Page 51: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/51.jpg)
OTV VLAN Translation
• VLAN translation allows OTV to map a local VLAN to a remote VLAN.
![Page 52: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/52.jpg)
OTV Fast Convergence
•Previously, AED election ran independently on each edge device which required a short black-holing timer to prevent multiple active AEDs for a VLAN
•AED Server: centralized model where a single edge device runs the AED election for each VLAN and assigns VLANs to edge devices.
•Per-VLAN AED and Backup AED assigned and advertised to all sites
•Fast Remote Convergence: on remote AED failure, OTV routes are updated to new AED immediately
•Fast Failure Detection: Detect site VLAN failures faster with BFD and core failures with route tracking
![Page 53: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/53.jpg)
OTV Fast Convergence
![Page 54: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/54.jpg)
OTV Fast Convergence
![Page 55: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/55.jpg)
OTV Fast Convergence
![Page 56: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/56.jpg)
Loopback Join-Interface
Physical Join Interface Limitations •Bandwidth to the core is limited to one physical link or port-channel •Changes to join-interface will churn all OTV overlay states, since the
overlay encapsulation for all routes need to be updated •PIM cannot be enabled on the join-interface, since the OTV solution
assumes it's an IGMP host interface •Unable to utilize the redundancy of multiple uplinks when available,
and the flexibility of dynamic unicast routing convergence on uplink failures
•If join-interface goes down, the connectivity to the core is broken. User intervention is needed to provide alternate core connectivity
![Page 57: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/57.jpg)
Loopback Join-Interface
![Page 58: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/58.jpg)
Tunnel Depolarization with Secondary IP
• All encapsulated traffic between AED’s have same source and destination IP’s limiting the advantages of Etherchannel and ECMP load-balancing
![Page 59: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/59.jpg)
• Secondary IPs allows OTV to forward traffic between multiple endpoints to prevent polarization along the path
Tunnel Depolarization with Secondary IP
![Page 60: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/60.jpg)
ARP Neighbor-Discovery (ND) Cache
• ARP cache maintained in Edge Device by snooping ARP replies
• First ARP request is broadcasted to all sites. Subsequent ARP requests are replied by local Edge Device
• Timeout can be adjusted (as per NX-OS 6.1(1))
• Drastic reduction of ARP traffic on DCI
• ARP spoofing can be disabled
• IPv4 only feature
• Default behavior: no configuration is required
![Page 61: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/61.jpg)
Site VLAN and Site Identifier
Dual Site Adjacency, 5.2(1) and above
1. Site Adjacency established across the site vlan
2. Overlay Adjacency established via the Join interface across Layer 3 network
![Page 62: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/62.jpg)
Internal Link
• If a communication problem occurs on the site vlan, each OTV device can still advertise AED capabilities across overlay to prevent an active/active scenario
![Page 63: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/63.jpg)
Join Interface Down
• Dual Site Adjacency also has mechanism for advertising AED capabilities on local failure to improve convergence
• Join interface down
![Page 64: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/64.jpg)
Interface VLAN Down
• Dual Site Adjacency also has mechanism for advertising AED capabilities on local failure to improve convergence
• Join interface down • Internal Vlans down
![Page 65: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/65.jpg)
AED Down
• Dual Site Adjacency also has mechanism for advertising AED capabilities on local failure to improve convergence
• Join interface down • Internal Vlans down • AED down or initializing
![Page 66: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/66.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation –New Feature–Multi-homing –L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 67: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/67.jpg)
OTV Multi-homing
![Page 68: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/68.jpg)
OTV Multi-homing
![Page 69: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/69.jpg)
OTV Multi-homing
![Page 70: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/70.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation –New Feature–Multi-homing –Mobility–L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 71: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/71.jpg)
OTV and MAC Mobility
![Page 72: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/72.jpg)
OTV and MAC Mobility
![Page 73: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/73.jpg)
OTV and MAC Mobility
![Page 74: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/74.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation –New Feature–Multi-homing –Mobility–L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 75: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/75.jpg)
L2 Multicast Traffic between Sites
![Page 76: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/76.jpg)
L2 Multicast Traffic between Sites
![Page 77: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/77.jpg)
L2 Multicast Traffic between Sites
![Page 78: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/78.jpg)
L2 Multicast Traffic between Sites
![Page 79: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/79.jpg)
L2 Multicast Traffic between Sites
![Page 80: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/80.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation –New Feature–Multi-homing –Mobility–L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 81: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/81.jpg)
QOS and OTV
![Page 82: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/82.jpg)
QOS and OTV
![Page 83: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/83.jpg)
Agenda
Distributed Data Centers: Goals and Challenges OTV Architecture Principles –Control Plane and Data Plane –Failure Isolation –New Feature–Multi-homing –Mobility–L2 Multicast Forwarding –QoS and Scalability –Path Optimization OTV Design Considerations & New Features
![Page 84: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/84.jpg)
Path Optimization
![Page 85: OTV PPT by NETWORKERS HOME](https://reader030.fdocuments.net/reader030/viewer/2022020106/55a79def1a28ab4d338b45be/html5/thumbnails/85.jpg)
Question ???