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 1

Agenda: QoS/CoS Workshop
Module 1: Overview of QoS/CoS

Module 2: JUNOS QoS implementation (J/M/T-
Series)
Module 3: Introduction to JUNOS CLI
Module 4: GEANT2 QoS services Implementation

Module 2: JUNOS CoS implementation
Router Architecture
Components and Implementation of JUNOS
QoS
Diffserv IPv6
Edge-optimized Intelligent Queuing PICs
Real-Time Performance Monitoring

Juniper Networks Product Portfolio
Application Secure Access Intrusion Integrated Edge Service

Acceleration SSL VPN Firewall / IPSec VPN Routers
Prevention
Data Centre
Application Session Small/Med Large Core

BRAS & Circuit
Border Controllers Circuit Aggregation Metro Aggregation
Acceleration Aggregation
WAN

M-series Service-Built Portfolio
Single JUNOS image
Gbps for all M Series
10Gig
Uplinks
320
M320
120
M120 2.5Gig
Uplinks
40
20
M40e
10
M20
5 M10i
M7i
Campus/Enterprise Med / Lg PoP 10G PoP

Purpose Built Architecture
Common Processor
Routing Forwarding Routing

Forwarding
Topology
Services@ Scale
Services
Delivered
on Purpose
Built Silicon
(ASIC’s)
‘Traditional’ CPU-Based Router Juniper Networks Architecture

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

M-series Packet Forwarding Engine
Architecture
Internet
Simplicity Processor II
ASIC
• One forwarding table
Distributed FEB Distributed
• One lookup Buffer Manager
SSB Buffer Manager
ASIC ASIC
SFM
• Single-stage, shared
memory Passive Midplane
High performance I/O I/O I/O I/O

Mgr Mgr Mgr Mgr
Highly integrated
PD PD PD PD
In Out In Out
CoS queuing
FPC FPC
Multicast
PIC PIC PIC PIC PIC PIC PIC PIC
Redundant SFMs

M-series CoS architecture

T-series Packet Forwarding Engine
Components and Data Flow

Router Architecture
QoS
Diffserv IPv6

Components of JUNOS QoS

Classifiers

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 packet’s 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.

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 ATM’s CLP or Frame’s DE
Marker rewrite often required to convey loss-priority status between routers
Out of Mild RED

Policer In Policer Low Loss Bronze
Profile Profile Priority
(LP = 0)
Packet B Packet A
Classifier
Aggressive RED
Bronze
High Loss
Priority (LP = 1)

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];

