1. 1 © 2004 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID 1 © 2003 Cisco Systems, Inc. All rights reserved. CISCO IP/MPLS INTERPROVIDER SOLUTION TECHNICAL OVERVIEW NEIL ABOGADO & SANTIAGO ALVAREZ FEBRUARY 2005

2. 222 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 2 © 2003 Cisco Systems, Inc. All rights reserved. Introduction Technology Overview Inter-AS 1 Multicast VPN Inter-AS TE 2 Interprovider 3 MPLS VPN over IP MPLS VPN Inter-AS/CsC 4 Load Balancing Interprovider Network Management Conclusion Agenda 1 Inter-Autonomous System 2 Traffic Engineering 3 Provider supporting other providers 4 Carrier Supporting Carrier

3. 333 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 3 © 2003 Cisco Systems, Inc. All rights reserved. INTRODUCTION 333 © 2004 Cisco Systems, Inc. All rights reserved.

4. 444 Presentation_ID 4 © 2003 Cisco Systems, Inc. All rights reserved. Assumptions This presentation covers the inter-autonomous system aspects of different technologies. It is expected that the audience has base knowledge of the following topics: IP/MPLS Core Operation IP/MPLS L3 VPN Operation IP/MPLS Traffic Engineering (TE) Multicast VPN (mVPN)

5. 555 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 5 © 2003 Cisco Systems, Inc. All rights reserved. New Capabilities Inter-AS Multicast VPN Inter-AS Traffic Engineering Interprovider MPLS VPN over IP Enhanced Capabilties IP/MPLS VPN Inter-AS/CsC Load Balancing Interprovider Network Management New Capabilities Inter-AS Multicast VPN Inter-AS Traffic Engineering Interprovider MPLS VPN over IP Enhanced Capabilties IP/MPLS VPN Inter-AS/CsC Load Balancing Interprovider Network Management What has changed?

6. 666 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 6 © 2003 Cisco Systems, Inc. All rights reserved. Integrated Applications: Integrated Services & Network: Voice Video Data Storage Revenue Growth with Deeper Enterprise Penetration & Customer Satisfaction Revenue Growth with Deeper Enterprise Penetration & Customer Satisfaction Inter-AS 2 Multicast VPN Inter-AS TE 3 Interprovider 4 MPLS VPN over IP MPLS VPN Inter-AS/CsC 5 Load Balancing Interprovider Network Management Inter-AS 2 Multicast VPN Inter-AS TE 3 Interprovider 4 MPLS VPN over IP MPLS VPN Inter-AS/CsC 5 Load Balancing Interprovider Network Management 1 GINI in short. NGN is next generation network. 2 Inter-Autonomous System 3 Traffic Engineering 4 Provider supporting other providers 5 Carrier Supporting Carrier Cisco IP/MPLS Enables Global Interprovider NGN Infrastructure 1

7. 777 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 7 © 2003 Cisco Systems, Inc. All rights reserved. Cisco Service Provider Vision CONSUMER SMALL/MEDIUM BUSINESS SP WHOLESALE ENTERPRISE VPNsINTERNETCONTENT VOICE & VIDEO MOBILITYTRANSPORT IP NEXT GENERATION NETWORK CONNECTING CUSTOMERS WITH SERVICES, SERVICES WITH NETWORKS, AND NETWORKS WITH EACH OTHER

8. 888 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 8 © 2003 Cisco Systems, Inc. All rights reserved. Inter- connect PSTN Internet / VPN TV / Video / Content Data Center Inter SP Working CUSTOMER ELEMENT CUSTOMER ELEMENT ACCESS / AGGREGATION INTELLIGENT IP / MPLS EDGE MULTISERVICE IP / MPLS CORE HOME NETWORKING HOT SPOT MOBILE ENTERPRISE/ BRANCH Cisco ISR SMALL/MEDIUM BUSINESS Hosted / Managed ISR / IPT Aironet Cable/DSL Cisco Catalyst & 7600 Metro Ethernet IP RAN / STP Wireless MGX 8800 AS5XXX FR / ATM / Media Gateway Cisco ONS 153xx MSPP TDM / Ethernet Transport Cisco ONS 15454 MSTP / MSPP Cisco ONS 15454 MSTP / MSPP Cisco 12000 Cisco 10000 Cisco 7x00 Cisco ONS 15600 MSPP Cisco ONS 15600 MSPP Cisco CRS-1 Cisco IP NGN Technology Spanning Secure Network Layer QoS SECURITY QoS SECURITY

9. 999 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 9 © 2003 Cisco Systems, Inc. All rights reserved. Interprovider NGN Convergence APPLICATION LAYER SERVICE CONTROL LAYER OPERATIONAL LAYER Open Framework for Enabling “Triple Play On The Move” (Data, Voice, Video, Mobility) Open Framework for Enabling “Triple Play On The Move” (Data, Voice, Video, Mobility) Service Exchange to Support Interprovider Business SECURE NETWORK LAYER VoD / HDTV GAMING STORAGE COMM WEB SERVICES MOBILE APPS IP CONTACT CENTER Self- Service PolicyIdentityBilling Interprovider 1 NGN Interprovider 2 NGN Interprovider 3 NGN Interprovider 4 NGN Security Redundancy & Resiliency QoS Interprovider Technologies INTELLIGENT NETWORKING

