Seeren Cos Junos Module2

SEEREN2 Summer School Heraklion, Sept 25th Routing Issues: QoS/CoS
Jean-Marc Uz Liaison Research & Education, EMEA juze@juniper.net
Copyright 2006 Juniper Networks, Inc.
www.juniper.net
Agenda: QoS/CoS Workshop

Module 1: Overview of QoS/CoS Module 2: JUNOS QoS implementation (J/M/TSeries) Module 3: Introduction to JUNOS CLI Module 4: GEANT2 QoS services Implementation
www.juniper.net
Module 2: JUNOS CoS implementation

Router Architecture Components and Implementation of JUNOS QoS Diffserv IPv6 Edge-optimized Intelligent Queuing PICs Real-Time Performance Monitoring
www.juniper.net
Juniper Networks Product Portfolio

Application Acceleration Data Centre Secure Access SSL VPN Intrusion Prevention Integrated Firewall / IPSec VPN Edge Service Routers
Application Acceleration WAN
Session Border Controllers
BRAS & Circuit Aggregation
Small/Med Circuit Aggregation
Large Core Metro Aggregation
www.juniper.net
M-series Service-Built Portfolio

Gbps 320
M320
Single JUNOS image for all M Series
10Gig Uplinks
120 40 20 10 5
M7i M10i
M120
2.5Gig Uplinks
M40e M20
Campus/Enterprise
Med / Lg PoP
10G PoP
www.juniper.net
Purpose Built Architecture

Common Processor Routing Forwarding Topology Forwarding Routing
Services
Services@ Scale
Delivered on Purpose Built Silicon (ASICs)
Traditional CPU-Based Router
Juniper Networks Architecture
www.juniper.net
M-series Logical View

Clean separation of routing and packet forwarding functions Consistent performance Stability Provider-class routing Routing Engine (RE) Intel-based processor JUNOS software Packet Forwarding Engine (PFE) Processor-based design FEB/SSB/SFM and FPC/PICs PFE RE Junos Internet Software
Forwarding Table
Update Internet Processor II
Forwarding Table
Switch Fabric
I/O Card I/O Card
www.juniper.net
M-series Packet Forwarding Engine

Architecture
Simplicity One forwarding table One lookup Single-stage, shared memory
I/O Mgr I/O Mgr PD In PD Out Distributed Buffer Manager ASIC
Internet Processor II ASIC

FEB SSB SFM
Distributed Buffer Manager ASIC
Passive Midplane
I/O Mgr I/O Mgr PD In PD Out
High performance Highly integrated CoS queuing Multicast Redundant SFMs
FPC
PIC PIC PIC PIC PIC PIC
FPC
PIC PIC
www.juniper.net
M-series CoS architecture
www.juniper.net
T-series Packet Forwarding Engine Components and Data Flow
www.juniper.net
10

www.juniper.net
11
Components of JUNOS QoS
www.juniper.net
12
Classifiers
www.juniper.net
13
Classifiers
Associate incoming packets with a forwarding class and loss priority and, based on the associated forwarding class, assign packets to output queues. Behavior aggregate (BA) or code point traffic classifiers Code points determine each packets forwarding class and loss priority. BA classifiers allow you to set the forwarding class and loss priority of a packet based on DiffServ code point (DSCP) bits, DSCP IPv6, IP precedence bits, MPLS EXP bits, and IEEE 802.1p bits. The default classifier is based on IP precedence bits. Multifield (MF) traffic classifiers Allow you to set the forwarding class and loss priority of a packet based on firewall filter rules.
www.juniper.net
14
Loss Priority
Each packet is associated with a loss priority during classification or policing
Action modifier in a multifield classifier or the interpretation of a behavior aggregate pattern A policer action for data in excess of the profile
Loss priority is used to influence probability of RED drops within a given forwarding class
Similar in function to ATMs CLP or Frames DE
Marker rewrite often required to convey loss-priority status between routers

