QoS Management & Traffic Engineering for IP Networks

60
QoS Management & Traffic Engin eering for IP Networks Taesang Choi 2001. 5. 24. Internet Technology Department ETRI

description

QoS Management & Traffic Engineering for IP Networks. Taesang Choi 2001. 5. 24. Internet Technology Department ETRI. Topics. QoS Management & TE Challenges QoS Management & TE in Papers QoS & TE Features in Devices QoS Management & TE in Action Summary Q&A. - PowerPoint PPT Presentation

Transcript of QoS Management & Traffic Engineering for IP Networks

Page 1: QoS Management & Traffic Engineering  for IP Networks

QoS Management & Traffic Engineering for IP Networks

Taesang Choi2001. 5. 24.

Internet Technology DepartmentETRI

Page 2: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 2

Topics

QoS Management & TE Challenges QoS Management & TE in Papers QoS & TE Features in Devices QoS Management & TE in Action Summary Q&A

Page 3: QoS Management & Traffic Engineering  for IP Networks

QoS Management & TE Challenges

Page 4: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 4

QoS Management Challenges

QoS Demand

No16%

Yes84%

YesNo

No44%

Yes56%

YesNo

WAN LAN

Courtesy: Forrester, 8.98., Fortune1000 Companies

Page 5: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 5

IP Application TaxonomyInteractive Stream- Distance

learning- Multi-Player

gamesInteractive Burst- Chat (IRC)- Resource

discovery- Shared editing

Isochronous Stream- A/V

Conferencing- Distributed

simulation- Real-time

modeling

Mission-CriticalStream- Distributed

process

Mission-CriticalBurst- Auction

Asynchronous Burst- News- Session

announcement

Interactive Stream- Thin client- X-windows

Interactive Burst- Web browsing- Resource Sharing- Database access

- POS transactions- Remote login- Chat (text-based)

Isochronous Stream- Telephone

Isochronous Burst

- Database updates

Mission-CriticalStream- Telemedicine- Remote control

Mission-CriticalBurst- Financial X-

actions

Asynchronous Burst- E-mail- File Transfer- Push Media

SynchronousStream- Streaming media- Data collection- Push media

Isochronous Stream- Data collection- Process

monitoring- Push media

Mission-CriticalStream- Data collection- Process

monitoring- Push media

Muti-Way(many-to-manybidirectional)

Two-Way(one-to-one

bidirectional)

One-Way(one-to-one orone-to-many

unidirectional)

Delay Tolerant Delay Intolerant

Best Effort Service Controlled Load Guaranteed

- Real-time Multimedia- Transaction Processing- Elastic or Bulk Transfer

Traffic

Page 6: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 6

IP Nets: Enterprises

Central Site

Remote Office

Remote Location: High-speed FR sites

Remote Location: Low-speed FR sites

Remote Locations: High-speed Leased Line sites

Remote Locations: Low-speed Leased Line sites

E-commercesite

ExtranetIDC

Intranet

Internet

T3

10MbpsEthernet

100MbpsEthernet

10MbpsEthernet

10MbpsEthernet

100Mbps – 1GbpsEthernet

Campus Net & NOC

Remote Office

IP VPN- Low to High speed Intra Nets- Heterogeneous net environ: intra, extra, VPN,

etc.- Heterogeneous app environ: simple ~ mission

critical- Increased QoS Management requirement

Page 7: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 7

IP Nets: Service Providers

POP

POP

POP

POP

POP

POP

-IP over Frame Relay-IP over ATM-IP over SONET-IP over (D)WDM-IP over DiffServ-IP over MPLS-T3 ~ OC768-Billing & Service Mgmt-Strong QoS & TE requirements

Page 8: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 8

QoS Management Challenges

To limit the amount of BW for web during the day but be flexible enough to impose fewer limits during off-hours

To ensure that file transfers don’t interfere with mission-critical traffic during the day but allow important ordering and financial file transfers that run during the night to get through during their time window

Page 9: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 9

QoS Management Challenges

To allow A/V to be delivered with minimum delay

To ensure that the response time for SAP, PeopleSoft, and Tn3270 traffic is three seconds or less and consistent

To ensure that the remote offices serviced by the VPN receive good service