10. 10 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 10 © 2003 Cisco Systems, Inc. All rights reserved. Cisco Interprovider Architecture Secure Network Layer New or Enhanced Components for this Announcement Scalable Platforms Carrier Supporting Carrier Inter-AS MPLS VPN over IP Multicast VPN IP/MPLS L3 VPNs Any Transport over MPLS (AToM) Any Transport over MPLS (AToM) Traffic Engineering Virtual Private LAN Services (VPLS) Virtual Private LAN Services (VPLS) Quality of Service Security Redundancy & Resiliency IP MPLS IP+ATM Inter-AS Management CRS-1, C12000, C10000, C7600, C7500, C7300, C7200

11. 11 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 11 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS Multicast VPN (mVPN) 11

12. 12 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 12 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS MPLS/VPN Options Three options for unicast listed in draft-ietf- l3vpn-rfc2547bis A.Back-to-back ASBR-PEs B.ASBRs exchanging VPNv4 routes C.VPNv4 routes via multi-hop MP-eBGP All three options must be supported for multicast packets

13. 13 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 13 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS MVPN Requirement AllAll options available for unicast traffic must be supported for multicast Protocol enhancement required Multicast DomainIf MVPN packets are encapsulated when forwarded between ASBRs, Multicast Domain must be built across multiple AS’es Inter-AS MDT

14. 14 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 14 © 2003 Cisco Systems, Inc. All rights reserved. Challenges -- RPF For Sources Inside MVPN In the context of MVPN, PIM RPF neighbor for source must be PE, not ASBR ASBR doesn’t have VRF configured, nor multicast tunnels created. Doesn’t participate in any MD thus cannot receive or process PIM control packets sent to multicast domain ASBR may rewrite BGP Next Hop attributes for VPNv4 prefixes Next hop information from unicast routing table points to ASBR, not PE router originating prefix

15. 15 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 15 © 2003 Cisco Systems, Inc. All rights reserved. Challenges -- Inter-AS MDT P routers maintain IGP routes from within the AS Doesn’t maintain routing information to PE routers in other AS (unless the prefixes are redistributed) PE PE Cannot process PIM messages for (PE, MDT- Group) when PE is in other AS ASBRs may not install PE prefixes from other AS in unicast routing table PE Cannot propagate (PE, MDT-Group) to other AS

16. 16 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 16 © 2003 Cisco Systems, Inc. All rights reserved. Option A: Back-to-back ASBR-PEs Native IP forwarding between ASBRs Protocol change not required Inter-AS MDT not required MDT limited to one AS No issue with managing MDT group ranges between AS No issue with RPF VRF created on the ASBRs

17. 17 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 17 © 2003 Cisco Systems, Inc. All rights reserved. Option B: ASBR Exchanging VPNv4 Routes VRFs are not created on ASBRs Packets must be encapsulated when forwarded between ASBRs – need inter-AS MDT PE routers may not be reachable natively from other AS How to build inter-AS MDT when a P router doesn’t have routing information to reach a remote PE ASBRs store all VPNv4 routes and modify BGP Nexthop of VPNv4 routes How to RPF to source inside an MVPN?

18. 18 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 18 © 2003 Cisco Systems, Inc. All rights reserved. Option C: VPNv4 Routes via Multi-Hop MP-eBGP VRFs are not created on ASBRs Packets must be encapsulated when forwarded between ASBRs – need inter-AS MDT PE routers may not be reachable natively from another AS Again, how to build inter-AS MDT? (Typically) RRs store all VPNv4 routes and preserve BGP Nexthop of VPNv4 routes Less impact on RPF to a source inside an MVPN

19. 19 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 19 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS MVPN – Option B & C Summary Need solution to RPF to source reachable via PE router in remote AS Specific for option B Not applicable for option C Use BGP Connector Attribute Solution: Use BGP Connector Attribute Need solution to build inter-AS MDT For both option B and C Leverage BGP MDT SAFI Use PIM RPF Vector Solution: Use PIM RPF Vector

20. 20 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 20 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS MVPN Solution Overview ConnectorIntroduce Connector attribute to MP-BGP Help preserve identity of PE router originating VPNv4 prefix MDT SAFILeverage BGP MDT SAFI Help ASBRs RPF to source PEs in remote AS RPF Vector Help ASBRs and receiver PEs insert RPF Vector to build MDT for source PEs in remote AS RPF VectorIntroduce RPF Vector to PIM Help P routers build MDT to source PEs in remote AS

21. 21 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 21 © 2003 Cisco Systems, Inc. All rights reserved. BGP Connector Attribute Transitive attribute Store PE router which originates VPNv4 prefix In local AS, it is the same as Next Hop Attribute When advertised to another ASBR (with option B), its value is preserved (Next Hop attributes are rewritten by ASBRs) RPF Vector Help ASBRs and receiver PEs insert RPF Vector to build MDT for source PEs in remote AS ValueSAFIAFI Which is the originating router IPv4 or IPv6 address Variable length Value field contains 0 0 8 8 24 31 7 7 23

22. 22 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 22 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS MVPN BGP MDT SAFI Advertise BGP MDT SAFI across AS boundaries Independent of advertisement of VPNv4 routes when RR and multi-hop EBGP peering used Processed and filtered like VPNv4 routes pathASBRs store path in separate table RPF path How SAFI is advertised determine RPF path to PE router originating SAFI pathPEs also store path in separate table exit Allows PEs to figure out exit ASBR to source PE

23. 23 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 23 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS MVPN PIM RPF Vector Encoded as part of source address in PIM Join/Prune messages IGP next hop for PIM RPF neighbor in PIM Join/Prune messages Typically the exit ASBR to prefix in a remote AS Can be used natively in non-VPN environment, or combined with RD in VPN environment MaskLen Rsvd/FlagEncode RD RPF Vector Source Address AddrFam 0 0 8 8 24 31 7 7 23

