mpls vpn技术原理与应用v3xqtvs9.pptVIP

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Terminology: PE: Provider Edge, P: Provider; CE: Customer Edge, * * Two heads: one for Provider Side the other for Edge side Not virtual routers: network management plane not virtualized * ??forwarding??? commande sur l’interface * Mono process, multiple instances - scalability Before Cisco?IOS Releases 12.3(4)T and 12.0(27)S, a separate OSPF process was necessary for each VRF that receives VPN routes via OSPF. When VPNs are deployed, an MPLS Provider Edge (PE) router will be running both multiprotocol Border Gateway Protocol (BGP) for VPN distribution, and Interior Gateway Protocol (IGP) for PE-P connectivity. It is a common scenario when OSPF is used as the IGP between a customer edge (CE) router and a PE router. OSPF was not scalable in VPN deployment because of the limit of 32 processes. By default one process is used for connected routes and another process is used for static routes, therefore only 28 processes can be created for VRFs. The OSPF Support for Unlimited Software VRFs per Provider Edge Router feature allows for an approximate range of 300 to 10,000 VRFs, depending on the particular platform and on the applications, processes, and protocols that are currently running on the platform. * Now that the VRFs are populated, MP-IBGP is used to exchange routes between VRFs * RD has a local interest only RT is useful to forward VRF routes. PEs exchange VPN-IPv4 updates through MP-iBGP sessions. The PE originating the route is the next hop of the route. * * * * * * * * * * * route-target both means export and import * * 5 * * * * * * * * * * The customer wants to reuse the same AS number on several sites: CE-BGP-A1 announces network /16 to PE-Site-X. The prefix announced by CE-BGP-A1 is propagated to PE-Site-Y as an internal route through MP-BGP. PE-Site-Y prepends AS 115 to the AS path and propagates the prefix to CE-BGP-A2. CE-BGP-A2 drops