Out of Policer Profile Packet B Mild RED
In Policer Profile Packet A
Low Loss Priority
Bronze (LP = 0)
Classifier
High Loss Priority
Bronze (LP = 1)
Aggressive RED
www.juniper.net
15
BA Classifier Configuration
1.
Create a dscp, exp, ieee-802.1p or ip precedence classifier:

[edit] class-of-service { classifiers { [dscp | exp | ieee-802.1 | inet-precedence] classifier-name { import [classifier-name | default]; forwarding-class class-name { loss-priority [low | high] code-points [alias | bits];
www.juniper.net
16
>>BA Classifier Configuration

2. Bind the classifier to an incoming logical interface:
[edit] class-of-service { interfaces { interface-name { unit unit-number { classifiers { default]; [dscp | exp | ieee-802.1 | inet-precedence] [classifier-name |
www.juniper.net
17
MF classifier example
1.
Define the firewall filter:

[edit] firewall { filter foo { term term-1 { from { match-conditions; } then { forwarding-class class-name; loss-priority [low|high]; accept; term default { then accept; }
www.juniper.net
18
>>MF classifier example

2. Apply the firewall filter to an interface:
[edit] interfaces interface-name { unit logical-unit-number { family inet { filter { input foo;
www.juniper.net
19
Policers
www.juniper.net
20
Policers
Ingress Interface Egress Interface
Interface Limiter/Shaper
Policing and shaping limit traffic volume and burstiness Enforce/protect service level agreements Excess traffic can be marked with loss priority or discarded
Interface policers can function at ingress, egress, or both
www.juniper.net
21
Rate Policing
firewall { policer limit-ingress-traffic { if-exceeding { bandwidth-limit 400k; burst-size-limit 100k; } then discard; } } interfaces { ge-0/0/0 { unit 0 { family inet { policer { input limit-ingress-traffic; } } } } }
JUNOS can perform rate policing on criteria such as protocol flow or ingress interface Policer actions include: discard loss-priority [high|low] forwarding-class class-name Multiple policer statements per filter Bandwidth-limit in bits per second Burst-size-limit in bytes per second Min should = MTU of IP packets Max = 16.7 Mb
www.juniper.net
22
Two-rate Tri-color Marking (on E2-FPC for T-Series and M320)

Behavior of trTCM Described in RFC 2698 Defined in terms of 2 token buckets P and C with rates PIR and CIR and bucket sizes PBS and CBS respectively
www.juniper.net
23
Color Blind Mode of trTCM

New token CIR times/sec New token PIR times/sec PBS CBS Not enough Yellow tokens Enough yellow tokens But not enough green tokens Enough yellow And green tokens
Tc
Tp
trTCM?
www.juniper.net
24
Color Aware Mode of trTCM

New token CIR times/sec New token PIR times/sec PBS CBS Pre-colored Red OR any other color and not enough yellow tokens Pre-colored yellow OR green and enough yellow tokens but not enough green tokens Pre-colored green and enough yellow and green tokens
Tc
Tp
trTCM?
www.juniper.net
25
Forwarding Policy Options
www.juniper.net
26
CoS-Based Forwarding
Used to select among a set of equal-cost nexthops based on the packets forwardingclass
If the prefix only has one nexthop, CBF does not apply A single forwarding-class can be mapped to multiple next-hops
load balancing will occur for that forwarding-class
Prefix next-hops which are not specified within the CoS next-hop-map are not placed in the forwarding table
i.e. unspecified next-hops wont be used
www.juniper.net
27
CoS-Based Forwarding
Example
2. 1.
Configure the next-hop-map
Define the interesting set of routes with policy options
[edit] # show policy-options policy-statement cosforwarding term a { from { route-filter 192.168.8.0/24 exact; } then cos-next-hop-map cos-map; } term b { then accept; }
[edit] # show class-of-service forwarding-policy next-hop-map cos-map { forwarding-class voice { lsp-next-hop voice-lsp-to-ny; } } class voice { classification-override { forwarding-class voice; } }
3.
Export the policy defined under policy options into the forwarding-table
[edit] # show routing-options } forwarding-table { export cos-forwarding; }
www.juniper.net
28
Forwarding Classes
www.juniper.net
29
Forwarding Classes: ordered aggregates

Affect the forwarding, scheduling, and marking policies applied to packets as they transit a routing platform. The forwarding class plus the loss priority define the per-hop behavior. Best effort, Assured forwarding, Expedited forwarding, Network control.
www.juniper.net
30
Queues: Define forwarding-classes

Queue numbers are now abstracted to forwarding-classes Default Forwarding-classes:
be -> queue0 ef -> queue1 af -> queue2 nc -> queue3
www.juniper.net
31
Queues: Define forwarding-classes

Assign forwarding-classes to queues:
[edit] class-of-service { forwarding-classes { queue queue-number class-name; queue queue-number class-name; queue queue-number class-name; queue queue-number class-name;
www.juniper.net
32
Scheduling and rate Control
www.juniper.net
33
M320 and T-Series QoS

Class-based queuing decisions made on egress PFE Eight queues available on egress PFE On ingress PFE, traffic classified into two strict priorities High and low for all packets bound for a destination PFE Fabric architecture based on these two priorities 2x speed-up in fabric to ensure no congestion
www.juniper.net
34
CoS Hardware Overview: Ingress PFE

Input L3 Hard and Soft Policing (All PICs) Fabric Strict Priority Queuing (All PICs)
Input L2 Rate Limiting and Policing (Specific PICs)
Switch Fabric
PIC PIC PIC PIC

L2/3 Packet Processing
Ingress PFE
SIB SIB SIB SIB
M320 Internet Processor
Queuing ASIC
www.juniper.net
35
Fabric Queuing
Two fabric queues are enough because One per forwarding class priority Very high fabric bandwidth makes scheduling among forwarding classes of the same priority meaningless Minimal Jitter Parallel virtual paths for high and low priority packets
No serialization delay for high priority packet
www.juniper.net
36
Scheduling and rate Control
www.juniper.net
37
Transmission Scheduling and rate control

Schedulers Define the priority, bandwidth, delay buffer size, rate control status, and RED drop profiles to be applied to a particular forwarding class for packet transmission. Policers for traffic classes limits traffic of a certain class to a specified bandwidth and burst size. Packets exceeding the policer limits can be discarded, or can be assigned to a different forwarding class or to a different loss priority, or to both. You define policers with filters that can be associated with input or output interfaces.
www.juniper.net
38
Queues: Size
Large queues may increase latency during congestion smaller queues may be more appropriate for delay sensitive traffic The default configuration has queue 0 with 95% of queue memory and queue 3 with 5%
www.juniper.net
39
Queues: Size Configuration

Queue size configuration:
[edit] class-of-service { schedulers { scheduler-name { buffer-size [time|percent percentage|remainder];
Bind the scheduler to a queue and interface
www.juniper.net
40
Queues: Transmit Rate

Determines the actual traffic bandwidth Rate is specified in bits per second
Limit the transmission bandwidth to the exact value Allow it to exceed the configured rate if additional bandwidth is available from other queues.
Also referred to as WRR% The default configuration has queue 0 with 95% of queue bandwith and queue 3 with 5%
www.juniper.net
41
Queues: Transmit Rate Configuration

Transmit rate configuration:
[edit] class-of-service { schedulers { scheduler-name { transmit-rate [rate | percent percentage | remainder] <exact>;
Bind the scheduler to a queue and interface
www.juniper.net
42
Queues: Priority
Determines the order in which an output interface transmits traffic from the queues JUNOS supports: Low priority, High priority, Strict-high priority
www.juniper.net
43
Queues: Priority Configuration

[edit] class-of-service { schedulers { scheduler-name { priority priority-level;
Bind the scheduler to a queue and interface Default no-config settings: All queues are low priority
Copyright 2006 Juniper Networks, Inc. www.juniper.net
44
Priority Level Mappings

Priority Levels low medium-low medium-high high strict-high (full interface bandwidth) Mappings for FPCs Mappings for M320 FPCs and T-series Enhanced FPCs
0 0 1 1 1
0 1 1 2 2
www.juniper.net
45
Schedulers Configuration
[edit] class-of-service { schedulers { scheduler-name { transmit-rate [rate|percent percentage|remainder] <exact>; WRR config buffer-size [milliseconds|percent percentage|remainder]; queue size config priority [low|high|strict-high]; queue priority config drop-profile-map loss-priority [low|high] protocol [non-tcp|tcp|any] drop-profile profile-name; RED profile assignment
www.juniper.net
46
Queues: Drop Profile

Defines the drop probabilities across the range of delay-buffer occupancy, thereby supporting the RED process For each scheduler, you can configure four separate drop profiles, one for each combination of loss priority (low or high) and IP transport protocol (TCP/IP or non-TCP/IP)
www.juniper.net
47
Congestion Management
www.juniper.net
48
1. Configure the RED profiles:
[edit] class-of-service { drop-profiles { profile-name { fill-level percentage1 drop-probability probability1; fill-level percentage2 drop-probability probability2; up to 64 times, OR interpolate { drop-probability [ p1 p2 p3 p4 p5 ]; fill-level [ f1 f2 f3 f4 f5 ] ;
www.juniper.net
49
Mapping queued packets to WRED profile
www.juniper.net
50
2. map the drop-profile to a scheduler:
[edit] class-of-service { schedulers { scheduler-name { drop-profile-map loss-priority [low|high] protocol [non-tcp|tcp|any] drop-profile profile-name;
www.juniper.net
51
Scheduler-map Configuration
[edit]
class-of-service { scheduler-maps { map-name { forwarding-class class-name1 scheduler scheduler-name1; forwarding-class class-name2 scheduler scheduler-name2; forwarding-class class-name3 scheduler scheduler-name3; forwarding-class class-name4 scheduler scheduler-name4;
www.juniper.net
52
>> Scheduler-map Configuration

Bind the scheduler map to a physical interface:
[edit] class-of-service { interfaces { interface-name { scheduler-map map-name;
www.juniper.net
53
DWRR Example
www.juniper.net
54
Combination of Strict Priority and DWRR
www.juniper.net
55
Rewrite
www.juniper.net
56
Rewrite Markers
Rewrite markers Redefines the code-point value of outgoing packets.
www.juniper.net
57
Rewriting Configuration
1. Configure rewrite-rule;
[edit] class-of-service { rewrite-rules { dscp|exp|ieee-802.1|inet-precedence <table-name> { import [<table-name>|default]; (default=exp-default) forwarding-class <class-name1> { loss-priority [low|high] code-point [<alias>|bits]; }
58
>>Rewriting Configuration
2. Apply rewrite-rule to outgoing logical interface;
[edit] class-of-service { interfaces { interface-name { unit <unit-number> { rewrite-rules [dscp|exp|ieee-802.1|inet-precedence] [rewrite-name |default] ;
www.juniper.net
59

www.juniper.net
60
Overview of Diffserv IPv6

Class of service Components:
BA Classifier Multi field Classifier Forwarding
Rewrite
Queuing / Scheduling
RED Drop
BA Classifier and Rewrite were enhanced to support IPv6. Rest of the components already support IPv6.
61
Overview Contd..
32 bits
Ver. Traffic class Ver. Traffic class 6 8 bits 6 8 bits Payload Length Payload Length 16 bits 16 bits Flow label Flow label 20 bits 20 bits Next Hdr. Next Hdr. 8 bits 8 bits Hop Limit Hop Limit 8 bits 8 bits
Traffic Class Field

DSCP DSCP 6bits 6bits Unused Unused 2 bits 2 bits
Source Address Source Address 128 bits 128 bits
Destination Address Destination Address 128 bits 128 bits
IPv6 header
Use 6 bits in Traffic Class field as DiffServ Code Point. User can configure IPv6 DSCP field to forwarding class/loss priority mapping. User can configure remarking of IPv6 DSCP field based on forwarding class/loss priority.
www.juniper.net
62
Configuring BA Classifier
[edit class-of-service] classifiers { dscp-ipv6 <classifier-name> { import [<classifier-name>|default]; forwarding-class <class-name> { loss-priority [low|high] code-points <alias> |<bits> ]; } } }
Not much difference from dscp classifier configuration. Just use type <dscp-ipv6>.
63
Assigning BA Classifier to a Logical Interface

[edit class-of-service] interfaces { <interface-name> { unit <unit-number> { classifiers { dscp <classifier-name>|default; dscp-ipv6 <classifier-name>|default; exp <classifier-name>|default; } } } } Logical Interface can have multiple classifiers bound to it.
But, there are some limitations.
www.juniper.net
64
Classifiers Known limitations

On M-series: We do not support both dscp & dscp-ipv6 classifiers on same interface. If a logical interface has dscp classifier, it will be used to classify both IPv4 & IPv6 packets. If a logical interface has just dscp-ipv6 classifier, it will be used to classify both IPv4 and IPv6 packets. We log a warning message to notify the user. If a logical interface has inet-precedence classifier, it will be used for classifying IPv6 packets too. But lower three bits of the DSCP field will be ignored. On T-series: We do not support IPv6 classifier with ieee classifier.
www.juniper.net
65
Configuring Rewrite Rule

[edit class-of-service] rewrite-rules { dscp-ipv6 <rewrite-name> { import [<rewrite-name>|default]; forwarding-class <class-name> { loss-priority [low|high] code-point [<alias>|<bits>...]; } } }
Similar to dscp configuration
www.juniper.net
66
Assigning Rewrite Rule to Logical interface

[edit class-of-service] interfaces { <interface-name> { unit <unit-number> { rewrite-rules { dscp <rewrite-name>|default; dscp-ipv6 <rewrite-name>|default; exp <rewrite-name>|default; ieee-802.1 <rewrite-name>|default; } } } }
Multiple Rewrite Rules can be applied to a Logical Interface. No limitations.

67
Configuring Code Point Aliases

[edit class-of-service] code-point-aliases { dscp-ipv6 { <alias-name> <bits>; } }
User can configure code point aliases of type IPv6. These exist solely for users convenience and are significant only from CLI perspective. Default dscp-ipv6 code points are pre-created and they are identical to dscp code points.
www.juniper.net
68

www.juniper.net
69
Edge-optimized Intelligent Queuing PICs

ATM2 IQ PICs Channelized IQ PICs Gigabit Ethernet IQ PICs Discrete IQ PICs (e.g. E3, DS3) Granular per-logical interface QoS VC, VP, DLCI, VLAN Dense multi-level channelization to DS0 With per channel QoS Granular accounting & statistics Extensive diagnostics VLAN tagging, deleting, and rewrite
Shaping & Policing
Queuing
Police Classify Shape Strict priority WRR RED WRED Marking
Multilink Services
Dedicated Access
Channelization
Marking
Accounting
Fractional
www.juniper.net
70
IQ PIC: Optimized for the Network Edge

Feature Rich Service Creation
4 configurable length output queues per channel WRR & Strict priority queuing Shaping & policing per channel/queue RED and WRED w/ 64 drop profiles GE Q-PIC: VLAN rewrite, tagging, deleting
Multilink Services
Accounting
Dense Multi-level Connectivity

768 Customer Channels per PIC Channelization to NxDS0 Dynamic channel re-provisioning ML support for NxT1/E1
Dedicated Line
Fractional
Queuing Shaping & Policing
Channelization
Granular Accounting & Statistics

4096 sets of L2 counter Per packet/byte Tx/Rx counters Per queue drop counters GE Q-PIC: per VLAN and MAC accounting
Extensive Diagnostics
CSU/DSU DS3 subrate & scrambling BERT patterns for T1, DS3, NxDS0 Alarm and error reporting FDL and inband loopback
www.juniper.net
71
ATM2 Details
Queuing and Classification 4/8 configurable length queues per VC/VP Output shaping/rate limiting
Per VP or VC output shaping Max Burst Size 4000 cells VP/VC shaping granularity 64 kbps UBR, nrt-VBR, CBR, rt-VBR
Cell relay support - 3 different modes Cell relay VCI mode Cell relay promiscuous VPI mode Cell relay promiscuous port mode Cell Packing Encapsulations Martini Cell mode and AAL5 mode
Counter for out-of-sequence packets
WRR, strict priority, alternate priority Per VC configurable queue length RED, EPD w/64 drop profiles L2 <-> L3 CoS mapping
PPPoA encaps
Cell Format Entire VCI range (16 bits) UNI VPI range ( 8 bits) NNI VPI range (12 bits) for cell relay port mode only
Diagnostic, Instrumentation, CLI and maintenance Idle cell/unassigned cells transmission F4 and F5 OAM loop back cells Counters: Per VC and Per VP counters Remote and local loop backs
www.juniper.net
72
New: IQ2 Models

PIC
4GE-TYPE1-SFP-IQ2 4 ports x 1GigE Type 1 4:1 Oversubscription 8GE-TYPE2-SFP-IQ2 8 ports x 1GigE Type 2 2:1 Oversubscription 8GE-TYPE3-SFP-IQ2 8 ports x 1GigE Type 3 Line Rate (no OSE) 1XGE-TYPE3-SFP-IQ2 1 Port x10GigE Type 3 Line Rate (no OSE)
Platform Support
M7i, M10i, M20, M40e, M320, T320, T640
Transponder
SFPs: SX, LX, H, Copper
Avail Date May 15 2006 Rel 7.6 May 15 2006 Rel 7.6 Nov 15 2006 Rel 8.1 Aug 15 2006 Rel 8.0
M40e, M320, T320, T640, Tx Matrix
M320, T320, T640, Tx Matrix
M320, T320, T640, Tx Matrix
XFPs: SR, LR, LX4 - WAN PHY
www.juniper.net
73
Key IQ2 Ethernet Service Engine Capabilities

GigE and 10 GigE ports with fine-grain QoS Intelligent Oversubscription for GigE Intelligent sharing of excess bandwidth Advanced QoS mechanisms at both egress and ingress Enhanced hierarchical QoS per VLAN/Logical Interface Software programmable for rich traffic engineering More VLANs & MACs per port and per card More ports per shelf, system, rack QoS w/802.3ad Ethernet Link Aggregation Advances Juniper Ethernet to carrier grade service
74
Hierarchical QoS for Multiple Services

IQ2 ESE PICs support Multiple services per end customer Multiple customers per GigE Service density and scalability
Cust n VoIP VideoConf VideoStream Data p1 Data p2 Internet
MPLS VPN
Internet
IQ 21 0G igE
Cust 4 Cust 3
Customer # 1 VLAN
MPLS Tunnel
IQ2 GigE
Cust 2 Cust 1
www.juniper.net
75
Enhanced QoS for Service Enablement

Fine-Grained per-VLAN QoS with 8 queues per VLAN Per-VLAN statistics and accounting VLAN ID Stacking and rewrite with COS Mapping & translation Hierarchical queuing, shaping, policing and scheduling on both Ingress & Egress MDRR scheduling with 64 RED drop profiles per PIC MAC learning, filtering, accounting, and policing Two Rate Three Color Marking (TrTCM) at line rate throughput
IFL B IFL C IFL D 8 Queues Up to 1024 shapers IFL A 8 Queues
Port
Dual shapers (VLAN and Port level)
www.juniper.net
76
IQ2 ESE Intelligent Oversubscription

Intelligent dropping during congestion Intelligent sharing of excess bandwidth Doubles the number of ports per system
Ethernet Service Engine assists PFE in data path packet processing

8 ports x 1 GigE
Packets in
8G
PIC PIC PIC
FPC
Ba + Mf Classifier
Intelligent drop
PIC
4G
www.juniper.net
77
IQ2 Benefits Summary

Industry-leading Ethernet densityInternet for the efficient and and QoS reliable deployment of intelligent converged services
MPLS VPN
Hierarchical QoS: Multiple services per VLAN, each with its own QoS Scalability: More VLANs and more customers per port, shelf, system Cust n
VoIP Intelligent Oversubscription: Lower cost per GigE Cust 4 Cust 3 Future Proof Programmable Architecture: New Customer VideoStream features added via software = superior investment #1 Cust 2 Data p1 protection (no need to purchase new cards to get new Data p2 Cust 1 features) Internet VideoConf IQ2 GigE
www.juniper.net
78

www.juniper.net
79
Real-Time Performance Monitoring

Active Probes to Monitor Performance
Probes collect on a per destination & application basis Ping (ICMP) packet UDP/TCP packets with user configured ports User configured DSCP (ToS) Web (HTTP) VPN tests supported
Alarm generation on SLA violation (SNMP & syslog) Ability to export records to JWeb and external network management applications
www.juniper.net
80
RPM Overview
Introduced in JUNOS 7.1 Supported on J, M & T series RFC 2925 MIB support with extensions Configuration and results supported via CLI & SNMP Probe types supported
ICMP Echo ICMP Timestamp HTTP Get UDP Echo TCP Connection TOS/DSCP marking support Packet size & content (all 1s, 0s, etc) configurable All Probe types supported over VPNs in 7.4
www.juniper.net
81
RPM Probe Results

Minimum round trip time Maximum round trip time Average round trip time Standard deviation of the round trip time Jitter of the round trip time (diff between min & max RTT) One way measurements for ICMP timestamp probes: min/max/stddev/jitter egress and ingress times Number of probes sent Number of probe responses received Percentage of lost probes
www.juniper.net
82
RPM Thresholds, Events & Traps

Configurable Thresholds: Round trip time Ingress/egress delay Standard deviation Jitter Successive lost probes Total lost probes (per test) Syslog events generated when threshold exceeded SNMP trap (if configured) generated when threshold exceeded
83
Reporting Tool/Data Export options

JUNOScope or JWeb SNMP (through rfc2925 & jnx-ping.mib) Potential Partner interoperability eHealth (by Concord) VistaView and VistaNext (by InfoVista) Brixworx PROVISO (by Quallaby) Performance Insight (by HP Openview) Netally (by Viola Networks) Firehunter (by Agilent)
www.juniper.net
84
Configuring RPM with J-Web

Users select the Configuration tab followed by the RPM Quick Configuration wizard
www.juniper.net
85

First time around users must create a Probe Owner
www.juniper.net
86

Users specify the name and source plus optional threshold values. Orange asterisk is a mandatory field. Tool tips are available on mouse over operations.
87

Specifying the frequency and probe type are mandatory. Supported types are: HTTP Get HTTP Metadata Get ICMP ping ICMP ping timestamp TCP ping UDP ping
www.juniper.net
88

Optionally the user can specify if SNMP notifications should be generated when thresholds are crossed. Traps go to targets defined in JUNOS SNMP trap groups
www.juniper.net
89
Configuring SNMP with J-Web

Trap groups are defined using the JWeb SNMP Quick Configuration wizard
www.juniper.net
90

The probe is created once the user clicks Apply or OK.
www.juniper.net
91
Monitoring RPM with J-Web

Users select the Monitor tab followed by the RPM option below it.
www.juniper.net
92

The current running tests are displayed in the browser
www.juniper.net
93

Users can expand results to view statistics for the test plus a graph displaying the results of each probe.
www.juniper.net
94
Deleting RPM with J-Web

Users select the Configuration tab followed by the RPM Quick Configuration option. A list of running probes are shown. Probe name is a link click it to edit the probe again or select the probe, check the box and delete it.
95
Additional Information on JUNOS CoS (1/2)

JUNOS Internet Software Class of Service Configuration Guide Release 8.0 http://www.juniper.net/techpubs/software/junos/junos80/swconfig80cos/frameset.htm CoS on J-Series http://www.juniper.net/techpubs/software/jseries/junos80/jseries80config-guide-advanced/frameset.html Operation of Modified Deficit Round Robin in M-series Routers http://www.juniper.net/solutions/literature/app_note/350061.pdf Applying JUNOS Class-of-service Features http://www.juniper.net/solutions/literature/app_note/350030.pdf MPLS DiffServ-aware Traffic Engineering http://www.juniper.net/solutions/literature/white_papers/200048.pdf
www.juniper.net
96
Additional Information on JUNOS CoS (2/2)

Supporting Differentiated Service Classes: Active Queue Memory Management http://www.juniper.net/solutions/literature/white_papers/200021.pdf Supporting Differentiated Service Classes in Large IP Networks http://www.juniper.net/solutions/literature/white_papers/200019.pdf Supporting Differentiated Service Classes: Queue Scheduling Disciplines http://www.juniper.net/solutions/literature/white_papers/200020.pdf Supporting Differentiated Service Classes: TCP Congestion Control Mechanisms http://www.juniper.net/solutions/literature/white_papers/200022.pdf
www.juniper.net
97
Thank you
Jean-Marc Uz
Liaison Research & Education, EMEA juze@juniper.net Mobile: +33615432512
31 Place Ronde, 92986 Paris-La-Defense, France
www.juniper.net
98

Seeren Cos Junos Module2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Seeren Cos Junos Module2

Uploaded by

Copyright:

Available Formats

SEEREN2 Summer School Heraklion, Sept 25th Routing Issues: QoS/CoS

Jean-Marc Uz Liaison Research & Education, EMEA juze@juniper.net

Copyright 2006 Juniper Networks, Inc.

Agenda: QoS/CoS Workshop

Copyright 2006 Juniper Networks, Inc.

Module 2: JUNOS CoS implementation

Copyright 2006 Juniper Networks, Inc.

Juniper Networks Product Portfolio

Application Acceleration WAN

Session Border Controllers

BRAS & Circuit Aggregation

Small/Med Circuit Aggregation

Large Core Metro Aggregation

Copyright 2006 Juniper Networks, Inc.

M-series Service-Built Portfolio

Single JUNOS image for all M Series

Copyright 2006 Juniper Networks, Inc.

Purpose Built Architecture

Traditional CPU-Based Router

Juniper Networks Architecture

Copyright 2006 Juniper Networks, Inc.

M-series Logical View

Update Internet Processor II

Copyright 2006 Juniper Networks, Inc.

M-series Packet Forwarding Engine

Internet Processor II ASIC

High performance Highly integrated CoS queuing Multicast Redundant SFMs

Copyright 2006 Juniper Networks, Inc.

M-series CoS architecture

Copyright 2006 Juniper Networks, Inc.

T-series Packet Forwarding Engine Components and Data Flow

Copyright 2006 Juniper Networks, Inc.

Module 2: JUNOS CoS implementation

Copyright 2006 Juniper Networks, Inc.

Components of JUNOS QoS

Copyright 2006 Juniper Networks, Inc.

Copyright 2006 Juniper Networks, Inc.

Copyright 2006 Juniper Networks, Inc.

Marker rewrite often required to convey loss-priority status between routers

In Policer Profile Packet A

Low Loss Priority

Copyright 2006 Juniper Networks, Inc.

Create a dscp, exp, ieee-802.1p or ip precedence classifier:

Copyright 2006 Juniper Networks, Inc.

>>BA Classifier Configuration

Copyright 2006 Juniper Networks, Inc.

Define the firewall filter:

Copyright 2006 Juniper Networks, Inc.

>>MF classifier example

Copyright 2006 Juniper Networks, Inc.

Copyright 2006 Juniper Networks, Inc.

Interface policers can function at ingress, egress, or both

Copyright 2006 Juniper Networks, Inc.

Copyright 2006 Juniper Networks, Inc.

Two-rate Tri-color Marking (on E2-FPC for T-Series and M320)

Copyright 2006 Juniper Networks, Inc.

Color Blind Mode of trTCM

Copyright 2006 Juniper Networks, Inc.

Color Aware Mode of trTCM

Copyright 2006 Juniper Networks, Inc.

Forwarding Policy Options

Copyright 2006 Juniper Networks, Inc.

Copyright 2006 Juniper Networks, Inc.

Configure the next-hop-map