24. 24 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 24 © 2003 Cisco Systems, Inc. All rights reserved. Originating Originating PIM RPF Vector Router doing RPF lookup of source can find origin of route If origin is from BGP Next Hop this can be used as RPF Vector in PIM join On the originating router, RPF Vector is learned from BGP In MVPN, it is learned from BGP MDT SAFI In native environment, it can be learned from BGP SAFI=1 or =2 Decide RPF vector inclusion by configuration It is unknown if upstream router runs BGP Routers understanding RPF Vector format advertise this in PIM Hello

25. 25 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 25 © 2003 Cisco Systems, Inc. All rights reserved. Receiving Receiving PIM RPF Vector Router receiving RPF Vector join needs to store vector P routers learn RPF Vector from PIM RPF Vector joins When multiple Vectors are received, the one from the lower originator address is used When RPF vector present it is used and takes priority Need to do periodic / triggered RPF check and re- advertise RPF Vector upstream Multiple P routers may be connected – RPF Vector needs to be advertised to each If router receives RPF Vector referencing local interface RPF Vector is ignored and normal lookup performed

26. 26 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 26 © 2003 Cisco Systems, Inc. All rights reserved. ASBR Receiving ASBR Receiving PIM RPF Vector ASBR receives PIM join with vector owned by local interface (probably loopback) Vector discarded and normal RPF lookup performed BGP MDT SAFIIf RD is present, RPF lookup is done in BGP MDT table – built from BGP MDT SAFI Lookup using both RD and source address in the PIM message

27. 27 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 27 © 2003 Cisco Systems, Inc. All rights reserved. Interoperability PIM RPF Vector -- Interoperability New PIM Hello option to indicate capability to process RPF Vector RPF Vector only included in PIM messages when all PIM neighbors on RPF interface support it PE 2#show ip pim neighbor PIM Neighbor Table NeighborInterfaceUptime/Expires Ver DR Address Priority/Mode V 30.0.2.1 Ethernet0/0 19:06:35/00:01:22 v2 1 / V

28. 28 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 28 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS Traffic Engineering 28 Advanced TE Applications, 09/04 © 2004 Cisco Systems, Inc. All rights reserved. Cisco Internal Use Only

29. 29 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 29 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS MPLS Traffic Engineering AS1 ASBR AB AS2 Goal: Build a TE LSP from A to B Why: Connect separate AS Extended/virtual POP Virtual Trunk between providers End-to-end TE LSP MPLS TE for multi-AS providers How: inter-AS TE

30. 30 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 30 © 2003 Cisco Systems, Inc. All rights reserved. Inter-AS TE Extends Existing TE Capabilities with ASBR node protection Loose path reoptimization ASBR forced link flooding RSVP local policy extensions for inter-AS Per-neighbor RSVP keys

31. 31 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 31 © 2003 Cisco Systems, Inc. All rights reserved. ASBR Node Protection New Node-Id flag in RRO object Backup tunnel selection now possible across AS boundaries Flag defined in draft-ietf-mpls-nodeid- subobject AS1 ASBR AB AS2 X

32. 32 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 32 © 2003 Cisco Systems, Inc. All rights reserved. Loose Path Reoptimization A B ASBR2 ASBR1 R1 R3 R4 ASBR4 ASBR3 Loose Hop Expansion Path to A Defined Using Loose Hops 1.ASBR2 (loose) 2.B (loose) 1.ASBR2 (loose) 2.B (loose) 1.R1 2.ASBR1 3.ASBR2 4.B (loose) 1.R1 2.ASBR1 3.ASBR2 4.B (loose) Loose Hop Expansion 1.R1 2.ASBR1 3.ASBR2 4.R3 5.R4 6.B 1.R1 2.ASBR1 3.ASBR2 4.R3 5.R4 6.B Topology information not shared across AS boundaries Headend cannot compute complete path to destination Path to destination “loosely” defined Path loose hops expanded during LSP setup

33. 33 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 33 © 2003 Cisco Systems, Inc. All rights reserved. ASBR Forced Link Flooding AS1 IGP TE Database AS2 IGP TE Database AS1 ASBR2 ASBR4 ASBR1 ASBR3 AB AS2 R1 R3 R4 ASBR-to-ASBR links added to IGP TE database Loose path definition requires fewer hops ASBR-to-ASBR links added to IGP TE database Loose path definition requires fewer hops

34. 34 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 34 © 2003 Cisco Systems, Inc. All rights reserved. RSVP Local Policy Extensions for inter-AS A B ASBR2 ASBR1 AS1 AS2 ASBR may perform policy admission control for TE LSPs Policies defined in terms of TE-LSP characteristics (source, destination, bandwidth, protection, priority, AS, etc.) Different policies can be applied to different AS Local Policy Each bandwidth reservation from AS1 may not exceed 10Mbps Local Policy Each bandwidth reservation from AS1 may not exceed 10Mbps

35. 35 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 35 © 2003 Cisco Systems, Inc. All rights reserved. RSVP Message Authentication Per-Neighbor Keys Authentication desired between admin domains ASBR may connect to multiple domains or use RSVP authentication internally An RSVP node can be configured with separate per-neighbor keys Each neighboring router has an identical key that is used to generate the Integrity Object – MD5 and SHA-1 hash available RSVP Control Message eg. PATH, RESV, etc. Integrity Object ASBR1 ASBR2 Key 1 ASBR3 Key 2

36. 36 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 36 © 2003 Cisco Systems, Inc. All rights reserved. Interprovider MPLS VPN over IP 36 © 2003, Cisco Systems, Inc. All rights reserved.