To limit new peer-to-peer traffic such as Napster

Page 10: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 10

QoS Management Challenges

To map and guarantee customer’s QoS requirements in a service provider’s network

To monitor, measure, and analyze traffic to ensure SLA and to account for billing

Not a few international firms adopted QoS solutions already and some domestic firms such as a national-scale bank is considering QoS solutions for their mission-critical applications

Page 11: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 11

TE Challenges

TE is particularly important concern to service providers

Traffic increases much faster than expected

Thus, over-provisioning doesn’t seem to justify the cost

Large NSPs & ISPs tend to depend on TE for their traffic (QoS) & resource (utilization) control

Current IGP control mechanism is limited

Page 12: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 12

TE Challenges Ideally TE requires

Modification of traffic management parameters, Modification of parameters associated with routing, Modification of attributes and constraints associated

with resources The level of manual intervention involved in the

TE process should be minimized whenever possible

TE system includes a set of interconnected network elements, a network performance monitoring system, a set of network configuration management tools

Page 13: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 13

TE Challenges On-line TE and Off-line TE is not competitive but

complementary to each other This is particularly important from the Network

Management perspective Although MPLS is designed to meet these

requirements, there are still some efforts to achieve TE objectives by modifying the current routing protocol mechanisms by changing link state flooding frequencies The integrated approach that achieves TE

objectives based on physical topology routing instead of full-mesh overlaying routing (e.g., ATM, MPLS)

Page 14: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 14

QoS Management & TE Challenges

The Question is not, “Do you need a QoS or TE manager?” but “Which QoS or TE manager is right for you?”

Page 15: QoS Management & Traffic Engineering  for IP Networks

QoS Management & TE in Papers

Page 16: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 16

Related Standards

IETF Sub-IP Area’s WGs: MPLS, TE, CCAMP, etc. CR-LDP/RSVP-TE, ISIS-TE/OSPF-TE, MPLS MIBs TE for TE requirements, framework, DiffServ-aware MPLS TE, and TE MI

B IETF O&M Area’s WGs: Policy, RAP, SNMPConf, RMON

COPS(Common Open Policy Service) SPPI (Structure of Policy Provisioning Info) PIB (Policy Information Base) SNMP Configuration MIB for DiffServ

IETF Transport Area’s WG: DiffServ PHBs, PDBs, DiffServ PIB

DMTF(Distributed Management Task Force) DEN (Directory Enabled Networking)

IEEE 802.1p, 802.1Q and 802.1D: classify Ethernet frames

Page 17: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 17

QoS Management & TE Tools:Control Plane Tools

Routing Intra-domain/Inter-domain Constraint-based Routing (OSPF-TE/ISIS-TE) Rerouting/Fast-rerouting (IGP-Shortcut LSPs)

Signaling and Reservation CR-LDP/RSVP-TE

Path selection/Class mapping based on QoS requirements (DiffServ-aware MPLS TE)

Policy and admission control (DiffServ PDB) Load sharing/balancing Path protection/restoration Accounting, authorization and authentication Policy-based off-line control

DiffServ-based QoS configuration MPLS, MPLS VPNs configuration

Page 18: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 18

QoS Management & TE Tools:

Data Plane Tools

Classification, metering, marking, policing, shaping

Buffer management Queue scheduling Congestion control Merging, aggregation and de-aggregation

Page 19: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 19

QoS Management & TE Tools:Data Plane Tools SLA Management

AdmissionControl/

Classification Constrain-basedRouting

Policing

Shaping

CongestionControl

Traffic Monitoring/Measurement

Signalling

QueueManagement

Traffic Analysis/Reporting

Policy-basedOff-line Configuration

Automation

Page 20: QoS Management & Traffic Engineering  for IP Networks

QoS & TE Features in Devices

Page 21: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 21

Cisco’s QoS Features Classification:

Committed Access Rate (CAR) Policy Based Routing (PBR) QoS Policy Propagation through BGP

Congestion Management: First In First Out (FIFO) Priority Queueing (PQ) Custom Queueing (CQ) Weighted Fair Queueing (WFQ) Weighted Random Early Detection (WRED)

Page 22: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 22

Cisco’s QoS Features

