Corp A. Site 3. Intranet A. VPNID 4. Intranet B. VPNID 12. Intranet B. VPNID 12. Service Provider. VPN Aware Network. Connectionless. IP VPNs. Connectionless.
2201 1325_06_2000_c1
1 1
© 2000, Cisco Systems, Inc.
Introduction to MPLS and Traffic Engineering Session 2201
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
2
Topics
• Motivations for MPLS • MPLS Overview • Applications • Roadmap
2201 1325_06_2000_c1
3
© 2000, Cisco Systems, Inc.
Why MPLS?
• Integrate best of Layer 2 and Layer 3 Keep up with growth Reduce operations costs Increase reliability Create new revenue from advanced IP services Standards based 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
4
Key Cisco MPLS Solutions RSVP
IP Multicast
IP CoS
IP/ATM Integration
Traffic Engineering
Internet Scale VPN/CoS 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
5
MPLS: Routing Scalability for IP over ATM • Internal routing scalability Limited adjacencies
• External routing scalability Full BGP4 support, with all the extras
• VC merge for very large networks 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
6
MPLS: End-to-End IP Services over ATM • IP services directly on ATM switches
RSVP
ATM switches support IP protocols directly Avoids complex translation
• Full support for IP CoS, RSVP, IP multicast, future IP services 2201 1325_06_2000_c1
IP Multicast
IP CoS
7
© 2000, Cisco Systems, Inc.
Benefits of MPLS Class of Service with ATM
IP CoS over Standard ATM
• Allocate resources: Per individual, edge-to-edge VCs By kbps bandwidth
• Mesh of VCs to configure
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
IP CoS with MPLS
• Allocate resources: Per class, per link By % bandwidth
• No VCs to configure • Simpler to provision and engineer • Even simpler with ABR 8
MPLS: Traffic Engineering • Characteristics High performance Low overhead End-to-end connectivity
• Applications Constraint-based routing Fast reroute Guaranteed bandwidth Frame/ATM transport Control plane for ATM and OXCs 2201 1325_06_2000_c1
9
© 2000, Cisco Systems, Inc.
Motivations for Traffic Engineering Link Failure
New Release of Netscape Software
No Physical Link
• Links not available • Economics • Failure scenarios • Unanticipated 300 Mbps traffic Traffic Flow 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
155 Mbps Fiber Link
10
MPLS: Bringing Layer 2 Benefits to Layer 3 Route Chosen By IP Routing Protocol
• Traffic engineering
Route Specified By Traffic Engineering
Aligning traffic flows to resources Optimize link utilization
• Fast re-route Fast, local, link and node protection
• Guaranteed bandwidth Hard end-to-end bandwidth and delay guarantees 2201 1325_06_2000_c1
Legacy FR Edge Node
11
© 2000, Cisco Systems, Inc.
IP VPN Taxonomy IP VPNs DIAL DEDICATED ClientInitiated
NASInitiated IP Tunnel
Security Appliance
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
Router
Virtual VPN Aware Circuit Networks FR
ATM
MPLS/BGP VPNs
12
Cisco MPLS/BGP VPNs
Corp A Site 3
Connectionless IP VPNs
Corp B Site 1
Corp A Site 2
VPN Management by Membership List
Corp A Site 1
Privacy without Tunnels 2201 1325_06_2000_c1
Intranet A VPNID 4
Intranet B VPNID 12
Corp B Site 2
Service Provider VPN Aware Network
13
© 2000, Cisco Systems, Inc.
Benefits of MPLS/BGP VPNs • Private, connectionless IP VPNs • Outstanding scalability • Customer IP addressing freedom • Multiple QoS classes • Secure support for intranets and extranets • Simplified VPN Provisioning • Support over any access or backbone technology 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
Connection-Oriented VPN Topology
VPN B
VPN A VPN C VPN B
VPN C
VPN A VPN A
VPN B VPN C
VPN C VPN B
VPN A
Connectionless VPN Topology
VPN B
VPN A VPN C
VPN C
VPN B
VPN A VPN A VPN B VPN C
VPN C VPN A
VPN B 14
MPLS Benefits Benefits of MPLS IP/ATM Integration
Shared Backbone for Economies of Scale Reduced Complexity for Lower Operational Cost Faster Time to Market for IP Services => More Revenue Use Best Technology => Lower Costs
Traffic Engineering
Traffic Eng. for Lower Trunk Costs and Higher Reliability Fast Reroute for Protection and Resiliency Guaranteed Bandwidth for Hard QoS Guarantees
MPLS BGP VPNs 2201 1325_06_2000_c1
New Revenue Opportunity for SPs Scalability for Lower Operational Costs and Faster Rollout L2 Privacy and Performance for IP
15
© 2000, Cisco Systems, Inc.
Topics
• Motivations for MPLS • MPLS Overview • Applications • Roadmap
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
16
MPLS Concept At Edge (Edge LSR): Classify Packets Label Them
In Core (LSR): Forward Using Labels As Opposed to IP Addr
• Enable ATM switches to act as routers • Create new IP capabilities via flexible classification 2201 1325_06_2000_c1
17
© 2000, Cisco Systems, Inc.
Router Example: Distributing Routing Information Address Prefix
I/F
Address Prefix
I/F
128.89
1
128.89
0
171.69
1
171.69
1
...
Address Prefix
I/F
128.89
0
…
…
128.89 0 0 1 You Can Reach 128.89 and 171.69 thru Me
You Can Reach 128.89 thru Me 1 171.69
Routing Updates (OSPF, EIGRP…) 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
You Can Reach 171.69 thru Me 18
Router Example: Forwarding Packets Address Prefix
I/F
Address Prefix
I/F
128.89
1
128.89
0
171.69
1
171.69
1
...
Address Prefix
I/F
128.89
0
…
…
128.89 0 0 1 128.89.25.4
Data
128.89.25.4
128.89.25.4
1
Data
128.89.25.4
Data
Data
171.69
Packets Forwarded Based on IP Address 2201 1325_06_2000_c1
19
© 2000, Cisco Systems, Inc.
MPLS Example: Routing Information Address Out Out In Label Prefix I'face Label
Address Out Out In Label Prefix I'face Label
128.89
1
128.89
0
171.69
1
171.69
1
...
...
...
...
In Address Out Out Label Prefix I'face Label 128.89
0
...
...
0
128.89
0
1
You Can Reach 128.89 thru Me You Can Reach 128.89 and 171.69 thru Me
Routing Updates (OSPF, EIGRP…) 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
1
You Can Reach 171.69 thru Me 171.69 20
MPLS Example: Assigning Labels Address Out Out In Label Prefix I'face Label
Address Out Out In Label Prefix I'face Label
-
128.89
1
4
4
128.89
0
9
-
171.69
1
5
5
171.69
1
7
...
...
...
...
...
...
...
...
In Address Out Out Label Prefix I'face Label 9
128.89
0
-
...
...
...
...
0
128.89
0
1
Use Label 9 for 128.89 Use Label 4 for 128.89 and Use Label 5 for 171.69
Routing Updates (OSPF, EIGRP…) 2201 1325_06_2000_c1
1
Use Label 7 for 171.69 171.69 21
© 2000, Cisco Systems, Inc.
MPLS Example: Forwarding Packets Address Out Out In Label Prefix I'face Label
Address Out Out In Label Prefix I'face Label
-
128.89
1
4
4
128.89
0
9
-
171.69
1
5
5
171.69
1
7
...
...
...
...
...
...
...
...
In Address Out Out Label Prefix I'face Label 9
128.89
0
-
...
...
...
...
0
128.89
0 128.89.25.4 Data
1 128.89.25.4 Data
4
9 128.89.25.4 Data
128.89.25.4 Data
1
LSR Forwards Based on Label 171.69 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
22
MPLS Example: More Details In Address Out Out Label Prefix I'face Label
Address Out Out In Label Prefix I'face Label
In Address Out Out Label Prefix I'face Label
7
128.89
1
4
4
128.89
0
X
X
128.89.25
0
-
2
171.69
1
5
5
171.69
1
7
X
117.59
1
-
7
117.59
1
4
4
117.59
0
X
...
...
...
...
0
128.89.25
0 1 128.89.25.4 Data
1 7
128.89.25.4 Data
4
128.89.25.4 Data 128.89.25.4 Data
Prefixes That Share a Path Can Share Label 2201 1325_06_2000_c1
Remove Tag One Hop Prior to DeAggregation Point
De-Aggregation Point Does L3 lookup
117.59
23
© 2000, Cisco Systems, Inc.
Encapsulations ATM Cell Header
GFC
VPI
VCI
PTI
CLP HEC
DATA
Label
PPP Header (Packet over SONET/SDH)
PPP Header
Label Header
Layer 3 Header
LAN MAC Label Header
MAC Header
Label Header
Layer 3 Header
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
24
Label Header for Packet Media 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Label
COS S
TTL
Label = 20 bits COS = Class of Service, 3 Bits S = Bottom of Stack, 1 Bit TTL = Time to Live, 8 Bits
• Can be used over Ethernet, 802.3, or PPP links • Uses two new ether types/PPP PIDs • Contains everything needed at forwarding time • One word per label 2201 1325_06_2000_c1
25
© 2000, Cisco Systems, Inc.
ATM MPLS Example: Routing Information Address Out Out In Label Prefix I'face Label
In In Address Out Out Label I/F Prefix I'face Label
128.89
1
128.89
0
171.69
1
171.69
1
...
...
...
...
In In Address Out Out Label I/F Prefix I'face Label 128.89
0
...
...
0 128.89
1 1
0
2
You Can Reach 128.89 thru Me You Can Reach 128.89 and 171.69 thru Me
Routing Updates (OSPF, EIGRP…) 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
1
You Can Reach 171.69 thru Me 171.69 26
ATM MPLS Example: Requesting Labels Address Out Out In Label Prefix I'face Label
In In Address Out Out Label I/F Prefix I'face Label
128.89
1
128.89
0
171.69
1
171.69
1
...
...
...
...
In In Address Out Out Label I/F Prefix I'face Label 128.89
0
...
...
0 128.89
1 1
0
2
Need a Label for 128.89 Need Another Label for 128.89
Need a Label for 128.89
1
Need a Label for 128.89
Need a Label for 171.69
Need a Label for 128.89 Label Distribution Protocol (LDP) (Downstream Allocation on Demand) 2201 1325_06_2000_c1
171.69 27
© 2000, Cisco Systems, Inc.
ATM MPLS Example: Assigning Labels Address Out Out In Label Prefix I'face Label
In In Address Out Out Label I/F Prefix I'face Label
In In Address Out Out Label I/F Prefix I'face Label
-
128.89
1
4
4
2
128.89
0
9
9
1
-
171.69
1
5
8
3
128.89
0
10
10
1
...
...
5
2
171.69
1
7
128.89
...
-
0
-
...
0 128.89
1 1
0
0
2
Use Label 9 for 128.89 Use Label 4 for 128.89
3
Use Label 10 for 128.89 1
Use Label 5 for 171.69
Use Label 8 for 128.89 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
Use Label 7 for 171.69
171.69 28
ATM MPLS Example: Packet Forwarding Address Out Out In Label Prefix I'face Label
In In Address Out Out Label I/F Prefix I'face Label
In In Address Out Out Label I/F Prefix I'face Label
-
128.89
1
4
4
2
128.89
0
9
9
1
-
171.69
1
5
8
3
128.89
0
10
10
1
...
...
5
2
171.69
1
7
128.89
...
-
0
-
...
0 128.89
1 1
0
0
2
128.89.25.4 Data 9 4
128.89.25.4 Data
128.89.25.4 Data
1
128.89.25.4 Data
LSR Forwards Based on Label 2201 1325_06_2000_c1
171.69 29
© 2000, Cisco Systems, Inc.
Why Multiple Labels with ATM? In I/F
Packet
Cells 5
5
5
In Address Label Prefix
Out Out I/F Label
1
5
128.89
0
3
2
8
128.89
0
3
…
…
…
…
…
5
1
Help! 0
128.89 Packet 8
8
8
8
2
3
3
3
3
3
3
• If didn’t allocate multiple labels Cells of different packets would have same label (VPI/VCI) Egress router can’t reassemble packets 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
30
Multiple Labels In I/F
Packet
Cells 5
5
5
In Address Label Prefix
Out Out I/F Label
1
5
128.89
0
3
2
8
128.89
0
7
…
…
…
…
…
5
1
Help! 0
128.89 Packet 8
8
8
8
2
7
3
7
3
7
3
• Multiple labels enable edge router to reassemble packets correctly 2201 1325_06_2000_c1
31
© 2000, Cisco Systems, Inc.
VC Merge In I/F
Packet
Cells 5
5
5
In Address Label Prefix
Out Out I/F Label
1
5
128.89
0
3
2
8
128.89
0
3
…
…
…
…
…
5
1
0
128.89 Packet 8
8
8
8
2
3
3
3
3
3
3
• With ATM switch that can merge VCs Can reuse outgoing label Hardware prevents cell interleave Fewer labels required For very large networks 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
32
Advanced MPLS • Basic MPLS: destination-based unicast • Many additional options for assigning labels • The key: separation of routing and forwarding Resource Destination-Based IP Class Reservation Unicast Routing of Service (eg RSVP)
Multicast Routing (PIM v2)
Explicit and Virtual Static Private Routes Networks
Label Information Base (LIB) Per-Label Forwarding, Queuing, and Multicast Mechanisms
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
33
Building VPNs with MPLS • Constrained distribution of routing information Routes are only communicated to routers that are members of a VPN
• VPN-IP addresses Supports overlapping address spaces
• Multiprotocol Label Switching (MPLS) Labels used to define VPNs Labels used to represent VPN-IP addresses
• Peer model Simplifies routing for end customers 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
34
MPLS VPN Example 12.1/16 VPN B/Site 1
VPN C/Site 2 CE1B1
11.1/16
CEA2 RIP
11.2/16 Static RIP
P1
RIP
CE2B1
BGP
PE1
Step 4
Step 2
CEA1
Static
Step 5 P3 CEB3
PE3
RIP BGP
2201 1325_06_2000_c1
16.2/16
CEA3
16.1/16 VPN A/Site 1
VPN B/Site 2
P2
Step 3 Step 1
CEB2
PE2
VPN A/Site 2 12.2/16
VPN C/Site 1
© 2000, Cisco Systems, Inc.
35
Routing Information Distribution Step 1: From site (CE) to service provider (PE) E.g. via RIP, OSPF, static routing, or BGP
Step 2: Export to provider’s BGP at ingress PE Step 3: Within/across service provider(s) (among PEs): E.g. via BGP
Step 4: Import from provider’s BGP at egress PE Step 5: From service provider (PE) to site (CE) E.g. via RIP, or static routing, or BGP
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
36
Packet Forwarding IP PKT Provider Edge LSR • IP packet received on sub-interface Label IP PKT • Sub-interfaced 1. Identify VPN configured with VPN ID FIB Table 3. Apply • BGP binds labels to Labels and Select VPN-IP routes Egress Port • LDP binds labels to IGP routes and defines CoS VPN LDP/CoS • Logically separate 2. Select FIB forwarding information for this VPN base (FIB) for each VPN 2201 1325_06_2000_c1
37
© 2000, Cisco Systems, Inc.
MPLS VPN Example 12.1/16 VPN B/Site 1
VPN C/Site 2 CE1B1
11.1/16 CE2B1
CEA2 RIP
11.2/16 Static RIP
P1
RIP
BGP
PE1
CEA1
Step 4
Step 2 Static
Step 5 P3 CEB3
PE3
RIP BGP
CEA3
16.1/16 VPN A/Site 1 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
VPN B/Site 2
P2
Step 3 Step 1
CEB2
PE2
16.2/16 VPN A/Site 2
12.2/16
VPN C/Site 1 38
Explicit Routing
• Traffic engineering requires the capability to specify a path • Voice networks, Frame Relay, ATM are explicitly routed at connection setup • But IP uses hop-by-hop destination-based routing 2201 1325_06_2000_c1
39
© 2000, Cisco Systems, Inc.
The “Fish” Problem R3 R4 R8
R2
R5
R1 R6
R7
IP Uses Shortest Path Destination-Based Routing Shortest Path May Not Be the only path Alternate Paths May Be under-Utilized while the Shortest Path Is over-Utilized 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
40
An LSP Tunnel R3 R4
R8
R2
R5
R1 R6
R7
Labels, Like VCIs Can Be Used to Establish Virtual Circuits Normal Route R1->R2->R3->R4->R5 Tunnel: R1->R2->R6->R7->R4 2201 1325_06_2000_c1
41
© 2000, Cisco Systems, Inc.
Traffic Engineering • Provides Constraint-based routing Similar to PNNI routing Control of traffic engineering Path selection Tunnel setup 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
42
Basic Traffic Engineering • LSP tunnels used to steer traffic (Termed traffic engineering or TE tunnels)
• Represent inter-POP traffic as flows in bits/sec • Determine bandwidth requirements for tunnels between POP pairs • Automated procedures route and setup the inter-POP TE tunnels 2201 1325_06_2000_c1
43
© 2000, Cisco Systems, Inc.
TE Components
(1) Information distribution Distributes constraints pertaining to links Available bandwidth is just one type of constraint
(2) Path selection algorithm Selects paths that obey the constraints 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
44
TE Components (Cont.) (3) Route setup Uses RSVP for signaling LSPs
(4) Link admission control Decides which tunnels may have resources
(5) Traffic engineering control Establishes and maintains tunnels
(6) Forwarding data 2201 1325_06_2000_c1
45
© 2000, Cisco Systems, Inc.
System Block Diagram Traffic Engineering Control Path Selection
TE Topology Database
RSVP
TE Link Adm Ctl
IS-IS/OSPF Routing
Flooding
Forwarding Engine 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
46
LSP Tunnel Setup R9
R8 R3 R4 R2
Pop
R5
R1
32 49 17
R6
R7
22
Setup: Path (R1->R2->R6->R7->R4->R9) Tunnel ID 5, Path ID 1 Reply: Communicates Labels and Label Operations Reserves Bandwidth on Each Link 2201 1325_06_2000_c1
47
© 2000, Cisco Systems, Inc.
Rerouting to an Alternate Path R9
R8 R3
X
R2
R4 Pop
R5
R1
32 49 17
R6
R7
22
Setup: Path (R1->R2->R3->R4->R9) Tunnel ID 5, Path ID 2 Until R9 Gets New Path Message, Current Resv Is Refreshed 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
48
Bridge and Roll R9
R8 R3 R4 R2
Pop Pop
26
89
R5
R1
32 38 49
17
R6
R7 22
Resv: Allocates Labels for Both Paths Reserves Bandwidth Once Per Link PathTear Can then Be Sent to Remove Old Path and Release Resources 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
49
Assigning Traffic to Tunnels • Automatic assignment based on IGP • Modified SPF calculation When the endpoint of a tunnel is reached, the next hop to that node is set to the tunnel interface Nodes downstream of the tunnel inherit the tunnel interface as their next hop (Encountering a node with its own tunnel replaces the next hop) 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
50
Topology with Tunnel R8 R3 R4 R2 R1 R5 R7
R6
Tunnel1: Path (R1->R2->R6->R7->R4) Tunnel2: Path (R1->R2->R3->R4->R5) Normal Dijkstra, Except Tunnel Interfaces Used when Tunnel Tail Is Encountered 2201 1325_06_2000_c1
51
© 2000, Cisco Systems, Inc.
Forwarding Tree R8 R3 R4 R2 R1
R5 R6
Tunnel1
R7
Tunnel2
R4 and R8 Have Tunnel1 Interface as Next Hop; R5 Has Tunnel2 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
52
Fast Reroute
• Goal—match Sonet restoral times—50 ms • Locally patch around lost facilities • Strategies Alternate tunnel (1->1 mapping) Tunnel within tunnel (n->1 mapping) 2201 1325_06_2000_c1
53
© 2000, Cisco Systems, Inc.
Fast Reroute
• Labels are carried in a stack, making it possible to nest tunnels • RSVP has a notion of PHOP, allowing the protocol to be independent of the back channel • A tunnel can use another tunnel as a tunnel hop to enable fast reroute 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
54
Nested Tunnels—Outer R9
R8 R3 R2
R5
R1
Pop 17
R6
R7
22
Setup: Path (R2->R3->R4) Session 5, ID 2 Labels Established on Resv Message 2201 1325_06_2000_c1
55
© 2000, Cisco Systems, Inc.
Nested Tunnels—Inner R9
R8
R2
14
R3
POP R5
R1
37 R6
R7
Setup: Path (R1->R2->R4->R9) Path Message Travels on Tunnel from R2 to R4 R4 Send Resv Message Directly to R2 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
56
Nested Tunnels—Operation
R8
Pop 14
Swap 37->14 Push 17
R9
R3
R2 Push 37 R5
R1
R7
R6 Swap 17->22 17 22 37 14 17
IP
2201 1325_06_2000_c1
Pop 22
57
© 2000, Cisco Systems, Inc.
Nested Tunnels—Fast Reroute
R8
Pop 14
Swap 37->14 Push 17 R2
Push 37
R3
X R5
R1
R6 Swap 17->22 IP
2201 1325_06_2000_c1
R9
17 22 37 14 17
© 2000, Cisco Systems, Inc.
R7 Pop 22
On Failure of Link from R2 -> R3, R2 Simply Changes the Outgoing Interface and Pushes on the Label for the Tunnel to R3 58
Conclusions: MPLS Fundamentals • Based on the label-swapping forwarding paradigm • As a packet enters an MPLS network, it is assigned a label based on its Forwarding Equivalence Class (FEC) As determined at the edge of the MPLS network
• FECs are groups of packets forwarded over the same Label Switched Path (LSP) 2201 1325_06_2000_c1
59
© 2000, Cisco Systems, Inc.
Conclusions: MPLS Main Ideas • Separate forwarding information (label) from the content of IP header • Single forwarding paradigm (label swapping)—multiple routing paradigms • Multiple link-specific realizations of the label swapping forwarding paradigm • Flexibility of forming Forwarding Equivalence Classes (FECs) • Forwarding hierarchy via label stacking 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
60
Topics
• Motivations for MPLS • MPLS Overview • Applications • Roadmap
2201 1325_06_2000_c1
61
© 2000, Cisco Systems, Inc.
Application: Multiservice ATM Backbone with IP • MPLS provides Scalable IP routing Advanced IP services ATM
Internet scale VPNs
• Benefits Lower operations costs Keep up with Internet growth
FR
IP
New revenue services Multiservice backbone Faster time to market 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
62
Application: Packet over SONET/SDH IP Backbone • MPLS provides Isolation of backbone from BGP Traffic engineering Guaranteed bandwidth Internet scale VPNs FR/ATM over MPLS
• Benefits Improved line utilization Increased reliability Convergence New revenue services 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
63
Application: Mixed POS/ATM Backbone • MPLS provides Tight integration of routers and ATM switches End-to-end IP services Internet scale VPNs
• Benefits Network design flexibility Transition to IP router backbone Faster time to market 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
64
Applications: Enterprise Backbone Other Campuses
FR, Voice
• MPLS provides Scalability
MPLS
IP services
Branches
Traffic engineering
Internet Si
Enterprise Backbone Enterprise LAN
• Benefits Flexibility Reduced complexity for lower cost 2201 1325_06_2000_c1
65
© 2000, Cisco Systems, Inc.
Topics
• Motivations for MPLS • MPLS Overview • Applications • Roadmap
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
66
Leadership MPLS Solutions
• IP and ATM integration
Available Today!
• MPLS traffic engineering • MPLS VPNs with integrated QoS 2201 1325_06_2000_c1
Available Today! Available Today!
67
© 2000, Cisco Systems, Inc.
Leadership MPLS Solutions
• MPLS VPN management • MPLS connection services
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
Available Today!
In Field Trial!
68
MPLS Platform Support BPX 8650
Catalyst 8540
BPX 8680
Cisco 4500, 4700
MGX 8850
LS1010 2201 1325_06_2000_c1
All Available Today! Cisco 3600, 2600
Cisco 7200
GSR 12000
Cisco 7500 69
© 2000, Cisco Systems, Inc.
Building on Open Standards IP Services VPNs
Tag Switching
QoS
Traffic Engineering
MPLS
• MPLS is based on Cisco’s tag switching • Cisco is using MPLS as the basis for developing support for new value-added IP services • Expect IETF ratification of the 12 MPLS RFCs in summer 2000 2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
70
MPLS: The Cisco Advantage • Industry IP leadership • Most advanced MPLS solutions • Broadest range of platforms supported in the industry today • MPLS solutions deployed in real world production networks • Standards-based solutions 2201 1325_06_2000_c1
71
© 2000, Cisco Systems, Inc.
Introduction to MPLS and Traffic Engineering Session 2201
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
72
Please Complete Your Evaluation Form Session 2201
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
73
2201 1325_06_2000_c1
© 2000, Cisco Systems, Inc.
74