37. 37 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 37 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPNs over IP MPLS VPN (RFC 2547) over IP transport Service characteristics Peer model Support for address overlapping Support for full mesh and complex topologies Leverages the same MPLS VPN control (MP-BGP) and forwarding plane Introduces extensions to support IP transport Intranet Extranet Intranet

38. 38 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 38 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPN over IP - Components VPN Label (a.k.a Inner Label) Identifies the specific VPN that a packet is destined. Is the same as the inner label that is used to support MPLS VPN over MPLS networks VPN Label (a.k.a Inner Label) Identifies the specific VPN that a packet is destined. Is the same as the inner label that is used to support MPLS VPN over MPLS networks Control Connection Tunneling Component Service Component VPN Identifier IGP and MP-BGP Used for Session ID/Cookie Advertisement and the establishment PE capabilities IGP and MP-BGP Used for Session ID/Cookie Advertisement and the establishment PE capabilities IP Tunnel Header (IPv4 Header) Transports MPLS VPN traffic among VPN PEs IP Tunnel Header (IPv4 Header) Transports MPLS VPN traffic among VPN PEs L2TPv3 Header Identifies traffic that is destined for the MPLS VPN Service and provides Service Integrity Check (4 byte Session ID + 8 byte Cookie) L2TPv3 Header Identifies traffic that is destined for the MPLS VPN Service and provides Service Integrity Check (4 byte Session ID + 8 byte Cookie)

39. 39 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 39 © 2003 Cisco Systems, Inc. All rights reserved. Native IP core leveraged for end to end transport L2TPv3 header is utilized to protect against blind insertion/brute force attacks Session ID + Cookie deliver a 96 bit value for attack mitigation. IP QoS mechanisms can be utilized for enhanced VPN Services MPLS VPN over IP – Data Plane Overview

40. 40 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 40 © 2003 Cisco Systems, Inc. All rights reserved. IP CE1CE2 PE1 Tunnel Header VPN Label PE2 VRF src add dst add src add dst add IP L2TP Session Id Cookie Session Id Cookie VPN Label IP Payload VPN traffic forwarded by PEs using separate routing instance (VRFs) Tunnel header and VPN label imposed on VPN traffic Packets switched to egress PE based on tunnel header Egress PE uses VPN label to forward packet to remote CE MPLS VPN over IP – Data Plane Illustrated

41. 41 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 41 © 2003 Cisco Systems, Inc. All rights reserved. CookieSession IdEndpoint A1216440F2E9ABA11025172.16.255.5 F12B644012E9B7C01025172.16.255.4 032B6440F1E9B80A1025172.16.255.3 BAB6440F209F02011025172.16.255.2 172B644AF2E9BB311025172.16.255.1 PE1 Multipoint Tunneling CookieSession IdEndpoint A1216440F2E9ABA11025172.16.255.5 F12B644012E9B7C01025172.16.255.4 032B6440F1E9B80A1025172.16.255.3 BAB6440F209F02011025172.16.255.2 172B644AF2E9BB311025172.16.255.1 CookieSession IdEndpoint A1216440F2E9ABA11025172.16.255.5 F12B644012E9B7C01025172.16.255.4 032B6440F1E9B80A1025172.16.255.3 BAB6440F209F02011025172.16.255.2 172B644AF2E9BB311025172.16.255.1 CookieSession IdEndpoint A1216440F2E9ABA11025172.16.255.5 F12B644012E9B7C01025172.16.255.4 032B6440F1E9B80A1025172.16.255.3 BAB6440F209F02011025172.16.255.2 172B644AF2E9BB311025172.16.255.1 CookieSession IdEndpoint A1216440F2E9ABA11025172.16.255.5 F12B644012E9B7C01025172.16.255.4 032B6440F1E9B80A1025172.16.255.3 BAB6440F209F02011025172.16.255.2 172B644AF2E9BB311025172.16.255.1 PE2 PE3 PE4 PE5 Multipoint tunnel used for receiving traffic from multiple PE’s Dynamically created with capabilities distributed via BGP Multipoint tunnel avoids the need for a full mesh of point-to-point tunnels PE6 EndpointSession IdCookie 172.16.255.11025172B644AF2E9BB31 172.16.255.21025172B644AF2E9BB31 172.16.255.31025172B644AF2E9BB31 172.16.255.41025F12B644012E9B7C0 172.16.255.51025A1216440F2E9ABA1

42. 42 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 42 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPN over IP – Control Plane Overview MP-BGP MP-BGP carries NLRI information (Prefix, VPN_IPv4 label, RD, RT) associated with the BGP Next-Hop MPLS VPN over IP adds a new SAFI for tunnel NLRI associated with the BGP Next-Hop (which may be associated with VPN_IPv4) Since VPN participation is established via BGP to avoid “Black hole” situations IGP IGP defines path to BGP Next-Hop Recursive Resolution through Tunnel Construct Provides Encapsulation Attributes (IP Header, L2TPv3 Header) Adjacency Adjacency defines egress interface for IGP next-hop

43. 43 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 43 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPN – Control Plane IP CE1CE2 PE1 PE2 VRF IPv4 Route Exchange VPNv4 Routes Advertised via BGP VPN Labels Exchanged via BGP Tunnel Endpoints Learned via BGP VPNv4 Routes Advertised via BGP VPN Labels Exchanged via BGP Tunnel Endpoints Learned via BGP New BGP IPv4 SAFI used to exchange tunnel endpoints Tunnel advertisements include (L2TP) tunnel parameters (Session Id and Cookie) MPLS VPN control plane reused (VPNv4 add family, RD, RT, etc.) … but VPNv4 next hop must be reachable through multipoint tunnel

