Juniper EX9200 Series Overview Manual
Juniper EX9200 Series Overview Manual

Juniper EX9200 Series Overview Manual

Class of service overview and examples
Hide thumbs Also See for EX9200 Series:
Table of Contents

Advertisement

Quick Links

Class of Service Overview and Examples for
EX9200 Switches
Published: 2013-08-28
Copyright © 2013, Juniper Networks, Inc.

Advertisement

Table of Contents
loading

Summary of Contents for Juniper EX9200 Series

  • Page 1 Class of Service Overview and Examples for EX9200 Switches Published: 2013-08-28 Copyright © 2013, Juniper Networks, Inc.
  • Page 2 Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
  • Page 3: Table Of Contents

    Common IPv4 Firewall Match Conditions ......36 Common Layer 2 Firewall Match Conditions ......36 Copyright © 2013, Juniper Networks, Inc.
  • Page 4 Class of Service Overview and Examples for EX9200 Switches Complete [edit firewall] Hierarchy ........38 [edit interfaces] Hierarchy Level .
  • Page 5 Figure 2: CoS Classifier, Queues, and Scheduler ......16 Figure 3: Packet Flow Through CoS Configurable Components ....16 Copyright © 2013, Juniper Networks, Inc.
  • Page 6 Class of Service Overview and Examples for EX9200 Switches Copyright © 2013, Juniper Networks, Inc.
  • Page 7: List Of Tables

    Table 4: CoS Mappings—Inputs and Outputs ......13 Copyright © 2013, Juniper Networks, Inc.
  • Page 8 Class of Service Overview and Examples for EX9200 Switches viii Copyright © 2013, Juniper Networks, Inc.
  • Page 9: About The Documentation

    ® To obtain the most current version of all Juniper Networks technical documentation, see the product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/ If the information in the latest release notes differs from the information in the documentation, follow the product Release Notes.
  • Page 10: Merging A Full Example

    Class of Service Overview and Examples for EX9200 Switches If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the command. These procedures are load merge relative described in the following sections.
  • Page 11: Documentation Conventions

    A policy term is a named structure new terms. that defines match conditions and actions. Identifies guide names. Junos OS CLI User Guide Identifies RFC and Internet draft titles. RFC 1997, BGP Communities Attribute Copyright © 2013, Juniper Networks, Inc.
  • Page 12: Documentation Feedback

    Class of Service Overview and Examples for EX9200 Switches Table 2: Text and Syntax Conventions (continued) Convention Description Examples Italic text like this Represents variables (options for which Configure the machine’s domain name: you substitute a value) in commands or [edit] configuration statements.
  • Page 13: Requesting Technical Support

    7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: http://www.juniper.net/customers/support/...
  • Page 14: Opening A Case With Jtac

    Class of Service Overview and Examples for EX9200 Switches Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone. Use the Case Management tool in the CSC at http://www.juniper.net/cm/ Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
  • Page 15: Overview

    PART 1 Overview CoS Overview on page 3 CoS Input and Output Configuration on page 13 Packet Flow Through the CoS Process on page 15 Copyright © 2013, Juniper Networks, Inc.
  • Page 16 Class of Service Overview and Examples for EX9200 Switches Copyright © 2013, Juniper Networks, Inc.
  • Page 17: Cos Overview

    CoS domain. You must also consider all the routing devices and other networking equipment in the CoS domain to ensure interoperability among all equipment. Because Juniper Networks routing devices implement CoS in hardware rather than in software, you can experiment with and deploy CoS features without adversely affecting packet forwarding and routing performance.
  • Page 18: Cos Standards

    Class of Service Overview and Examples for EX9200 Switches CoS Standards ® ® The standards for Juniper Networks Junos operating system (Junos OS) class of service (CoS) capabilities are defined in the following RFCs: RFC 2474, Definition of the Differentiated Services Field in the IPv4 and IPv6 Headers...
  • Page 19: Junos Cos Components

    You can configure up to one each of the four types of forwarding classes. For M120 and M320 Multiservice Edge Routers, Juniper Networks MX Series 3D Universal Edge Routers, Juniper Networks T Series Core Routers and EX Series switches, 16 forwarding classes are supported, so you can classify packets more granularly.
  • Page 20: Default Cos Settings

    Class of Service Overview and Examples for EX9200 Switches priority. You set loss priority by configuring a classifier or a policer. The loss priority is used later in the workflow to select one of the drop profiles used by RED.
  • Page 21 Default Frame Relay Loss Priority Map Loss-priority-map: frame-relay-de-default, Code point type: frame-relay-de, Index: Code point Loss priority high Default Rewrite Rules Rewrite rule: dscp-default, Code point type: dscp, Index: 24 Forwarding class Loss priority Code point best-effort 000000 Copyright © 2013, Juniper Networks, Inc.
  • Page 22: Cos Applications Overview

    Class of Service Overview and Examples for EX9200 Switches best-effort high 000000 Rewrite rule: dscp-ipv6-default, Code point type: dscp-ipv6, Index: 25 Rewrite rule: exp-default, Code point type: exp, Index: 26 Rewrite rule: ieee8021p-default, Code point type: ieee-802.1, Index: 27 Rewrite rule: ipprec-default, Code point type: inet-precedence, Index: 28 Default Drop Profile Drop profile: <default-drop-profile>, Type: discrete, Index: 1...
  • Page 23: Interface Types That Do Not Support Cos

    MPLS EXP mapping. Interface Types That Do Not Support CoS For original Channelized OC12 PICs, limited CoS functionality is supported. For more information, contact Juniper Networks customer support. NOTE: Transmission scheduling is not supported on 8-port, 12-port, and 48-port Fast Ethernet PICs.
  • Page 24: Vpls And Default Cos Classification

    VPLS on CoS CLI, the custom classifier binding results in default classifier binding on Packet Forwarding Engine (PFE). For example, on routing devices with eight queues (Juniper Networks M120 and M320 Multiservice Edge Routers, MX Series 3D Universal Edge Routers, and T Series Core...
  • Page 25: Table 3: Default Vpls Classifiers

    (CRC) field. NOTE: On MX Series routers, if you apply a counter in a firewall for egress MPLS or VPLS packets with the EXP bits set to 0, the counter will not tally these packets. Copyright © 2013, Juniper Networks, Inc.
  • Page 26 Class of Service Overview and Examples for EX9200 Switches Copyright © 2013, Juniper Networks, Inc.
  • Page 27: Cos Input And Output Configuration

    The map sets the code points for a specific forwarding class and rewrite-rules loss-priority code-points PLP. Related Default Behavior Aggregate Classification Overview Documentation Configuring Drop Profile Maps for Schedulers Applying Default Rewrite Rules CoS Inputs and Outputs Examples Copyright © 2013, Juniper Networks, Inc.
  • Page 28 Class of Service Overview and Examples for EX9200 Switches Copyright © 2013, Juniper Networks, Inc.
  • Page 29: Packet Flow Through The Cos Process

    NOTE: You can only rewrite the values of these bits on ingress on the Juniper Networks M40e, M120, M320 Multiservice Edge Routers, and T Series Core Routers with IQE PICs. For more information about rewriting the values of these bits on ingress, see Configuring ToS Translation Tables.
  • Page 30: Figure 2: Cos Classifier, Queues, And Scheduler

    Class of Service Overview and Examples for EX9200 Switches The scheduler defines how traffic is treated in the output queue—for example, the transmit rate, buffer size, priority, and drop profile (at the [edit class-of-service hierarchy level). schedulers] The scheduler map assigns a scheduler to each forwarding class (at the [edit hierarchy level).
  • Page 31 Typically, only a combination of some components (not all) is used to define a CoS service offering. Related Packet Flow Through the CoS Process Configuration Example Documentation Copyright © 2013, Juniper Networks, Inc.
  • Page 32 Class of Service Overview and Examples for EX9200 Switches Copyright © 2013, Juniper Networks, Inc.
  • Page 33: Configuration

    PART 2 Configuration Configuration Statements on page 21 Copyright © 2013, Juniper Networks, Inc.
  • Page 34 Class of Service Overview and Examples for EX9200 Switches Copyright © 2013, Juniper Networks, Inc.
  • Page 35: Configuration Statements

    (ignore | red | yellow); ethernet { link-down (ignore | red | yellow); integrated-services { failure (ignore | red | yellow); management-ethernet { link-down (ignore | red | yellow); relay input { port port-number { Copyright © 2013, Juniper Networks, Inc.
  • Page 36 Class of Service Overview and Examples for EX9200 Switches mode (close | open); trigger (ignore | red | yellow; output{ port port-number { input-relay input-relay; mode (close | open); temperature; serial { cts-absent (ignore | red | yellow); dcd-absent (ignore | red | yellow);...
  • Page 37 (increased-bandwidth | redundant); filter; fpc slot-number { ... the fpc subhierarchy appears after the main [edit chassis] hierarchy ... fpc-feb-connectivity { fpc slot-number feb (slot-number | none); fpc-resync; fru-poweron-sequence sequence; lcc index { Copyright © 2013, Juniper Networks, Inc.
  • Page 38 Class of Service Overview and Examples for EX9200 Switches ... the lcc subhierarchy appears after the main [edit chassis] hierarchy ... maximum-ecmp value; memory-enhanced { filter; route; vpn-label; network-services (ethernet | enhanced-ethernet | ip | enhanced-ip); (packet-scheduling | no-packet-scheduling); pem { minimum number;...
  • Page 39 (bits | gps) { priority number; quality-level (prc | prs |sec | smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 | stu | tnc); request (force-switch | lockout); interfaces interface-name { Copyright © 2013, Juniper Networks, Inc.
  • Page 40 Class of Service Overview and Examples for EX9200 Switches priority number; quality-level (prc | prs |sec | smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 | stu | tnc); request (force-switch | lockout); wait-to-restore minutes;...
  • Page 41 { bandwidth (1g | 10g); linerate-mode; max-queues-per-interface (4 | 8); mlfr-uni-nni-bundles number; no-concatenate; no-multi-rate; port port-number { framing (e1 | e3 | sdh | sonet | t1 | t3); forwarding-mode { sa-multicast; Copyright © 2013, Juniper Networks, Inc.
  • Page 42 Class of Service Overview and Examples for EX9200 Switches speed ( oc3-stm1 | oc12-stm4 | oc48-stm16); port-mirror-instance port-mirror-instance-name; q-pic-large-buffer { (large-scale | small-scale); red-buffer-occupancy { weighted-averaged <instant-usage-weight-exponent weight-value>; shdsl { pic-mode (1-port-atm | 2-port-atm); sparse-dlcis; traffic-manager { egress-shaping-overhead number; ingress-shaping-overhead number;...
  • Page 43: [Edit Class-Of-Service] Hierarchy Level

    (high | low | medium-high | medium-low) code-points [ aliases bits ]; import (classifier-name | default); code-point-aliases { (dscp | dscp-ipv6 | exp | ieee-802.1 | ieee-802.1ad | inet-precedence) { alias-name bits; drop-profiles { Copyright © 2013, Juniper Networks, Inc.
  • Page 44 Class of Service Overview and Examples for EX9200 Switches profile-name { fill-level percentage drop-probability percentage; interpolate { drop-probability value; fill-level value; fabric { scheduler-map { priority (high | low) scheduler scheduler-name; forwarding-class-map { map-name { class class-name queue-num queue-number <restricted-queue queue-number>;...
  • Page 45 (bps | percent percentage | burst-size size); transmit-rate (bps | percent percentage | remainder) <exact | rate-limit>; traceoptions { file <files number> <match regular-expression> <size maximum-file-size> <world-readable | no-world-readable>; flag flag; no-remote-trace; traffic-control-profiles { profile-name { Copyright © 2013, Juniper Networks, Inc.
  • Page 46 Class of Service Overview and Examples for EX9200 Switches adjust-minimum rate; delay-buffer-rate (bps | cps cps | percent percentage); excess-rate (percent percentage | proportion value); guaranteed-rate (bps | percent percentage) <burst-size bytes>; overhead-accounting (frame-mode | cell-mode) <bytes byte-value>; scheduler-map map-name;...
  • Page 47: [Edit Firewall] Hierarchy Level

    [edit firewall family (any | ccc | ethernet-switching | inet | inet6 | mpls | vpls) filter filter-name term term-name then] [edit firewall filter filter-name term term-name then] Copyright © 2013, Juniper Networks, Inc.
  • Page 48 Class of Service Overview and Examples for EX9200 Switches The common firewall actions are as follows: count counter-name; forwarding-class class-name; loss-priority (high | low | medium-high | medium-low); next term; policer policer-name; three-color-policer policer-name { (single-rate single-rate-policer-name | two-rate two-rate-policer-name);...
  • Page 49 { list-name <except>; service-filter-hit; source-address { ip-prefix</prefix-length> <except>; (source-class [ class-names ] | source-class-except [ class-names ]); (source-port [ port-names ] | source-port-except [ port-names ]); source-prefix-list { list-name <except>; tcp-established; tcp-flags flag; tcp-initial; Copyright © 2013, Juniper Networks, Inc.
  • Page 50 Class of Service Overview and Examples for EX9200 Switches Common IPv4 Firewall Match Conditions This section lists statements that are valid at the following hierarchy levels, and is referenced at those levels in “Complete [edit firewall] Hierarchy” on page 38 instead of the statements being repeated.
  • Page 51 [ broadcast known-unicast multicast unknown-unicast ]); (user-vlan-1p-priority [ priorities ] | user-vlan-1p-priority [ priorities ]); (user-vlan-id [ vlan-ids ] | user-vlan-id-except [ vlan-ids ]); (vlan-ether-type [ protocol-types ] | vlan-ether-type-except [ protocol-types ]); Copyright © 2013, Juniper Networks, Inc.
  • Page 52 Class of Service Overview and Examples for EX9200 Switches Complete [edit firewall] Hierarchy firewall { family (any | ccc | ethernet-switching | inet | inet6 | mpls | vpls) { ... the family subhierarchies appear after the main [edit firewall] hierarchy ...
  • Page 53 (loss-priority [ priorities ] | loss-priority-except [ priorities ]); (packet-length [ values ] | packet-length-except [ values ]); then { ... statements in Common Firewall Actions on page 33 PLUS ... (accept | discard); Copyright © 2013, Juniper Networks, Inc.
  • Page 54 Class of Service Overview and Examples for EX9200 Switches firewall { family ccc { filter filter-name { accounting-profile [ profile-names ]; physical-interface-filter; interface-specific; term term-name { filter filter-name; from { (forwarding-class [ class-names ] | forwarding-class-except [ class-names ]); (interface-group [ group-names ] | interface-group-except [ group-names ]);...
  • Page 55 (loss-priority [ priorities ] | loss-priority-except [ priorities ]); # NOT valid at this level service-filter-hit; # NOT valid at this level (source-class [ class-names ] | source-class-except [ class-names ]); # NOT valid at this level then { (ignore | note); log; Copyright © 2013, Juniper Networks, Inc.
  • Page 56 Class of Service Overview and Examples for EX9200 Switches sample; syslog; filter filter-name { accounting-profile [ profile-names ]; interface-specific; term term-name { filter filter-name; from { ... statements in Common IP Firewall Match Conditions on page 35 statements in Common IPv4 Firewall Match Conditions on page 36 then { ...
  • Page 57 # NOT valid at this level (interface-group [ group-names ] | interface-group-except [ group-names ]); # NOT valid at this level (loss-priority [ priorities ] | loss-priority-except [ priorities ]); # NOT valid at this level Copyright © 2013, Juniper Networks, Inc.
  • Page 58 Class of Service Overview and Examples for EX9200 Switches service-filter-hit; # NOT valid at this level (source-class [ class-names ] | source-class-except [ class-names ]); # NOT valid at this level tcp-established; # NOT valid at this level tcp-flags flag; # NOT valid at this level tcp-initial;...
  • Page 59 (forwarding-class [ class-names ] | forwarding-class-except [ class-names ]); interface interface-name; interface-set set-name; (loss-priority [ priorities ] | loss-priority-except [ priorities ]); then { ... statements in Common Firewall Actions on page 33 PLUS ... (accept | discard); sample; Copyright © 2013, Juniper Networks, Inc.
  • Page 60 Class of Service Overview and Examples for EX9200 Switches firewall { family vpls { filter filter-name { accounting-profile [ profile-names ]; interface-specific; term term-name { filter filter-name; from { ... statements in Common Layer 2 Firewall Match Conditions on page 36 then { ...
  • Page 61 [ addresses ]; vrrp-inherit-from vrrp-group; filter { input filter-name; output filter-name; mtu bytes; no-neighbor-learn; no-redirects; primary; rpf-check { fail-filter filter-name; Copyright © 2013, Juniper Networks, Inc.
  • Page 62 Class of Service Overview and Examples for EX9200 Switches mode { loose; targeted-broadcast { forward-and-send-to-re; forward-only; family inet6 { accounting { destination-class-usage; source-class-usage { input; output; address address { eui-64; ndp ip-address (mac | multicast-mac) mac-address <publish>; preferred; primary; vrrp-inet6-group group-id { accept-data | no-accept-data;...
  • Page 63 <filename> <files number> <match regular-expression> <size maximum-file-size> <world-readable | no-world-readable>; flag flag <disable>; no-remote-trace; interfaces { interface-name { disable; accounting-profile name; aggregated-ether-options { ethernet-switch-profile { tag-protocol-id [ hexadecimal-identifiers ]; (flow-control | no-flow-control); lacp { (active | passive); admin-key key; fast-failover; Copyright © 2013, Juniper Networks, Inc.
  • Page 64 Class of Service Overview and Examples for EX9200 Switches link-protection { disable; (revertive | non-revertive); periodic (fast | slow); system-id mac-address; system-priority priority; (link-protection | no-link-protection); link-speed (100m | 1g | 8g | 10g | 40g | 50g | 80g | 100g | oc192);...
  • Page 65 { ethernet-policer-profile { input-priority-map { ieee802.1p premium [ values ]; output-priority-map { classifier { premium { forwarding-class class-name { loss-priority (high | low); policer cos-policer-name { aggregate { bandwidth-limit bps; burst-size-limit bytes; premium { Copyright © 2013, Juniper Networks, Inc.
  • Page 66 Class of Service Overview and Examples for EX9200 Switches bandwidth-limit bps; burst-size-limit bytes; tag-protocol-id; (mac-learn-enable | no-mac-learn-enable); (flow-control | no-flow-control); ignore-l3-incompletes; link-mode (automatic | full-duplex | half-duplex); (lloopback | no-loopback); keepalives <interval seconds> <down-count number> <up-count number>; speed (1g | 10m | 100m | 10m-100m | auto-negotiation);...
  • Page 67 (pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap); inner-tag-protocol-id tpid; inner-vlan-id number; tag-protocol-id tpid; vlan-id number; interface-shared-with psdnumerical-index; layer2-policer { input-hierarchical-policer policer-name; input-policer policer-name; input-three-color policer-name; output-policer policer-name; output-three-color policer-name; multi-chassis-protection peer-ip-address { interface interface-name; Copyright © 2013, Juniper Networks, Inc.
  • Page 68 Class of Service Overview and Examples for EX9200 Switches native-inner-vlan-id number; output-vlan-map { (pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap); inner-tag-protocol-id tpid; inner-vlan-id number; tag-protocol-id tpid; vlan-id number; peer-interface interface-name; peer-unit unit-number;...
  • Page 69 { hold-time seconds; priority number; track { interface interface-name { bandwidth-threshold bits-per-second priority-cost priority; priority-cost priority; priority-hold-time seconds; route ip-address-prefix/prefix-length routing-instance instance-name priority-cost priority; virtual-inet6-address [ addresses ]; virtual-link-local-address ipv6-address; vrrp-inherit-from { active-group group-number; Copyright © 2013, Juniper Networks, Inc.
  • Page 70 Class of Service Overview and Examples for EX9200 Switches active-interface interface-name; (dad-disable | no-dad-disable); filter { group filter-group-number; (input filter-name | input-list [ filter-names ]); (output filter-name | output-list [ filter-names ]); input-hierarchical-policer policer-name; mtu bytes; nd6-stale-time seconds; no-neighbor-learn; policer { input policer-name;...
  • Page 71 { group filter-group-number; (input filter-name | input-list [ filter-names ]); (output filter-name | output-list [ filter-names ]); policer { input policer-name; output policer-name; Related Notational Conventions Used in Junos OS Configuration Hierarchies Documentation Copyright © 2013, Juniper Networks, Inc.
  • Page 72 Class of Service Overview and Examples for EX9200 Switches Copyright © 2013, Juniper Networks, Inc.

Table of Contents