Download Print this page

Nokia 7450 Quality Of Service Manual

Ethernet service switch, service router, extensible routing system
Hide thumbs

Advertisement

QUALITY OF SERVICE GUIDE RELEASE 15.0.R1
7450 ETHERNET SERVICE SWITCH
7750 SERVICE ROUTER
7950 EXTENSIBLE ROUTING SYSTEM
QUALITY OF SERVICE GUIDE
RELEASE 15.0.R1
3HE 11974 AAAA TQZZA 01
Issue: 01
March 2017
Nokia — Proprietary and confidential.
Use pursuant to applicable agreements.

Advertisement

loading

  Related Manuals for Nokia 7450

  Summary of Contents for Nokia 7450

  • Page 1 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 7450 ETHERNET SERVICE SWITCH 7750 SERVICE ROUTER 7950 EXTENSIBLE ROUTING SYSTEM QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 3HE 11974 AAAA TQZZA 01 Issue: 01 March 2017 Nokia — Proprietary and confidential. Use pursuant to applicable agreements.
  • Page 2 © 2017 Nokia. Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.
  • Page 3: Table Of Contents

    QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table of Contents Getting Started ................15 About This Guide..................15 QoS Configuration Process ...............16 QoS Policies .................17 QoS Overview ...................17 Forwarding Classes...................18 2.2.1 High-Priority Classes .................19 2.2.2 Assured Classes..................19 2.2.3 Best-Effort Classes..................20 Queue Parameters ..................20 2.3.1 Queue ID ....................20 2.3.2...
  • Page 4 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 2.4.9.4 Tiers......................72 2.4.9.5 Scheduler Policies Applied to Applications..........73 2.4.9.6 Scheduler Policies Applied to SAPs ............74 2.4.9.7 Scheduler Policies Applied to Customer SLAs..........75 2.4.9.8 Scheduler Policies Applied to Multiservice Sites ........75 2.4.10 Shared-queue QoS Policies ..............75 2.4.11 ATM Traffic Descriptor Profiles..............76 2.4.12...
  • Page 5 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 4.3.2.3 SONET/SDH Ports ..................158 4.3.3 Default Network Queue Policy Values ............158 Service Management Tasks ..............164 4.4.1 Deleting QoS Policies................165 4.4.2 Removing a Policy from the QoS Configuration ........165 4.4.3 Copying and Overwriting QoS Policies............165 4.4.4 Editing QoS Policies ................166 Network Queue QoS Policy Command Reference........167...
  • Page 6 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 5.5.3 Copying and Overwriting QoS Policies............225 5.5.4 Deleting QoS Policies................226 5.5.5 Removing a Policy from the QoS Configuration ........227 Service Ingress and Egress QoS Policy Command Reference....229 5.6.1 Command Hierarchies................229 5.6.1.1 Service Ingress QoS Policy Commands..........229 5.6.1.2 Service Egress QoS Policy Commands ..........233 5.6.1.3...
  • Page 7 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.9.2 Egress PW Shaping using Spoke-SDP Forwarding Class-Based Redirection ....................443 6.9.2.1 Feature Configuration................443 6.9.2.2 Provisioning Model ..................444 6.9.2.3 Egress Marking of PW Packet Header ............446 6.9.2.4 Ingress and Egress PW Statistics ............446 6.10 Queue Group Behavior on LAG ..............447 6.10.1 Queue Group Queue Instantiation Per Link ..........447 6.10.2...
  • Page 8 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 7.1.1.4 Parental Association Scope..............576 7.1.1.5 Service or Subscriber or Multiservice Site-Level Scheduler Parental Association Scope..............576 7.1.1.6 Network Queue Parent Scheduler............577 7.1.1.7 Foster Parent Behavior for Orphaned Queues and Schedulers....578 7.1.1.8 Congestion Monitoring on Egress Port Scheduler........579 7.1.2 Frame-Based Accounting ................584 7.1.2.1...
  • Page 9 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 7.4.1.2 Port Scheduler Policy Configuration Commands ........623 7.4.1.3 Operational Commands................624 7.4.1.4 Show Commands ..................624 7.4.1.5 Clear Commands..................625 7.4.2 Command Descriptions ................626 7.4.2.1 Configuration Commands................626 7.4.2.2 Operational Commands................626 7.4.2.3 Scheduler Policy Commands ..............627 7.4.2.4 Port Scheduler Policy Commands............636 7.4.2.5 Show Commands ..................644 7.4.2.6...
  • Page 10 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 9.4.1 Command Hierarchies................719 9.4.1.1 Configuration Commands................719 9.4.1.2 Show Commands ..................719 9.4.2 Command Descriptions ................720 9.4.2.1 Configuration Commands................720 9.4.2.2 Show Commands ..................729 Advanced QoS Policies..............731 10.1 Overview....................731 10.2 Basic Configurations................731 10.2.1 Creating an Advanced QoS Policy ............731 10.2.2 Applying Advanced Policies ..............732 10.2.2.1...
  • Page 11 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 11.2.2.4 Ipipe SAPs....................761 11.2.2.5 VPRN SAPs.....................761 11.2.2.6 VPLS SAPs .....................761 11.2.3 Default ATM-TD-Profile Policy Values ............762 11.3 Service Management Tasks ..............763 11.3.1 Removing a Profile from the QoS Configuration ........763 11.3.2 Copying and Overwriting Profiles ............763 11.3.3 Editing QoS Policies ................764 11.4...
  • Page 12 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 13.1.7.8 HSMDA Available Buffer Register Operation ..........828 13.1.8 HSMDA Queue Congestion and Buffer Utilization Controls ....829 13.1.8.1 Maximum HSMDA Queue Depth.............830 13.1.8.2 Control Plane HSMDA RED Slope Policy Management ......830 13.1.8.3 HSMDA Slope Policy MBS Parameter ............831 13.1.8.4 HSMDA Slope Policy Slope Parameters ..........831 13.1.8.5...
  • Page 13 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 14.4.2 QoS in FRF.12 End-to-End Fragmentation ..........895 14.5 MLPPP Command Reference ..............897 14.5.1 Command Hierarchies................897 14.5.1.1 Configuration Commands................897 14.5.2 Command Descriptions ................898 14.5.2.1 Configuration Commands................898 Class Fair Hierarchical Policing (CFHP) ........903 15.1 Overview....................903 15.2 Parent Policer Priority and Unfair Sensitive Discard Thresholds.....904 15.3 CFHP Ingress and Egress Use Cases ............906...
  • Page 14 QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 15.13.1.1 Class Fair Hierarchical Policing Commands ...........937 15.13.1.2 Operational Commands................937 15.13.1.3 Show Commands ..................938 15.13.2 Command Descriptions ................938 15.13.2.1 Configuration Commands................938 Frequently Used QoS Terms ............955 16.1 Overview....................955 16.2 Above CIR Distribution ................955 16.3 Available Bandwidth ................955 16.4 CBS ......................956...
  • Page 15: Getting Started

    SR OS router. Table 1 Supported SR OS Router Chassis Types 7450 ESS 7750 SR 7950 XRS • 7450 ESS-7/12 running in • 7450 ESS-7/12 running in • 7950 XRS-16c standard mode (not mixed- mixed-mode (not standard • 7950 XRS-20/40...
  • Page 16: Qos Configuration Process

    Service Ingress and Egress QoS Policies Scheduler Scheduler QoS Policies Slope Slope QoS Policies Shared queue Shared-Queue QoS Policies 7450 ESS, 7750 SR ATM traffic descriptor QoS ATM Traffic Descriptor Profiles 7750 SR Named pools Named Pools 7450 ESS, 7750 SR...
  • Page 17: Qos Policies

    Nokia service routers (such as the 7950 XRS, 7750 SR, 7750 SR MG, and 7450 ESS) appears like a Layer 2 path to the service data although it is really traversing an IP or IP/MPLS core. The tunnel from one edge device to the other edge device is provisioned with an encapsulation and the services are mapped to the tunnel that most appropriately supports the service needs.
  • Page 18: Forwarding Classes

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 2.2 Forwarding Classes Routers support multiple forwarding classes and class-based queuing, so the concept of forwarding classes is common to all of the QoS policies. Each forwarding class (also called Class of Service (CoS)) is important only in relation to the other forwarding classes.
  • Page 19: High-Priority Classes

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 • High-priority/Premium • Assured • Best-Effort 2.2.1 High-Priority Classes The high-priority forwarding classes are Network-Control (nc), Expedited (ef), High- 1 (h1), and High-2 (h2). High-priority forwarding classes are always serviced at congestion points over other forwarding classes; this behavior is determined by the router queue scheduling algorithm (Virtual Hierarchical Scheduling).
  • Page 20: Best-Effort Classes

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Multiple assured classes are supported with relative weighting between them. In DiffServ, the code points for the various Assured classes are AF4, AF3, AF2, and AF1. Typically, AF4 has the highest weight of the four and AF1 the lowest. The Assured and Low-1 classes are differentiated based on the default DSCP mappings.
  • Page 21: Queue Hardware Scheduler

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 2.3.3 Queue Hardware Scheduler The hardware scheduler for a queue dictates how it will be scheduled relative to other queues at the hardware level. When a queue is defined in a service ingress or service egress QoS policy, it is possible to explicitly define the hardware scheduler to use for the queue when it is applied to a SAP.
  • Page 22: Peak Information Rate

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 When defining the CIR for a queue, the value specified is the administrative CIR for the queue.The router has a number of native rates in hardware that it uses to determine the operational CIR for the queue. The user has some control over how the administrative CIR is converted to an operational CIR if the hardware does not support the exact CIR and PIR combination specified.
  • Page 23: Adaptation Rule

    CIR and PIR rates. As the hardware has a very granular set of rates, Nokia’s recommended method to determine which hardware rate is used for a queue is to configure the queue rates with the associated adaptation rule and use the show pools output to display the rate achieved.
  • Page 24: Committed Burst Size

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 *A:PE# show qos sap-egress 10 detail | match expression "Queue-Id|CIR Rule" Queue-Id Queue-Type : auto-expedite PIR Rule : closest CIR Rule : closest *A:PE# *A:PE# show pools 1/1/1 access-egress service 1 | match expression "PIR|CIR" Admin PIR : 403000 Oper PIR...
  • Page 25: Maximum Burst Size

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 2.3.8 Maximum Burst Size The maximum burst size (MBS) parameter specifies the maximum queue depth to which a queue can grow. This parameter ensures that a customer that is massively or continuously over-subscribing the PIR of a queue will not consume all the available buffer resources.
  • Page 26 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Each profile type can only fill the queue up to its corresponding drop tail. Figure 1 shows the ingress and egress queue drop tails. Figure 1 Ingress and Egress Queue Drop Tails Scheduler Ingress Queue In profile...
  • Page 27: Wred Per Queue

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 The low drop tail configuration can be overridden for ingress and egress SAP and queue group queues, and for network egress queues. It is also possible to override the low drop tail for subscriber queues within an SLA profile using the keyword high- prio-only.
  • Page 28: Native Queue Mode

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 4 WRED Per Queue Congestion Control Summary Inplus- Out-of- Exceed- WRED- Slope Comments profile profile profile profile queue Usage Traffic Traffic Traffic Traffic Mode FP3 queues Drop tail Drop tail Exceed Native Exceed- If slope...
  • Page 29 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 To configure a native WRED queue, the wred-queue command is used under queue in a SAP egress QoS policy or egress queue group template with the mode set to native as follows: queue-group-templates egress queue-group <queue-group-name>...
  • Page 30 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 wred-queue policy "slope1" mode native slope-usage exceed-low exit exit The details of both the pool and queue can then be shown using the following command: *A:PE# show pools 1/1/1 access-egress service 1 =============================================================================== Pool Information ===============================================================================...
  • Page 31: Pool Per Queue Mode

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 ------------------------------------------------------------------------------- State : disabled Start Average : 0 KB Max Average : 0 KB Max Probability : 0 % Curr Probability : 0 % ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- High Slope Information ------------------------------------------------------------------------------- State : disabled Start Average : 0 KB Max Average...
  • Page 32 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Figure 3 WRED Queue: Pool-per-queue Mode Buffers from shared portion of WRED megapool Buffers from reserved portion of WRED megapool low-slope exceed-slope highplus- slope Queue depth Slopes in WRED queues operate on the full high-slope WRED pool size (MBS) WRED queue...
  • Page 33 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Egress wred 24576 93696 =============================================================================== *A:PE# To configure a pool per queue, the wred-queue command is used under queue in a SAP egress QoS policy or egress queue group template with the mode set to pool- per-queue as follows: queue-group-templates egress...
  • Page 34 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 exit The details of both the megapool and queue pool usages can then be shown using the show megapools command (detailed version): *A:PE# show megapools 5 fp 1 wred service-id 1 =============================================================================== MegaPool Information =============================================================================== Slot...
  • Page 35: Packet Markings

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 State : enabled Start Average : 6144 KB Max Average : 9216 KB Max Probability : 80 % Curr Probability : 0 % ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Exceed Slope Information ------------------------------------------------------------------------------- State : enabled Start Average : 3648 KB Max Average...
  • Page 36: Queue Counters

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 At ingress and egress, the current dynamic rate of the queue relative to the queue’s CIR does affect the scheduling priority between queues going to the same destination (either the switch fabric tap or egress port). The strict operating priority for queues is (from highest to lowest): •...
  • Page 37: Color Aware Profiling

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 2.3.14 Color Aware Profiling The normal handling of SAP ingress access packets applies an in-profile or out-of- profile state to each packet relative to the dynamic rate of the queue while the packet is forwarded toward the egress side of the system.
  • Page 38: Qos Policies Overview

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 2.4 QoS Policies Overview Service ingress, service egress, and network QoS policies are defined with a scope of either template or exclusive. Template policies can be applied to multiple SAPs or IP interfaces; exclusive policies can only be applied to a single entity. On most systems, the number of configurable SAP ingress and egress QoS policies per system is larger than the maximum number that can be applied per FP.
  • Page 39 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 The characteristics of the forwarding class queues are defined within the policy as to the number of forwarding class queues for unicast traffic and the queue characteristics. There can be up to eight unicast forwarding class queues in the policy;...
  • Page 40 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 5 QoS Policy Types and Descriptions Policy Type Applied at… Description Service Ingress SAP ingress Defines up to 32 forwarding class queues and queue Service parameters for traffic classification Ingress Defines up to 31 multipoint service queues for Policies broadcast, multicast, and destination unknown traffic in multipoint services...
  • Page 41: Service Versus Network Qos

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Table 5 QoS Policy Types and Descriptions (Continued) Policy Type Applied at… Description Shared Queue SAP ingress Shared queues can be implemented to mitigate the Shared- queue consumption on an MDA queue QoS Policies ATM Traffic SAP ingress...
  • Page 42: Qos Policy Entities

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • Network QoS policies • Network Queue QoS policies 2.4.2 QoS Policy Entities Services are configured with default QoS policies. Additional policies must be explicitly created and associated. There is one default service ingress QoS policy, one default service egress QoS policy, and one default network QoS policy.
  • Page 43: Network Qos Policies

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Default QoS policies map all traffic with equal priority and allow an equal chance of transmission (Best Effort (be) forwarding class) and an equal chance of being dropped during periods of congestion. QoS prioritizes traffic according to the forwarding class and uses congestion management to control access ingress, access egress, and network traffic with queuing according to priority.
  • Page 44 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • LSP EXP value-to-forwarding class and profile state mappings for all EXP values received • Ingress FC fp-redirect-group policer mapping • Egress FC port-redirect-group queue/policer mapping Network policy ID 1 is reserved as the default network QoS policy. The default policy cannot be deleted or changed.
  • Page 45: Network Queue Qos Policies

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Table 7 Default Network QoS Policy DSCP to Forwarding Class Mappings Ingress DSCP Forwarding Class dscp-name dscp-value FC ID Name Label Profile (binary - decimal) State Default Best-Effort 101110 - 46 Expedited 110000 - 48 High-1 111000 - 56...
  • Page 46 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • Committed Buffer Size (CBS) as a percentage of the buffer pool • Maximum Buffer Size (MBS) as a percentage of the buffer pool • Low drop tail as a percentage reduction from MBS •...
  • Page 47 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Table 8 Default Network Queue Policy Definition (Continued) Forwarding Class Queue Definition (Continued) • PIR = 100% High-2 (h2) Queue 5 Multicast Queue 13 • CIR = 100% • MBS = 50% •...
  • Page 48: Service Ingress Qos Policies

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 2.4.5 Service Ingress QoS Policies Service ingress QoS policies define ingress service forwarding class queues and map flows to those queues. When a service ingress QoS policy is created by default, it always has two queues defined that cannot be deleted: one for the default unicast traffic and one for the default multipoint traffic.
  • Page 49 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 To facilitate more forwarding classes, subclasses are supported. Each forwarding class can have one or multiple subclass associations for SAP ingress classification purposes. Each subclass retains the chassis-wide behavior defined to the parent class while providing expanded ingress QoS classification actions.
  • Page 50: Fc Mapping Based On Exp Bits At Vll/Vpls Sap

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 9 Forwarding Class and Enqueuing Priority Classification Hierarchy Based on Rule Type (Continued) Rule Forwarding Class Enqueuing Priority Comments dscp dscp-name Set when an fc-name Set when the priority Each dscp-name that defines exists in the policy.
  • Page 51 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Figure 6 Example Configuration — Carrier Application MPLS LSP VPLS/VLL ISP-1 Backbone ISP-1 Site A Provider Site B PE-B PE-B 7x50-1 7x50-2 ISP-Ether-Header BB-Link-Header ISP-Ether-Header ISP-Tunnel-Label BB-Tunnel-Label ISP-Tunnel-Label ISP-Svc-Label BB-Svc-Label ISP-Svc-Label ISP-Payload ISP-Ether-Header ISP-Payload ISP-Tunnel-Label...
  • Page 52 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The enqueuing priority is specified as part of the classification rule and is set to “high” or “low”. The enqueuing priority relates to the forwarding class queue’s low drop tail where only packets with a high enqueuing priority are accepted into the queue once the queue’s depth reaches the defined threshold.
  • Page 53 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 The MAC match criteria that can be used for an Ethernet frame depends on the frame’s format; see Table Table 11 MAC Match Ethernet Frame Types Frame Format Description 802dot3 IEEE 802.3 Ethernet frame. Only the source MAC, destination MAC, and IEEE 802.1p value are compared for match criteria.
  • Page 54: Egress Forwarding Class Override

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 13 Default Service Ingress Policy ID 1 Definition Characteristic Item Definition Queues Queue 1 One queue for all unicast traffic: • Forward Class: best-effort (be) • CIR = 0 • PIR = max (line rate) •...
  • Page 55: Service Egress Qos Policies

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Figure 7 Egress Forwarding Class Override Ingress (Service 1): These 2 AF classes are FC EF combined and use FC AF21 FC AF L1 across the core AF11 FC L1 Egress (Network): FC BE FC EF FC L1...
  • Page 56 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • A unique service egress QoS policy ID • A QoS policy scope of template or exclusive • At least one defined default queue Optional service egress QoS policy elements include: • Additional queues up to a total of eight separate queues (unicast) •...
  • Page 57: Named Pool Policies

    RELEASE 15.0.R1 2.4.7 Named Pool Policies The named buffer pool feature for the 7450 ESS and 7750 SR allows for the creation of named buffer pools at the MDA and port level. Named pools allow for a customized buffer allocation mode for ingress and egress queues that goes beyond the default pool behavior.
  • Page 58 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • Per-port named pools cannot be used by ingress network queues, but pools defined in a named pool policy defined on an ingress all network port are still created: − Ingress network queues use the default network pool or MDA named pools. −...
  • Page 59 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 When named pool mode is enabled, the system changes the way that default pools are created. The system no longer creates default pools per port; instead, a set of per forwarding plane level pools are created that are used by all queues that are not explicitly mapped to a named pool.
  • Page 60: Slope Policies

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 2.4.8 Slope Policies For network ingress, a buffer pool is created for the XMA or MDA and is used for all network ingress queues for ports on the XMA or MDA. Slope policies define the RED slope characteristics as a percentage of pool size for the pool on which the policy is applied.
  • Page 61 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 For access and network buffer pools, the percentage of the buffers that are to be reserved for CBS buffers is configurable. This setting indirectly assigns the amount of shared buffers on the pool. This is an important function that controls the ultimate average and total shared buffer utilization value calculation used for RED slope operation.
  • Page 62 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 9. The new SBAU is used as the SBAU the next time that a packet’s probability is plotted on the RED slope. 10. When a packet is removed from a queue (if the buffers returned to the buffer pool are from the shared buffers), the SBU is reduced by the amount of buffers returned.
  • Page 63: Tuning The Sbau Calculation

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 Plotting any value of shared buffer average utilization will result in a value for packet discard probability from 0 to 1. Changing the values for start-avg, max-avg, and max- prob allows the adaptation of the RED slope to the needs of the access or network queues using the shared portion of the buffer pool, including disabling the RED slope.
  • Page 64 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 15 TAF Impact on Shared Buffer Average Utilization Calculation Equates Instantaneous SBU SBAU Portion Portion 1/1 (1) 0 (0) 1/2 (0.5) 1/2 (0.5) 1/4 (0.25) 3/4 (0.75) 1/8 (0.125) 7/8 (0.875) 1/16 (0.0625) 15/16 (0.9375) 1/32 (0.03125)
  • Page 65: Slope Policy Parameters

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 2.4.8.3 Slope Policy Parameters The elements required to define a slope policy are: • a unique policy ID • the highplus, high, low, and exceed RED slope shapes for the buffer pool: the start-avg, max-avg and max-prob •...
  • Page 66: Scheduler Policies

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 16 Default Slope Policy Definition (Continued) Parameter Description Setting Low (RED) slope Administrative state Shutdown start-avg 50% utilization max-avg 75% utilization max-prob 80% probability Exceed (RED) Administrative state Shutdown slope start-avg 30% utilization max-avg 55% utilization...
  • Page 67 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 When a parent scheduler is defined without specifying level, weight, or CIR parameters, the default bandwidth access method is weight with a value of 1. If any orphaned policers or queues (where the specified scheduler name does not exist) exist on the ingress SAP and the policy application creates the required scheduler, the status on the queue becomes non-orphaned at this time.
  • Page 68 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Figure 9 Virtual Scheduler Internal Bandwidth Allocation Scheduler Loop Within CIRL Policy CIRL Child Offered Within CIR and Above CIR Load CIRL Limited by Child Maximum Rate (PIR) Child Served Within CIR Loop According to Within CIRL Provisioned CIR-Level...
  • Page 69: Virtual Hierarchical Scheduling

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 2.4.9.1 Virtual Hierarchical Scheduling Virtual hierarchical scheduling is a method that defines a bounded operation for a group of queues and, at egress only, policers. One or more policers and queues are mapped to a scheduler with strict and weighted metrics controlling access to the scheduler.
  • Page 70: Single-Tier Scheduling

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 2.4.9.2 Single-Tier Scheduling Single-tier scheduling is the default method of scheduling queues in the router. Queues are scheduled with single-tier scheduling if no explicit hierarchical scheduler policy is defined or applied. There are no configurable parameters for single-tier scheduling.
  • Page 71: Hierarchical Scheduler Policies

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 • Queues associated with the low-priority scheduler operating within their CIR • All queues with traffic above CIR and within PIR will be serviced by a biased round-robin • Queues associated with the high-priority scheduler operating above their CIR •...
  • Page 72: Tiers

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Figure 10 Hierarchical Scheduler and Queue Association Tier 3 Tier 2 Tier 1 Queue Weighted Rate Limiting Scheduler Queue Weighted Rate Limiting Scheduler Queue Weighted Rate Limiting Scheduler Queue Weighted Rate Limiting Scheduler Queue Weighted...
  • Page 73: Scheduler Policies Applied To Applications

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 2.4.9.5 Scheduler Policies Applied to Applications A scheduler policy can be applied either on a SAP (see Figure 11) or on a multiservice customer site (a group of SAPs with common origination/termination point) (see Figure 12).
  • Page 74: Scheduler Policies Applied To Saps

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Figure 12 Scheduler Policy on Customer Site and Scheduler Hierarchy Creation Hierarchical Schedulers Created Through Scheduler Policy Application To Individual SAP Scheduler Policy Ingress or Egress Forwarding Service Class Queue Weighted Packet Rate Limiting Packet Scheduler...
  • Page 75: Scheduler Policies Applied To Customer Slas

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.0.R1 2.4.9.7 Scheduler Policies Applied to Customer SLAs The router implementation of hierarchical QoS allows a common set of virtual schedulers to govern bandwidth over a set of customer services that is considered to be from the same site.
  • Page 76: Atm Traffic Descriptor Profiles

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 However, as a tradeoff, the total amount of traffic throughput at ingress of the node is reduced because any ingress packet serviced by a shared-queuing SAP is recirculated for further processing. When the node is only used for access SAPs, 5 Gbps ingress traffic is the maximum that can be processed without seeing packet drops at the MDA ingress.
  • Page 77: Network Qos Policies

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 3 Network QoS Policies 3.1 Network QoS Policies Overview The ingress component of the policy defines how DiffServ Code Points (DSCPs) and MPLS EXP bits are mapped to internal forwarding class and profile state. The forwarding class and profile state define the Per Hop Behavior (PHB) or the QoS treatment through the router.
  • Page 78: Network Ingress Tunnel Qos Override

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 3.2 Network Ingress Tunnel QoS Override 3.2.1 Override For Tunnel Terminated IP Routing Decisions This section describes a mechanism that provides the ability to ignore the network ingress QoS mapping of a terminated tunnel containing an IP packet that is to be routed to a base router or VPRN destination.
  • Page 79: Network Ingress Ip Match Criteria

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 3.2.1.2 Network Ingress IP Match Criteria IP match criteria classification is supported in the ingress section of a network QoS policy. The classification only applies to the outer IPv4 header of non-tunneled traffic; consequently, the use of an ip-criteria statement in a network QoS policy is ignored for received traffic when the network QoS policy is applied on the ingress network IP interface in the following cases:...
  • Page 80: Tunnel Termination Qos Override Operation

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The classification only applies to the outer IPv6 header of non-tunneled traffic; consequently, the use of an ipv6-criteria statement in a network QoS policy is ignored for received traffic when the network QoS policy is applied on the ingress network IP interface in the following cases: •...
  • Page 81: Enabling And Disabling Tunnel Termination Qos Override

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 When tunnel termination QoS override is enabled, the ToS field within the routed IP header is evaluated against the IP ToS precedence and DSCP entries in the applied network QoS policy on the ingress IP interface. If an explicit match entry is not found, the default QoS mapping is used.
  • Page 82: Qos For Self-Generated (Cpu) Traffic On Network Interfaces

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The IP precedence and DSCP based re-classification are supported on a network interface, on a CSC network interface in a VPRN, and on a PW used in an IES or VPRN spoke-interface. The CLI blocks the application of a network QoS policy with the egress re-classification commands to a network IP interface or to a spoke-SDP part of L2 service.
  • Page 83 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 The DSCP value can be set per application. When an application is configured to use a specified DSCP value, the 802.1p and MPLS EXP bits will be marked in accordance with the network (default 802.1p value of 7) or access (default 802.1p value of 0) egress policy as it applies to the logical interface that the packet will be egressing.
  • Page 84 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 19 Default QoS Values for Self-Generated Traffic (Continued) Protocol DSCP ICMP BE, NC1 IGMP IGMP Reporter IS-IS L2TP LDP/T-LDP MSC (Multichassis Support) MSDP ND (NDIS) NC1, NC2 NTP/SNTP OpenFlow OSPF PCEP PPPoE RADIUS...
  • Page 85: Default Dscp Mapping Table

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Table 19 Default QoS Values for Self-Generated Traffic (Continued) Protocol DSCP TACACS+ AF41 Telnet AF41 TFTP AF41 Traceroute TWAMP, TWAMP Light VRRP XMPP Note: ICMP echo requests (type 8) and ICMPv6 echo requests (type 128) initiated from the router will use the DSCP value set by the sgt-qos command.
  • Page 86: Basic Configurations

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Default 0x00 0b000000 0x30 0b110000 0x38 0b111000 0x2e 0b101110 af11 0x0a 0b001010 assured af12 0x0c 0b001100 assured af13 0x0e 0b001110 assured af21 0x12 0b010010 af22 0x14 0b010100 af23 0x16 0b010110 af31 0x1a 0b011010 af32...
  • Page 87 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 − Remarking — When enabled, this command remarks all packets that egress on the specified network port. The remarking is based on the forwarding class to DSCP and LSP EXP bit mapping defined under the egress node of the network QoS policy.
  • Page 88 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 − Default action — Defines the default action to be taken for packets that have an undefined configured classification. The default action specifies the forwarding class and profile to which such packets are assigned. −...
  • Page 89 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 port-redirect-group {queue queue-id | policer plcr-id [queue queue-id]} prec dscp-name fc fc-name profile {in | out | egress | inplus} remarking ingress default-action fc fc-name profile {in | out} dot1p dot1p-priority fc fc-name profile {in | out | use-de} dscp dscp-name fc {be | l2 | af | l1 | h2 | ef | h1 | nc} profile {in | out}...
  • Page 90: Applying Network Qos Policies

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 src-port [{lt | gt | eq} src- port-number src-port range start end renum old-entry-id new-entry-id ler-use-dscp lsp-exp lsp-exp-value fc fc-name profile {in | out} scope {exclusive | template} A:ALA-10:A:ALA-12>config>qos# info #------------------------------------------ echo "QoS Policy Configuration"...
  • Page 91: Default Network Qos Policy Values

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 3.5.3 Default Network QoS Policy Values The default network policy for IP interfaces is identified as policy-id 1. Default policies cannot be modified or deleted. Table 20 lists default network policy parameters. Table 20 Network Policy Defaults Field...
  • Page 92 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 20 Network Policy Defaults (Continued) Field Default fc be profile out fc l2 profile in fc af profile out fc af profile in fc h2 profile in fc ef profile in fc h1 profile in fc nc...
  • Page 93 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Table 20 Network Policy Defaults (Continued) Field Default dscp-out-profile lsp-exp-in-profile lsp-exp-out-profile fc h2 dscp-in-profile af41 dscp-out-profile af42 lsp-exp-in-profile lsp-exp-out-profile fc l dscp-in-profile af21 dscp-out-profile af22 lsp-exp-in-profile lsp-exp-out-profile fc l2 dscp-in-profile dscp-out-profile lsp-exp-in-profile lsp-exp-out-profile fc nc...
  • Page 94 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 default-action fc be profile out no ler-use-dscp dscp be fc be profile out dscp ef fc ef profile in dscp cs1 fc l2 profile in dscp nc1 fc h1 profile in dscp nc2 fc nc profile in dscp af11 fc af profile in dscp af12 fc af profile out...
  • Page 95: Service Management Tasks

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 dot1p-in-profile 6 dot1p-out-profile 6 exit fc h2 dscp-in-profile af41 dscp-out-profile af42 lsp-exp-in-profile 4 lsp-exp-out-profile 4 dot1p-in-profile 4 dot1p-out-profile 4 exit fc l1 dscp-in-profile af21 dscp-out-profile af22 lsp-exp-in-profile 3 lsp-exp-out-profile 2 dot1p-in-profile 3 dot1p-out-profile 3 exit fc l2...
  • Page 96: Removing A Policy From The Qos Configuration

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 interface interface-name qos network-policy-id The following output displays a sample configuration. A:ALA-7>config>router# info #------------------------------------------ echo "IP Configuration" #------------------------------------------ interface "ALA-1-2" address 10.10.4.3/24 broadcast host-ones no port no arp-timeout no allow-directed-broadcasts icmp mask-reply redirects 100 10 unreachables 100 10...
  • Page 97: Copying And Overwriting Network Policies

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 3.6.3 Copying and Overwriting Network Policies You can copy an existing network policy to a new policy ID value or overwrite an existing policy ID. The overwrite option must be specified or an error occurs if the destination policy ID exists.
  • Page 98: Editing Qos Policies

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 dscp nc2 fc nc profile in dscp af11 fc af profile in dscp af12 fc af profile out dscp af13 fc af profile out dscp af21 fc l1 profile in dscp af22 fc l1 profile out --------------------------------------------- A:ALA-12>config>qos# 3.6.4 Editing QoS Policies...
  • Page 99: Network Qos Policy Command Reference

    — no weight — description description-string — no description 3.7.1.1.2 Network QoS Policy Commands The commands listed in this section apply only to the 7450 ESS and 7750 SR. config — qos Issue: 01 3HE 11974 AAAA TQZZA 01...
  • Page 100 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — network network-policy-id [create] — no network network-policy-id — description description-string — no description — ingress — default-action fc fc-name profile {in | out} — dot1p dot1p-priority fc fc-name profile {in | out | use-de} —...
  • Page 101: Self-Generated Traffic Commands

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 — dst-port range start end — no dst-port — fragment {true | false | first-only | non-first- only} — no fragment — src-ip {ipv6-address/prefix-length | ipv6-address ipv6-address-mask} — no src-ip — src-port {lt | gt | eq} src-port-number —...
  • Page 102: Operational Commands

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — application dscp-app-name dscp {dscp-value | dscp-name} — application dot1p-app-name dot1p dot1p-priority — no application {dscp-app-name | dot1p-app-name} — dscp dscp-name fc fc-name — no dscp dscp-name — router — sgt-qos —...
  • Page 103: Command Descriptions

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 3.7.2 Command Descriptions 3.7.2.1 Configuration Commands 3.7.2.1.1 Generic Commands description Syntax description description-string no description Context config>qos>mc-fr-profile-egress config>qos>mc-fr-profile-ingress config>qos>network config>qos>network>ingress>ip-criteria>entry config>qos>network>ingress>ipv6-criteria>entry Description This command creates a text description stored in the configuration file for a configuration context.
  • Page 104 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The copy command is used to create new policies using existing policies and also allows bulk modifications to an existing policy with the use of the overwrite keyword. Parameters network src-pol dst-pol — Indicates that the source and destination policies are network policy IDs.
  • Page 105 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Description This command provides the Frame Relay scheduling class context for the user to configure the ingress or egress QoS parameters of an MLFR bundle or an FRF.12 UNI/NNI link for this profile.
  • Page 106 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 create — Required parameter when creating a multi-class Frame Relay egress profile. max-queue-size Syntax max-queue-size queue-size no max-queue-size Context config>qos>mc-fr-profile-egress>class Description This command configures the maximum size for each Frame Relay scheduling class queue for this profile.
  • Page 107 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Description This command configures the WRR weight scheduling parameter for each Frame Relay scheduling class queue for this profile. Default Class 0 = N/A Class 1 = 1 (not configurable) Class 2 = 89 Class 3 = 10 Parameters weight —...
  • Page 108 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Network policy-id 1 exists as the default policy that is applied to all network ports by default. This default policy cannot be modified or deleted. It defines the default DSCP-to-FC mapping and default unicast meters for ingress IP traffic.
  • Page 109 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Parameters exclusive — When the scope of a policy is defined as exclusive, the policy can only be applied to one interface. If a policy with an exclusive scope is assigned to a second interface, an error message is generated.
  • Page 110 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters fc-name — Specifies the forwarding class name. All packets with DSCP value or MPLS EXP or dot1p bits that are not defined will be placed in this forwarding class. Values be, l2, af, l1, h2, ef, h1, nc profile {in | out} —...
  • Page 111 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 fc-name — The value given for the fc-name parameter must be one of the predefined forwarding classes in the system. Specifying the fc-name is optional. When a packet matches the rule, the forwarding class is only overridden when the fc fc-name parameter is defined on the rule.
  • Page 112 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 21 Default DSCP Names to DSCP Value Mapping DSCP Name DSCP Value DSCP Value DSCP Value Decimal Binary Hexadecimal 0x30 0b110000 0x38 0b111000 0x2e 0b101110 af41 0x22 0b100010 af42 0x24 0b100100 af43 0x26...
  • Page 113 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Table 22 Default Class Selector Code Points to DSCP Value Mapping DSCP Name DSCP Value DSCP Value DSCP Value Decimal Binary Hexadecimal 0b001000 fc-name — Enter this required parameter to specify the fc-name with which the code point will be associated.
  • Page 114 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 fp-redirect-group Syntax fp-redirect-group policer-type-policer policer-id no fp-redirect-group policer-type Context config>qos>network>ingress>fc Description This command is used to redirect the FC of a broadcast packet received in a VPLS service over a PW or network IP interface to an ingress forwarding plane queue-group. It defines the mapping of an FC to a policer-id and redirects the lookup of the policer of the same ID in some ingress forwarding plane queue-group instance.
  • Page 115 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Attempting to apply a network QoS policy containing an ip-criteria statement to any object except a network IP interface will result in an error. The no form of this command deletes all the entries specified under this node. Once IP criteria entries are removed from a network ingress policy, the IP criteria is removed from all network interfaces where that policy is applied.
  • Page 116 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The list of flow criteria is evaluated in a top-down manner with the lowest entry ID at the top and the highest entry ID at the bottom. If the defined match criteria for an entry within the list matches the information in the ingress packet, the system stops matching the packet against the list and performs the matching entries reclassification actions.
  • Page 117 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 The action command must be executed for the match criteria to be added to the active list of entries. Each time action is executed on a specific entry ID, the previously entered values for fc fc- name and profile are overridden with the newly defined parameters.
  • Page 118 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of this command removes the match criteria for the entry-id. Parameters protocol protocol-id — Specifies an IP protocol to be used as an ingress network QoS policy match criterion. The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number.
  • Page 119 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Table 23 Protocol ID Descriptions (Continued) Protocol Protocol ID Description iso-ip ISO Internet Protocol eigrp EIGRP ospf-igp OSPFIGP ether-ip Ethernet-within-IP Encapsulation encap Encapsulation Header pnni PNNI over IP Protocol Independent Multicast vrrp Virtual Router Redundancy Protocol l2tp...
  • Page 120 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 802.1p bits • DSCP • IP quintuple The no form of this command removes the match criteria for the entry-id. Parameters next-header next-header — Specifies the next header to match. The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number.
  • Page 121 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Context config>qos>network>ingress>ip-criteria>entry>match config>qos>network>ingress>ipv6-criteria>entry>match Description This command configures a destination address range to be used as a network ingress QoS policy match criterion. To match on the destination address, specify the address and its associated mask, for example, 10.1.0.0/16.
  • Page 122 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 fragment Syntax fragment {true | false} no fragment Context config>qos>ingress>ip-criteria>entry>match Description This command configures fragmented or non-fragmented IP packets as a network ingress QoS policy match criterion. The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not.
  • Page 123 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 no src-ip Context config>qos>network>ingress>ip-criteria>entry>match config>qos>network>ingress>ipv6-criteria>entry>match Description This command configures a source IPv4 or IPv6 address range to be used as a network ingress QoS policy match criterion. To match on the source IPv4 or IPv6 address, specify the address and its associated mask, for example, 10.1.0.0/16.
  • Page 124 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command configures a source TCP or UDP port number or port range for a network ingress QoS policy match criterion. The no form of this command removes the source port match criterion. Default No src-port match criterion.
  • Page 125 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Description This command is used to enable tunnel QoS mapping on all ingress network IP interfaces that the network-qos-policy-id is associated with. The command may be defined at anytime after the network QoS policy has been created. Any network IP interfaces currently associated with the policy will immediately start to use the internal IP ToS field of any tunnel terminated IP routed packet received on the interface, ignoring any QoS markings in the tunnel portion of the packet.
  • Page 126 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 fc fc-name — Enter this required parameter to specify the fc-name that the EXP bit pattern will be associated with. Values be, l2, af, l1, h2, ef, h1, nc profile {in | out} — Enter this required parameter to indicate whether the LSP EXP value is the in-profile or out-of-profile value.
  • Page 127 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Description This command is used to explicitly define the marking of the DE bit for fc fc-name according to the inplus-profile or in-profile and out-of-profile or exceed-profile status of the packet (fc- name may be used to identify the dot1p value).
  • Page 128 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command specifies dot1p in-profile mappings. The inplus-profile traffic is marked with the same value as in-profile traffic. The no form of the command resets the configuration to the default in-profile dot1p-priority setting for policy-id 1.
  • Page 129 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Description This command specifies the in-profile DSCP name for the forwarding class. The corresponding DSCP value will be used for all IP packets that require marking at egress on this forwarding class queue, and that are in-profile. The inplus-profile traffic is marked with the same value as in-profile traffic.
  • Page 130 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command specifies the in-profile LSP EXP value for the forwarding class. The EXP value will be used for all LSP labeled packets requiring marking that require marking at egress on this forwarding class queue, and that are in-profile.
  • Page 131 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 port-redirect-group Syntax port-redirect-group {queue queue-id | policer policer-id [queue queue-id]} no port-redirect-group Context config>qos>network>egress>fc Description This command is used to redirect the FC of a packet of a pseudowire (PW) or network IP interface to an egress port queue group.
  • Page 132 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The IP precedence- and DSCP-based reclassification are supported on a network interface, on a CSC network interface in a VPRN, and on a PW used in an IES or VPRN spoke interface.
  • Page 133 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 prec Syntax prec ip-prec-value fc fc-name profile {in | out | exceed | inplus} no prec ip-prec-value Context config>qos>network>egress Description This command defines a specific IP precedence value that must be matched in order to perform the associated reclassification actions.
  • Page 134 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 profile {in | out | exceed | inplus} — The profile reclassification action is mandatory. When specified, packets matching the IP precedence value will be explicitly reclassified to the profile specified regardless of the ingress profiling decision. To remove the profile reclassification action for the specified IP precedence value, the no prec command must be executed.
  • Page 135 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Ingress IP Interface Type Egress Network IP Interface Trust Egress Network IP Interface Trust and Trust State Remark Disabled (Default) Remark Enabled IES Non-Trusted (Default) Egress Remarked Egress Remarked IES Trusted Egress Not Remarked Egress Remarked VPRN Non-Trusted...
  • Page 136 Values The following values apply to the 7450 ESS: bgp, call-trace, dhcp, dns, ftp, icmp, igmp, ldp, mld, ntp, ospf, radius, rsvp, rip, ssh, snmp, snmp-notification, syslog, telnet, tftp, traceroute, tacplus, vrrp dscp-value —...
  • Page 137 — Specifies the dot1p application name. Values The following values apply to the 7750 SR and 7950 XRS: arp, isis, pppoe Values The following values apply to the 7450 ESS arp, isis dscp Syntax dscp dscp-name fc fc-name no dscp dscp-name Context config>router>sgt-qos...
  • Page 138: Show Commands

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 3.7.2.3 Show Commands dscp-table Syntax dscp-table [value dscp-value] Context show>qos Description This command displays the DSCP name-to-DSCP value mappings. Parameters value dscp-value — The specific DSCP value for which to display information. Values 0 to 63 Default...
  • Page 139 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 af32 0111 0000 cp29 0111 0100 af33 0111 1000 cp31 0111 1100 1000 0000 cp33 1000 0100 af41 1000 1000 cp35 1000 1100 af42 1001 0000 cp37 1001 0100 af43 1001 1000 cp39 1001 1100 1010 0000...
  • Page 140 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 24 Show QoS DSCP Table Output Fields (Continued) Label Description DSCP Value Displays the DSCP values, between 0 and 63. TOS (bin) Displays the type of service in binary format. TOS (hex) Displays the type of service in hex format.
  • Page 141 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 mc-fr-profile-egress Syntax mc-fr-profile-egress mc-fr-profile-egress profile-id [detail] Context show>qos Description This command displays MLFR egress profile details. Output The following output is an example of MLFR ingress profile information. Sample Output *A:Cpm-A# show qos mc-fr-profile-egress 1 ======================================================================== Multi-class FR Egress Profile (1) ========================================================================...
  • Page 142 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters policy-id — Displays information for the specific policy ID. Values 1 to 65535 Default all network policies detail — Includes information about ingress and egress DSCP and LSP EXP bit mappings and network policy interface associations.
  • Page 143 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 af22 af23 af31 af32 af33 af41 af42 af43 ------------------------------------------------------------------------------ LSP EXP Bit Map Fowarding Class Profile ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ Egress Forwarding Class Queuing ------------------------------------------------------------------------------ FC Name : af - DSCP Mapping Out-of-Profile : af12 In-Profile : af11 - LSP EXP Bit Mapping...
  • Page 144 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 FC Name : l2 - DSCP Mapping Out-of-Profile : cs1 In-Profile : cs1 - LSP EXP Bit Mapping Out-of-Profile : 1 In-Profile FC Name : nc - DSCP Mapping Out-of-Profile : nc2 In-Profile : nc2 - LSP EXP Bit Mapping...
  • Page 145 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 - DE Mark : Force 1 FC Value FC Name : l2 - DSCP Mapping Out-of-Profile : cs1 In-Profile : cs1 - dot1p Mapping Out-of-Profile : 1 In-Profile - LSP EXP Bit Mapping Out-of-Profile : 1 In-Profile - DE Mark...
  • Page 146 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 ------------------------------------------------------------------------------- Egress Forwarding Class Mapping ------------------------------------------------------------------------------- FC Value FC Name : be - DSCP Mapping Out-of-Profile : be In-Profile : be - dot1p Mapping Out-of-Profile In-Profile - LSP EXP Bit Mapping Out-of-Profile In-Profile DE Mark...
  • Page 147 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 - dot1p Mapping Out-of-Profile In-Profile - LSP EXP Bit Mapping Out-of-Profile In-Profile DE Mark None Redirect Grp Q None Redirect Grp Plcr: None FC Value FC Name : ef - DSCP Mapping Out-of-Profile : ef In-Profile...
  • Page 148: Configuration File

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Redirect UniCast Plcr : None Redirect MultiCast Plcr : None Redirect BroadCast Plcr : None Redirect Unknown Plcr : None FC Value FC Name : af Redirect UniCast Plcr : None Redirect MultiCast Plcr : None Redirect BroadCast Plcr : None Redirect Unknown Plcr...
  • Page 149 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.0.R1 Table 25 Show QoS Network Output Fields (Continued) Label Description Forward Class/ Specifies the forwarding class name. FC Name Profile Out — Specifies that IP packets requiring marking the egress on this forwarding class queue that are out of profile.
  • Page 150 Values The following values apply to the 7450 ESS: arp, bgp, dhcp, dns, ftp, icmp, isis, ldp, ntp, ospf, radius, rip, rsvp, snmp, snmp-notification, ssh, syslog, tacplus, telnet, tftp, traceroute,...
  • Page 151: Network Queue Qos Policies

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 4 Network Queue QoS Policies 4.1 Overview Network queue policies define the ingress network queuing at the XMA/MDA network node level. Network queue policies are also used at the Ethernet port and SONET/ SDH path level to define network egress queuing.
  • Page 152: Basic Configurations

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 4.3 Basic Configurations A basic network queue QoS policy must conform to the following: • Each network queue QoS policy must have a unique policy name. • Queue parameters can be modified, but cannot be deleted. 4.3.1 Creating a Network Queue QoS Policy Configuring and applying QoS policies other than the default policy is optional.
  • Page 153 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 description "Default network queue QoS policy." queue 1 create mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10 exit exit exit queue 2 create rate 100 cir 25 mbs 50 cbs 3 drop-tail percent-reduction-from-mbs 10 exit...
  • Page 154 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 exit queue 7 create rate 100 cir 10 mbs 25 cbs 3 drop-tail percent-reduction-from-mbs 10 exit exit exit queue 8 create rate 100 cir 10 mbs 25 cbs 3 drop-tail percent-reduction-from-mbs 10 exit exit...
  • Page 155 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 exit queue 13 multipoint create rate 100 cir 100 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10 exit exit exit queue 14 multipoint create rate 100 cir 100 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10 exit...
  • Page 156: Applying Network Queue Qos Policies

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 queue 5 exit fc l1 create multicast-queue 12 queue 4 exit fc l2 create multicast-queue 10 queue 2 exit fc nc create multicast-queue 16 queue 8 exit 4.3.2 Applying Network Queue QoS Policies Apply network queue policies to the following entities: •...
  • Page 157: Ethernet Ports

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 exit egress pool default resv-cbs sum slope-policy "default" exit exit exit access ingress pool default resv-cbs sum slope-policy "default" exit exit egress pool default resv-cbs sum slope-policy "default" exit exit exit no shutdown ----------------------------------------------...
  • Page 158: Sonet/Sdh Ports

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 4.3.2.3 SONET/SDH Ports Use the following CLI syntax to apply a network queue policy to a SONET/SDH port: CLI Syntax: config>port# sonet-sdh path path network queue-policy name The following output displays the port configuration. A:ALA-48>config>port# info ---------------------------------------------- description "OC-12 SONET/SDH"...
  • Page 159 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 Table 26 Network Queue Policy Defaults (Continued) Field Default low percent-reduction- from-mbs queue 2 low percent-reduction- from-mbs queue 3 low percent-reduction- from-mbs queue 4 low percent-reduction- from-mbs queue 5 Issue: 01 3HE 11974 AAAA TQZZA 01...
  • Page 160 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 26 Network Queue Policy Defaults (Continued) Field Default low percent-reduction- from-mbs queue 6 low percent-reduction- from-mbs queue 7 low percent-reduction- from-mbs queue 8 low percent-reduction- from-mbs fc af queue 3 multicast-queue 11 fc be queue 1...
  • Page 161 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 Table 26 Network Queue Policy Defaults (Continued) Field Default fc h1 queue 67 multicast-queue 15 fc h2 queue 5 multicast-queue 13 fc l1 queue 7 multicast-queue 12 fc l2 queue 2 multicast-queue 10 fc nc queue 8...
  • Page 162 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 queue 4 auto-expedite create rate 100 cir 25 mbs 25 cbs 3 drop-tail percent-reduction-from-mbs 10 exit exit exit queue 5 auto-expedite create rate 100 cir 100 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10 exit...
  • Page 163 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 exit queue 10 multipoint auto-expedite create rate 100 cir 5 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10 exit exit exit queue 11 multipoint auto-expedite create rate 100 cir 5 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10...
  • Page 164: Service Management Tasks

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 exit exit queue 16 multipoint auto-expedite create rate 100 cir 10 mbs 25 cbs 1 drop-tail percent-reduction-from-mbs 10 exit exit exit fc af create multicast-queue 11 queue 3 exit fc be create multicast-queue 9 queue 1 exit...
  • Page 165: Deleting Qos Policies

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 • Removing a Policy from the QoS Configuration • Copying and Overwriting QoS Policies • Editing QoS Policies 4.4.1 Deleting QoS Policies A network queue policy is associated by default with XMA or MDA network ingress ports.
  • Page 166: Editing Qos Policies

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 4.4.4 Editing QoS Policies Existing policies, except the default policies, and entries in the CLI can be modified. The changes are applied immediately to all interfaces where the policy is applied. To prevent configuration errors, use the copy command to make a duplicate of the original policy to a work area, make the edits, then overwrite the original policy.
  • Page 167: Network Queue Qos Policy Command Reference

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 4.5 Network Queue QoS Policy Command Reference 4.5.1 Command Hierarchies • Configuration Commands • Operational Commands • Show Commands 4.5.1.1 Configuration Commands config — qos — network-queue policy-name [create] — no network-queue policy-name —...
  • Page 168: Operational Commands

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — queue queue-id [multipoint] [queue-type] [create] — no queue queue-id — adaptation-rule [pir adaptation-rule] [cir adaptation-rule] — no adaptation-rule — avg-frame-overhead percent — no avg-frame-overhead — percent — no — drop-tail —...
  • Page 169: Command Descriptions

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 4.5.2 Command Descriptions 4.5.2.1 Configuration Commands 4.5.2.1.1 Generic Commands description Syntax description description-string no description Context config>qos>network-queue Description This command creates a text description stored in the configuration file for a configuration context.
  • Page 170 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The copy command is a configuration-level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword. Parameters network-queue —...
  • Page 171 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 Description This command enters the context to configure queue definitions for use on HSMDAs. packet-byte-offset Syntax packet-byte-offset {add add-bytes | subtract sub-bytes} no packet-byte-offset Context config>qos>network-queue>egress-hsmda Description This command adds or subtracts the specified number of bytes to the accounting function for each packet handled by the HSMDA queue.
  • Page 172 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The packet-byte-offset value may be overridden for the HSMDA queue at the network queue level. The no form of the command removes any accounting size changes to packets handled by the queue.
  • Page 173 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 The no form of the command restores the defined queue-id to its default parameters. All HSMDA queues having the queue-id and associated with the QoS policy are re-initialized to default parameters. Parameters queue-id —...
  • Page 174 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The MBS value is used by a queue to determine whether it has exhausted its total allowed buffers while enqueuing packets. Once the queue has exceeded its maximum amount of buffers, all packets are discarded until the queue transmits a packet.
  • Page 175 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 Description This command associates an existing HSMDA slope policy with the QoS policy HSMDA queue. The specified hsmda-slope-policy-name must exist for the command to succeed. If the policy name does not exist, the command has no effect on the existing slope policy association.
  • Page 176 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 High Slope: • Start-Utilization 100% • Max-Utilization 100% • Max-Probability 100% • Shutdown Low Slope: • Start-Utilization 90% • Max-Utilization 90% • Max-Probability 1 • No Shutdown Time-Average-Factor: 0 The no form of the command restores the association between the queue and the HSMDA default slope policy.
  • Page 177 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 Context config>qos>network-queue>egress-hsmda Description This command associates an existing HSMDA weighted-round-robin (WRR) scheduling loop policy with the HSMDA queue. Parameters hsmda-wrr-policy-name — Specifies the existing HSMDA WRR policy name to associate with the queue.
  • Page 178 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of the command sets the multicast forwarding type queue-id back to the default queue for the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
  • Page 179 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 between the members of the group. Two weighted groups are supported and each may contain up to three consecutive scheduling classes. The weighed group assumes its highest member class’s inherent strict scheduling level for scheduling purposes. Strict priority level 8 has the highest priority while strict level 1 has the lowest.
  • Page 180 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The queue command allows the creation of multipoint queues. Only multipoint queues can receive ingress packets that need flooding to multiple destinations. By separating the unicast for multipoint traffic at service ingress and handling the traffic on separate multipoint queues, special handling of the multipoint traffic is possible.
  • Page 181 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 queue-type — The expedite, best-effort, and auto-expedite queue types are mutually exclusive. Each defines the method that the system uses to service the queue from a hardware perspective. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy.
  • Page 182 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters adaptation-rule — Specifies the adaptation rule to be used while computing the operational CIR or PIR value. Values pir — Defines the constraints enforced when adapting the PIR rate defined within the queue queue-id rate command.
  • Page 183 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 • Frame-encapsulation overhead — Using the avg-frame-overhead parameter, the frame- encapsulation overhead is the queue’s current offered-load (how much has been received by the queue) multiplied by the avg-frame-overhead. If a queue had an offered load of 10 000 octets and the avg-frame-overhead equals 10%, the frame-encapsulation overhead would be 10 000 x 0.1 or 1000 octets.
  • Page 184 SAP and Subscriber SLA-Profile Average Frame Overhead Override (applies only to the 7450 ESS and 7750 SR) — The average frame overhead parameter on a sap-egress may be overridden at an individual egress queue basis. On each SAP and within the sla-profile policy used by subscribers, an avg-frame-overhead command may be defined under the queue-override context for each queue.
  • Page 185 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 The CBS for a queue is used to determine whether it has exhausted its reserved buffers while enqueuing packets. Once the queue has exceeded the amount of buffers considered in reserve for this queue, it must contend with other queues for the available shared buffer space within the buffer pool.
  • Page 186 The configuration parameters for each queue come from the applied egress network-queue policy on the network port or channel. Forwarding class queue on egress channel applies only to the 7450 ESS and 7750 SR.
  • Page 187 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 Syntax Context config>qos>network-queue>queue>drop-tail Description This command enters the context to configure the queue low drop tail parameters. The low drop tail defines the queue depth beyond which out-of-profile packets will not be accepted into the queue and will be discarded.
  • Page 188 Forwarding class queue on egress channel applies only to the 7450 ESS and 7750 SR. The mbs value is used to calculate the queue’s MBS size based on the total amount buffer space allocated for the buffer pool on the egress network port or channel.
  • Page 189 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 Parameters percent — The percent of buffers from the total buffer pool space for the maximum amount of buffers, expressed as a decimal integer. If 10 Mbytes is the total buffer space in the buffer pool, a value of 10 would limit the maximum queue size to 1 Mbyte (10%) of buffer space for the forwarding class queue.
  • Page 190 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command specifies whether this queue feeds off a port-level scheduler. For the network- queue policy context, only the port-parent command is supported. When a port scheduler exists on the port, network queues without a port-parent association will be treated as an orphan queue on the port scheduler and treated according to the current orphan behavior on the port scheduler.
  • Page 191 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 rate Syntax rate percent [cir percent] no rate Context config>qos>network-queue>queue Description This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the percentage that the queue can transmit packets through the switch fabric (for SAP ingress queues) or out an egress interface (for SAP egress queues).
  • Page 192: Show Commands

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 4.5.2.3 Show Commands network-queue Syntax network-queue [network-queue-policy-name] [detail] Context show>qos Description This command displays network queue policy information. Parameters network-queue-policy-name — The name of the network queue policy. Values Valid names consist of any string up to 32 characters long composed of printable, 7-bit ASCII characters.
  • Page 193 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.0.R1 ------------------------------------------------------------------------------ UCastQ ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ Associations ------------------------------------------------------------------------------ Port-id : 1/1/1 ============================================================================== A:ALA-12>show>qos# Table 28 Network Queue Labels and Descriptions Label Description Policy The policy name that uniquely identifies the policy. Description A text string that helps identify the policy’s context in the configuration file.
  • Page 194 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 3HE 11974 AAAA TQZZA 01 Issue: 01...
  • Page 195: Service Ingress And Egress Qos Policies

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 5 Service Ingress and Egress QoS Policies 5.1 Overview There is one default service ingress policy and one default service egress policy. Each policy can have up to 32 ingress queues and 8 egress queues per service. The default policies can be copied and modified but they cannot be deleted.
  • Page 196: Service Ingress Qos Policy

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 5.3 Service Ingress QoS Policy To create a service ingress policy, define the following: • A policy ID value. The system will not dynamically assign a value. • A description. The description provides a brief overview of policy features. •...
  • Page 197: Service Ingress Qos Queue

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 5.3.1 Service Ingress QoS Queue To create a service ingress queue, define the following: • A new queue ID value — The system will not dynamically assign a value. •...
  • Page 198: Percent-Rate Support

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 parent VPN_reserved rate 1 exit queue 25 multipoint create parent VPN_video rate 1500 cir 1500 exit queue 26 multipoint create parent VPN_voice rate 2500 cir 2500 exit queue 27 multipoint create parent VPN_nc rate 100 cir 36 exit...
  • Page 199: Ingress Forwarding Class (Fc)

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 <police> : keyword <port-limit | local-*> : keyword *B:Dut-A>config>qos>sap-ingress# policer 1 percent-rate - no percent-rate - percent-rate <pir-percent> [cir <cir-percent>] <pir-percent> : [0.01..100.00] <cir-percent> : [0.00..100.00] 5.3.3 Ingress Forwarding Class (FC) The following displays a forwarding class and precedence configurations: A:ALA-7>config>qos# info #------------------------------------------...
  • Page 200: Ingress Ip Match Criteria

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 prec 2 fc af prec 3 fc ef prec 5 fc h1 prec 6 fc h2 prec 7 fc nc #------------------------------------------ A:ALA-7>config>qos# 5.3.4 Ingress IP Match Criteria When specifying SAP ingress match criteria, only one match criteria type (IP/IPv6 or MAC) can be configured in the SAP ingress QoS policy.
  • Page 201: Ingress Ipv6 Match Criteria

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 5.3.5 Ingress IPv6 Match Criteria When specifying SAP ingress match criteria, only one match criteria type (IP/IPv6 or MAC) can be configured in the SAP ingress QoS policy. This feature applies only to the 7750 SR and 7950 XRS.
  • Page 202: Vlan Id Matching

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • Match criteria for ingress SAP QoS policy. Optionally, specify an IP protocol to be used as an ingress SAP QoS policy match criterion. The following displays an ingress MAC criteria configuration: A:ALA-7>config>qos# info #------------------------------------------ echo "QoS Policy Configuration"...
  • Page 203: Ingress Criteria Classification Directly To Policer

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 exit exit exit exit 5.3.7 Ingress Criteria Classification Directly to Policer It is possible to classify traffic directly to a policer, independent of the policer/queue assigned to the traffic’s forwarding class. This is supported at SAP ingress by configuring a policer in the action statement: ip-criteria, ipv6-criteria, or mac-criteria.
  • Page 204: Virtual Network Identifier (Vni) Classification

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 src-mac 00-xx-yy-00-00-00 ff-ff-ff-00-00-00 exit action policer 1 exit exit exit 5.3.8 Virtual Network Identifier (VNI) Classification Virtual Network Identifier (VNI) classification is supported for VXLAN and VXLAN GPE traffic within a SAP ingress QoS policy. This classification is configured in the ip-criteria and ipv6-criteria contexts with type vxlan-vni (changed from the default type normal).
  • Page 205 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 vxlan-vni range 2 10 exit action policer 2 exit exit exit Ingress VNI classification is applicable to all Ethernet SAPs, except for PW-SAPs, B- VPLS SAPs, and CCAG SAPs, in any applicable service. The feature is supported on FP2- and higher-based hardware.
  • Page 206: Fc Mapping Based On Exp Bits

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 5.3.9 FC Mapping Based on EXP Bits You can use the lsp-exp command to set your sap-ingress qos policy on Ethernet L2 SAPs to perform FC mapping based on EXP bits. The lsp-exp option causes the forwarding class and drop priority of incoming traffic to be determined by the mapping result of the EXP bits in the top label.
  • Page 207: Service Egress Qos Queue

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 5.4.1 Service Egress QoS Queue To create a service egress queue, define the following: • The forwarding class name or names associated with the egress queue. The egress queue for the service traffic is selected based on the forwarding classes that are associated with the queue.
  • Page 208: Dynamic Mbs For Egress Queue Group Queues

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 For queues, when the queue rate is in percent-rate, either a local-limit or a port-limit can be applied. When the local-limit is used, the percent-rate is relative to the queue’s parent scheduler rate or the agg-rate rate at egress.
  • Page 209 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 When using HQoS, the PIR is modified by the HQoS algorithm to give an operational PIR that is equal to or lower than the administrative PIR. As the operational PIR changes, the delay through the queue can also change if the length of the queue is fixed.
  • Page 210 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 egress queue-group <queue-group-name> create queue <queue-id> The operational MBS can be shown using the show pools and show qos scheduler-hierarchy commands. The following example shows the use of dynamic MBS. A queue group template is applied to port 5/1/1 configured with multiple queues using HQoS, one of which has the following parameters: queue-group "qg1"...
  • Page 211: Queue Length As A Delay Value

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Slope : not-applicable The output shows that the operational MBS is now 50% of the administrative MBS and that the queue’s drop tails have changed accordingly. 5.4.3.1 Queue Length as a Delay Value The length of a queue within an egress queue group template can be configured as a target queue delay, in milliseconds, rather than an absolute byte/kbytes value.
  • Page 212: Egress Sap Fc And Fp Overrides

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Admin PIR : 50000 Oper PIR : 50000 Admin CIR Oper CIR Admin MBS : 612 KB Oper MBS : 612 KB High-Plus Drop Tail : 612 KB High Drop Tail : 612 KB Low Drop Tail...
  • Page 213 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The policed traffic by default exits through one of the following methods: • A queue in the policer-output-queues queue group that is automatically created on an access or hybrid port with the queue used that was chosen by the forwarding class definition in that queue group.
  • Page 214: Dot1P Egress Remarking

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 This is supported on all FP2- and higher-based hardware, excluding when a HS- MDA is used. QPPB processing takes precedence over this feature. This could be used, for example, when it is required that egress traffic with a DSCP value EF is to be policed instead of shaped in a queue on a given SAP.
  • Page 215: Dei Egress Remarking

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 CLI Syntax: configure qos sap-egress policy-id create fc fc-name create dot1p {dot1p-value | in-profile dot1p-value out- profile dot1p-value [exceed-profile dot1p-value]} dot1p-inner {dot1p-value | in-profile dot1p-value out-profile dot1p-value} dot1p-outer {dot1p-value | in-profile dot1p-value out-profile dot1p-value [exceed-profile dot1p- value]} exit...
  • Page 216 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Previously, the discard eligibility was determined using existing QoS fields; for example, the three MPLS EXP and Ethernet dot1p bits. Using certain combinations of these bits to indicate both forwarding class (priority) and discard eligibility meant decreasing the number of forwarding classes that can be differentiated in the network.
  • Page 217 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 5.4.6.1.1 DEI in IEEE 802.1ad The IEEE 802.1ad-2005 standard allows drop eligibility to be conveyed separately from priority in-service VLAN TAGs (STAGs). The STAG has a new format where the priority and discard eligibility parameters are conveyed in the 3-bit priority code point (PCP) field and in the DE bit, respectively (see Figure...
  • Page 218 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 5.4.6.1.3 IEEE 802.1ad Use Case Figure 16 shows an example of a topology where the new DE feature may be used: a DE aware, 802.1ad access network connected via a regular SAP to a router PE. In the following example, PE1 can ensure coherent processing of the DE indication between the 802.1ad and the MPLS networks.
  • Page 219 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 2. The SAP on PE1 may use the DE bit from the customer STAG to classify the frames as in/out-of-profile. Color aware policing/metering can generate additional out-of-profile packets as the result of packet flow surpassing the CIR. 3.
  • Page 220: Dscp/Prec Egress Remarking

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 5.4.7 DSCP/Prec Egress Remarking DSCP/prec remarking can be performed on egress for all services and with respect to the profile of the packet. Use the following CLI syntax to remark the DSCP/prec values at a SAP egress: CLI Syntax: configure qos sap-egress policy-id create fc fc-name create...
  • Page 221 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 An override (monitor-depth) is used to enable queue depth monitoring, which is configured under the SAP or queue group queue-overrides. There are show and clear commands, using the queue-depth parameter, for both service SAPs and port queue groups with associated MIB variables.
  • Page 222: Service Management Tasks

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The output shows the percentage of polls for each 10% range of queue depth. The output includes the name of the queue, its MBS configuration, the average elapsed time over which the depth was monitored (this is the elapsed time since the start of monitoring or the last clear), and the weighted average polling interval.
  • Page 223: Applying Service Ingress And Egress Policies

    • VPRN Refer to the Subscriber Services Overview section of the Services Guide for information about configuring service parameters on the 7750 SR and 7450 ESS. 5.5.1.1 Epipe The following output displays an Epipe service configuration with SAP ingress policy 100 and SAP egress 105 applied to the SAP.
  • Page 224: Vpls

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 A:ALA-7>config>service# info ---------------------------------------------- ies 88 customer 8 vpn 88 create interface "Sector A" create sap 1/1/1.2.2 create ingress qos 100 exit egress qos 105 exit exit exit no shutdown exit ---------------------------------------------- 5.5.1.3...
  • Page 225: Editing Qos Policies

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 vprn 1 customer 1 create ecmp 8 autonomous-system 10000 route-distinguisher 10001:1 auto-bind-tunnel resolution-filter resolution-filter ldp vrf-target target:10001:1 interface "to-ce1" create address 11.1.0.1/24 sap 1/1/10:1 create ingress qos 100 exit egress qos 105...
  • Page 226: Deleting Qos Policies

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 description "Used on VPN sap" queue 1 create exit queue 2 multipoint create exit queue 10 create parent "VPN_be" rate 11000 exit sap-ingress 101 create description "Used on VPN sap" queue 1 create exit queue 2 multipoint create...
  • Page 227: Removing A Policy From The Qos Configuration

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 5.5.5 Removing a Policy from the QoS Configuration CLI Syntax: config>qos# no sap-ingress policy-id Example: config>qos# no sap-ingress 100 config>qos# no sap-egress 1010 Issue: 01 3HE 11974 AAAA TQZZA 01...
  • Page 228 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 3HE 11974 AAAA TQZZA 01 Issue: 01...
  • Page 229: Service Ingress And Egress Qos Policy Command Reference

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 5.6 Service Ingress and Egress QoS Policy Command Reference 5.6.1 Command Hierarchies • Service Ingress QoS Policy Commands • Service Egress QoS Policy Commands • Operational Commands • Show Commands 5.6.1.1 Service Ingress QoS Policy Commands...
  • Page 230 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — broadcast-policer policer-id [fp-redirect-group] — no broadcast-policer — broadcast-queue queue-id [group queue-group-name] — no broadcast-queue — [no] de-1-out-profile — egress-fc fc-name — no egress-fc — in-remark {dscp dscp-name | prec ip-prec-value} —...
  • Page 231 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 — type filter-type — no type — [no] ipv6-criteria — entry entry-id [create] — no entry entry-id — action [fc fc-name] [priority {low| high}] [policer policer-id] — no action —...
  • Page 232 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — no inner-tag — outer-tag value [vid-mask] — no outer-tag — snap-oui [zero | non-zero] — no snap-oui — snap-pid snap-pid — no snap-pid — src-mac ieee-address [ieee-address-mask] —...
  • Page 233: Service Egress Qos Policy Commands

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 — size-in-kbytes — no — drop-tail — — percent-reduction-from-mbs percent — no percent-reduction-from-mbs — {size [bytes | kilobytes] | default} — no — packet-byte-offset {add bytes | subtract bytes} —...
  • Page 234 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — stat-mode {no-stats | minimal | offered-profile-no-cir | offered- profile-cir | offered-total-cir | offered-limited-capped-cir | offered-profile-capped-cir | offered-total-cir-exceed} — no stat-mode — [no] ethernet-ctag — fc-name [create] — no fc-name —...
  • Page 235 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 — no wrr-weight — wrr-policy wrr-policy-name — no wrr-policy — [no] ip-criteria — entry entry-id [create] — no entry entry-id — action [hsmda-counter-override counter-id] [fc fc-name] [profile {in | out | exceed | inplus}] [policer policer-id [port-redirect-group-queue queue queue-id | queue queue-id | use-fc-mapped-queue]] —...
  • Page 236 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — no src-ip — src-port {lt | gt | eq} src-port-number — src-port range start end — no src-port — renum old-entry-number new-entry-number — parent-location {default | sla} —...
  • Page 237 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 — avg-frame-overhead percent — no avg-frame-overhead — burst-limit — no burst-limit — size — no — drop-tail — exceed — percent-reduction-from-mbs percent — no percent-reduction-from-mbs — high — percent-reduction-from-mbs percent —...
  • Page 238: Operational Commands

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 5.6.1.3 Operational Commands config — qos — copy sap-egress src-pol dst-pol [overwrite] — copy sap-ingress src-pol dst-pol [overwrite] — copy hsmda-pool-policy src-name dst-name [overwrite] — copy hsmda-scheduler-policy src-name dst-name [overwrite] —...
  • Page 239: Operational Commands

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Description This command creates a text description stored in the configuration file for a configuration context. The no form of this command removes any description string from the context. Default No description is associated with the configuration context.
  • Page 240 Specify the source policy ID that the copy command will attempt to copy from and specify the destination policy ID to which the command will copy a duplicate of the policy. This parameter applies only to the 7450 ESS and 7750 SR. hsmda-slope-policy src-name dst-name — Indicates that the source HSMDA slope policy ID and the destination policy ID are HSMDA slope policy IDs.
  • Page 241 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 1. 802.1p bits 2. DSCP 3. IP quintuple or MAC headers The SAP ingress policy with policy-id 1 is a system-defined policy applied to services when no other policy is explicitly specified. The system SAP ingress policy cannot be modified or deleted.
  • Page 242 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The default forwarding class is best effort (be). The default-fc settings are displayed in the show configuration and save output regardless of inclusion of the detail keyword. Default Parameters fc-name —...
  • Page 243 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 no dot1p dot1p-priority Context config>qos>sap-ingress Description This command explicitly sets the forwarding class or subclass or enqueuing priority when a packet is marked with a dot1p-priority specified. Adding a dot1p rule on the policy forces packets that match the dot1p-priority specified to override the forwarding class and enqueuing priority based on the parameters included in the dot1p rule.
  • Page 244 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 low — This parameter is used in conjunction with the priority parameter. Setting the enqueuing parameter to low for a packet decreases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing.
  • Page 245 Removing the dscp-name from the policy immediately removes the dscp-name on all ingress SAPs using the policy. This is supported on FP2- and higher-based line cards for the 7450 ESS. Parameters dscp-name — The DSCP name is a required parameter that specifies the unique IP header ToS byte DSCP bits value that will match the DSCP rule.
  • Page 246 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 0110 0000 cp25 0110 0100 af31 0110 1000 cp27 0110 1100 af32 0111 0000 cp29 0111 0100 af33 0111 1000 cp31 0111 1100 1000 0000 cp33 1000 0100 af41 1000 1000 cp35...
  • Page 247 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The subclass-name parameter is optional and used with the fc-name parameter to define a preexisting subclass. The fc-name and subclass-name parameters must be separated by a period (dot). If subclass-name does not exist in the context of fc - name, an error will occur.
  • Page 248 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command enables the context in which common properties for dynamic-policers can be configured. Dynamic policers are instantiated and terminated on demand due to an action request submitted by the policy server (for example, via Gx interface). The actions types behind dynamic policers are typically related to rate-limiting or volume monitoring.
  • Page 249 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Parameters fc-name — The parameter subclass-name is optional and must be defined using a dot separated notation with a preceding valid system-wide forwarding class name. Creating a subclass follows normal naming conventions. Up to sixteen ASCII characters may be used.
  • Page 250 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description Within a sap-ingress QoS policy forwarding class context, the broadcast-policer command is used to map packets that match the forwarding class and are considered broadcast in nature to the specified policer-id. The specified policer-id must already exist within the sap- ingress QoS policy.
  • Page 251 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 fp-redirect-group — Redirects a forwarding class to a forwarding plane queue-group as specified in a SAP QoS policy. broadcast-queue Syntax broadcast-queue queue-id [group queue-group-name] no broadcast queue Context config>qos>sap-ingress>fc Description This command overrides the default broadcast forwarding type queue mapping for fc fc-...
  • Page 252 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 When this QoS policy is applied to the ingress of a Frame Relay VLL SAP, the system will treat the received FR frames with DE bit set as out-of-profile, regardless of their previous marking as the result of the default classification or on a match with an IP filter.
  • Page 253 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Parameters fc-name — Specifies the forwarding class name to be used by the egress QoS processing. Values be, l2, af, l1, h2, ef, h1, nc in-remark Syntax in-remark {dscp dscp-name | prec ip-prec-value} no in-remark Context config>qos>sap-ingress>fc...
  • Page 254 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters dscp dscp-name — This parameter is one of two mutually exclusive settings that are applicable to the in-remark command. The in-remark command can be configured to either remark the DiffServ Code Point (DSCP) 6-bit value or the three precedence bits.
  • Page 255 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 If ingress forwarding logic has resolved a packet to the multicast forwarding type within the forwarding class, it will be mapped to either an ingress multipoint queue (using the multicast queue-id or multicast queue-id group ingress-queue-group commands) or an ingress policer (multicast-policer policer-id).
  • Page 256 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Context config>qos>sap-ingress>fc Description This command overrides the default multicast forwarding type queue mapping for fc fc-name. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made.
  • Page 257 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The out-remark command is only applicable to ingress IP routed packets that are considered out-of-profile. The profile of a SAP ingress packet is affected by either the explicit in-profile/ out-of-profile definitions or the ingress policing function applied to the packet.
  • Page 258 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 32 characters, maximum. The name specified by dscp-name is used to refer to the 6-bit value represented by dscp-name. It must be one of the predefined DSCP names defined on the system.
  • Page 259 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 A policer defined within the sap-ingress policy is not actually created on an ingress SAP or a subscriber using an sla-profile where the policy is applied until at least one forwarding type (unicast, broadcast, unknown, or multicast) from one of the forwarding classes is mapped to the policer.
  • Page 260 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 A queue operating in profile-mode may support in-profile, out-of-profile, and non-profiled packets simultaneously. However, the high- and low-priority classification actions are ignored when the queue is in profile-mode. The no form of the command removes an explicit in-profile or out-of-profile configuration on a forwarding class or subclass.
  • Page 261 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 group queue-group-name — This optional parameter is used to redirect the forwarding type within the forwarding class to the specified queue-id within the queue-group- name. When the policy is applied, all packets matching the forwarding class and forwarding type will be redirected to the queue within the specified queue group.
  • Page 262 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of this command is used to restore the mapping of the unknown forwarding type within the forwarding class to the default multipoint queue. If all forwarding class forwarding types had been removed from the default multipoint queue, the queue will not exist on the SAPs or subscriber or multiservice site associated with the QoS policy and the no broadcast- policer command will cause the system to attempt to create the default multipoint queue on...
  • Page 263 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 group queue-group-name — This optional parameter is used to redirect the forwarding type within the forwarding class to the specified queue-id within the queue-group- name. When the policy is applied, all packets matching the forwarding class and forwarding type will be redirected to the queue within the specified queue group.
  • Page 264 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 An entry is not populated in the list unless the action command is executed for the entry. An entry that is not populated in the list has no effect on egress packets. If the action command is executed without any explicit reclassification actions specified, the entry is populated in the list allowing packets matching the entry to exit the list, preventing them from matching entries lower in the list.
  • Page 265 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 When a policer is specified in the action, a matching packet is directed to the configured policer instead of the policer/queue assigned to the forwarding class of the packet. The action command must be executed for the match criteria to be added to the active list of entries.
  • Page 266 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 high — The high parameter is used in conjunction with the priority parameter. Setting the priority enqueuing parameter to high for a packet increases the likelihood to enqueue the packet when the queue is congested. The enqueuing priority only affects ingress SAP queuing.
  • Page 267 Values The following values apply to the 7450 ESS: keywords: none, crtp, crudp, egp, eigrp, encap, ether-ip, gre, icmp, idrp, igmp, igp, ip, ipv6, ipv6-frag, ipv6-icmp, ipv6-no-nxt, ipv6-opts,...
  • Page 268 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 30 IP Protocol Names (Continued) Protocol Protocol ID Description ipv6-opts Destination Options for IPv6 iso-ip ISO Internet Protocol eigrp EIGRP ospf-igp OSPFIGP ether-ip Ethernet-within-IP Encapsulation encap Encapsulation Header pnni PNNI over IP Protocol Independent Multicast...
  • Page 269 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Parameters dscp-name — Specifies a dscp name that has been previously mapped to a value using the dscp-name command. The DiffServ code point can only be specified by its name.
  • Page 270 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 dst-port Syntax dst-port {lt | gt | eq} dst-port-number dst-port range start end no dst-port Context config>qos>sap-ingress>ip-criteria>entry>match config>qos>sap-egress>ip-criteria>entry>match config>qos>sap-ingress>ipv6-criteria>entry>match config>qos>sap-egress>ipv6-criteria>entry>match Description This command configures a destination TCP or UDP port number or port range for a SAP QoS policy match criterion.
  • Page 271 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 false — Configures a match on all non-fragmented IP packets. Non-fragmented IP packets are packets that have the MF bit set to zero and have the Fragment Offset field also set to zero.
  • Page 272 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command configures a source TCP or UDP port number or port range for a SAP QoS policy match criterion. The no form of this command removes the source port match criterion. Default no src-port Parameters...
  • Page 273 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 renum Syntax renum old-entry-number new-entry-number Context config>qos>sap-ingress>ip-criteria config>qos>sap-egress>ip-criteria config>qos>sap-ingress>ipv6-criteria config>qos>sap-egress>ipv6-criteria config>qos>sap-ingress>mac-criteria Description This command renumbers existing QoS policy criteria entries to properly sequence policy entries. This can be required in some cases since the router exits when the first match is found and executes the actions in accordance with the accompanying action command.
  • Page 274 This is supported on FP2- and higher-based line cards and requires mixed-mode for the 7450 ESS. The no form of this command deletes all the entries specified under this node. Once ipv6- criteria entries are removed from a SAP ingress policy, the ipv6-criteria is removed from all services where that policy is applied.
  • Page 275 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 It is possible that a SAP ingress policy includes the dscp map command, the dot1p map command, and an IPv6 match criteria. When multiple matches occur for the traffic, the order of precedence is used to arrive at the final action.
  • Page 276 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 prefix-length — The IPv6 prefix length for the ipv6-address expressed as a decimal integer (applies to the 7750 SR and 7950 XRS). Values 1 to 128 mask — Eight 16-bit hexadecimal pieces representing bit match criteria. Values x:x:x:x:x:x:x (eight 16-bit pieces) fragment...
  • Page 277 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Default no src-ip Parameters ipv6-address — Specifies the IPv6 prefix for the IP match criterion in hex digits. Values ipv6-address: x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x: [0 to FFFF]H d: [0 to 255]D prefix —...
  • Page 278 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 A maximum of eight lsp-exp rules are allowed on a single policy. Values 0 to 7 fc fc-name — The value given for the fc-name parameter must be one of the predefined forwarding classes in the system.
  • Page 279 1 and 8. To remove the HSMDA exception counter reclassification action for the specified lsp-exp-value, the lsp-exp command must be re-executed without the hsmda-counter-override reclassification action defined. This parameter only applies to the 7450 ESS and 7750 SR. Values 1 to 8...
  • Page 280 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters frame-type keyword — The frame-type keyword configures an Ethernet frame type or an ATM frame type to be used for the MAC filter match criteria. Values 802dot3, 802dot2-llc, 802dot2-snap, ethernet_II, atm Default 802dot3 802dot3 —...
  • Page 281 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Parameters vci-value — The value of the VCI field in the received ATM cell header. Values 1, 2, 5 to 65535 dot1p Syntax dot1p dot1p-value [dot1p-mask] no dot1p Context config>qos>sap-ingress>mac-criteria>entry>match Description...
  • Page 282 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Use the no form of this command to remove the dsap value as the match criterion. Default no dsap Parameters dsap-value — The 8-bit dsap match criteria value in hexadecimal. Values 0x00 to 0xFF (hex) dsap-mask —...
  • Page 283 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 All packets with a source MAC OUI value of 00-03-FA, subject to a match condition, should be specified as: 0003FA000000 0x0FFFFF000000 Values 0x00000000000000 to 0xFFFFFFFFFFFF (hex) Default 0xFFFFFFFFFFFF (hex) (exact match) etype Syntax etype etype-value...
  • Page 284 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command configures the matching of the second tag that is carried transparently through the service. The inner tag on ingress is the second tag on the frame if there are no service delimiting tags.
  • Page 285 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The default vid-mask is set to 4095 for exact match. snap-oui Syntax snap-oui [zero | non-zero] no snap-oui Context config>qos>sap-ingress>mac-criteria>entry>match Description Configures an IEEE 802.3 LLC SNAP Ethernet frame OUI zero or non-zero value to be used as a service ingress QoS policy match criterion.
  • Page 286 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 src-mac Syntax src-mac ieee-address [ieee-address-mask] no src-mac Context config>qos>sap-ingress>mac-criteria>entry>match Description This command configures a source MAC address or range to be used as a service ingress QoS policy match criterion. The no form of this command removes the source mac as the match criteria.
  • Page 287 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Default no ssap Parameters ssap-value — The 8-bit ssap match criteria value in hex. Values 0x00 to 0xFF (hex) ssap-mask — This is optional and can be used when specifying a range of ssap values to use as the match criteria.
  • Page 288 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command is used in the sap-ingress and sap-egress QoS policies to create, modify, or delete a policer. Policers are created and used in a similar manner to queues. The policer ID space is separate from the queue ID space, allowing both a queue and a policer to share the same ID.
  • Page 289 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 no adaptation-rule Context config>qos>sap-ingress>policer config>qos>sap-egress>policer Description This command is used to define how the policer’s configuration parameters are translated into the underlying hardware capabilities used to implement each policer instance. For instance, the configured rates for the policer need to be mapped to the timers and decrement granularity used by the hardware's leaky bucket functions that actually perform the traffic metering.
  • Page 290 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 max — The max keyword is used to inform the system that the profiling rate defined for the policer is the maximum allowed rate. The system will choose a hardware supported rate that is closest but not exceeding the specified rate.
  • Page 291 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Context config>qos>sap-ingress>dyn-policer config>qos>sap-egress>dyn-policer config>qos>sap-ingress>policer config>qos>sap-egress>policer Description This command is used to configure the policer’s CIR leaky bucket’s exceed threshold. The CIR bucket’s exceed threshold represents the committed burst tolerance allowed by the policer.
  • Page 292 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters percent-of-mbs — The percent-of-mbs parameter is required when specifying high-prio- only and is expressed as a percentage. Values 0 to 100 Default Syntax mbs {size [bytes | kilobytes] | default} no mbs Context config>qos>sap-ingress>dyn-policer...
  • Page 293 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 kilobytes — When kilobytes is defined, the value is interpreted as the queue’s MBS value given in kilobytes. Values 0 – 16777216 or default Default kilobytes packet-byte-offset Syntax packet-byte-offset {add bytes | subtract bytes} no packet-byte-offset Context...
  • Page 294 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 subtract bytes — The subtract keyword is mutually exclusive to the add keyword. Either add or subtract must be specified. When subtract is defined, the corresponding bytes parameter specifies the number of bytes that is subtracted from the size of each packet associated with the policer for rate metering, profiling, and accounting purposes.
  • Page 295 QoS policy. The combining of the sub-profile and the sla-profile at the subscriber level provides the system with the proper information to create the policer control hierarchy instance for the subscriber. This functionality is available only for the 7450 ESS and 7750 SR.
  • Page 296 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Context config>qos>sap-egress>policer config>qos>sap-ingress>policer Description The percent-rate command within the SAP ingress and egress QoS policies enables supports for a policer’s PIR and CIR rate to be configured as a percentage of the immediate parent root policer/arbiter rate or the FP capacity.
  • Page 297 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 • At egress, soft-in-profile packets (packets received from ingress as in-profile) are treated the same as explicit in-profile (unless explicitly reclassified as out-of-profile) and have an initial policer state of in-profile. •...
  • Page 298 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of this command is used to restore the default metering and profiling rate to a policer. Parameters {max | pir-rate} — Specifying the keyword max or an explicit pir-rate parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket.
  • Page 299 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 While a no-stats mode is supported that prevents any packet accounting, the use of the policer’s parent command requires that the policer's stat-mode be set at least to the minimal setting so that offered stats are available for the policer's Fair Information Rate (FIR) to be calculated.
  • Page 300 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 31 Ingress Policer Stat Mode Summary (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-priority-cir High/low entering In/out exiting policer Intended for when policer packet priority entering the policer...
  • Page 301 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The no form of this command attempts to return the policer’s stat-mode setting to minimal. The command will fail if insufficient policer counter resources exist to implement minimal where the QoS policer is currently applied and has a forwarding class mapping.
  • Page 302 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters. The offered-profile-no-cir mode is most useful when the policer is receiving only in- profile and out-of-profile premarked (and trusted) packets.
  • Page 303 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The offered-priority-no-cir mode is most useful when the policer is receiving only untrusted packets and the ingress priority high and priority low classification options are being used without a CIR profiling rate defined. This mode does not prevent the policer from receiving trusted packets that are premarked in-profile or out-of-profile nor does it prevent the policer from being configured with a CIR rate.
  • Page 304 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The offered-profile-cir mode is most useful when the policer is receiving trusted out- of-profile and in-profile traffic and is also receiving untrusted packets that are being applied to a defined CIR profiling rate. This mode differs from offered-limited- profile-cir mode in that it expects both trusted in-profile and out-of-profile packets while still performing CIR profiling on packets with untrusted markings.
  • Page 305 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the priority of traffic entering the policer and the profile exiting the policer. The offered-priority-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters.
  • Page 306 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer. All offered traffic is provided in a single counter. The offered-total-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
  • Page 307 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises of hard out and uncolored.
  • Page 308 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 offered-profile-cir — Counter resource allocation: 4 offered-profile-capped-cir — Counter resource allocation: 5 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer when ingress reclassification is performed so that the traffic entering the policer comprises of hard in/out and uncolored.
  • Page 309 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 39 Ingress Accounting Statistics Collected in offered-profile- capped-cir stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description For. OutProf OutOfProfilePacketsForwarded OutOfProfileOctetsForwarded offered-limited-capped-cir — Counter resource allocation: 4 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer when ingress reclassification is performed resulting in the...
  • Page 310 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 40 Ingress Accounting Statistics Collected in offered-limited- capped-cir stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description Off. Uncolor UncoloredPacketsOffered UncoloredOctetsOffered Dro. InProf InProfilePacketsDropped InProfileOctetsDropped Dro. OutProf OutOfProfilePacketsDropped OutOfProfileOctetsDropped For.
  • Page 311 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Context config>qos>sap-ingress Description This command explicitly sets the forwarding class or enqueuing priority when a packet is marked with an IP precedence value (ip-prec-value). Adding an IP precedence rule on the policy forces packets that match the specified ip-prec-value to override the forwarding class and enqueuing priority based on the parameters included in the IP precedence rule.
  • Page 312 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 fc fc-name — The value given for the fc-name parameter must be one of the predefined forwarding classes in the system. Specifying the fc-name is optional. When a packet matches the rule, the forwarding class is only overridden when the fc fc-name parameter is defined on the rule.
  • Page 313 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 no queue queue-id Context config>qos>sap-ingress Description This command creates the context to configure an ingress SAP QoS policy queue. Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue allows support for multiple forwarding classes.
  • Page 314 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters queue-id — The queue-id for the queue, expressed as an integer. The queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.
  • Page 315 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 priority-mode: The queue is capable of handling traffic differently with two distinct priorities. These priorities are assigned by the stages preceding the queueing framework in the system. In priority mode, the queue does not have the functionality to support the profiled traffic and in such cases the queue will have a degraded performance.
  • Page 316 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 max — The max keyword is used to inform the system that the profiling rate defined for the policer is the maximum allowed rate. The system will choose a hardware supported rate that is closest but not exceeding the specified rate.
  • Page 317 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 kilobytes — The kilobyte qualifier is used to specify that the value given for size must be interpreted as the burst limit in Kilobytes. The kilobyte qualifier is optional and mutually exclusive with the bytes qualifier.
  • Page 318 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 drop-tail Syntax drop-tail Context config>qos>sap-egress>queue config>qos>sap-ingress>queue Description This command enters the context to configure queue drop tail parameters. exceed Syntax exceed Context config>qos>sap-egress>queue>drop-tail Description This command enters the context to configure the queue exceed drop tail parameters. The exceed drop tail defines the queue depth beyond which exceed-profile packets will not be accepted into the queue and will be discarded.
  • Page 319 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Description This command enters the context to configure the queue low drop-tail parameters. The low drop tail defines the queue depth beyond which out-of-profile packets will not be accepted into the queue and will be discarded.
  • Page 320 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command configures the ingress SAP low drop tail as a percentage reduction from the MBS of the queue. For example, if a queue has an MBS of 600 kbytes and this percentage is configured to be 30% for the low drop tail, then the low drop tail will be at 420 kbytes and out-of-profile packets will not be accepted into the queue if its depth is greater than this value and will be discarded.
  • Page 321 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Parameters size [bytes | kilobytes] — The size parameter is the maximum number of bytes or kilobytes of buffering allowed for the queue. The default unit is kilobytes; to configure the MBS in bytes, specify the bytes parameter.
  • Page 322 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Context config>qos>sap-ingress>queue config>qos>sap-egress>queue Description This command defines an optional parent scheduler that further governs the available bandwidth given the queue aside from the queue’s PIR setting. When multiple schedulers, policers (at egress only), and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent’s bandwidth.
  • Page 323 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 weight weight — weight defines the relative weight of this queue in comparison to other child schedulers, policers, and queues, while vying for bandwidth on the parent scheduler-name. Any queues, policers, or schedulers defined as weighted receive no parental bandwidth until all policers, queues, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
  • Page 324 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 cir-level cir-level — Defines the port priority that the queue or scheduler will use to receive bandwidth for its within-cir offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir-level parameter is ignored.
  • Page 325 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The no form of this command returns the queue to its default shaping rate and CIR rate. When no percent-rate is defined within a SAP ingress or egress queue-override, the queue uses the defined shaping and CIR rates within the SAP ingress and egress QoS policy associated with the queue.
  • Page 326 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of this command is used to remove a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool. Default no pool Parameters...
  • Page 327 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned. Values [1 to 200000000 | max] kbps Default cir-rate —...
  • Page 328 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 sub-insert-shared-pccrule Syntax sub-insert-shared-pccrule start-entry entry-id count count no sub-insert-shared-pccrule Context config>qos>sap-egress config>qos>sap-ingress Description This command defines the range of filter and QoS policy entries that are reserved for shared entries received in Flow-Information AVP via Gx interface (PCC rules –...
  • Page 329 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The sap-egress policy with policy-id 1 is the default sap-egress QoS policy and is applied to service egress SAPs when an explicit policy is not specified or removed. The default sap- egress policy cannot be modified or deleted.
  • Page 330 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The reclassification actions from a dot1p reclassification rule may be overridden by a DSCP, prec, or IP flow matching event. The fc keyword is optional. When specified, the egress classification rule will overwrite the forwarding class derived from ingress.
  • Page 331 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 inplus — Specifies that any packets matching the reclassification rule will be treated as inplus-profile by the egress forwarding plane. dscp Syntax dscp dscp-name [dscp-name...(up to 8 max)] [fc fc-name] [hsmda-counter-override counter-id] [profile {in | out | exceed | inplus}] no dscp dscp-name [dscp-name...(up to 8 max)] Context...
  • Page 332 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The profile keyword is optional. When specified, the egress classification rule will overwrite the profile of the packet derived from ingress. The new profile value is used for egress remarking and queue congestion behavior.
  • Page 333 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 af12 0011 0000 cp13 0011 0100 af13 0011 1000 cp15 0011 1100 0100 0000 cp17 0100 0100 af21 0100 1000 cp19 0100 1100 af22 0101 0000 cp21 0101 0100 af23 0101 1000 cp23...
  • Page 334 To remove the HSMDA exception counter reclassification action for the specified DSCP value, the dscp command must be re-executed without the hsmda-counter-override reclassification parameter defined. This parameter applies only to the 7450 ESS and 7750 SR. Values 1 to 8...
  • Page 335 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Description This command specifies that the top customer tag should be used for egress reclassification based on dot1p criteria. This command applies to all dot1p criteria configured in a given SAP egress QoS policy.
  • Page 336 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 In the PBB case, for a Backbone SAP (B-SAP) and for packets originated from a local I-VPLS/ PBB-Epipe, the command dictates the marking of the DE bit for both the BVID and ITAG. If this command is not used, the DE bit should be preserved if an ingress TAG exist;...
  • Page 337 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Parameters de-value — Specifies the DE marking value. Values 0 or 1 de-mark-outer Syntax de-mark-outer [force de-value] no de-mark-outer Context config>qos>sap-egress>fc Description This command is used to explicitly define the marking of the DE bit in the outer or single VLAN tag on a qinq or dot1q SAP, respectively, according to the in, out, or exceed-profile status of the packet.
  • Page 338 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The optional in-profile dot1p-value out-profile dot1p-value [exceed-profile dot1p-value] parameters added to the existing dot1p command adds the capability to mark on an egress SAP the in, out, and exceed-profile status via a certain dot1p combination, similarly with the DE options.
  • Page 339 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 dot1p-inner Syntax dot1p-inner {dot1p-value | in-profile dot1p-value out-profile dot1p-value} no dot1p-inner Context config>qos>sap-egress>fc Description This command explicitly defines the egress inner VLAN tag IEEE 802.1p (dot1p) bits marking for fc-name.
  • Page 340 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 in-profile dot1p-value — Specifies the 802.1p value to set for in-profile frames in this forwarding class. Values 0 to 7 out-profile dot1p-value — Specifies the 802.1p value to set for out-of-profile frames in this forwarding class.
  • Page 341 All inplus- profile traffic is marked with the same value as in-profile traffic. This is supported on FP2- and higher-based line cards for the 7450 ESS. Default...
  • Page 342 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 exceed-profile dscp-name — This optional parameter specifies the DSCP name to be used to remark the traffic that is exceed-profile. If not specified, this defaults to the same value configured for out-profile parameter. in-profile dscp-name —...
  • Page 343 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 41 Default FC HSMDA Queue ID Mappings Forwarding Class Default HSMDA Queue ID queue 8 queue 7 queue 6 queue 5 queue 4 queue 3 queue 2 queue 1 Table 42 presents the way that packets are mapped to queues based on the type of service...
  • Page 344 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 1 to 8 BE Default: L2 Default: AF Default: L1 Default: H2 Default: EF Default: H1 Default: NC Default: port-redirect-group-queue — This parameter is used to mark a given forwarding class queue for redirection to an egress port queue group.
  • Page 345 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Packets that are mapped to an egress policer that are not discarded by the policer must be placed into a default queue on the packets destination port. The system uses egress port queue groups for this purpose.
  • Page 346 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 If an egress policed packet is discarded by the egress port queue group queue, the source policer discard stats are incremented. This means that the discard counters for the policer represent both the policer discard events and the destination queue drop tail events associated with the policer.
  • Page 347 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 queue group-queue-id — The queue group-queue-id is optional when the group queue- group-name parameter is specified and is used to override the forwarding class mapping within the group's egress queue group template. The specified group- queue-id must exist within the group's egress queue group template or the policer command will fail.
  • Page 348 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 queue Syntax queue queue-id [{group queue-group-name [instance instance-id] | port-redirect-group- queue}] no queue Context config>qos>sap-egress>fc Description This command overrides the default queue mapping for fc fc-name. The specified queue-id must exist within the policy before the mapping can be made.
  • Page 349 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Description This command enters the context to configure queue definitions for use on SAPs or subscribers on HSMDAs. A single QoS policy simultaneously defines queues for both standard MDA and for HSMDA subscribers and SAPs. This allows the policy association decision to be unaware of the type of hardware that the SAP or subscriber is traversing.
  • Page 350 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The secondary shaper leaky bucket, scheduler priority level leaky bucket, and the port maximum rate updates are not affected by the configured packet-byte-offset. Each of these accounting functions are frame-based and always include the preamble, DLC header, payload, and the CRC regardless of the configured byte offset.
  • Page 351 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 no queue queue-id Context config>qos>sap-egress>hsmda-queues Description This command, within the QoS policy HSMDA-queues context, is a container for the configuration parameters controlling the behavior of an HSMDA queue. Unlike the standard QoS policy queue command, this command is not used to actually create or dynamically assign the queue to the object to which the policy is applied.
  • Page 352 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Redirection to an egress port queue group specified for the HSMDA is possible using the port-redirect-group parameter. If this is specified, packets are redirected to the queue-id in the HSMDA queue group instance named at the time the egress QoS policy is applied to the SAP.
  • Page 353 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Syntax mbs {size [bytes | kilobytes] | default} no mbs Context config>qos>sap-egress>hsmda-queues>queue Description This command configures the maximum number of buffers allowed for a specific queue. The value is given in bytes or kilobytes and overrides the default value for the context. The no form of this command returns the policer to its default MBS.
  • Page 354 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Egress Profiling-Based Dot1p Remarking HSMDA egress queues are capable of remarking dot1p and DEI bits based on the current state of the queues CIR. Egress dot1p remarking is enabled at the forwarding class level. Using egress profiling-based dot1p remarking, either two distinct dot1p values may be used to distinguish in-profile and out-of-profile, or just the DEI bit may be toggled.
  • Page 355 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 • Out-of-Profile — Low Slope (priority ignored) • Profile-Undefined, Low Priority — Low Slope Egress Slope Mapping • In-Profile from ingress — High Slope • Out-of-Profile from ingress — Low Slope The specified policy contains a value that defines the queue’s MBS value (queue-mbs).
  • Page 356 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of the command restores the association between the queue and the HSMDA default slope policy. The command has no immediate effect for queues that have a local override defined for the slope policy.
  • Page 357 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 config>qos>sap-egress>ipv6-criteria>entry Description This command defines the reclassification actions that should be performed on any packet matching the defined IP flow criteria within the entries match node. When defined under the ip-criteria context, the reclassification only applies to IPv4 packets.
  • Page 358 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The policer keyword is optional. When specified, the egress packet will be redirected to the configured policer. Optional parameters allow the user to control how the forwarded policed traffic exits the egress port.
  • Page 359 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 exceed — The exceed parameter is mutually exclusive to the out, inplus, and in parameters following the profile reclassification action keyword. In, exceed, inplus, or out must be specified when the profile keyword is present. When exceed is specified, any packets matching the reclassification rule will be treated as exceed- profile by the egress forwarding plane.
  • Page 360 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 no parent-location Context config>qos>sap-egress Description This command determines the expected location of the parent schedulers for queues configured with a parent command within the sap-egress policy. All parent schedulers must be configured within a scheduler-policy applied at the location corresponding to the parent- location parameter.
  • Page 361 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Context config>qos>sap-egress>policer cfg>qos>qgrps>egr>qgrp Description This command enables the forwarding of packets with an exceed-profile state and traffic exceeding the PIR for a SAP egress or a network egress queue group (configured in the egress queue group template) policer.
  • Page 362 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of this command removes a port scheduler parent association for the policer. Once removed, if a port scheduler is defined on the port on which the policer instance exists, the policer will be treated as orphaned to the port scheduler.
  • Page 363 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 profile-out-preserve Syntax [no] profile-out-preserve Context config>qos>sap-egress>policer Description This command specifies whether to preserve the color of offered out-of-profile traffic at sap- egress policer (profile of the packet can change based on egress CIR state). When enabled, traffic determined as out-of-profile at ingress policer will be treated as out-of- profile at sap-egress policer.
  • Page 364 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The no form of the command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and no error message is returned.
  • Page 365 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 cir-weight cir-weight — Defines the relative weight of this policer in comparison with other child policers, queues, or schedulers competing for bandwidth on the parent scheduler-name at the within-cir priority level defined by the cir-level parameter. All cir-weight values from all weighted active policers, queues, and schedulers with a common parent are added together.
  • Page 366 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 While a no-stats mode is supported that prevents any packet accounting, the use of the policer's parent command requires that the policer’s stat-mode be set at least to the minimal setting so that offered stats are available for the policer’s Fair Information Rate (FIR) to be calculated.
  • Page 367 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 43 Egress Policer Stat-mode Summary (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-limited- In or out entering In/out exiting policer Intended for when capped-cir policer the policer has...
  • Page 368 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 43 Egress Policer Stat-mode Summary (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-total-cir- Single counter Inplus, in, out, or Intended to be used four-profile entering policer exceed exiting...
  • Page 369 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 44 Egress Accounting Statistics Collected in minimal stat-mode Show Output Accounting Stats Collected Field Field Description Off. All AllPacketsOffered AllOctetsOffered Dro. All AllPacketsDropped AllOctetsDropped For. All AllPacketsForwarded AllOctetsForwarded offered-profile-no-cir —...
  • Page 370 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 45 Egress Accounting Statistics Collected in offered-profile-no-cir stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description Dro. InProf InProfilePacketsDropped InProfileOctetsDropped Dro. OutProf OutOfProfilePacketsDropped OutOfProfileOctetsDropped For. InProf InProfilePacketsForwarded InProfileOctetsForwarded For.
  • Page 371 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 46 Egress Accounting Statistics Collected in offered-profile-cir stat-mode Show Output Accounting Stats Collected Field Field Description Off. InProf InProfilePacketsOffered InProfileOctetsOffered Off. OutProf OutOfProfilePacketsOffered OutOfProfileOctetsOffered Off. Uncolor UncoloredPacketsOffered UncoloredOctetsOffered Dro.
  • Page 372 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Table Table 47 Egress Accounting Statistics Collected in offered-total-cir stat-...
  • Page 373 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The impact of using offered-limited-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in instead of offered-undefined.
  • Page 374 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 traffic reclassified to in-profile (which includes traffic reclassified to inplus-profile), traffic reclassified to out-of-profile (which includes traffic reclassified to exceed- profile) and traffic that has not been reclassified at egress (uncolored). In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter and exceed-profile traffic is counted with the out-of-profile counter.
  • Page 375 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 49 Egress Accounting Statistics Collected in offered-profile- capped-cir stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description For. InProf InProfilePacketsForwarded InProfileOctetsForwarded For. OutProf OutOfProfilePacketsForwarded OutOfProfileOctetsForwarded offered-total-cir-exceed — Counter resource allocation: 3 This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer.
  • Page 376 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 50 Egress Accounting Statistics Collected in offered-total-cir- exceed stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description Dro. OutProf OutOfProfilePacketsDropped OutOfProfileOctetsDropped Dro. ExcProf ExceedProfilePktsDropped ExceedProfileOctetsDropped For. InProf InProfilePacketsForwarded InProfileOctetsForwarded For.
  • Page 377 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 51 Egress Accounting Statistics Collected in offered-four-profile- no-cir stat-mode Show Output Accounting Stats Collected Field Field Description Off. InProf InProfilePacketsOffered InProfileOctetsOffered Off. OutProf OutOfProfilePacketsOffered OutOfProfileOctetsOffered Off. ExcProf ExceedProfilePacketsOffered ExceedProfileOctetsOffered Off.
  • Page 378 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer. All offered traffic is provided in a single counter. There is a separate dropped and forwarded counter for inplus, in, out and exceed-profile traffic.
  • Page 379 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 52 Egress Accounting Statistics Collected in offered-total-cir-four- profile stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description For. ExcProf ExceedProfilePktsForwarded ExceedProfileOctetsForwarded For. InplusProf InplusProfilePktsForwarded InplusProfileOctetsForwarded policers-hqos-manageable Syntax [no] policers-hqos-manageable Context...
  • Page 380 The default behavior for HSMDA queue accounting is to use the counters associated with the queue to which the packet is mapped (applies to the 7450 ESS and 7750 SR). The IP precedence bits used to match against precedence reclassification rules come from the Type of Service (ToS) field within the IPv4 header.
  • Page 381 If the higher priority match actions do not specify a new profile, the profile from the IP precedence match will be used. The hsmda-counter-override keyword applies to the 7450 ESS and 7750 SR and is optional. When specified and the egress SAP is created on an HSMDA, the egress classification rule will override the default queue accounting function for the packet.
  • Page 382 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 exceed — Specifies that any packets matching the reclassification rule will be treated as exceed-profile by the egress forwarding plane. inplus — Specifies that any packets matching the reclassification rule will be treated as inplus-profile by the egress forwarding plane.
  • Page 383 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 queue-type — The expedite, best-effort, and auto-expedite queue types are mutually exclusive to each other. Each defines the method that the system uses to service the queue from a hardware perspective. A keyword can be specified at the time the queue is created.
  • Page 384 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 For egress Ethernet queues, the frame-encapsulation overhead is calculated by multiplying the number of offered-packets for the queue by 20 bytes. If a queue was offered 50 packets then the frame-encapsulation overhead would be 50 x 20 or 1,000 octets.
  • Page 385 — This parameter sets the average amount of packet-to-frame encapsulation overhead expected for the queue. This value is not used by the system for egress Ethernet queues. This parameter only applies to the 7450 ESS and 7750 SR. Values 0.00 to 100.00...
  • Page 386 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 packet-byte-offset Syntax packet-byte-offset {add bytes | subtract bytes} no packet-byte-offset Context config>qos>sap-egress>queue Description This command is used to modify the size of each packet handled by the queue by adding or subtracting a number of bytes.
  • Page 387 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 port-parent Syntax port-parent [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level] no port-parent Context config>qos>sap-egress>queue Description This command specifies whether this queue feeds off a port-level scheduler. When configured, this SAP egress queue is parented by a port-level scheduler.
  • Page 388 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 level level — Defines the port priority the queue or scheduler will use to receive bandwidth for its above-cir offered-load. Values 1 to 8 (8 is the highest priority) Default cir-weight cir-weight —...
  • Page 389 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 The rate command can be executed at anytime, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id. The no form of the command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).
  • Page 390 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 When the wred-queue mode native command is configured, the queue uses the WRED capabilities of the FP3. In this case, the out-of-profile and exceed-profile traffic map to the low and exceed WRED slopes specified within the slope policy, and the inplus-profile and in- profile traffic uses the MBS drop tail;...
  • Page 391 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 As packets attempt to enter the egress queue, they are associated with the highplus, high, low, or exceed WRED slope based on the packet’s profile. If the packet is inplus-profile, the highplus slope is used.
  • Page 392 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 scope Syntax scope {exclusive | template} no scope Context config>qos>sap-egress Description Enter the scope of this policy. The scope of the policy cannot be changed if the policy is applied to one or more services.
  • Page 393: Show Commands

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Parameters ip-prefix-list-name — A string of up to 32 characters of printable ASCII characters. If the string contains special characters (#, $, spaces, etc), the entire string must be enclosed within double quotes.
  • Page 394 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters policy-id — Displays information about the specific policy ID. Values 1 to 65535 Default all SAP ingress policies detail — Displays detailed policy information including policy associations. Output The following output is an example of QoS SAP ingress information, and Table 53...
  • Page 395 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Entry : 40000 Description : Auto-created entry for pcc-rule RULE_ingress_FC Source IP : Undefined Dest. IP : 75.24.24.3/32 Source Port : None Dest. Port : None Protocol : tcp DSCP : cp60 Fragment...
  • Page 396 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Prio None closest closest def Prio None closest closest def Prio 11000 VPN_be closest closest def Prio None closest closest def Prio 11000 VPN_prio* closest closest def Prio VPN_rese* closest closest def...
  • Page 397 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Prec Value Priority ------------------------------------------------------------------------------- Default Default Default Default Default Default ------------------------------------------------------------------------------- Match Criteria ------------------------------------------------------------------------------- IP Match Criteria ------------------------------------------------------------------------------- Entry : 10 Description : Entry 10-FC-AF Source IP : 10.10.10.104/24 Source Port : None Dest.
  • Page 398 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 UCastQ MCastQ BCastQ UnknownQ ------------------------------------------------------------------------ ------------------------------------------------------------------------ SubFC DE-1-out-profile Profile In-Remark Out-Remark ------------------------------------------------------------------------ None None None None None None ------------------------------------------------------------------------ dot1p Priority ------------------------------------------------------------------------ No Dot1p-Map Entries Found. ------------------------------------------------------------------------ DSCP Priority ------------------------------------------------------------------------ No DSCP-Map Entries Found.
  • Page 399 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 53 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) Template Implies that this policy can be applied to multiple SAPs on the router. Description A text string that helps identify the policy’s context in the configuration file.
  • Page 400 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 53 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) PIR Admin Specifies the administrative Peak Information Rate (PIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the switch fabric (for SAP ingress queues) or out an egress interface (for SAP egress queues).
  • Page 401 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 53 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) CIR Lvl/Wt Specifies the level of hierarchy when compared to other schedulers and queue when vying for bandwidth on the parent scheduler.
  • Page 402 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 53 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) Specifies that the low enqueuing parameter for a packet decreases the likelihood of enqueuing the packet when the ingress queue is congested.
  • Page 403 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 53 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) Dot1p Specifies a IEEE 802.1p value to be used as the match. Snap-pid Specifies an IEEE 802.3 LLC SNAP Ethernet Frame PID value to be used as a Service Ingress QoS policy match.
  • Page 404 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Sample Output A:ALA-49# show qos sap-egress =============================================================================== Sap Egress Policies =============================================================================== Policy-Id Scope Description ------------------------------------------------------------------------------- Template Default SAP egress QoS policy. 1010 Template 1020 Template =============================================================================== A:ALA-49# A:ALA-49# show qos sap-egress 1010 =============================================================================== QoS Sap Egress ===============================================================================...
  • Page 405 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 =============================================================================== A:ALA-49# config>qos# show qos sap-egress 2 detail ======================================================================== QoS Sap Egress ------------------------------------------------------------------------ Sap Scheduler Policy (2) ------------------------------------------------------------------------ Policy-id Scope : Template ------------------------------------------------------------------------ Queue CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent AvgOvrhd...
  • Page 406 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 ip-criteria entry 10 create match dst-ip ip-prefix-list "ip-prefix-list-1" exit action fc "af" exit exit exit exit The IPv4 prefix list can be shown as follows: *A:PE# show qos match-list ip-prefix-list "ip-prefix-list-1" =============================================================================== QoS Match IP Prefix List ===============================================================================...
  • Page 407 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 54 Show QoS SAP Egress Output Fields (Continued) Label Description (Continued) CIR Admin Specifies the administrative Committed Information Rate (CIR) parameters for the queue. The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth.
  • Page 408 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 54 Show QoS SAP Egress Output Fields (Continued) Label Description (Continued) Specifies that the CBS value reserved for the queue. value Specifies the value to override the default reserved buffers for the queue.
  • Page 409 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Table 54 Show QoS SAP Egress Output Fields (Continued) Label Description (Continued) Service-Id The unique service ID number that identifies the service in the service domain. Customer-Id Specifies the customer ID that identifies the customer to the service.
  • Page 410 If the specified subscriber-id does not exist, the system should return ‘The specified subscriber does not exist’. This parameter applies to the 7450 ESS and 7750 SR only. network {mda-id | port-id} — The network keyword is used to specify that the system should find and display the queue information for the queues associated with the specified mda-id or port-id.
  • Page 411 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.0.R1 Syntax bcg burst-control-group-name [member-queues [at-risk-only]] [exp-util-bw megabits-per- second] Context show>qos Description The show qos bcg command outputs the current and historical visitation time associated with the specified BCG name. A Burst Control Group (BCG) represents a list of queues that share the same non-scheduling PIR and CIR bucket target update interval.
  • Page 412 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The show qos bcg command allows visibility into a BCG’s historic and current visitation time. The system samples the amount of time it takes each list to visit each of its associated queues once each second and stores the last 10 samples.
  • Page 413: Queue Sharing And Redirection

    6.1.1 Supported Platforms Queue sharing and redirection is supported on the 7950 XRS, 7750 SR, and 7450 ESS platforms as follows: • Access SAP port and network port queue groups • Ingress access and network forwarding plane queue groups except on the...
  • Page 414: Queue Group Applications

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.2 Queue Group Applications 6.2.1 Access SAP Queue Group Applications Normally, each SAP (Service Access Point) has dedicated ingress and egress queues that are only used by that particular SAP. The SAP queues are created based on the queue definitions within the SAP ingress and SAP egress QoS policy applied to the SAP.
  • Page 415: Ingress Per Sap Statistics With Ingress Queue Groups

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 The above scenarios can be supported with access queue groups. A single ingress queue group is supported per access port, while multiple ingress queue group instances are supported per IOM/IMM/XMA forwarding plane. To provide more flexibility on the egress side of the access port, multiple egress access queue group queue-group instances are supported per egress access port.
  • Page 416: Ingress Access Port Queue Group Hardware Queue Allocation

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Last Cleared Time : 04/04/2014 11:51:12 Packets Octets CPM Ingress Forwarding Engine Stats Dropped Received Valid Off. HiPrio Off. LowPrio Off. Uncolor Off. Managed Queueing Stats(Ingress QoS Policy 100) Dro. HiPrio Dro.
  • Page 417: Network Port Queue Groups For Ip Interfaces

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 The allocation of ingress access port queue group hardware queues has been optimized for the 7950 XRS-20 systems to avoid allocating ingress hardware queues to XCMs in slots 11 and above. When the first XCM in slot 11 or above is provisioned, additional ingress hardware queues will be allocated to XCMs in slots 11 to 20 for any configured ingress access port queue group queue.
  • Page 418 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Operationally, the provisioning model in the case of the ingress PW shaping feature consists of the following steps: 1. Create an ingress queue-group template and configure policers for each FC that needs to be redirected and optionally, for each traffic type (unicast, broadcast, unknown, or multicast).
  • Page 419: Qos On Ingress Bindings

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.2.4 QoS on Ingress Bindings Traffic is tunneled between VPRN service instances on different PEs over service tunnels bound to MPLS LSPs or GRE tunnels. The binding of the service tunnels to the underlying transport is achieved either automatically (using the auto-bind- tunnel command) or statically (using the spoke-sdp command;...
  • Page 420: Vxlan Vni Queue Group Redirection

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 configure vprn network ingress qos <network-policy-id> fp-redirect-group <queue-group-name> instance <instance-id> When this command is configured, it overrides the QoS applied to the related network interfaces for unicast traffic arriving on bindings in that VPRN. The IP and IPv6 criteria statements are not supported in the applied network QoS policy This is supported for all available transport tunnel types and is independent of the label mode (vrf or next-hop) used within the VPRN.
  • Page 421: Queue Group Redirect List

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.2.5.1 Queue Group Redirect List A queue group redirection list allows packets that match a configured type value to be redirected to a specific queue group instance at SAP ingress or egress. The queue group instance must be an instance of the default queue group, which is the queue group configured under the SAP with the QoS policy.
  • Page 422 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 interface ip-int-name sap sap-id ingress qos policy-id fp-redirect-group queue-group-name instance instance-id queue-group-redirect-list redirect-list-name egress qos policy-id port-redirect- group queue-group-name instance instance-id queue-group-redirect-list redirect-list-name In order for packets to be redirected to the policer or queue in the queue group instance specified in a queue group redirect list, the following criteria must be met: •...
  • Page 423 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Sap IngQGrp RedirLst Entries | 31999 31997 Dynamic Service Entries + 131071 131069 SapInst EgrQGrp RedirLst Entries - 31999 31997 =============================================================================== *A:PE# If a queue group instance specified in an applied queue group redirect list does not exist on the SAP's FP ingress or port egress, a flag is displayed in the show output for the SAP, for example: *A:PE# show service id 1 sap 1/1/1...
  • Page 424: Queue Group Redirect List Example

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.2.5.2 Queue Group Redirect List Example This section provides a configuration example for the use of queue group redirection lists. In this example, each ingress queue group instance contains three policers and each egress queue group instance contains three queues (the details of the queue group templates and instance creation are not shown).
  • Page 425: Show Output

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 queue 1 port-redirect-group-queue exit fc ef create queue 3 port-redirect-group-queue exit dscp af11 fc "af" dscp ef fc "ef" exit Queue group redirect list: queue-group-redirect-list list1 create type vxlan-vni match 1 instance 1 match 2 instance 2 match 3 instance 3 exit...
  • Page 426: Queue Group Templates

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 ------------------------------------------------------------------------------- Service Associations ------------------------------------------------------------------------------- Service ID Service Type ------------------------------------------------------------------------------- 1/1/1 (Ingress/Egress) ------------------------------------------------------------------------------- =============================================================================== A:PE# 6.3 Queue Group Templates Before a queue group with a specific name may be created on a port or an IOM/IMM/ XMA ingress forwarding plane, a queue group template with the same name must first be created.
  • Page 427: Percent-Rate Support

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 port queue groups of the same template name may be created on egress ports if they have a different instance identifier. These are termed ‘queue group instances’. Each instance of a named queue group created on a port is an independent set of queues structured as per the queue group template.
  • Page 428: Redirection Models

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 policers are created based on the defined policer IDs within the associated queue group template. Multiple forwarding plane queue groups of the same template name may be created on ingress if they have a different instance identifier. These are termed queue group instances.
  • Page 429: Access Sap Forwarding Class-Based Redirection

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.7 Access SAP Forwarding Class-Based Redirection Forwarding class redirection is provisioned within the SAP ingress or SAP egress QoS policy. In each policy, the forwarding class to queue ID mapping may optionally specify a named queue group instance (policy-based redirection) or may simply tag the forwarding class for redirection (SAP-based redirection).
  • Page 430 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 config>qos>sap-egress policy-id fc fc-name policer policer-id group queue-group-name instance instance-id 4. Finally, the SAP ingress or SAP egress QoS policy must be applied to the SAP. Redirecting a SAP forwarding class to a queue within an egress port-based or ingress forwarding plane queue group using SAP-based redirection requires four steps: 1.
  • Page 431: Ingress And Egress Sap Forwarding Class Redirection Association Rules

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 fc fc-name policer policer-id port-redirect-group-queue 4. Finally, the SAP ingress or SAP egress QoS policy must be applied to the SAP. The named queue group instance that was created on the ingress forwarding plane or the egress port must be specified at this time.
  • Page 432 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • If the SAP ingress QoS policy is currently applied to a non-Ethernet port or an Ethernet port where the specified ingress queue group does not exist, the forwarding class redirection will fail. When a SAP ingress QoS policy forwarding class redirection is removed from a queue group queue ID: •...
  • Page 433 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 If the above operation is successful: • The system decrements the association counter for the egress queue group template with the same name as the queue group previously specified in the forwarding class redirection.
  • Page 434: Sap-Based Provisioning Model

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.7.1.2 SAP-Based Provisioning Model When a redirection to a named forwarding plane queue group instance is applied to a SAP on ingress: • If the queue group name does not exist as an ingress queue group template, the redirection will fail.
  • Page 435: Access Queue Group Statistics

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 • The system decrements the association counter for the ingress queue group template with the same name as the queue group previously specified in the forwarding class redirection. • The system decrements the policer ID association counter within the queue group template for the policer ID previously specified in the forwarding class redirection.
  • Page 436: Forwarding Plane Queue Groups

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 This means that it is not possible to perform accounting within a queue group based on the source SAPs feeding packets to the queue. The statistics associated with the SAP will not reflect packets redirected to a port queue group queue. The set of statistics per queue are eligible for collection in a similar manner as SAP queues.
  • Page 437: Egress Network Forwarding Class Redirection Association Rules

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 3. Configure the network QoS policy used on the IP interface to redirect ingress traffic to a policer ID (defined in the ingress queue-group template created in step 1) on the basis of forwarding-class and forwarding-type (unicast vs. multicast).
  • Page 438 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • If the IP interface is currently bound to a port (or LAG), the association counter for the queue group on the port is incremented. When the queue group parameter is removed from an IP interface: •...
  • Page 439: Egress Network Ip Interface Statistics

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.8.2 Egress Network IP Interface Statistics The statistics for network interfaces work differently than statistics on SAPs. Counter sets are created for each egress IP interface and not per egress queue. When a forwarding class for an egress IP interface is redirected from the default egress port queue to a queue group queue, the system continues to use the same counter set.
  • Page 440: Provisioning Model

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 config>qos>network>ingress>fc>fp-redirect-group policer policer-id config>qos>network>ingress>fc>fp-redirect-group broadcast-policer policer- config>qos>network>ingress>fc>fp-redirect-group unknown-policer policer-id config>qos>network>ingress>fc>fp-redirect-group mcast-policer policer-id The user can redirect the unicast, broadcast, unknown, and multicast packets of an FC to different policers to allow for different policing rates for these packet types (broadcast and unknown are only applicable to VPLS services).
  • Page 441 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 b. One or more spoke-SDPs can have their FCs redirected to use policers in the same policer queue-group instance. The following are the constraints and rules of this provisioning model when used in the ingress PW shaping feature: 1.
  • Page 442: Ingress Packet Classification

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 9. If a network QoS policy is applied to the ingress context of a PW, any PW FC, that is not explicitly redirected in the network QoS policy has the corresponding packets feed directly into the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the MDA/FP.
  • Page 443: Redirection

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.9.2 Egress PW Shaping using Spoke-SDP Forwarding Class-Based Redirection 6.9.2.1 Feature Configuration The user applies a network QoS policy to the egress context of a spoke-sdp to redirect the mapping of a Forwarding Class (FC) to a policer and/or a queue part of a queue-group instance created in the egress of a network port.
  • Page 444: Provisioning Model

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The CLI configuration in this section uses a spoke-sdp defined in the context of a VPRN interface. However, the PW shaping feature is supported with all PW-based services including the PW template. 6.9.2.2 Provisioning Model This provisioning model allows the mapping of one or more PWs to the same...
  • Page 445 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6. When a PW FC is redirected to use a queue or a policer and a queue in a queue- group and the queue-group name does not exist, the association fails at the time the user associates the egress context of a spoke-SDP with the named queue- group.
  • Page 446: Egress Marking Of Pw Packet Header

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.9.2.3 Egress Marking of PW Packet Header When the queue-group name that the PW is redirected to exists and the redirection succeeds, the marking of the packet’s DEI/dot1p/DSCP and the tunnel’s DEI/dot1p/ DSCP/EXP is performed according to the relevant mappings of the {FC, profile} in the egress context of the network QoS policy applied to the PW.
  • Page 447: Queue Group Behavior On Lag

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Similar to the SDP binding stats, the ingress policer stats for a spoke-SDP does not count the label stack. When the spoke-SDP is part of a L2-service, they will count the L2-encapsulation, minus CRC and VLAN tag if popped out, and they also count the PW CW, if included in the packet.
  • Page 448: Adding A Queue Group To An Existing Lag

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.10.3 Adding a Queue Group to an Existing LAG A queue group must be created on the primary (lowest port ID) port of the LAG. If an attempt is made to create a queue group on a port other than the primary, the attempt will fail.
  • Page 449: Configuring Egress Queue Group Template

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 queue 3 best-effort create mbs 100 exit queue 4 best-effort create mbs 100 exit exit exit ---------------------------------------------- *A:Dut-T>cfg>qos>qgrps# Note: To fully use the queue group feature to save queues, you must explicitly map all forwarding classes to queue group queues.
  • Page 450 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.11.3 Applying Ingress Queue Group to SAP Ingress Policy The following displays a SAP ingress policy configuration with group queue-group- name specified: *A:Dut-T>config>qos>sap-ingress# info ---------------------------------------------- queue 1 create exit queue 11 multipoint create exit fc "af"...
  • Page 451: Configuring Sap-Based Egress Queue Redirection

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 queue 4 group "QG_egress_1" exit ---------------------------------------------- A:Dut-T>config>qos>sap-egress# 6.11.5 Configuring SAP-based Egress Queue Redirection The following displays a SAP egress policy configuration with port-redirect-group- queue construct (shown for both regular and HS-MDA egress queues) and the actual queue-group-name is determined by the SAP egress QoS configuration: *A:Dut-A# configure qos sap-egress 3 *A:Dut-A>config>qos>sap-egress# info...
  • Page 452 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 hsmda queue 3 port-redirect-group-queue exit exit fc l2 create queue 3 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue exit exit fc nc create queue 3 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue exit exit ---------------------------------------------- This is to be in-conjunction with: *A:Dut-A# configure service vpls 1...
  • Page 453 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 − Map forwarding classes to queue-group queues. − Identify or create the SAP ingress QoS policy that will be used on the ingress SAP where queue redirection is desired − Map the desired forwarding classes to the queue group name and the specific queue ID within the group •...
  • Page 454: Configuring Overrides

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.11.7 Configuring Overrides The following output displays a port queue group queue override example. *A:Dut-T>config>port>ethernet>access# /configure port 9/2/1 *A:Dut-T>config>port# info ---------------------------------------------- ethernet mode access access ingress queue-group "QG_ingress_1" create queue-overrides queue 2 create rate 800000 cir 20000 exit...
  • Page 455 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.11.8 Configuring Queue Group on Ethernet Access Egress Port The provisioning steps involved in using a queue-group queue on an egress access port are: • Queue Group Template Creation − Create the queue group template in the egress context −...
  • Page 456 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 − Identify or create the egress SAP requiring forwarding class redirection to the queue group − Assign the QoS policy and the egress queue-group template's instance to the SAP. 3HE 11974 AAAA TQZZA 01 Issue: 01...
  • Page 457 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.11.9 Configuring Queue Group for Network Egress Traffic on Port The provisioning steps involved in using a queue-group queue on an egress network port are: • Queue Group Template Creation: −...
  • Page 458 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 • Queue Group Creation: − Identify the ingress forwarding plane on which the queue group will be needed. − Create a queue group with the same name as the template in the FP ingress network configuration context.
  • Page 459 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 exit egress fc be port-redirect-group policer 2 exit exit exit card 1 card-type xcm-x20 mda 1 mda-type cx20-10g-sfp no shutdown exit fp 1 ingress network queue-group "Ingress_QG_1" instance 550 create exit exit exit...
  • Page 460 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 #-------------------------------------------------- queue-group-templates ingress queue-group "QGIng1" create policer 1 create exit policer 2 create exit policer 3 create exit policer 4 create exit exit exit egress queue-group "QGEgr1" create queue 1 best-effort create exit policer 1 create exit...
  • Page 461 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 port-redirect-group policer 1 exit fc l1 port-redirect-group policer 2 exit fc l2 port-redirect-group policer 3 exit exit exit exit #-------------------------------------------------- echo "Card Configuration" #-------------------------------------------------- card 3 fp 1 ingress network queue-group "QGIng1"...
  • Page 462: Specifying Qos Policies On Service Saps

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 description "Default tls description for service id 1" service-mtu 9000 shutdown exit service-name "XYZ Vpls 1" sap 9/2/1:1.* create description "Default sap description for service id 1" static-mac 00:00:1e:00:01:02 create ingress qos 10 exit...
  • Page 463 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 sap 9/2/2 create ingress qos 10 exit egress qos 10 exit exit no shutdown ---------------------------------------------- *A:Dut-T>config>service>vpls# Issue: 01 3HE 11974 AAAA TQZZA 01...
  • Page 464 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 3HE 11974 AAAA TQZZA 01 Issue: 01...
  • Page 465: Command Hierarchies

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.12 QoS Queue Group Template Command Reference 6.12.1 Command Hierarchies • Configuring Ingress Queue Group Templates • Configuring Egress Queue Group Templates • Configuring VXLAN VNI Queue Group Redirection • Show Commands •...
  • Page 466: Configuring Egress Queue Group Templates

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — no rate — stat-mode {no-stats | minimal | offered-profile-no-cir | offered-priority-no-cir | offered-limited-profile-cir | offered-profile-cir | offered-priority-cir | offered- total-cir | offered-profile-capped-cir | offered- limited-capped-cir} — no stat-mode — queue queue-id [multipoint] [queue-type] [queue-mode] [create]...
  • Page 467 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 — low-burst-max-class class — no low-burst-max-class — packet-byte-offset {add add-bytes | subtract sub-bytes} — no packet-byte-offset — [no] queue queue-id — adaptation-rule [pir {max | min | closest}] — no adaptation-rule —...
  • Page 468: Configuring Vxlan Vni Queue Group Redirection

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 — burst-limit size [bytes | kilobytes] — no burst-limit — size-in-kbytes — no — [no] dynamic-mbs — drop-tail — exceed — percent-reduction-from-mbs percent — no percent-reduction-from-mbs — high — percent-reduction-from-mbs percent —...
  • Page 469: Show Commands

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 6.12.1.4 Show Commands show — qos — queue-group [queue-group-name] [ingress | egress] [association | detail] — queue-group summary — queue-group-redirect-list [policy-name] [association | detail] — sap-egress [policy-id] [association | match-criteria | hsmda | detail] —...
  • Page 470: Command Descriptions

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 6.12.2 Command Descriptions 6.12.2.1 Configuration Commands 6.12.2.1.1 Generic Commands description Syntax description description-string no description Context config>qos>queue-group-templates>egress>queue-group config>qos>queue-group-templates>ingress>queue-group config>qos>queue-group-templates>egress>queue-group>policer config>qos>queue-group-templates>ingress>queue-group>policer Description This command creates a text description stored in the configuration file for a configuration context.
  • Page 471 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 ingress Syntax ingress Context config>qos>queue-group-templates Description This command enables the context to create ingress queue group templates. Ingress queue group templates can be applied to ingress ports to create an ingress queue group of the same name.
  • Page 472 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 no policer policer-id Context config>qos>queue-group-templates>ingress>queue-group Description This command is used in ingress and egress queue-group templates to create, modify, or delete a policer. Policers are created and used in a similar manner to queues. The policer ID space is separate from the queue ID space, allowing both a queue and a policer to share the same ID.
  • Page 473 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation- rule is removed, the default constraints for rate and cir apply.
  • Page 474 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Syntax cbs size-in-kbytes no cbs Context config>qos>queue-group-templates>egress>queue-group>queue config>qos>queue-group-templates>ingress>queue-group>queue config>qos>queue-group-templates>egress>queue-group>policer config>qos>queue-group-templates>ingress>queue-group>policer Description The cbs command is used to define the default committed buffer size for the template queue or the CBS for the template policer. Overall, the cbs command follows the same behavior and provisioning characteristics as the cbs command in the SAP ingress and egress QoS policy.
  • Page 475 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Parameters percent-of-mbs — The percent-of-mbs parameter is required when specifying high-prio- only and is expressed as a percentage. Values 0 to 100 Default Syntax mbs {size [bytes | kilobytes] | default} no mbs Context config>qos>queue-group-templates>egress>queue-group>queue...
  • Page 476 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 At ingress, trusted in-profile packets and untrusted high-priority packets use the policer’s high-priority violate threshold while trusted out-of-profile and untrusted low-priority packets use the policer's low-priority violate threshold. At egress, inplus-profile and in-profile packets use the policer’s high-priority violate threshold and out-of-profile packets use the policer's low-priority violate threshold.
  • Page 477 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Default none Parameters add bytes — Specifies the number of bytes to add as the offset amount. Values 0 to 31 subtract bytes — Specifies the number of bytes to add as the offset amount. Values 1 to 32 parent...
  • Page 478 QoS policy. The combining of the sub-profile and the sla-profile at the subscriber level provides the system with the proper information to create the policer control hierarchy instance for the subscriber. This functionality is available only for the 7450 ESS and 7750 SR.
  • Page 479 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Context config>qos>queue-group-templates>ingress>queue-group>policer config>qos>queue-group-templates>egress>queue-group>policer Description This command enables a limit on the profile. Default no profile-capped rate Syntax rate {max | pir-rate} [cir {max | cir-rate}] no rate Context config>qos>queue-group-templates>egress>queue-group>policer config>qos>queue-group-templates>ingress>queue-group>policer Description This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue or policer.
  • Page 480 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue or policer is provisioned. Values {[1 to 2000000000 | max} Kbps Default cir-rate —...
  • Page 481 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Each mode uses a certain number of counters per policer instance that are allocated from the forwarding plane’s policer counter resources. The total/allocated/free stats can be viewed by using the tools dump resource-usage card fp command. If insufficient counters exist to implement a mode on any policer instance, the stat-mode change will fail and the previous mode will continue unaffected for all instances of the policer.
  • Page 482 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 55 Stat Mode Descriptions (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-limited- Out/uncolored In/out exiting policer Intended for when profile-cir entering policer the policer can change the profile of packet to in- and out-of-profile.
  • Page 483 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 When collect-stats is enabled, no statistics are generated. minimal — Counter resource allocation: 1 This stat-mode provides the minimal accounting resource usage and counter information, and includes the total offered, dropped and forwarded packet and octet counters for traffic entering (offered) and exiting (dropped/forwarded) the policer.
  • Page 484 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Table Table 57 Ingress Accounting Statistics Collected in offered-profile-no-cir...
  • Page 485 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Table 58 Ingress Accounting Statistics Collected in offered-priority-no-cir stat-mode Show Output Accounting Stats Collected Field Field Description Off. HiPrio HighPriorityPacketsOffered HighPriorityOctetsOffered Off. LowPrio LowPriorityPacketsOffered LowPriorityOctetsOffered Dro. HiPrio HighPriorityPacketsDropped HighPriorityOctetsDropped Dro. LowPrio LowPriorityPacketsDropped LowPriorityOctetsDropped For.
  • Page 486 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Table Table 59 Ingress Accounting Statistics Collected in offered-profile-cir...
  • Page 487 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.
  • Page 488 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.
  • Page 489 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 This mode is intended to be used without profile-capped configured within the policer as it could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics.
  • Page 490 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The impact of using offered-profile-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used. The counters displayed in the show output and those collected when collect-stats is enabled (the actual fields collected depends on the record configured in the applied accounting policy) are described in Table...
  • Page 491 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 offered-limited-capped-cir is defined, the system creates four forwarding plane offered-output counters in the network processor and four discard counters in the traffic manager. The offered-limited-capped-cir mode is similar to the offered-profile-capped-cir mode except that it combines soft in-profile with profile in (InProf) and profile out (OutProf) with soft-out-of-profile (Uncolor) and eliminates the 'offered undefined' statistic.
  • Page 492 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 queue Syntax queue queue-id [multipoint] [queue-type] [queue-mode] [create] no queue queue-id Context config>qos>queue-group-templates>ingress>queue-group Description This command creates a queue for use in a queue group template. Once created, the defined queue-id acts as a repository for the default parameters for the queue.
  • Page 493 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 queue-mode — These keywords are optional and mutually exclusive when creating a new template queue. The keywords specify how the queue manages ingress explicitly profiled packets. Values profile-mode — Overrides the default priority mode of the queue and allows the adoption of color aware profiling within the queue.
  • Page 494 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 bytes — The bytes qualifier is used to specify that the value given for size must be interpreted as the burst limit in bytes. The byte qualifier is optional and mutually exclusive with the kilobytes qualifier.
  • Page 495 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 packet-byte-offset Syntax packet-byte-offset {add bytes | subtract bytes} no packet-byte-offset Context config>qos>queue-group-templates>ingress>queue-group>queue Description This command is used to modify the size of each packet handled by the queue by adding or subtracting a number of bytes.
  • Page 496 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Description This command defines an optional parent scheduler that further governs the available bandwidth given the queue aside from the queue’s PIR setting. When multiple schedulers, policers (at egress only), and/or queues share a child status with the parent scheduler, the weight or level parameters define how this queue contends with the other children for the parent’s bandwidth.
  • Page 497 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 weight weight — weight defines the relative weight of this queue in comparison to other child schedulers and queues while vying for bandwidth on the parent scheduler- name. Any queues or schedulers defined as weighted receive no parental bandwidth until all policers, queues, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
  • Page 498 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 pool Syntax pool pool-name no pool Context config>qos>queue-group-templates>egress>queue-group>queue config>qos>queue-group-templates>ingress>queue-group>queue Description This command allows the queue to receive buffers from an explicit buffer pool instead of the default buffer pool. The specified pool-name must have been explicitly created in a named pool policy and the policy must have been applied to the MDA or port on which the queue resides.
  • Page 499 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. For SAP ingress, the CIR also defines the rate that packets are considered in-profile by the system.
  • Page 500 On the 7450 ESS and 7750 SR, egress policed subscriber traffic works in a slightly different way. The subscriber and subscriber host support destination and organization strings are used to identify the egress port queue group.
  • Page 501 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Parameters fc-name — A valid forwarding class must be specified as fc-name when the fc command is executed. When the fc fc-name command is successfully executed, the system will enter the specified forwarding class context where the queue queue-id command may be executed.
  • Page 502 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 When a packet-byte-offset value is applied to a queue or policer instance, it adjusts the immediate packet size. This means that the queue rates (i.e., operational PIR and CIR) and policer or queue bucket updates use the adjusted packet size.
  • Page 503 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 enable-exceed-pir Syntax [no] enable-exceed-pir Context config>qos>sap-egress>policer cfg>qos>qgrps>egr>qgrp Description This command enables the forwarding of traffic exceeding the PIR for a SAP egress or a network egress queue group (configured in the egress queue group template) policer. This traffic is forwarded as exceed-profile instead of being dropped.
  • Page 504 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The ingress policer stat-modes are summarized in Table Table 65 Egress Policer Stat Mode Summary Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded no-stats None None Minimal Single counter Single counter for entering policer...
  • Page 505 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Table 65 Egress Policer Stat Mode Summary (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-total-cir- Single counter In/out/exceed Intended for when exceed entering policer exiting policer the policer is configured with enable-exceed-pir...
  • Page 506 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The policer does not have any forwarding plane counters allocated and cannot provide offered, discard, and forward statistics. A policer using no-stats cannot be a child to a parent policer and the policer’s parent command will fail. When collect-stats is enabled, no statistics are generated.
  • Page 507 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 The offered-profile-no-cir mode is most useful when profile-based offered, dropped and forwarded statistics are required from the egress policer, but a CIR or enable- exceed-pir is not being used to recolor the soft in-profile and out-of-profile packets. This mode does not prevent the policer from being configured with a CIR rate or using enable-exceed-pir.
  • Page 508 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer when egress reclassification is performed so that the traffic entering the policer comprises of hard inplus/in/out/exceed and soft in/out.
  • Page 509 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Table 68 Egress Accounting Statistics Collected in offered-profile-cir stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description For. OutProf OutOfProfilePacketsForwarded OutOfProfileOctetsForwarded offered-total-cir — Counter resource allocation: 2 This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer.
  • Page 510 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 69 Egress Accounting Statistics Collected in offered-total-cir stat- mode (Continued) Show Output Accounting Stats Collected Field Field Description For. InProf InProfilePacketsForwarded InProfileOctetsForwarded For. OutProf OutOfProfilePacketsForwarded OutOfProfileOctetsForwarded offered-limited-capped-cir — Counter resource allocation: 4 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer when egress reclassification is performed so that the traffic...
  • Page 511 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Table 70 Egress Accounting Statistics Collected in offered-limited- capped-cir stat-mode Show Output Accounting Stats Collected Field Field Description Off. InProf InProfilePacketsOffered InProfileOctetsOffered Off. OutProf OutOfProfilePacketsOffered OutOfProfileOctetsOffered Dro. InProf InProfilePacketsDropped InProfileOctetsDropped Dro.
  • Page 512 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 The impact of using offered-profile-capped-cir stat-mode while profile-capped mode is disabled is that one of the counting resources in the forwarding plane and traffic manager will not be used and soft-in-profile will be treated as offered-in (hard in-profile) instead of offered-undefined (uncolored).
  • Page 513 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering (offered) and exiting (dropped/ forwarded) the policer. All offered traffic is provided in a single counter. In the dropped and forwarded counters, inplus-profile traffic is counted with the in-profile counter.
  • Page 514 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 offered-four-profile-no-cir — Counter resource allocation: 4 This stat-mode provides offered, dropped, and forwarded packet and octet counters corresponding to the profile of traffic entering the policer. Offered, dropped, and forwarded counters are provided for inplus-profile, in-profile, out-of-profile, and exceed-profile traffic.
  • Page 515 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Table 73 Egress Accounting Statistics Collected in offered-four-profile- no-cir stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description Dro. InplusProf InplusProfilePktsDropped InplusProfileOctetsDropped For. InProf InProfilePacketsForwarded InProfileOctetsForwarded For. OutProf OutOfProfilePacketsForwarded OutOfProfileOctetsForwarded For.
  • Page 516 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Table 74 Egress Accounting Statistics Collected in offered-total-cir-four- profile stat-mode Show Output Accounting Stats Collected Field Field Description Off. All AllPacketsOffered AllOctetsOffered Dro. InProf InProfilePacketsDropped InProfileOctetsDropped Dro. OutProf OutOfProfilePacketsDropped OutOfProfileOctetsDropped Dro.
  • Page 517 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 Description This command creates a queue for use in a queue group template. Once created, the defined queue-id acts as a repository for the default parameters for the queue. The template queue is created on each queue group object that is created with the queue group template name.
  • Page 518 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 exceed Syntax exceed Context config>qos>qgrps>egr>qgrp>queue>drop-tail Description This command enters the context to configure the queue exceed drop-tail parameters. The exceed drop tail defines the queue depth beyond which exceed-profile packets will not be accepted into the queue and will be discarded.
  • Page 519 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 • exceed drop tail: exceed-profile • high drop tail: in-profile • highplus drop tail: inplus-profile • low drop tail: out-of-profile Default exceed drop tail: 20% low drop tail: 10% high drop tail: 0% highplus drop tail: 0% Parameters percent —...
  • Page 520 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 Parameters pir-percent — Expresses the queue’s shaping rate as a percentage of line rate. The line rate associated with the queue’s port may dynamically change due to configuration or auto-negotiation and the egress rate setting. Values 0.01 to 100.00 percent Default...
  • Page 521 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 cir-weight cir-weight — Defines the weight the queue or scheduler will use at the within- cir port priority level (defined by the cir-level parameter). The weight is specified as an integer value from 0 to 100 with 100 being the highest weight. When the cir- weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir- level parameter is ignored.
  • Page 522 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 wred-queue Syntax wred-queue [policy slope-policy-name] [mode {native | pool-per-queue}] [slope-usage {default | exceed-low}] no wred-queue Context config>qos>qgrps>egr>qgrp>queue Description This command allows the configuration of WRED per queue with the following options: •...
  • Page 523 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 In the case where this is applied on FP2- or higher-based hardware that has WRED queue support shutdown (config>card>fp>egress>wred-queue-control>shutdown), the queue will continue to map to either its default pool or the pool defined in the pool command. If the no shutdown command is executed in the wred-queue-control context, the queue will be automatically moved to its own WRED pool.
  • Page 524 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 pool-per-queue - Each queue uses its own pool and the WRED capabilities of the pool to provide WRED per queue. This is supported on both FP2 and later hardware and requires slope- usage default.
  • Page 525 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.0.R1 When a queue group template with no queues-hqos-manageable is configured under a port's Ethernet access egress context, the configuration of an aggregate rate or scheduler policy is not permitted under that context, nor are parent overrides for any of the queues in the queue group.
  • Page 526: Show Commands

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.0.R1 0x1 to 0xFFFFFF (Hexadecimal) 0b1 to 0b1111111111111111111