44. 44 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 44 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPN over IP – Inter-AS Support Back-to-Back VRF Connectivity ASBRs are directly connected over a physical interface Sub-interface per VRF is created and mapped Packet is forwarded as an IP packet between the ASBRs Each PE-ASBR router treats the other as a CE PE-ASBR to PE-ASBR link may use any supported PE-CE routing protocol Recommended for fewer VRFs requiring simpler connectivity when ASBRs are directly connected over a physical interface

45. 45 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 45 © 2003 Cisco Systems, Inc. All rights reserved. Back-to-Back VRF Connectivity One logical interface & VRF per VPN client IP Core AS #100 MPLS Core AS #200 VPN-A-1 PE-1 VPN-A-2 PE-2 CE-4 VPN-B-1 CE-2CE-1CE-3 VPN-B-2 PE-ASBR-1 PE-ASBR-2 VRF to VRF Connectivity between PE-ASBRs

46. 46 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 46 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPN over IP Tunnels CsC Scenarios Customer Carrier Backbone Carrier Customer Carrier MPLS VPN over IP MPLS VPN over IP MPLS VPN over IP IP IP/MPLS 1. Internet Service 2. VPN Service

47. 47 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 47 © 2003 Cisco Systems, Inc. All rights reserved. Customer Carrier Backbone Carrier IP Customer Scenario 1: Control Plane IP MPLS VPN over IP Tunnels eBGP IPv4+Label MP-iBGP VPNv4 MP-iBGP IPv4 Tunnel IGP+LDP iBGP/eBGP IPv4 CSC-PE1CSC-PE2CE1PE1CSC-CE1PE2CSC-CE2CE2 Customer carrier exchanges external IPv4 routes directly Customer carrier exchanges internal IPv4 routes (plus labels) with backbone carrier Backbone carrier exchanges customer carrier internal IPv4 routes as VPNv4 routes Backbone carrier exchanges IPv4 tunnel endpoints internally Backbone carrier never sees customer carrier external IPv4 routes

48. 48 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 48 © 2003 Cisco Systems, Inc. All rights reserved. Scenario 1: Forwarding Plane Customer Carrier Backbone Carrier IP Customer IP MPLS VPN over IP Tunnels CSC-PE1CSC-PE2CE1PE1CSC-CE1PE2CSC-CE2CE2 IP L2TPv3 IPIPIPIP Label IPIP VPN Label IPIP Label IPIPIPIPIPIP PushSwap Tunnel De-encap Swap Pop

49. 49 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 49 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPN IP/MPLS MPLS VPN IP/MPLS MPLS VPN IP/MPLS MPLS VPN IP/MPLS Scenario 2: Control Plane Customer Carrier Backbone Carrier IP Customer MPLS VPN over IP Tunnels eBGP IPv4+Label MP-iBGP VPNv4 MP-iBGP IPv4 Tunnel IGP+LDP iBGP/eBGP IPv4 CSC-PE1CSC-PE2CE1PE1CSC-CE1PE2CSC-CE2CE2 Customer carrier exchanges external VPNv4 routes directly Customer carrier exchanges internal IPv4 routes (plus labels) with backbone carrier Backbone carrier exchanges customer carrier internal IPv4 routes as VPNv4 routes Backbone carrier exchanges IPv4 tunnel endpoints internally Backbone carrier never sees customer carrier VPNv4 routes

50. 50 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 50 © 2003 Cisco Systems, Inc. All rights reserved. Scenario 2: Forwarding Plane MPLS VPN over IP Tunnels IPIPIPIPIPIPIPIPIPIPIPIPIPIP Customer Carrier Backbone Carrier IP VPN Customer MPLS VPN IP/MPLS MPLS VPN IP/MPLS MPLS VPN IP/MPLS MPLS VPN IP/MPLS IP L2TPv3 Label VPN Label Label VPN Label Label VPN Label Label VPN Label Swap Tunnel De-encap Swap Push Swap Pop CSC-PE1CSC-PE2CE1PE1CSC-CE1PE2CSC-CE2CE2

51. 51 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 51 © 2003 Cisco Systems, Inc. All rights reserved. MPLS VPN Inter-AS/CsC Load Balancing 51 © 2004 Cisco Systems, Inc. All rights reserved.

52. 52 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 52 © 2003 Cisco Systems, Inc. All rights reserved. Inter-Autonomous System – Reference Model CE1 Two ISPs peer up providing services to some of the common customer base Single SP POPs not available in all geographical areas required by their customers Both SPs must support MPLS VPNs Customer’s sites distribute reachability information directly to the participating Service Providers IP/MPLS (with IP or MPLS Core) AS 1 IP/MPLS (with IP or MPLS Core) AS 1 IP/MPLS (with IP or MPLS Core) AS 2 IP/MPLS (with IP or MPLS Core) AS 2 ASBR 2 ASBR 1 PE1 PE2 CE4

53. 53 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 53 © 2003 Cisco Systems, Inc. All rights reserved. Why Inter-AS? Extends MPLS-VPN services across geographical boundaries allowing service providers to support customer base in geographical locations where their POPs are not available Allows multiple Service Providers to build common services Allows separate ASs to communicate Implies exchange of VPN routing information between providers Provides traffic separation and maintains privacy end-to-end Allows a single service provider to partition their network into multiple domains for scalability and inter-departmental privacy

54. 54 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 54 © 2003 Cisco Systems, Inc. All rights reserved. VPN Client Connectivity AS #1 AS #2 How to Distribute Routes between SPs? VPN-A-1 VPN-A-2 149.27.2.0/24 VPN-v4 update: RD:1:27:149.27.2.0/24, NH=PE-1 RT=1:231, Label=(28) BGP, OSPF, RIPv2 149.27.2.0/24,NH=CE-1 VPN-A VRF Import Routes with route-target 1:231 PE-1 PE2 CE2 CE-1 VPN Sites Attached to Different MPLS VPN Service Providers

