Kireeti Kompella Bhupesh Kothari Thomas Spencer

Slides:



Advertisements
Similar presentations
APNOMS03 1 A Resilient Path Management for BGP/MPLS VPN Jong T. Park School of Electrical Eng. And Computer Science Kyungpook National University
Advertisements

Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 BGP based Virtual Private Multicast Service Auto-Discovery and Signaling.
1 Analysis of VPLS Deployment R. Gu, J. Dong, M. Chen, Q. Zeng (Huawei) Z. Liu (China Telecom) IETF80 L2VPN Mar Prague draft-gu-l2vpn-vpls-analysis-00.
Nortel Confidential Information 1 MPLS & Ethernet OAM Interworking (draft-mohan-pwe3-mpls-eth-oam-iwk) L2VPN WG, IETF-71 (Philadelphia) Mar 13, 2008 Dinesh.
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 181th IETF - Quebec VPLS PE Model with E-Tree Support Yuanlong Jiang.
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 79th IETF - Beijing VPLS PE Model with E-Tree Support Yuanlong Jiang.
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 80th IETF - Prague VPLS PE Model with E-Tree Support Yuanlong Jiang.
BGP based Multi-homing in VPLS IETF-75
Update on LDP Extensions for Optimized MAC Address Withdrawal in H-VPLS draft-ietf-l2vpn-vpls-ldp-mac-opt-04 Geraldine Calvignac
BGP based Multi-homing in Virtual Private LAN Service
Requirements for MEF E-Tree Support in VPLS draft-key-l2vpn-vpls-etree-reqt-02 Presenter : Manuel Paul, Deutsche Telekom IETF79, Nov 2010 Beijing, China.
Update on LDP Extensions for Optimized MAC Address Withdrawal in H-VPLS draft-ietf-l2vpn-vpls-ldp-mac-opt-03.
© 2009 AT&T Intellectual Property. All rights reserved. Multicast Redux: A First Look at Enterprise Multicast Traffic Elliott Karpilovsky 1, Lee Breslau.
MPLS VPN.
Use of BGP and MPLS VPNs: A Case Study
BGP VPLS Auto Site ID Bhupesh Kothari
BGP L2VPN Auto-discovery and Signaling
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPN Technology Introducing the MPLS VPN Routing Model.
Dual Homing Experiment Christian Huitema Architect Windows Networking & Communications Microsoft Corporation.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—5-1 MPLS VPN Implementation Configuring BGP as the Routing Protocol Between PE and CE Routers.
Deployment of MPLS VPN in Large ISP Networks
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public Presentation_ID 1 BGP Diverse Paths draft-ietf-grow-diverse-bgp-paths-dist-02 Keyur Patel.
Campus Networking Workshop
Internetworking II: MPLS, Security, and Traffic Engineering
1 © 2000, Cisco Systems, Inc. Integrated-ISIS Route Leaking.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 draft-boutros-l2vpn-vpls-active-active-00.txt.
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 Multicast in BGP/MPLS VPNs draft-ietf-l3vpn-2547bis-mcast-00.txt.
Entire Routes Reflecting capability draft-zhang-idr-bgp-entire-routes-reflect-00.txt Zhang Renhai :
© J. Liebeherr, All rights reserved 1 Border Gateway Protocol This lecture is largely based on a BGP tutorial by T. Griffin from AT&T Research.
Consensus Routing: The Internet as a Distributed System John P. John, Ethan Katz-Bassett, Arvind Krishnamurthy, and Thomas Anderson Presented.
1 Interdomain Routing Protocols. 2 Autonomous Systems An autonomous system (AS) is a region of the Internet that is administered by a single entity and.
MPLS L3 and L2 VPNs Virtual Private Network –Connect sites of a customer over a public infrastructure Requires: –Isolation of traffic Terminology –PE,
Chapter 27 Q and A Victor Norman IS333 Spring 2015.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.2—5#-1 MPLS VPN Implementation Configuring OSPF as the Routing Protocol Between PE and CE Routers.
Draft-ietf-mpls-entropy-label ietf 82. Entropy Labels Generalize what’s been done in the fat PW draft – Define general characteristics of entropy labels.
1 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential Session Number Presentation_ID Advanced BGP Convergence Techniques Pradosh Mohapatra.
L3VPN WG2013-Nov-71 Ingress Replication P-Tunnels in MVPN I ngress Replication has always been one of the P-tunnel technologies supported by MVPN But there’s.
IETF San Francisco Multicast-only Fast ReRoute (MoFRR)
Advertising Equal Cost Multi-Path Routes in BGP Manav Bhatia Samsung India Software Operations, Bangalore – India July 17, th IETF - Vienna draft-ecmp-routes-in-bgp-00.txt.
Lecture 4: BGP Presentations Lab information H/W update.
Border Gateway Protocol (BGP) W.lilakiatsakun. BGP Basics (1) BGP is the protocol which is used to make core routing decisions on the Internet It involves.
More on Internet Routing A large portion of this lecture material comes from BGP tutorial given by Philip Smith from Cisco (ftp://ftp- eng.cisco.com/pfs/seminars/APRICOT2004.
Inter AS option D (draft-mapathak-interas-option-d-00) Manu Pathak Keyur Patel Arjun Sreekantiah November 2012.
Using BGP between PE and CE in EVPN draft-li-l2vpn-evpn-pe-ce-01 Zhenbin Li, Junlin Zhuang, Shunwan Zhuang (Huawei Technologies) IETF 90, Toronto, Canada.
1MPLS QOS 10/00 © 2000, Cisco Systems, Inc. rfc2547bis VPN Alvaro Retana Alvaro Retana
R-BGP: Staying Connected in a Connected World Nate Kushman Srikanth Kandula, Dina Katabi, and Bruce Maggs.
Copyright © 2004 Juniper Networks, Inc. 1 Operational Aspects of Virtual Private LAN Service Kireeti Kompella.
OSPFv3 as a PE-CE Routing Protocol
MPLS VPNs by Richard Bannister. The Topology The next two slides display both the physical and logical topology of our simple example network –Please.
D1 - 08/12/2015 Requirements for planned maintenance of BGP sessions draft-dubois-bgp-pm-reqs-02.txt
Kireeti Kompella draft-kompella-mpls-rmr-01
VPLS Multi-homing draft-ietf-l2vpn-vpls-multihoming-03 Kothari, Kompella, Hendrickx, Balus, Uttaro.
Applicability of Existing Solutions to the Problem Space draft-takeda-l1vpn-applicability-03.txt.
1 Chapter 4: Internetworking (IP Routing) Dr. Rocky K. C. Chang 16 March 2004.
2547 egress PE Fast Failure Protection draft-minto-2547-egress-node-fast-protection-00 Jeyananth Minto Maciek
19 March 2003Page 1 BGP Vulnerabilities Draft March 19, 2003 Sandra Murphy
Redundancy. Single point of failure Hierarchical design produces many single points of failure Redundancy provides alternate paths, but may undermine.
1 QOS ©2000, Cisco Systems, Inc. BGP MED Churn Daniel Walton

Border Gateway Protocol
John Scudder October 24, 2000 BGP Update John Scudder October 24, 2000.
MPLS VPNs by Richard Bannister.
EVPN Interworking with IPVPN
Dynamic Routing and OSPF
draft-sajassi-bess-evpn-ip-aliasing- 00.txt
draft-sajassi-bess-evpn-vpls-all-active- 00.txt
BGP-Based SPF IETF 98, Chicago
Computer Networks Protocols
draft-kompella-spring-rmr
EVPN Interworking with IPVPN
Presentation transcript:

Kireeti Kompella Bhupesh Kothari Thomas Spencer BGP VPLS Multi-homing Kireeti Kompella Bhupesh Kothari Thomas Spencer

Problem Statement CE2 PE3 PE1 BGP VPLS CE1 PE2 PE4 CE3 CE1 wants resilient connectivity as a VPLS CE, so it is dual-homed to PE1 and PE2 Simple dual connectivity leads to loops and duplicate packets. One answer is to run STP on CE1

Solution Let PE1 and PE2 know that they are connected to the same site Configure the VPLS VE ID to be the same Use BGP path selection to arbitrate among PE1 and PE2 as to which should be used to reach CE1 And which forwards packets from CE1

Multi-homing in 4364 VPNs CE2 LP=200 PE3 PE1 BGP VPN 10.1/16 CE1 CE1 wants resilient connectivity as a VPN CE, so it is dual-homed to PE1 and PE2 Choices: pick one of PE1 or PE2 to service CE1; or use both (ECMP)

Differences in VPLS Cannot do ECMP: must pick one of PE1 or PE2 (say PE1), and must do so consistently from all “other” PEs Both PE3 and PE4 must both choose PE1 In particular, the “losing” PE (here, PE2) must know that it lost The “winning” PE (here, PE1) is called the ‘designated PE’

Changes to BGP Path Selection When are prefixes comparable? What part of the NLRI is to be compared? Who wins, and how can we ensure that everyone picks consistently? Simple answer: don’t use IGP metric in the tie-breaking rules Control? (via Local Preference) Details in draft

Result Designated PE forwards packets from and to CE Non-designated PEs (losing PEs) drop packets from CE as well as from other PEs The effect is as if CE was single-homed to just the designated PE

Re-homing If the designated PE fails, or if the CE-PE link breaks, the designated PE withdraws its “route” All other PEs (including non-designated PEs) redo path selection and pick a new designated PE Traffic is re-established via the new PE

Effect of Route Reflection CE2 PE3 PE1 RR CE1 PE2 PE4 CE3 If there is an RR in the path, the RR also does path selection; this can affect convergence. To get around this, use different RDs on each PE (as in 4364 VPNs)

Status RFC 4761, section 3.5 talks about multi-homing and how to accomplish it However, there aren’t enough details on how prefixes are to be compared, and how BGP path selection should be done This draft attempts to rectify this

Questions?