Policing and Shaping: Committed Access Rate (CAR) Generic Traffic Shaping (GTS) Frame Relay Traffic Shaping (FRTS)

Link Efficiency Mechanisms: Compressed Real Time Protocol Link Fragmentation and Interleaving (LFI)

Signalling: RSVP

IP-ATM CoS (Class of Service)

Page 23: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 23

The Cisco QoS Framework

PR

OV

ISIO

NIN

G &

MO

NIT

OR

ING

PR

OV

ISIO

NIN

G &

MO

NIT

OR

ING

VPNsVPNsMultimediaVideo Conference,

Collaborative Computing

MultimediaVideo Conference,

Collaborative Computing

Mission Critical Services

Mission Critical ServicesVoIPVoIP

HybridHybridMPLSMPLSDiffServDiffServIntServIntServ

Signaling Techniques (RSVP, DSCP*, ATM (UNI/NNI))Signaling Techniques (RSVP, DSCP*, ATM (UNI/NNI))

Link Efficiency Mechanisms (Compression, Fragmentation)Link Efficiency Mechanisms (Compression, Fragmentation)

Congestion Avoidance Techniques (WRED)Congestion Avoidance Techniques (WRED)

Congestion Management Techniques (WFQ, CBWFQ, LLQ)Congestion Management Techniques (WFQ, CBWFQ, LLQ)

Classification & Marking Techniques (DSCP, MPLS EXP, NBAR, etc.)Classification & Marking Techniques (DSCP, MPLS EXP, NBAR, etc.)

FrameRelay

FrameRelay

PPPHDLC

PPPHDLC SDLC

SDLCATM, POSATM, POS FE,Gig.E

10GE

FE,Gig.E 10GE

WirelessFixed,Mobile

WirelessFixed,Mobile

BroadBandCable,xDSL

BroadBandCable,xDSL

PO

LIC

Y-B

AS

ED

NETW

OR

KIN

GP

OLIC

Y-B

AS

ED

NETW

OR

KIN

G

Traffic Conditioners (Policing, Shaping, CAR)Traffic Conditioners (Policing, Shaping, CAR)

Courtesy: 2001@ Cisco Systems Inc.

Page 24: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 24

Cisco’s MPLS TE Features

MPLS TE is built on the following IOS mechanisms LSP tunnels Link-state IGPs

with extensions for the global flooding of resource info. and for the automatic routing of traffic onto tunnels as appropriate

Path Calculation Module Link Management Module

link admission control, bookkeeping of the resource info to be flooded

Label Switching and Forwarding Signaling Module Load Sharing Module Link Protection/Restoration Module

Page 25: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 25

Juniper’s QoS & TE Features

No DiffServ Support yet Mostly focused on MPLS TE & MPLS-based VPN Not many QoS features like Cisco are provided

Policing, Classification, IP Precedence Rewrite, Queuing and WRR, and RED

But MPLS TE features are superior to that of Cisco’s in some aspects

BGP-based LSP (enable transit traffic ride on it) per-interface reoptimize timer, etc.

Page 26: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 26

Juniper’s MPLS TE Features

LSP tunnels Link-state IGPs Path Calculation Module Link Management Module Label Switching and Forwarding Signaling Module Load Sharing Module Link Protection/Restoration Module Fast-Reroute for IGP shortcuts

Page 27: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 27

Cisco’s DiffServ Config Example

InternetInternet

Edge Router 1Edge Router 2

Core Router

DiffServ Domain

Page 28: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 28

Cisco’s DiffServ Config Example

SETDSCP Policy Map class-map match-all EF match access-group 101 class-map match-all AF1 match access-group 102 class-map match-all AF21 match access-group 108 class-map match-all AF22 match access-group 109 class-map match-all AF23 match access-group 110 class-map match-all AF3 match access-group 104

policy-map SETDSCP class EF set ip dscp 46 class AF1 set ip dscp 10 class AF21 set ip dscp 18 class AF22 set ip dscp 20 class AF23 set ip dscp 22 class AF3 set ip dscp 26

Page 29: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 29

Cisco’s DiffServ Config Example