55. 55 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 55 © 2003 Cisco Systems, Inc. All rights reserved. VPNv4 Distribution Options VPN-A-1 VPN-A-2 PE2 CE2 CE-1 AS #1 AS #2 PE-1 MP-eBGP for VPNv4 Multihop MP-eBGP between RRs Back-to-Back VRFs PE-ASBR-1 PE-ASBR-2 2547bis Refers to These as “Option 10(a)”, “Option 10(b)”, “Option 10(c)” Respectively

56. 56 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 56 © 2003 Cisco Systems, Inc. All rights reserved. Each ASBR Thinks the Other Is a CE Back-to-Back VRFs (Option 10(a)) 10(a) is the most popular Inter-AS tool today Directly connects ASBRs, over a sub-interface per VRF Packet is forwarded as an IP packet between the ASBRs Link may use any supported PE-CE routing protocol 10(a) is the most secure and easiest to provision May not be easy to manage as it grows ASBR 2 ASBR1

57. 57 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 57 © 2003 Cisco Systems, Inc. All rights reserved. EBGP VPNv4 (Option 10(b)) VPN-A-1 PE-1 VPN-A-2 PE-2 CE-4 VPN-B-1 CE-2CE-1CE-3 VPN-B-2 PE-ASBR-1 PE-ASBR-2 AS #1 AS #2 Label Exchange between Gateway PE-ASBR Routers Using eBGP eBGP for VPNv4 MP-BGP VPNv4 Prefix Exchange Between Gateway PE-ASBRs

58. 58 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 58 © 2003 Cisco Systems, Inc. All rights reserved. EBGP VPNv4 (Option 10(b)) PE-ASBRs exchange routes directly using BGP External MP-BGP for VPNv4 prefix exchange; no LDP or IGP MP-BGP session with NH to advertising PE-ASBR Next-hop and labels are rewritten when advertised across the inter-provider MP-BGP session Receiving PE-ASBR automatically creates a /32 host route to a peer ASBR Which must be advertised into receiving IGP if next-hop-self is not in operation to maintain the LSP PE-ASBR stores all VPN routes that need to be exchanged But only within the BGP table No VRFs; labels are populated into the LFIB of the PE-ASBR Receiving PE-ASBRs may allocate new label Controlled by configuration of next-hop-self (default is off)

59. 59 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 59 © 2003 Cisco Systems, Inc. All rights reserved. AS #1 AS #2 PE-1 PE-2 VPN-B-1 CE-2 CE-3 VPN-B-2 PE-ASBR-1 PE-ASBR-2 152.12.4.0/24 BGP, OSPF, RIPv2 152.12.4.0/24,NH=CE-2 VPN-v4 update: RD:1:27:152.12.4.0/24, NH=PE-1 RT=1:222, Label=(L1) VPN-v4 update: RD:1:27:152.12.4.0/24, NH=PE-ASBR-2 RT=1:222, Label=(L3) BGP, OSPF, RIPv2 152.12.4.0/24,NH=PE-2 VPN-v4 update: RD:1:27:152.12.4.0/24, NH=PE-ASBR-1 RT=1:222, Label=(L2) EBGP VPNv4 Control Plane (Option 10(b))

60. 60 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 60 © 2003 Cisco Systems, Inc. All rights reserved. PE-ASBR-1 PE-ASBR-2 152.12.4.1 LDP PE-ASBR- 2 Label L3 152.12.4.1 152.12.4.1L3 L2152.12.4.1 LDP PE-1 Label L1 152.12.4.1 152.12.4.1 L1 152.12.4.1 PE-1 VPN-B-1 CE-2 152.12.4.0/24 PE-2 CE-3 VPN-B-2 EBGP VPNv4 Forwarding Plane (Option 10(b))

61. 61 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 61 © 2003 Cisco Systems, Inc. All rights reserved. Multihop EBGP VPNv4 between RRs (Option 10(c)) VPN-A-1 PE-1 VPN-A-2 PE-2 CE-4 VPN-B-1 CE-2CE-1CE-3 VPN-B-2 AS #1 AS #2 ASBR-1 Multihop eBGP for VPNv4 with next- hop-unchanged ASBR-2 RR-1 RR-2 ASBRs Exchange BGP next-hop Addresses with Labels eBGP IPv4 + Labels Multihop MP-eBGP VPNv4 Prefix Exchange Between Route Reflectors

62. 62 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 62 © 2003 Cisco Systems, Inc. All rights reserved. Multihop EBGP VPNv4 between RRs (Option 10(c)) MPLS VPN providers exchange VPNv4 prefixes via their route reflectors Requires multihop MP-eBGP (VPNv4 routes) Next-hop-self must be disabled on route reflector Preserves next-hop and label as allocated by the originating PE router Providers exchange IPv4 routes with labels between directly connected ASBRs using eBGP Only PE loopback addresses exchanged as these are BGP next-hop addresses

63. 63 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 63 © 2003 Cisco Systems, Inc. All rights reserved. VPN-B-1 CE-2 CE-3 VPN-B-2 ASBR-1 RR-2 ASBR-2 RR-1 Network=PE-1 NH=ASBR-1 Label=(L2) BGP, OSPF, RIPv2 152.12.4.0/24,NH=CE-2 152.12.4.0/24 VPN-v4 update: RD:1:27:152.12.4.0/24, NH=PE-1 RT=1:222, Label=(L1) BGP, OSPF, RIPv2 152.12.4.0/24,NH=PE-2 Network=PE-1 NH=ASBR-2 Label=(L3) PE-1 PE-2 Multihop EBGP VPNv4 between RRs (Option 10(c)): Control Plane

