© 2006 Cisco Systems, Inc. All rights reserved. MPLS v2.24-1 MPLS VPN Technology Forwarding MPLS VPN Packets. - презентация

1 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPN Technology Forwarding MPLS VPN Packets

2 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v Outline Overview What Are the End-to-End VPN Forwarding Mechanisms? What Is VPN PHP? Propagating VPN Labels Between PE Routers What Are the Effects of MPLS VPNs on Label Propagation? What Are the Effects of MPLS VPNs on Packet Forwarding? Summary

3 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v VPN Packet Forwarding Across an MPLS VPN Backbone: Approach 1 Approach 1: The PE routers will label the VPN packets with an LDP label for the egress PE router, and forward the labeled packets across the MPLS backbone. Results: The P routers perform the label switching, and the packet reaches the egress PE router. Because the egress PE router does not know which VRF to use for packet switching, the packet is dropped.

4 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v VPN Packet Forwarding Across an MPLS VPN Backbone: Approach 2 Result: The P routers perform label switching using the top label, and the packet reaches the egress PE router. The top label is removed. The egress PE router performs a lookup on the VPN label and forwards the packet toward the CE router. Approach 2: The PE routers will label the VPN packets with a label stack, using the LDP label for the egress PE router as the top label, and the VPN label assigned by the egress PE router as the second label in the stack.

5 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v VPN PHP Penultimate hop popping on the LDP label can be performed on the last P router. The egress PE router performs label lookup only on the VPN label, resulting in faster and simpler label lookup. IP lookup is performed only oncein the ingress PE router.

6 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v VPN Label Propagation Question: How will the ingress PE router get the second label in the label stack from the egress PE router? Answer: Labels are propagated in MP-BGP VPNv4 routing updates.

7 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v Step 1:A VPN label is assigned to every VPN route by the egress PE router. VPN Label Propagation (Cont.) Step 2:The VPN label is advertised to all other PE routers in an MP-BGP update. Step 3:A label stack is built in the VRF table.

8 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPNs and Label Propagation The VPN label must be assigned by the BGP next hop. The BGP next hop should not be changed in the MP-IBGP update propagation. –Do not use the next-hop-self command on confederation boundaries. The PE router must be the BGP next hop. –Use the next-hop-self command on the PE router. The label must be reoriginated if the next hop is changed. –A new label is assigned every time that the MP-BGP update crosses the AS boundary where the next hop is changed.

9 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPNs and Packet Forwarding The VPN label of the BGP route is understood only by the egress PE router. An end-to-end LSP tunnel is required between the ingress and egress PE routers. BGP next-hop addresses must be IGP routes. –LDP labels will be assigned to addresses in the global routing table. –LDP labels are not assigned to BGP routes (BGP routes receive VPN labels). BGP next hops announced in IGP must not be summarized in the core network. –Summarization breaks the LSP tunnel.

10 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPNs and Packet Forwarding: Summarization in the Core

11 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v Summary PE routers forward packets across the MPLS VPN backbone using label stacking. The last P router in the LSP tunnel pops the LDP label, and the PE router receives a labeled packet that contains only the VPN label. Labels are propagated between PE routers using MP-BGP. BGP next hops should not be announced as BGP routes. LDP labels are not assigned to BGP routes.

12 © 2006 Cisco Systems, Inc. All rights reserved. MPLS v