VOIP Policy Map class-map match-all premium match ip dscp 46 class-map match-all gold match ip dscp 10 12 14 class-map match-all silver match ip dscp 18 20 22 class-map match-all bronze match ip dscp 26 28 30 class-map best-effort match access-group 105

policy-map VOIP class premium priority 500 class gold bandwidth percent 35 class silver shape average 320000 bandwidth percent 25 class bronze bandwidth percent 15 class best-effort police 56000 1750 1750 conform-action

set-dscp-transmit 0

Page 30: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 30

Cisco’s DiffServ Config Example

access-list 101 permit udp any any range 16384 32768

access-list 102 permit tcp any any eq tacacs access-list 104 permit tcp any any eq www access-list 105 permit ip any any access-list 108 permit tcp any any eq telnet access-list 109 permit tcp any any eq smtp access-list 110 permit tcp any any eq ftp

Page 31: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 31

Cisco’s MPLS Config Example

Configuring MPLS TE comprises Configuring a device to support tunnels Configuring an interface to support RSVP based tu

nnel signaling and IGP flooding Configuring IS-IS or OSPF for MPLS TE Configuring an MPLS TE tunnel Configuring a tunnel that an IGP can use

Page 32: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 32

Cisco’s MPLS Config Example

Sample MPLS TE Configuration

Page 33: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 33

Global Configuration Sample for router 1

ip cefmpls traffic-eng tunnels

interface loopback0 ip address 11.11.11.11 255.255.255.255

interface s1/0 ip address 131.0.0.1 255.255.0.0 mpls traffic-eng tunnels ip rsvp bandwidth 1000

Page 34: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 34

Tunnel Configuration

interface tunnel1 ip unnumbered loopback0 tunnel destination 17.17.17.17 tunnel mode mpls traffic-eng tunnel mpls traffic-eng bandwidth 100 tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng path-option 1 dynamic

Configuring tunnel 1

Verifying tunnel 1show mpls traffic-eng tunnelsshow ip interface tunnel1

Page 35: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 35

Tunnel Configuration – cont’d

interface tunnel2 ip unnumbered loopback0 tunnel destination 17.17.17.17 tunnel mode mpls traffic-eng tunnel mpls traffic-eng bandwidth 100 tunnel mpls traffic-eng priority 1 1 tunnel mpls traffic-eng path-option 1 explicit identifier 1

Configuring tunnel 2

ip explicit-path identifier 1 next-address 131.0.0.1 next-address 135.0.0.1 next-address 136.0.0.1 next-address 133.0.0.1

Configuring an explicit IP path

Page 36: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 36