64. 64 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 64 © 2003 Cisco Systems, Inc. All rights reserved. VPN-B-1 CE-2 CE-3 VPN-B-2 ASBR-1 RR-2 ASBR-2 RR-1 152.12.4.0/24 PE-1 PE-2 152.12.4.1 L1 L3 L2L1152.12.4.1 L1 152.12.4.1 Multihop EBGP VPNv4 between RRs (Option 10(c)): Forwarding Plane LDP PE-ASBR-2 Label L3 L1 152.12.4.1 152.12.4.1 LDP PE-1 Label L1 152.12.4.1

65. 65 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 65 © 2003 Cisco Systems, Inc. All rights reserved. ASBR may connect through multiple links Load balancing desirable to maximize bandwidth utilization One BGP interface peering per link Each peering uses their associated link as a separate resource No BGP session can load balance across multiple links Load balancing limitation may happen regardless of the Inter-AS option ASBR Link A Link B eBGP Peering between physical interfaces Inter-AS Load Balancing The Problem AS 2 AS 1

66. 66 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 66 © 2003 Cisco Systems, Inc. All rights reserved. ASBR Loopback Interface Link A Link B eBGP Peering between lookback interfaces ASBRs maintain a single eBGP peering using loopback interfaces BGP peering session uses all links as a collective resource Inter-As traffic effectively load balanced across physical links Inter-AS Load Balancing Enhancement AS 2 AS 1

67. 67 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 67 © 2003 Cisco Systems, Inc. All rights reserved. CsC-CE Backbone Carrier Customer Carrier A Site 1 Customer Carrier A Site 2 MPLS or IP Network CsC-PE ISP or MPLS VPN provider is a customer of another MPLS VPN backbone provider MPLS VPN backbone services needed between the same carrier POPs Subscribing Service Provider may or may not have been MPLS-enabled Customer’s sites do not distribute reachability information to the backbone carrier Carrier’s Carrier Service Reference Model

68. 68 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 68 © 2003 Cisco Systems, Inc. All rights reserved. The Problem MPLS-VPN works well for carrying customer IGPs Platforms, network scale to N*O(IGP) routes What if the CE wants the PE to carry all their BGP routes? Or if CE wants to run their own VPN service? Or if the CE just has a lot of route? (example: 30 sites, 20k prefixes)

69. 69 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 69 © 2003 Cisco Systems, Inc. All rights reserved. ISP A/Site 1 ISP A/Site 2 Carrier’s Carrier: The Problem (Internet) CE A1 CE A3 PE 1 PE 2 PE 3 P1P1 P2P2 P3P3 Step 1 IP Dest=Internet iBGP IPv4 Internet

70. 70 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 70 © 2003 Cisco Systems, Inc. All rights reserved. Carrier’s Carrier: The Problem (VPN) ISP A/Site 1 ISP A/Site 2 CE A1 CE A3 PE 1 PE 2 PE 3 P1P1 P2P2 P3P3 VRF A 1.2.3.0/24 VRF A 1.2.3.0/24 Step 1 IP Dest=1.2.3.4 Label (iBGP VPnv4) Dest=VRF A iBGP VPNv4

71. 71 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 71 © 2003 Cisco Systems, Inc. All rights reserved. Carrier’s Carrier: The Solution MPLS between PE and CE Either IGP+LDP or BGP+Label CEs exchange labels for their IGP routes with the PEs CEs iBGP peer with each other PEs are back to O(IGP) information

72. 72 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 72 © 2003 Cisco Systems, Inc. All rights reserved. ISP A/Site 1 ISP A/Site 2 Internet Carrier’s Carrier: The Solution (Internet) CE A1 CE A3 PE 1 PE 2 PE 3 P1P1 P2P2 P3P3 IP Dest=Internet Step 1 Label (LDP/BGP+Label) Dest=CEa1 Step 4 IP Dest=Internet Step 2 IP Dest=Internet Label (VPNv4/IBGP) Dest=CEa1 Label (LDP/TE) Dest=PE1 Step 3 IP Dest=Internet Label (VPNv4) Dest=CEa1

73. 73 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 73 © 2003 Cisco Systems, Inc. All rights reserved. ISP A/Site 1 ISP A/Site 2 Carrier’s Carrier: The Solution (VPN) CE A1 CE A3 PE 1 PE 2 PE 3 P1P1 P2P2 P3P3 VPN1-Cust Step 2 Step 3 Step 4 Step 1 IP Dest=VPN1-Cust Label (iBGP VPNv4) Dest=VPN1 Label (LDP/BGP) Dest=CEa1 IP Dest=VPN1-Cust Label (VPNv4) Dest=VPN1 Label (VPnv4) Dest=CEa1 Label (LDP/TE) Dest=PE1 IP Dest=VPN1-Cust Label (VPNv4) Dest=VPN1 Label (VPnv4) Dest=CEa1 IP Dest=VPN1-Cust Label (VPNv4) Dest=VPN1

74. 74 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 74 © 2003 Cisco Systems, Inc. All rights reserved. CsC-PE and CsC-CE may connect through multiple links Load balancing desirable to maximize bandwidth utilization One BGP interface peering per link Each peering uses their associated link as a separate resource No BGP session can load balance across multiple links CsC - PE CsC CE Link A Link B eBGP Peering between physical interfaces Carrier Supporting Carrier (CsC) Load Balancing - The Problem Customer MPLS Carrier Backbone MPLS Carrier