>>BA Classifier Configuration
2. Bind the classifier to an incoming logical
interface:
[edit]
class-of-service {
interfaces {
interface-name {
unit unit-number {
classifiers {
[dscp | exp | ieee-802.1 | inet-precedence] [classifier-name |

default];

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;

>>MF classifier example
2. Apply the firewall filter to an interface:
[edit]
interfaces interface-name {
unit logical-unit-number {
family inet {
filter {
input foo;

Policers

Policers
Ingress Egress
Interface 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

Rate Policing
firewall { JUNOS can perform rate policing on
policer limit-ingress-traffic {
if-exceeding {
criteria such as protocol flow or
bandwidth-limit 400k; ingress interface
burst-size-limit 100k;
} Policer actions include:
discard
then discard;
}
} loss-priority [high|low]
forwarding-class class-name
interfaces {
ge-0/0/0 {
unit 0 { Multiple policer statements per filter
family inet {
policer {
input limit-ingress-traffic;
Bandwidth-limit in bits per second
}
} Burst-size-limit in bytes per second
}
}
Min should = MTU of IP packets
} Max = 16.7 Mb

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

Color Blind Mode of trTCM
New token
CIR times/sec
Not enough
New token CBS Yellow tokens
PIR times/sec
PBS Tc Enough yellow tokens

But not enough green
tokens
Tp
Enough yellow
And green
tokens
trTCM?

Color Aware Mode of trTCM
New token
CIR times/sec Pre-colored Red OR any
other color and not enough
New token CBS yellow tokens
PIR times/sec
Pre-colored yellow OR
PBS Tc green and enough yellow
tokens but not enough green
tokens
Tp
Pre-colored green
and enough yellow
and green tokens
trTCM?

Forwarding Policy Options

CoS-Based Forwarding
Used to select among a set of equal-cost
nexthops based on the packet’s forwarding-
class
• 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 won’t be used

CoS-Based Forwarding
Example
2. Configure the next-hop-map
1. Define the interesting set of routes with
policy options [edit]
# show class-of-service forwarding-policy
[edit] next-hop-map cos-map {
# show policy-options policy-statement cos- forwarding-class voice {
forwarding lsp-next-hop voice-lsp-to-ny;
term a { }
from { }
route-filter 192.168.8.0/24 exact; class voice {
} classification-override {
then cos-next-hop-map cos-map; forwarding-class voice;
} }
term b { }
then accept;
}
3. Export the policy defined under policy
options into the forwarding-table
[edit]
# show routing-options
}
forwarding-table {
export cos-forwarding;
}

Forwarding Classes

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.

Queues: Define forwarding-classes
Queue numbers are now abstracted to
“forwarding-classes”
Default Forwarding-classes:
• be -> queue0
• ef -> queue1
• af -> queue2
• nc -> queue3

Queues: Define forwarding-classes
Assign forwarding-classes to queues:
[edit]
class-of-service {
forwarding-classes {
queue queue-number class-name;

Scheduling and rate Control

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

CoS Hardware Overview:
Ingress PFE
Input L3 Hard and Fabric Strict

Input L2 Rate Soft Policing Priority Queuing
Limiting and Policing (All PICs) (All PICs)
(Specific PICs)
Switch Fabric
PIC Ingress PFE

SIB
PIC SIB
SIB
PIC L2/3 M320 Queuing
Packet Internet ASIC SIB
PIC Processing Processor

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

Scheduling and rate Control

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.

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%

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

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%

Queues: Transmit Rate Configuration
Transmit rate configuration:
[edit]
class-of-service {
schedulers {
scheduler-name {
transmit-rate [rate | percent percentage | remainder]
<exact>;

Queues: Priority
Determines the order in which an output
interface transmits traffic from the queues
JUNOS supports:
• Low priority,
• High priority,
• Strict-high priority

Queues: Priority Configuration
[edit]
class-of-service {
schedulers {
scheduler-name {
priority priority-level;

Default “no-config” settings:
• All queues are low priority

Priority Level Mappings
Mappings for Mappings for M320 FPCs and T-series
Priority Levels
FPCs Enhanced FPCs
low 0 0
medium-low 0 1
medium-high 1 1
high 1 2
strict-high (full
interface 1 2
bandwidth)

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

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)

Congestion Management

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 …] ;

Mapping queued packets to WRED profile

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;

Scheduler-map Configuration
[edit]
class-of-service {
scheduler-maps {
map-name {
forwarding-class class-name1 scheduler scheduler-name1;

>> Scheduler-map Configuration
Bind the scheduler map to a physical interface:
[edit]
class-of-service {
interfaces {
interface-name {
scheduler-map map-name;

DWRR Example

Combination of Strict Priority and DWRR

Rewrite

Rewrite Markers
Rewrite markers
• Redefines the code-point value of outgoing
packets.

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];

>>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] ;

Router Architecture
QoS
Diffserv IPv6

Overview of Diffserv IPv6
Class of service Components:
BA Multi field
Forwarding
Classifier Classifier
Queuing /
Rewrite RED Drop
Scheduling
•BA Classifier and Rewrite were enhanced to

support IPv6.
•Rest of the components already support IPv6.

Overview Contd..
32 bits
Traffic Class Field
Ver.
Ver. Traffic
Traffic class
class Flow
Flow label
label DSCP
DSCP Unused
Unused
66 88 bits
bits 20
20 bits
bits 6bits
6bits 22 bits
bits
Payload
Payload Length
Length Next
Next Hdr.
Hdr. Hop
Hop Limit
Limit
16
16 bits
bits 88 bits
bits 88 bits
bits
• Use 6 bits in Traffic Class
Source
Source Address
Address field as DiffServ Code Point.
128
128 bits
bits
• User can configure IPv6
DSCP field to forwarding
Destination
Destination Address
Address class/loss priority mapping.
128
128 bits
bits
• User can configure remarking
of IPv6 DSCP field based on
IPv6 header forwarding class/loss priority.

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>.

Assigning BA Classifier to a Logical
Interface
interfaces {
<interface-name> {
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.

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.

Configuring Rewrite Rule
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

Assigning Rewrite Rule to Logical
interface
interfaces {
<interface-name> {
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.

Configuring Code Point Aliases
code-point-aliases {
dscp-ipv6 {
<alias-name> <bits>;
}
}
¾ User can configure code point aliases of type IPv6. These

exist solely for user’s convenience and are significant only
from CLI perspective.
¾ Default dscp-ipv6 code points are pre-created and they are
identical to dscp code points.

Router Architecture
QoS
Diffserv IPv6

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

IQ PIC: Optimized for the Network Edge
Feature Rich Service Creation Dense Multi-level Connectivity
4 configurable length output queues per channel 768 Customer Channels per PIC
WRR & Strict priority queuing Channelization to NxDS0
Shaping & policing per channel/queue Dynamic channel re-provisioning
RED and WRED w/ 64 drop profiles ML support for NxT1/E1
GE Q-PIC: VLAN rewrite, tagging, deleting
Multilink Services Dedicated Line
Accounting
Queuing Shaping &

Fractional Policing Channelization
Granular Accounting & Statistics Extensive Diagnostics

4096 sets of L2 counter CSU/DSU DS3 subrate & scrambling
Per packet/byte Tx/Rx counters BERT patterns for T1, DS3, NxDS0
Per queue drop counters Alarm and error reporting
GE Q-PIC: per VLAN and MAC accounting FDL and inband loopback

ATM2 Details
Queuing and Classification Cell relay support - 3 different modes
• 4/8 configurable length queues per • Cell relay VCI mode
VC/VP • Cell relay promiscuous VPI mode
• Output shaping/rate limiting • Cell relay promiscuous port mode
• Per VP or VC output shaping
• Cell Packing
• Max Burst Size 4000 cells
• VP/VC shaping granularity –64 kbps
• UBR, nrt-VBR, CBR, rt-VBR
Encapsulations
• WRR, strict priority, alternate priority • Martini – Cell mode and AAL5 mode
• Counter for out-of-sequence packets
• Per VC configurable queue length
• PPPoA encaps
• RED, EPD w/64 drop profiles
• L2 <-> L3 CoS mapping
Diagnostic, Instrumentation, CLI and
maintenance
Cell Format • Idle cell/unassigned cells transmission
• Entire VCI range (16 bits) • F4 and F5 OAM loop back cells
• UNI VPI range ( 8 bits) • Counters: Per VC and Per VP
• NNI VPI range (12 bits) for cell relay counters
port mode only • Remote and local loop backs

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

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

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

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

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
8G
PIC 4G
Packets in Ba + Mf Intelligent
Classifier drop
FPC
PIC
PIC
PIC

IQ2 Benefits Summary
MPLS VPN
Industry-leading Ethernet densityInternet
and QoS for the efficient and
reliable deployment of intelligent converged services
• Hierarchical QoS: Multiple services per VLAN, each

with its own QoS
• Scalability: More VLANs and more customers per
port, shelf, system Cust n
•VoIPIntelligent Oversubscription:
Cust 4 Lower cost per GigE
VideoConf IQ2 GigE
• Future Proof ProgrammableCust 3 Architecture: New
VideoStream Customer
features added
#1 via software
Cust 2 = superior investment
Data p1
protection (no need to purchase new cards to get new
Data p2 Cust 1
features)
Internet

Router Architecture
QoS
Diffserv IPv6

Active Probes to Monitor Performance
Probes collect on a per

destination & application
basis
• Ping (ICMP) packet
• UDP/TCP packets with
user configured ports Alarm generation on SLA
violation (SNMP & syslog)
• User configured DSCP
(ToS) Ability to export records to J-
Web and external network
• Web (HTTP) management applications
• VPN tests supported

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 TOS/DSCP marking support
• ICMP Timestamp Packet size & content (all 1s, 0s,
• HTTP Get etc) configurable
• UDP Echo All Probe types supported over
VPNs in 7.4
• TCP Connection

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

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

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)

Configuring RPM with J-Web
Users select the
“Configuration” tab followed by
the “RPM” Quick Configuration
wizard…

First time around users
must create a Probe
Owner…

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

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

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

Configuring SNMP with J-Web
Trap groups are
defined using the J-
Web SNMP Quick
Configuration
wizard…

The probe is
created once the
user clicks “Apply”
or “OK”.

Monitoring RPM with J-Web
Users select the “Monitor” tab
followed by the “RPM” option
below it.

The current running tests are displayed in the
browser…

Users can expand results to view statistics for
the test plus a graph displaying the results of
each probe.

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.

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/swconfig80-
cos/frameset.htm
CoS on J-Series
• http://www.juniper.net/techpubs/software/jseries/junos80/jseries80-
config-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

Additional Information on JUNOS CoS (2/2)
Supporting Differentiated Service Classes: Active Queue Memory
Management
Supporting Differentiated Service Classes in Large IP Networks
Supporting Differentiated Service Classes: Queue Scheduling Disciplines
Supporting Differentiated Service Classes: TCP Congestion Control
Mechanisms

Thank you
Jean-Marc Uzé
Liaison Research & Education, EMEA
juze@juniper.net
Mobile: +33615432512
31 Place Ronde, 92986 Paris-La-Defense, France

SEEREN CoS JUNOS Module2

Uploaded by

Copyright:

Available Formats

You might also like

SEEREN CoS JUNOS Module2

Uploaded by

Document Information

Original Title

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

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 1

 Module 1: Overview of QoS/CoS

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 2

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 3

Application Secure Access Intrusion Integrated Edge Service

Application Session Small/Med Large Core

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 4

Campus/Enterprise Med / Lg PoP 10G PoP

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 5

Routing Forwarding Routing

‘Traditional’ CPU-Based Router Juniper Networks Architecture

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 6

• FEB/SSB/SFM and FPC/PICs

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 7

 High performance I/O I/O I/O I/O

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 8

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 9

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 10

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 11

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 12

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 13

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 14

Out of Mild RED

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 15

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 16

[dscp | exp | ieee-802.1 | inet-precedence] [classifier-name |

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 17

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 18

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 19

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 20

 Policing and shaping limit traffic volume and burstiness

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 21

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 22

• Described in RFC 2698

• Defined in terms of 2 token buckets P and C

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 23

PBS Tc Enough yellow tokens

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 24

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 25

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 26

 Prefix next-hops which are not specified within the CoS

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 27

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 28

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 29

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 30

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 31

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 32

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 33

 On ingress PFE, traffic classified into two strict

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 34

Input L3 Hard and Fabric Strict

PIC Ingress PFE

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 35

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 36

Copyright © 2006 Juniper Networks, Inc. www.juniper.net 37

Module 1: Overview of QoS/CoS

High performance I/O I/O I/O I/O

Policing and shaping limit traffic volume and burstiness

Prefix next-hops which are not specified within the CoS

On ingress PFE, traffic classified into two strict

Probes collect on a per