80 likes | 282 Views
MPLS Over L3VPN. Ron Bonica. Reference Model and Requirement. Customer LSP. 1. PE1. P1. CE2. CE1. PE1. C0. C3. Service Provider L3VPN. Customer VPN Site B. Customer VPN Site A. The Problem. Customer LSP. 1. PE1. P1. CE2. CE1. PE1. C0. C3. Service Provider L3VPN.
E N D
MPLS Over L3VPN Ron Bonica
Reference Model and Requirement Customer LSP 1 PE1 P1 CE2 CE1 PE1 C0 C3 Service Provider L3VPN Customer VPN Site B Customer VPN Site A
The Problem Customer LSP 1 PE1 P1 CE2 CE1 PE1 C0 C3 Service Provider L3VPN Customer VPN Site B Customer VPN Site A
Carrier’s Carrier Nearly Solves The Problem VPN LSP SP-LSP 1 PE1 P1 CE2 CE1 PE1 C0 C3 Service Provider L3VPN Customer VPN Site B Customer VPN Site A
You Want This Customer LSP VPN LSP SP-LSP 1 PE1 P1 CE2 CE1 PE1 C0 C3 Service Provider L3VPN Customer VPN Site B Customer VPN Site A
Challenges • RSVP signal C0-CE1-CE2-C3 • Make CE1 believe that the next-hop to C3 is CE2 • Not PE1 • Three proposed solutions (BGP Next Hop Attribute, iBGP, policy manipulation) • Partial ERO calculation • C0 to CE2 • CE2 toC3 • TE Considerations
TE Considerations: A New BGPAttribute • CE2 tells SP network TE attributes associated with path between itself and C3 • PE2 tells CE1 TE attributes associated with path between itself and C3 • Path through SP network • Path from CE2 to C3 • CE1 injects TE information into IGP