75. 75 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 75 © 2003 Cisco Systems, Inc. All rights reserved. CsC - PE Core Carrier MPLS Stub Carrier CsC CE Loopback Interface Link A Link B eBGP Peering between lookback interfaces CsC-PE and CsC-CE maintain a single eBGP peering using loopback interfaces BGP peering session uses all links as a collective resource CsC traffic effectively load balanced across physical links Carrier Supporting Carrier (CsC) Load Balancing - Enhancement

76. 76 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 76 © 2003 Cisco Systems, Inc. All rights reserved. Interprovider Network Management

77. 77 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 77 © 2003 Cisco Systems, Inc. All rights reserved. IP/MPLS Interprovider Management Strategy Trouble- shooting PlanningProvisioningFaultPerformance Centralized end-to-end Service Provisioning Centralized end-to-end Service Provisioning Fault collection, analysis and reporting Fault collection, analysis and reporting Operations management (config, inventory, software) Performance data collection and reporting Integrated Network Management System Device Manager Device Abstraction Layer Device Manager QoS Applications Device Manager MPLS VPN Applications L2VPN Applications Metro Ethernet Applications MPLS Traffic Engineering Applications Metro Ethernet Applications

78. 78 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 78 © 2003 Cisco Systems, Inc. All rights reserved. IP/MPLS Interprovider Management Strategy Trouble- shooting PlanningProvisioningFaultPerformance Integrated Network Management System Device Manager Device Abstraction Layer Device Manager QoS Applications Device Manager MPLS VPN Applications L2VPN Applications Metro Ethernet Applications MPLS Traffic Engineering Applications Metro Ethernet Applications Cisco IP Solution Center Cisco Info Center CiscoWorks LAN Management Solution Cisco IOS Netflow with Reporting

79. 79 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 79 © 2003 Cisco Systems, Inc. All rights reserved. * *Also known as ISC Managing IP/MPLS Networks with ISC

80. 80 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 80 © 2003 Cisco Systems, Inc. All rights reserved. Automated Management of Layer 3 and Layer 2 Resources Rapid Profile-based Provisioning of IP/MPLS VPNs, L2 VPNs and Metro Ethernet Services Planning, visualization, and automatic provisioning of Cisco MPLS-TE tunnels. Recognize incorrect service configuration Cisco IP Solution Center Key Features Comprehensive Cisco IOS Software and line card support Carrier-grade infrastructure for large deployments

81. 81 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 81 © 2003 Cisco Systems, Inc. All rights reserved. Cisco IP Solution Center Benefits Automated Layer 3 and Layer 2 Resource Management and Rapid profile-based Provisioning Reduces provisioning failures due to error prone manual procedures Reduces costly OSS changes due to upgrades in Platform/IOS/Line Card upgrades delaying time to market of new services. Provides service differentiation - ISC L2VPN and Metro Ethernet application provides flexibility to be able to create varied service profiles MPLS-backbone Planning Avoids costly network upgrades by enhancing appropriate MPLS-backbone optimization tools. Helps guarantee premium SLA by providing advanced MPLS-TE management tools that outperform the alternative options. Troubleshooting Provides post-provisioning validation of the service design in order to determine if the Layer 3 and Layer 2 VPN is active and functional. On-demand and scheduled audits for configuration troubleshooting

82. 82 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 82 © 2003 Cisco Systems, Inc. All rights reserved. Cisco Info Center IP/MPLS Solution NOCCXOCustomerMarketingNOC Event Browser Troubleshooting tools Topo Maps MPLS customer & service data IP Solution Center Intra Device Correlation Syslog Traps L2, L2 and VPN network discovery SAA Metrics PE CE Cisco CRS-1 IP/MPLS Core Precision Visionary Mediators ISM SAA CIC Info Server CIC VPN Policy Manager Cisco Info Center

83. 83 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 83 © 2003 Cisco Systems, Inc. All rights reserved. Cisco Info Center IP/MPLS Policy Manager correlates network events to impacted sites by extracting service information from Cisco IP Solution Center Cisco Info Center IP/MPLS Management: Key Features Visibility of core MPLS topology Automatic discovery and display of each VPN Troubleshooting tools that leverage Precision IP topology data e.g. “VRF Ping Connected Device” uses Precision data to auto populate the “connected device field” Events are enriched with topology information from Precision IP, including “connected device”, and “VPN name IP Solution Center CIC VPN Policy Manager Cisco Info Center CIC Info Server

84. 84 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 84 © 2003 Cisco Systems, Inc. All rights reserved. Network Operations Management with CiscoWorks Integrated modules provide management operations functionality Centralized inventory device status and reporting Configuration archive and editing functions Change Audit control Software Image Management helps keeps network software images up to date

85. 85 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 85 © 2003 Cisco Systems, Inc. All rights reserved. CONCLUSION 85 © 2004 Cisco Systems, Inc. All rights reserved.

86. 86 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 86 © 2003 Cisco Systems, Inc. All rights reserved. Multicast VPN services are no longer limited to a single autonomous system TE LSP can now be signaled across AS boundaries for protection, bandwidth optimization and better QoS guarantees Pure IP networks can be part of MPLS VPN Inter-AS/CsC agreements Service providers with Inter-AS/CsC agreements can take advantage of load balancing between ASBRs Cisco IP Solution Center, Cisco Info Center and Cisco Works can be used as management platforms for interprovider deployments Cisco Interprovider IP/MPLS

87. 87 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID 87 © 2003 Cisco Systems, Inc. All rights reserved.