Title Slide: First Slide in a Presentation

advertisement
Service Provider QoS
Providing e2e Guarantees
Vijay Krishnamoorthy
Cisco IOS Technologies Division
April 2001
© 2001, Cisco Systems, Inc.
1
Agenda
• What is QoS?
• QoS Models
• Differentiated Services - DiffServ
• DiffServ in MPLS Networks
• MPLS Traffic Engineering
• DiffServ-Aware Traffic Engineering (DS-TE)
• DS-TE Solutions
• QoS Management
• Summary
© 2001, Cisco Systems, Inc.
2
What is Quality of Service?
ARM Your Network!
“
The Pragmatic Answer: QoS is Advanced
Resource Management
The Technical Answer: The Resources!!
Set of techniques to manage:
• Delay
• Delay Variation (Jitter)
• Bandwidth
• Packet Loss
© 2001, Cisco Systems, Inc.
”
3
The Value Proposition!
• Offer Any to Any Differentiated Services for Profitability:
Premium-Class Service – (E.g.: VoIP, Multicast Stock
Quotes, etc.)
Business-Class Service – (E.g.: SAP,Oracle,Citrix, etc.)
Best-Effort Service – (E.g.: Database Replication,
Backups, etc.)
• Icing on the profitability cake  Point-to-Point
QoS Guarantees:
P2P guarantees for Voice over IP trunks.
P2P guarantees for highly critical data traffic.
• Revenue in addition to Basic MPLS VPN & Internet
Service!
© 2001, Cisco Systems, Inc.
4
Service Provider Revenue/Margin
Potential
Today’s Basic Internet Access
Basic Internet Access @ 768 kpbs…………
Monthly Revenue/Margin
$500/$50
Managed Internet Access
Access prioritization by user, group………... $75/$60
Priority access during times of congestion… $75/$60
Usage reporting………………………………. $75/$60
Business Applications (ASP)
Priority to each customer’s requirements….. $100/$90
Streaming Services
Blocking delivery of undesirable services…. $50/$40
VPN Services
Low cost, software based …………………… $150/$100
TOTAL MARGIN POTENTIAL:
$460/customer = +820%
Source: Session M16C, SuperNet 2001
© 2001, Cisco Systems, Inc.
5
But…but… Bandwidth…...
“
“Money and sex, storage and bandwidth: only too
much is ever enough”
•Arno Penzias - Former Head of Bell Labs, and Nobel prizewinner
“The worldwide services market is about $1 trillion
US. By 2005 it will be around $5-7 trillion. Look for
growth in new services.”
•Vinod Khosola - Kleiner Perkins Ventures
”According to CIMI Corporation, by 2010, 67% of
transactions will be on value networks, not the
Internet”
© 2001, Cisco Systems, Inc.
”
6
So, What Will Fill Up The Pipe?
Source: Internet2 QBone WG
© 2001, Cisco Systems, Inc.
7
QoS Models
©©2001,
2001,Cisco
CiscoSystems,
Systems,Inc.
Inc.
8
The IP QoS Pendulum
Time
No state
Aggregated
state
Best Effort
DiffServ
Per-flow state
IntServ / RSVP
1. The original IP service
2. First efforts at IP QoS
3. Seeking simplicity and scale
4. Bandwidth Optimization & e2e SLAs
((IntServ+DiffServ+ Traffic Engineering))
© 2001, Cisco Systems, Inc.
9
The Cisco QoS Framework
POLICY-BASED NETWORKING
IntServ
Multimedia
Video Conference,
Collaborative Computing
DiffServ
MPLS
VPNs
Hybrid
Signaling Techniques (RSVP, DSCP*, ATM (UNI/NNI))
Classification & Marking Techniques (DSCP, MPLS EXP, NBAR, etc.)
Congestion Avoidance Techniques (WRED)
Traffic Conditioners (Policing, Shaping)
Congestion Management Techniques (WFQ, CBWFQ, LLQ)
PROVISIONING & MONITORING
Mission Critical
Services
VoIP
Link Efficiency Mechanisms (Compression, Fragmentation)
Frame
Relay
© 2001, Cisco Systems, Inc.
PPP
HDLC
SDLC
ATM, POS
FE,Gig.E
10GE
Wireless
Fixed,Mobile
BroadBand
Cable,xDSL
10
Differentiated Services
Architecture - DiffServ
©©2001,
2001,Cisco
CiscoSystems,
Systems,Inc.
Inc.
11
Differentiated Services
The IETF DiffServ Model
• Use 6 bits in IP header to sort traffic into
“Behavior Aggregates”…AKA Classes!
• Defines a number of “Per Hop Behaviors PHBs”
• Two-Ingredient Recipe:
Condition the Traffic at the Edges
Invoke the PHBs in the Core
• Use PHBs to Construct Services such as
Virtual Leased Line!
© 2001, Cisco Systems, Inc.
12
The Hook for IPv4 Classification
Referred to as Packet Classification or Coloring
Layer 3
IPV4
Version ToS
Len
Length 1 Byte
Standard IPV4: Bits 0-2 Called IP Precedence (Three MSB)
(DiffServ Uses Six ToS bits…: Bits 0-5, with Two Reserved)
ID
offset
TTL Proto FCS IP-SA IP-DA
Data
Layer 3 Mechanisms Provide End-to-End Classification
© 2001, Cisco Systems, Inc.
13
IPv4 ToS vs. DS-Field
© 2001, Cisco Systems, Inc.
14
Defined PHBs
• Expedited Forwarding (EF): RFC2598
dedicated low delay queue
Comparable to Guaranteed B/W in IntServ
• Assured Forwarding (AF): RFC2597
4 queues  3 drop preferences
Comparable to Controlled Load in IntServ
• Class Selector: Compat. with IP Prec
• Default (best effort)
© 2001, Cisco Systems, Inc.
15
AF PHB Group Definition
AF Class 1: 001dd0
AF Class 2: 010dd0
AF Class 3: 011dd0
AF Class 4: 100dd0
dd = drop preference
Eg. AF12 = Class 1, Drop 2, thus “001100”
• 4 independently-forwarded AF classes
• Within each AF class, 3 levels of drop priority! This is very
useful to protect conforming to a purchased, guarantee rate,
while increasing chances of packets exceeding contracted rate
being dropped if congestion is experienced in the core.
© 2001, Cisco Systems, Inc.
16
The DiffServ Traffic Conditioner
•Classifier: selects a packet in a traffic stream based on the content of some portion
of the packet header
•Meter: checks compliance to traffic parameters (e.g., Token Bucket) and passes
result to marker and shaper/dropper to trigger particular action for in/out-of-profile
packets
•Marker: Writes/rewrites the DSCP value
•Shaper: delay some packets for them to be compliant with the profile
© 2001, Cisco Systems, Inc.
17
The DiffServ Architecture
(RFC-2475)
© 2001, Cisco Systems, Inc.
18
Cisco IOS DiffServ
• Cisco IOS 12.1(5)T+ & 12.2+ are fully
compliant with all the Core DiffServ
RFCs (RFCs: 2474,2475,2597,2598)
• Compliant Platforms*:
C36xx, C72xx, C75xx - Now
More Platforms in the Near Future...
© 2001, Cisco Systems, Inc.
19
An Application Note
©©2001,
2001,Cisco
CiscoSystems,
Systems,Inc.
Inc.
20
Source Predictability
• TCP will keep at most a certain amount of
traffic in flight
We say it is “elastic”—rate is proportional to
latency
• Voice will send only and exactly as fast as
the coding algorithm permits (Also Video
to an extent)
We say it is “inelastic”
© 2001, Cisco Systems, Inc.
21
TCP Flow Statistics
• >90% of sessions have ten packets each
way or less
Transaction mode (mail, small web page)
• >80% of all TCP traffic results from <10%
of the sessions, in high
rate bursts
It is these that we worry about managing
© 2001, Cisco Systems, Inc.
22
Behavior of a High-Throughput /
Bulk-Transfer TCP Session
45
40
35
Congestion Avoidance Phase
Linear Growth
30
25
20
15
10
5
Slow Start
Exponential Growth
0
20
© 2001, Cisco Systems, Inc.
50
23
VoIP Delay Budget
Cumulative Transmission Path Delay
Satellite Quality
Fax Relay, Broadcast
High Quality
0
100
200
300
400
500
600
700
800
Time (msec)
Delay Target (max)
ITU’s G.114 Recommendation = 0–150 msec 1-Way Delay
© 2001, Cisco Systems, Inc.
24
Application QoS Requirements
Voice
FTP
ERP and
Mission-Critical
Bandwidth
Low to
Moderate
Moderate
to High
Low
Random Drop Sensitive
Low
High
Moderate
To High
Delay Sensitive
High
Low
Low to
Moderate
Jitter Sensitive
High
Low
Moderate
© 2001, Cisco Systems, Inc.
25
DiffServ & MPLS
©©2001,
2001,Cisco
CiscoSystems,
Systems,Inc.
Inc.
26
DiffServ Scalability via
Aggregation
1000’s
of flows
Diff-Serv:
Diff-Serv:
Aggregation on Edge
Aggregated Processing in
Core
Many flows associated with
a Class (marked with DSCP)
Scheduling/Dropping (PHB)
based on DSCP
DiffServ scalability comes from:
- aggregation of traffic on Edge
- processing of Aggregate only in Core
© 2001, Cisco Systems, Inc.
27
MPLS Scalability via Aggregation
1000’s
of flows
MPLS:
MPLS:
Aggregation on Edge
Many flows associated with
a Forwarding Equivalent
Class (marked with label)
Aggregated Processing in
Core
Forwarding based on label
MPLS scalability comes from:
- aggregation of traffic on Edge
- processing of Aggregate only in Core
© 2001, Cisco Systems, Inc.
28
MPLS & DiffServ - The Perfect
Match!
1000’s
of flows
MPLS: flows
associated with
FEC, mapped
into one label
DS: flows associated
with Class, mapped
to DSCP
MPLS:
Switching
based on
Label
DS:
Scheduling/Dropping
based on DSCP
Because of same scalability goals, both models do:
- aggregation of traffic on Edge
- processing of Aggregate only in Core
© 2001, Cisco Systems, Inc.
29
MPLS - So What’s New?
The Shim Header!!
Non-MPLS
Diff-Serv Domain
IPv4 Packet
MPLS
Diff-Serv Domain
MPLS Header
DSCP
DSCP
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
| EXP |S|
TTL
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
• DSCP field is not directly visible to MPLS Label Switch Routers
(they forward based on MPLS Header)
• Information on DiffServ must be made visible to LSR in MPLS
Header (using EXP field / Label)
© 2001, Cisco Systems, Inc.
30
DiffServ o MPLS : “Coloring”
MPLS Frames
• This describes how “DiffServ” information
is conveyed to LSRs in MPLS Header
• Two methods:
– E-LSP {{ Cisco IOS 12.1(5)T, 12.0(11)ST }}
“Queue” inferred from Label and EXP field
“Drop priority” inferred from label and EXP
field
– L-LSP {{ Planned, once an RFC }}
“Queue” inferred exclusively from Label
“Drop priority” inferred from EXP field
© 2001, Cisco Systems, Inc.
31
The E-LSP Story...
LDP/RSVP
LSR
LDP/RSVP
E-LSP
AF1
EF
• E-LSPs can be established by various label binding protocols
(LDP or RSVP)…no new Signalling Needed.
• Example above illustrates support of EF and AF1 on a single ELSP (Note: This is the plain old LSP established for MPLS
Switching)
Note: EF and AF1 packets travel on single LSP (single label)
but are enqueued in different queues (different EXP values)
• Queue & Drop Precedence is selected based on EXP
© 2001, Cisco Systems, Inc.
32
L- LSP Example (Tomorrow)
Supporting 64 Classes!
LDP/RSVP
LDP/RSVP
LSR
L-LSPs
• L-LSPs can be established by various label binding
protocols (LDP or RSVP)…EXTENSIONS REQUIRED!
• Example above illustrates support of EF and AF1 on
separate L-LSPs
– EF and AF1 packets travel on separate LSPs and are
enqueued in different queues (different label values)
– Queue selected based on Label, Drop Precedence Selected
with Optional EXP field.
© 2001, Cisco Systems, Inc.
33
Cisco DiffServ o MPLS
• Cisco IOS 12.1(5)T
• C72xx, C75xx, C12xxx [12.0(ST)]
• MPLS QoS Enhancements*
• Operate exclusively on EXP bits
• Leave the IP ToS Byte Untouched
• QoS is QoS!
– Some New Stuff, But Same Goals!
– Service the Applications!!
© 2001, Cisco Systems, Inc.
34
The QoS is In the Details!
• So, What’s Changed?:
Can Classify based on the EXP bits
(MQC/CAR)
Can Mark the EXP bits
(MQC/Policer/CAR)
WRED & WFQ & MDRR act on EXP bits
(instead of Precedence/DSCP)
© 2001, Cisco Systems, Inc.
35
A Note on CoS Translation…
(Preservation of Classification e2e)
• Developed as flexible translation:
• CoS = {IP Prec., DSCP, EXP, ATM CLP, F.Relay DE-Bit, 802.1Q/p}
• CoS translation = Translation from Any (Except ATM CLP) to Any
• Extensions to the “Modular QoS CLI”:
1) Extended “matches” for “class-maps”:
match
match
match
match
match
fr-de
cos <0-7>
ip precedence n
ip dscp n
mpls exp <0-7>
2) Extended “sets” for “policy-maps”:
set
set
set
set
set
set
© 2001, Cisco Systems, Inc.
atm-clp
fr-de
cos <0-7>
ip precedence n
ip dscp n
mpls exp n
36
MQC CoS Translation: An
Example
Incoming IP packets with Prec=p
to be transmitted with EXP=e
LDP
IP
LSR
LDP
LSP
MPLS
class-map inputc
match ip prec p
policy-map inputp
class inputc
set qos-group q
Incoming interface> service-policy input inputp
© 2001, Cisco Systems, Inc.
class-map outputc
match qos-group q
policy-map outputp
class outputc
set mpls exp e
Outgoing interface> service policy output outputp
37
MPLS Traffic Engineering
©©2001,
2001,Cisco
CiscoSystems,
Systems,Inc.
Inc.
38
The “Fish” Problem
R8
R3
R4
R5
R2
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
© 2001, Cisco Systems, Inc.
39
An LSP Tunnel
(A Constrained MPLS Label Switched Path)
R8
R3
R4
R5
R2
R1
R6
R7
Labels, Like VCIs (ATM) Can Be Used to Establish Virtual Circuits
Normal Route R1->R2->R3->R4->R5
Tunnel: R1->R2->R6->R7->R4
© 2001, Cisco Systems, Inc.
40
LSP Tunnel Setup
(a.k.a Traffic Engineering [TE] Tunnel)
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
© 2001, Cisco Systems, Inc.
41
Real-World MPLS TE Use!
Find route & set-up tunnel for 20 Mb/s from POP1 to POP4
Find route & set-up tunnel for 10 Mb/s from POP2 to POP4
WAN area
POP4
POP1
POP
POP2
POP
© 2001, Cisco Systems, Inc.
POP
42
MPLS TE & QoS –
The Relationship
• MPLS TE designed as tool to improve backbone efficiency
independently of core QoS techniques:
MPLS TE compute routes for aggregates across all PHBs.
A Single Chunk of Bandwidth requested for the
Tunnel
MPLS TE performs admission control over a global b/w pool.
Un-aware of bandwidth allocated to each Class / PHB
• MPLS TE and MPLS DiffServ:
Can run simultaneously in a network.
Can provide their own individual benefits
TE distributes aggregate load
DiffServ provides differentiation)
Are unaware of each other
© 2001, Cisco Systems, Inc.
43
DiffServ-Aware
Traffic Engineering
©
© 2001,
2001, Cisco
Cisco Systems,
Systems, Inc.
Inc.
44
Delay/Load Trade-Off
Delay
Good
Best-Effort
Target
Data
Premium
Target
Percentage
Priority
Traffic
Voice
Target
0%
%
 % 100%