JunOS MPLS Config Example:Minimum & Named Path Config[edit]interfaces { interface-name { logical-unit-number { family mpls; # required to enable MPLS on this intf. } }}protocols { mpls { interface (interface-name | all); # required to enable MPLS on this intf. path to-san-jose { # required to setup explicit LSP 14.1.1.1 strict; 11.1.1.1 loose; } } rsvp { interface interface-name; # required for RSVP signaled MPLS only }}

Page 37: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 37

JunOS MPLS Config Example:LSP Creation Config & Attributes

[edit protocols mpls]label-switched-path lsp-path-name { to address; # egress address from address; # ingress address

# lots of statements for setting various LSP attributes;

primary path-name {

# lots of statements for setting various path attributes;

} secondary path-name {

# lots of statements for setting various path attributes;

} }

adaptive admin-group bandwidth class-of-service fast-reroute hop-limit no-cspf optimize-timer preference priority retry-timer record or no-record standby

Page 38: QoS Management & Traffic Engineering  for IP Networks

QoS Management & TE in Action

Page 39: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 39

PacketShaper: Application QoS

Packeteer’s QoS solution Enterprise Edge Solution PacketShaper/AppCelera ICX Hardware and Software bundle

Classify Traffic Based on 5-tuples, mime-types, users, etc.

Analyze Behavior Apps bandwidth consumption rate, response time, etc.

Control Performance Apply policy based on the analysis results

Report Trends http://www.packeteer.com

Page 40: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 40

QoSWorks Sitara Networks’ QoS Solution

Enterprise Edge Solution Hardware and Software bundle solution

Bandwidth Management Layer2 through 7 classification, switching, shaping,

queuing, statistics and bridging Application-specific Traffic Management

Proxies, signaling, caching, redirection for specific application types

Policy Management Analysis, decisions, and enforcement across the network

http://www.sitaranetworks.com

Page 41: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 41

ServicePoint System

ADC’s QoS Solution WAN QoS solution (e.g. FR-based Intranet) Hardware and Software bundle solution ServicePoint SDU & Manager

Policy-based bandwidth management Service partitioning WAN performance analysis

Puts SDUs at the boundary of LAN & WAN TCP rate control http://www.adc.com/access

Page 42: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 42

FloodGate-1: Secure QoS Checkpoint’s integrated solution for VPNs, Firewalls, a

nd QoS Bandwidth control

Upto 4Mbps bidirectional Traffic classification

Over 150 IP services and applications based on src, dst, file designator, URL, time of day

Policy-based Management Scalability and Ease of use http://www.checkpoint.com

Page 43: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 43

FloodGate-1: Secure QoS

Internet

LAN

DMZ

VPNStandaloneQoS Device

• When the VPN encrypts packets, classification is impossible

• NAT is performed in Firewall, Classification/prioritization is impossible

Firewall

Page 44: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 44

FloodGate-1: Secure QoS

Internet

LAN

StandaloneQoS Device VPN

• When located behind VPN/Firewall, bandwidth management decisions corrupted by VPN encryption and Firewall traffic

Firewall

DMZ

Page 45: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 45

FloodGate-1: Secure QoS

Internet

LAN

DMZ

• Integration solves all

Firewall

StandaloneQoS Device

VPN

Page 46: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 46

Cisco’s QoS & Service Mgmt

Network servicelevel verification

CW2000 SMSCW2000 SMS

CONFIGURECONFIGURE VERIFICATION VERIFICATION TROUBLESHOOT TROUBLESHOOT

Qos networkpolicy configuration

Per-device trafficclass monitoring

Per-device traffic class configuration

Dev

ice

Net

wo

rk W

ide

Dev

ice

Net

wo

rk W

ide XML

Service leveltroubleshooting

XML

QDM, ...QDM, ...QDM, ...QDM, ...

QPMQPM CW2000 RWAN(IPM)

CW2000 RWAN(IPM)

Courtesy: 2001@ Cisco Systems Inc.

Page 47: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 47

Orchestream 2.1

Market leading Policy-based QoS & MPLS VPN Manager

Multi Protocol Label Switching (MPLS) control module for implementing network-based IP-Virtual Private Networks (IP-VPNs)

QoS control module for managing the Quality of Service (QoS) levels of specific traffic

Security control module for managing access to specific parts of the network

Integration Module for integration with other IP network management software

Page 48: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 48

Orchestream 2.1

Courtesy: 2001 @ Orchestream Inc.

Page 49: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 49

NPAT & MPLSView WANDL’s MPLS Modeling Tools Leading provider of MPLS modeling tools Design and simulate IP/MPLS networks Multi-vendor config file parsing and integrity

checking Bottleneck discovery and solutions Prediction of e2e delays, throughputs, packet

drops, and link utilization Failure scenario simulations Reports and topology diagrams http://www.wandl.com

Page 50: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 50

MPLSView Screenshot

Page 51: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 51

ETRI’s QoS&MPLS TE Server

Topology & Resource Status Visualization Policy-based QoS Provisioning & TE control Traffic Monitoring, Measurement & Analysis Routing Control for Traffic Engineering Targeted for Backbone network’s QoS & TE m

anagement but can be applied to Enterprise networks as well

Page 52: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 52

Visualization Various topology views

Layer 3, OSPF, BGP, DiffServ Domain, MPLS Domain, Optical Domain, etc.

Elements & Link status General & element specific info, traffic in colors, etc.

Flow & Path views Live visualization over L3 topology with source-destination, and flow di

rection and TT, ES-LSP, Lightpath, etc. TE views

Traffic Statistics Matrix (AS-to-AS, Prefix-to-prefix), LSP statistics, LSP tables (LDP signaled, Explicitly signaled, Primary, Secondaries), etc.

Policy views Network-wide DiffServ and/or MPLS policy rules and enforced network

elements relationship map

Page 53: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 53

Visualization: ExamplesTE C onsoleF ile(F ) Edit(E) View(V) S imulation(S) Option(O) Tool(T) Help(H)

MP LS ViewViews:

35 %

20~40 %0 ~ 20 %

40~60 %60~80 %

80 ~100 %

TM

DiffServNEsMPLS

Traffic Trunks

TT 1

root

TT 2

LSP Tunnels

Tunnel 1Tunnel 2

LSP Tunnel 1

P athSecondary LSP s

F EC

P rimary LSP

RSVP TP

LSP 1

LSP 2

TT 3

LSP Tunnel 2

P ath

RSVP TP s

TP 1

F ilter 1

TC G OFS

+

-

서 울

수 원

대 전

광 주

부 산

대 구

Statistic s View Interval

2001 2 23 12:00년 월 일F rom :

2002 2 23 24:00년 월 일To :

적 용 취 소

5분

하 루 일 주 일 한 달

Status C onsole

Server Initiating...

Status console example.

Page 54: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 54

Policy-based Provisioning

Away from individual device mgmt Away from individual traffic trunk and LSP mgmt Consistent configuration and admission control accor

ding to network policies Independent of signaling/management protocol High level support for the operation of DiffServ & MPL

S networks Automate QoS provisioning and traffic engineering (hu

ge relief to NA, hopefully) Automate TE decision enforcement to multi-vendor ne

twork environment

Page 55: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 55

Traffic Monitoring & Analysis

MIB Polling MIB II, DiffServ MIB, MPLS MIBs(LDP, LSR, TE, etc.)

Passive Traffic Measurement Flow-based traffic measurement (DiffServ, MPLS LSP, MPLS VPN flo

ws etc.) using SNMP Polling and Netflow mechanism Measurement Results Analysis

Traffic characterization, Network monitoring, and Traffic control Traffic distribution based on flows, interfaces, node-pairs(ingress-eg

ress), path, destination, prefix, or AS Traffic load estimation based on class types

Page 56: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 56

Routing Control for TE MIB Polling

OSPF, BGP MIBs Topology Auto discovery

With the help of QRMS Path Calculation

L3 path, CSPF + alpha(DS ClassType, etc.) TED Import & Processing

Via passive OSPF participation Measurement-based Admission Control Simulations

Path availability simulation Path attribute modification simulation Failure scenario simulation Global path optimization simulation

Page 57: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 57

System Architecture: Overview

ConfigurationPackage

MeasurementPackage

GlobalConfig

Package

MiscPackage

GUI

TMS

RMS

PS

RATE

CSI (Common Service Interfaces)

TMSAgent

RMSAgent

COPSAgent

JunoscriptClient

CiscoCLI

Proxy Agent

COPS

CORBA

ACE2000JuniperRouter

CISCORouter

ACECLI

SNMPMeasured

Traffic Data

CORBA

OSPF/BGP

Page 58: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 58

Summary

Talked about QoS management & TE requirements Efforts from standard bodies, industries, re

search & academic communities Solutions from device and management vie

wpoints

Page 59: QoS Management & Traffic Engineering  for IP Networks

KNOM2001 59

References Geoff Huston, Internet Performance Survival Guide: QoS Strategies for

Multiservice Networks, Wiley, 2000 ITU-T E.800, “Telephone Network and ISDN Quality Of Service, Netw

ork Management and Traffic Engineering”, 1994 Stardust.com Inc, “A White paper - QoS Protocols & Architectures”, 199

9: http://www.stardust.com Internet Protocol Journal, “QoS-Fact or Fiction”, Vol 3. Num 1, 2000 IETF, Internet Draft: draft-iab-qos-02.txt, “Next Steps for the IP QoS Arch

itecture”, August 2000 Vijay P. Kumar, T.V. Lakshman, Dimitrios Stiliadis, “Beyond Best Effort:

Router Architectures for the Differentiated Services of Tomorrow’s Internet, IEEE Communications Magazine, May 1998

P. Aukia, et. al., “RATES: A Server for MPLS Traffic Engineering”, IEEE Network, March/April 2000

Page 60: QoS Management & Traffic Engineering  for IP Networks

Thank You&

Q & A