If I can keep EF traffic <  % , I will keep EF delay under M1 ms
If I can keep AF1 traffic <  % , I will keep AF1 delay under M2 ms
© 2001, Cisco Systems, Inc.
45
Motivation for DiffServ-Aware TE
(DS-TE)
• Thus, with DiffServ, there are additional constraints to
ensure the QoS of each class:
- Good EF behavior requires that aggregate EF traffic is less
than small  % of link
- Good AF behaviors requires that aggregate AF traffic is less
than reasonable  % of link
• =>Cannot be enforced by current Aggregate TE
• => Requires DiffServ-Aware TE
•
- Constraint Based Routing per Class with different
bandwidth constraints
•
- Admission Control per Class over different
bandwidth pools (ie bandwidth allocated to class
queue)
© 2001, Cisco Systems, Inc.
46
The Trouble With DiffServ
(We Want it All, We Want it Now!)
• As currently formulated, DiffServ is strong
on simplicity and weak on guarantees
• Virtual Leased Line using EF is quite firm,
but how much can be deployed?
No topology-aware admission control
mechanism
• Example: How do I reject the “last straw”
VoIP TRUNK that will degrade service of
calls & trunks currently active?
© 2001, Cisco Systems, Inc.
47
DiffServ-Aware TE:
Protocol Components
• Current IGP(*) extensions for TE:
advertise “unreserved TE bandwidth” (at each
preemption level)
• Proposed IGP(*) extensions for DS aware
TE:
Class-Types= group of DiffServ classes sharing
the same bandwidth constraint (e.g. AF1x and
AF2x)
advertise “unreserved TE bandwidth” (at each
preemption level) for each Class-Type
(*) OSPF and ISIS
© 2001, Cisco Systems, Inc.
48
DiffServ-Aware TE:
Protocol Components
• Current LSP-signalling (*) extensions for
TE:
at LSP establishment signal TE tunnel
parameters (label, explicit route, affinity ,
preemption,…)
• Proposed LSP-signalling (*) extensions for
DS aware TE:
also signal the Class-Type
perform Class-Type aware CAC
(*) RSVP-TE and CR-LDP
© 2001, Cisco Systems, Inc.
49
DiffServ - Aware TE:
Protocol Components
• Current Constraint Based Routing for TE:
compute a path such that on every link :
- there is sufficient “unreserved TE
bandwidth”
• Proposed Constraint Based Routing for
DS aware TE:
same CBR algorithm but satisfy bandwidth
constraint over the “unreserved bandwidth for
the relevant Class-Type” (instead of aggregate
TE bandwidth)
© 2001, Cisco Systems, Inc.
50
DS-TE Standardization Status
• Standardization effort initiated 2 IETFs ago
• Internet Drafts submitted at Dec 2000
IETF:
draft-ietf-mpls-diff-te-reqts-01.txt
draft-ietf-mpls-diff-te-ext-00.txt
draft-lefaucheur-diff-te-ospf-00.txt
draft-lefaucheur-diff-te-isis-00.txt
© 2001, Cisco Systems, Inc.
51
Aggregate TE in a Best Effort
Network
Find route & set-up tunnel for 20 Mb/s from POP1 to POP4
Find route & set-up tunnel for 10 Mb/s from POP2 to POP4
WAN area
POP4
POP1
POP
POP2
POP
© 2001, Cisco Systems, Inc.
POP
52
Aggregate TE in a DiffServ
Network
Find route & set-up tunnel for 20 Mb/s (aggregate) from POP1 to POP4
Find route & set-up tunnel for 10 Mb/s (aggregate) from POP2 to POP4
WAN area
POP4
POP1
POP
POP2
POP
© 2001, Cisco Systems, Inc.
POP
53
DiffServ-Aware Traffic
Engineering
Find route & set-up tunnel for 5 Mb/s of EF from POP1 to POP4
Find route & set-up tunnel for 3 Mb/s of EF from POP2 to POP4
WAN area
POP4
POP1
POP2
POP
Find route & set-up tunnel for 15 Mb/s of BE from POP1 to POP4
Find route & set-up tunnel
for 7 Mb/s of BE from POP2POP
to POP4
POP
© 2001, Cisco Systems, Inc.
54
DS-TE Applications
Guaranteed Bandwidth Services
©©2001,
2001,Cisco
CiscoSystems,
Systems,Inc.
Inc.
55
DiffServ-Aware Traffic
Engineering
Find route & set-up tunnel for 5 Mb/s of EF from POP1 to POP4
Find route & set-up tunnel for 3 Mb/s of EF from POP2 to POP4
WAN area
POP4
POP1
POP2
POP
Find route & set-up tunnel for 15 Mb/s of BE from POP1 to POP4
Find route & set-up tunnel
for 7 Mb/s of BE from POP2POP
to POP4
POP
© 2001, Cisco Systems, Inc.
56
MPLS Guaranteed Bandwidth
• Combining MPLS DiffServ & DS-TE to achieve
strict point-to-point QoS guarantees
• A new “sweet-spot” on the QoS Spectrum
Aggregated State (DiffServ)
Aggregate Admission Control (DS-TE)
Aggregate Constraint Based Routing (DS-TE)
No state
Best effort
Aggregated
state
Per-flow state
MPLS DiffServ
+ MPLS DS-TE
DiffServ
MPLS
guaranteed
bandwidth
© 2001, Cisco Systems, Inc.
RSVP v1/
Intserv
57
MPLS Guaranteed Bandwidth
• “Guaranteed QoS” is a unidirectional point-to-point
bandwidth guarantee from Site-Sx to Site-Sy: Point-toPoint
• “Site” may include a single host, a “pooling point”, etc.
N2 Mb/s
guarantee
CE
10.2
CE
11.5
N1 Mb/s guarantee
CE
11.6
© 2001, Cisco Systems, Inc.
10.1
CE
58
MPLS Guaranteed Bandwidth
• “Guaranteed QoS” is a unidirectional point-to-point
bandwidth guarantee from Site-Sx to Site-Sy
• “Site” may include a single host, a “pooling point”, etc.
N2 Mb/s
guarantee
10.2
CE
CE
11.5
N1 Mb/s guarantee
CE
11.6
CE 10.1
DS-TE LSP for AF or EF, used to transport guaranteed
bandwidth traffic edge-to-edge
© 2001, Cisco Systems, Inc.
59
DS-TE Applications
Voice over MPLS Trunks
© 2001, Cisco Systems, Inc.
60
Target Applications
• Voice Trunking
Solution 1: Toll Bypass with Voice Network
Solution 2: Toll Bypass with Voice/Data
Converged Network
Solution 3: Toll Bypass with VoIP Network
• Virtual Leased Lines
Solution 4: Virtual Leased Lines – Serial Links
Solution 5: Virtual Leased Lines – Frame Relay
Solution 6: Virtual Leased Lines – ATM
© 2001, Cisco Systems, Inc.
61
Solution 1: Toll Bypass with Voice
Network
Class 5
legacy
switches
PSTN –
Traditional TDM
Network
Traditional
Telephony
PBX with
Packet
Interface
Toll Bypass
PE
Solution
Requirements

© 2001, Cisco Systems, Inc.
PBX with
Packet
Interface
QoS on PE
Router
+
Mapping
Traffic to
Tunnels
GB Tunnel
+
QoS on
Core
Routers
Traditional
Telephony
PE
=
Diffserv Aware
Traffic Engineering
62
Solution 2: Toll Bypass with Voice/Data
Converged Network
PBX with
Circuit
Emulation
Interface
Class 5
legacy
switches
PSTN –
Traditional TDM
Network
CE
CE
Enterprise
LAN
PE
Solution
Requirements
Enterprise
LAN
Toll Bypass

© 2001, Cisco Systems, Inc.
QoS on CE
Router
+
QoS on PE
Router
GB Tunnel
+
Mapping
Traffic to
Tunnels
PE
+
QoS on
Core
Routers
=
Diffserv Aware
Traffic Engineering
63
Solution 3: Toll Bypass with VoIP
Network
Class 5
legacy
switches
PSTN –
Traditional TDM
Network
IP Phone
MultiService
Switch
MultiService
Switch
CE
CE
Enterprise
LAN
Enterprise
LAN
Toll Bypass
PE
Solution
Requirements
IP Phone

© 2001, Cisco Systems, Inc.
QoS on CE
Router
+
QoS on PE
Router
GB Tunnel
+
Mapping
Traffic to
Tunnels
PE
+
QoS on
Core
Routers
=
Diffserv Aware
Traffic Engineering
64
Voice Trunking - Summary
PSTN –
Traditional TDM
Network
Central
Traditional Office
Telephony
Class 5
legacy switches
Central
Office
Traditional
Telephony
MPLS Network
VoIP
Gateway
VoIP
Gateway
Toll Bypass
Voice Trunking
PE
GB Tunnel
PE
PE
CE
CE
PE
Enterprise
LAN
Enterprise
LAN
PE
VPN Service
Internet Service
© 2001, Cisco Systems, Inc.
Enterprise
LAN
PE
Regular TE Tunnel
Internet
Access
Router
Internet
Access
Router
Enterprise
LAN
65
Solution 4: Virtual Leased Lines –
Serial Links
MPLS Backbone
Serial Link
Serial Link
PE
Virtual Leased
Line (DS-TE +
QoS)
CE
PE
CE
Serial IP
or PPP or
HDLC over
MPLS
© 2001, Cisco Systems, Inc.
DS-TE Tunnel
Serial IP
or PPP or
HDLC over
MPLS
66
Solution 5: Virtual Leased Lines –
FR Networks
Any Transport over
MPLS (AToM)
Tunnel
MPLS
Backbone
PE
Virtual Leased Line
(DS-TE + QoS)
DS-TE Tunnel
Frame Relay
PE
Frame Relay
Frame Relay DLCI
CPE Router, FRAD
© 2001, Cisco Systems, Inc.
CPE Router, FRAD
67
Solution 6: Virtual Leased Lines –
ATM Networks
Any Transport over
MPLS (AToM)
Tunnel
MPLS
Backbone
PE
Virtual Leased Line
(DS-TE + QoS)
DS-TE Tunnel
ATM
PE
ATM
ATM Virtual Circuits
CPE Router
© 2001, Cisco Systems, Inc.
CPE Router
68
QoS Management
©
© 2001,
2001, Cisco
Cisco Systems,
Systems, Inc.
Inc.
69
Complete Service Management
VERIFICATION
XML
Qos network
QPM
policy configuration
TROUBLESHOOT
XML
Network
CW2000service
SMS
level verification
ServiceRWAN
level
CW2000
troubleshooting
(IPM)
Device
Network Wide
CONFIGURE
Per-device
traffic
QDM, ...
class configuration
© 2001, Cisco Systems, Inc.
Per-device
QDM, ... traffic
class monitoring
70
The Service Level Management
Architecture
A proven architecture
Data
Collector
Aggregator
http
http
XML
CW2000 SMS
SLM Server
http
http
XML
http XML
http XML
ME1100
http interface
SNMP
Data
Collector
Aggregator
HTTP Interface
ME1100
http interface
SNMP
SDK
Third Party
Third Party
Application
Third Party
Application
Application
© 2001, Cisco Systems, Inc.
71
Summary
© 2001, Cisco Systems, Inc.
72
How to Build
A “Point-to-Cloud” Service?
• Scenario 1:
– Constrained Access
– Unconstrained Backbone
Best-Effort o MPLS
DiffServ o IP
DiffServ o IP
MPLS VPN
© 2001, Cisco Systems, Inc.
73
How to Build
A “Point-to-Cloud” Service?
• Scenario 2:
– Constrained Access
– Constrained Backbone
DiffServ o MPLS
DiffServ o IP
DiffServ o IP
MPLS VPN
© 2001, Cisco Systems, Inc.
74
How to Build
A “Point-to-Cloud” Service?
• Scenario 3:
– Constrained Access
– Constrained Backbone
– Optimised Backbone (Traffic Eng.)
DiffServ o MPLS, GB-TE
DiffServ o IP
DiffServ o IP
MPLS VPN
© 2001, Cisco Systems, Inc.
75
© 2001, Cisco Systems, Inc.
76
Download