Download Print this page

Nokia 7450 Quality Of Service Manual

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

Advertisement

QUALITY OF SERVICE GUIDE RELEASE 15.1.R1
7450 ETHERNET SERVICE SWITCH
7750 SERVICE ROUTER
7950 EXTENSIBLE ROUTING SYSTEM
VIRTUALIZED SERVICE ROUTER
QUALITY OF SERVICE GUIDE
RELEASE 15.1.R1
3HE 13639 AAAA TQZZA 01
Issue: 01
November 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.1.R1 7450 ETHERNET SERVICE SWITCH 7750 SERVICE ROUTER 7950 EXTENSIBLE ROUTING SYSTEM VIRTUALIZED SERVICE ROUTER QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01 November 2017 Nokia — Proprietary and confidential.
  • 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.1.R1 Table of Contents Getting Started ................15 About This Guide..................15 QoS Configuration Process ...............17 QoS Policies .................19 QoS Overview ...................19 Forwarding Classes...................20 2.2.1 High-Priority Classes .................21 2.2.2 Assured Classes..................21 2.2.3 Best-Effort Classes..................22 Queue Parameters ..................23 2.3.1 Queue ID ....................23 2.3.2...
  • Page 4 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 2.4.9.4 Tiers......................75 2.4.9.5 Scheduler Policies Applied to Applications..........76 2.4.9.6 Scheduler Policies Applied to SAPs ............77 2.4.9.7 Scheduler Policies Applied to Customer SLAs..........78 2.4.9.8 Scheduler Policies Applied to Multiservice Sites ........78 2.4.10 Shared-Queue QoS Policies ..............78 2.4.11 ATM Traffic Descriptor Profiles..............79 2.4.12...
  • Page 5 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 4.3.2 Applying Network Queue QoS Policies ...........165 4.3.2.1 XMAs and MDAs ..................165 4.3.2.2 Ethernet Ports..................166 4.3.2.3 SONET/SDH Ports ..................166 4.3.3 Default Network Queue Policy Values ............167 Service Management Tasks ..............174 4.4.1 Deleting QoS Policies................174 4.4.2 Removing a Policy from the QoS Configuration ........174 4.4.3...
  • Page 6 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Service Management Tasks ..............241 5.5.1 Applying Service Ingress and Egress Policies ........241 5.5.1.1 Epipe .......................241 5.5.1.2 IES......................242 5.5.1.3 VPLS .......................242 5.5.1.4 VPRN.......................243 5.5.2 Editing QoS Policies ................243 5.5.3 Copying and Overwriting QoS Policies............243 5.5.4 Deleting QoS Policies................244 5.5.5 Removing a Policy from the QoS Configuration ........245...
  • Page 7 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Network IP Interface Forwarding Class-Based Redirection ....463 6.8.1 Egress Network Forwarding Class Redirection Association Rules ..463 6.8.2 Egress Network IP Interface Statistics ............465 PW Shaping.....................466 6.9.1 Ingress PW Shaping Using Spoke-SDP Forwarding Class-Based Redirection ....................466 6.9.1.1 Feature Configuration................466 6.9.1.2...
  • Page 8 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Scheduler QoS Policies .............595 Scheduler Policies ...................595 7.1.1 Egress Port-Based Schedulers ...............595 7.1.1.1 Service/Subscriber or Multiservice Site Egress Port Bandwidth Allocation ....................598 7.1.1.2 Service or Subscriber or Multiservice Site Scheduler Child to Port Scheduler Parent..................600 7.1.1.3 Frame and Packet-Based Bandwidth Allocation ........603 7.1.1.4...
  • Page 9 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 7.3.1.1 Removing a QoS Policy from a Customer Multiservice Site....649 7.3.1.2 Removing a QoS Policy from SAP(s) ............649 7.3.1.3 Removing a Policy from the QoS Configuration ........650 7.3.2 Copying and Overwriting Scheduler Policies...........651 7.3.3 Editing QoS Policies ................652 QoS Scheduler Policy Command Reference ..........653 7.4.1...
  • Page 10 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 9.2.2 Ingress Service Queuing .................736 9.2.2.1 Ingress Shared Queuing................737 9.2.2.2 Ingress Multipoint Shared Queuing ............739 Basic Configurations................742 9.3.1 Modifying the Default Shared-Queue Policy..........742 9.3.1.1 Applying Shared-Queue Policies.............743 9.3.2 Default Shared Queue Policy Values .............745 Shared-Queue QoS Policy Command Reference ........751 9.4.1 Command Hierarchies................751...
  • Page 11 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 11.8 Congestion Avoidance................797 11.9 Basic Configurations................798 11.9.1 Creating an ATM-TD-Profile QoS Policy ..........798 11.9.2 Applying ATM-TD-Profile Policies ............798 11.9.2.1 ATM VLL (Apipe) SAPs ................799 11.9.2.2 Epipe SAPs .....................799 11.9.2.3 IES SAPs....................799 11.9.2.4 Ipipe SAPs....................799 11.9.2.5 VPRN SAPs.....................800 11.9.2.6...
  • Page 12 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 13.1.7.1 HSMDA Buffer Pools ................856 13.1.7.2 Identifying Queue Groups as Provisioned or System......856 13.1.7.3 Provisioned and System Port Class Pools ..........857 13.1.7.4 Aggregate Pools for Type and Class Separation ........858 13.1.7.5 Use of Aggregate Control Buffer Pools ...........859 13.1.7.6 HSMDA Buffer Pool Policy ..............862 13.1.7.7...
  • Page 13 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 QoS in MC-MLPPP ..............921 14.1 Overview....................921 14.2 Ingress MLPPP Class Reassembly............925 14.3 Basic Configurations................926 14.3.1 Configuring MC-MLPPP ................927 14.3.2 Configuring MC-MLPPP QoS Parameters ..........927 14.4 QoS in MLFR and FRF.12 Fragmentation..........930 14.4.1 QoS in MLFR...................930 14.4.2 QoS in FRF.12 End-to-End Fragmentation ..........932 14.5...
  • Page 14 QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 15.10.10 Post Egress Policer Packet Forwarding Class and Profile State Remapping ....................967 15.10.11 Ingress Child Policer Stat-Mode ..............969 15.10.12 Egress Child Policer Stat-Mode...............972 15.11 Profile-Preferred Mode Root Policers............974 15.12 Child Policer Hierarchical QoS Parenting..........976 15.13 Class Fair Hierarchical Policing (CFHP) Policy Command Reference ....................981...
  • 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 Getting Started QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Note: This guide generically covers Release 15.1.Rx content and may contain some content that will be released in later maintenance loads. Refer to the SR OS R15.1.Rx Software Release Notes, part number 3HE 13648 000x TQZZA or the VSR Release Notes, part number 3HE 12092 000x TQZZA, for information on features supported in each load of the Release 15.1.Rx software.
  • Page 17: Qos Configuration Process

    QUALITY OF SERVICE GUIDE Getting Started RELEASE 15.1.R1 1.2 QoS Configuration Process Table 2 lists the tasks necessary to configure and apply QoS policies. This guide is presented in an overall logical configuration flow. Each section describes a software area and provides CLI syntax and command usage to configure parameters for a functional area.
  • Page 18 Getting Started QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 19: 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 20: Forwarding Classes

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 21: High-Priority Classes

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 22: Best-Effort Classes

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 23: Queue Parameters

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 2.3 Queue Parameters This section describes the queue parameters provisioned on access and queues for QoS. 2.3.1 Queue ID The queue ID is used to uniquely identify the queue. The queue ID is only unique within the context of the QoS policy within which the queue is defined.
  • Page 24: Committed Information Rate

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 2.3.4 Committed Information Rate The committed information rate (CIR) for a queue performs two distinct functions: 1. Profile marking by service ingress queues — Service ingress queues mark packets in-profile or out-of-profile based on the CIR. For each packet in a service ingress queue, the CIR is compared to the current transmission rate of the queue.
  • Page 25: Peak Information Rate

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 2.3.5 Peak Information Rate The PIR defines the maximum rate at which packets are allowed to exit the queue. The PIR does not specify the maximum rate at which packets may enter the queue; this is governed by the queue's ability to absorb bursts and is defined by its maximum burst size (MBS).
  • Page 26 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 27: Committed Burst Size

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 2.3.7 Committed Burst Size The committed burst size (CBS) parameters specify the size of buffers that can be drawn from the reserved buffer portion of the queue buffer pool. When the reserved buffers for a given queue have been used, the queue competes with other queues for additional buffer resources up to the maximum burst size.
  • Page 28 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 At ingress there is a low drop tail in addition to the MBS. High enqueuing priority packets (for ingress SAP priority mode queues) and in-profile packets (for ingress SAP profile mode queues, network, and shared queues) are allowed to fill up the queue up to the MBS, however, low enqueuing priority packets (for ingress SAP priority mode queues) and out-of-profile packets (for ingress SAP profile mode queues, network, and shared queues) can only fill the queue up to the queue's low...
  • Page 29: Wred Per Queue

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 The default percentages for the drop tails for egress SAP, queue group, and network queues is a percentage reduction from the MBS of: • exceed = 20% • low = 10% • high = 0% •...
  • Page 30: Native Queue Mode

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 WRED per queue is supported for SAP egress QoS policy queues (and therefore to egress SAP and subscriber queues) and for queues within an egress queue group template. There are two modes available: •...
  • Page 31 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 Figure 2 WRED Queue: Native Mode Buffers from shared portion of egress access/network pool Buffers from reserve portion of egress access/network pool low-slope exceed-slope Queue MBS drop tail depth Slopes in WRED queues operate on the full WRED pool size (MBS) Egress access/network...
  • Page 32 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 • Exceed-profile maps to the exceed slope. The instantaneous queue depth is used against the slopes when native mode is configured; consequently, the time-average-factor within the slope policy is ignored. The inplus and in-profile traffic uses the MBS drop tail for congestion control (the highplus or high slopes are not used with a native mode queue).
  • Page 33 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 WA Shared In Use : 0 KB HiPlus-Slope Drop Pr*: 0 Hi-Slope Drop Prob Lo-Slope Drop Prob Excd-Slope Drop Prob =============================================================================== Queue : 1->1/1/1->1 =============================================================================== FC Map : be l2 af l1 h2 ef h1 nc : not-applicable Admin PIR : 10000000...
  • Page 34: Pool Per Queue Mode

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 2.3.10.2 Pool Per Queue Mode When pool per queue mode is used, the queue resides in its own pool that is located in the forwarding plane egress megapool. The size of the pool is the same as the size of the queue (based on the MBS);...
  • Page 35 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 The buffer allocation determines how much of the egress normal megapool is allocated for the egress WRED megapool, with the resv-cbs defining the amount of reserved buffer space in the egress WRED megapool. In both cases, the min and max values must be equal.
  • Page 36 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Congestion control is provided by the slope policy applied to the queue, with the slopes to be used having been no shutdown (otherwise traffic will use the MBS drop tail or a megapool slope). The slope-usage defines the mapping of the traffic profile to the WRED slope and only default is allowed with pool-per-queue that gives the following mapping: •...
  • Page 37 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 Admin CIR Oper CIR Admin MBS : 12288 KB Oper MBS : 12288 KB High-Plus Drop Tail : not-applicable High Drop Tail : not-applicable Low Drop Tail : not-applicable Exceed Drop Tail : not-applicable : 0 KB Depth Slope...
  • Page 38: Packet Markings

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 2.3.11 Packet Markings Typically, customer markings placed on packets are not treated as trusted from an in-profile or out-of-profile perspective. This allows the use of the ingress buffering to absorb bursts over PIR from a customer and only perform marking as packets are scheduled out of the queue (as opposed to using a hard policing function that operates on the received rate from the customer).
  • Page 39: Queue Counters

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 2.3.12 Queue Counters The router maintains counters for queues within the system for granular billing and accounting. Each queue maintains the following counters: • Counters for packets and octets accepted into the queue •...
  • Page 40 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Color aware profiling adds the ability to selectively treat packets received on a SAP as in-profile or out-of-profile regardless of the queue forwarding rate. This allows a customer or access device to color a packet out-of-profile with the intention of preserving in-profile bandwidth for higher priority packets.
  • Page 41: Qos Policies Overview

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 42 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 43 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 44: Service Versus Network Qos

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 Policies ATM Traffic SAP ingress...
  • Page 45: Qos Policy Entities

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.R1 • Service egress QoS policies • 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 46: Network Qos Policies

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 47 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 48: Network Queue Qos Policies

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 49 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 50 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 51: Service Ingress Qos Policies

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 52 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 53: Fc Mapping Based On Exp Bits At Vll/Vpls Sap

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 54 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 55 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 when the queue’s depth reaches the defined threshold.
  • Page 56 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 57: Egress Forwarding Class Override

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 58: Service Egress Qos Policies

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 59 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 60: Named Pool Policies

    RELEASE 15.1.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 61 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 62 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 63: Slope Policies

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 64 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 65 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 66: Tuning The Sbau Calculation

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 67 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 68: Slope Policy Parameters

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 69: Scheduler Policies

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 70 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 71 QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 72: Virtual Hierarchical Scheduling

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 73: Single-Tier Scheduling

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 74: Hierarchical Scheduler Policies

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 75: Tiers

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 76: Scheduler Policies Applied To Applications

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 77: Scheduler Policies Applied To Saps

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 78: Scheduler Policies Applied To Customer Slas

    QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 79: Atm Traffic Descriptor Profiles

    QUALITY OF SERVICE GUIDE QoS Policies RELEASE 15.1.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 Gb/s ingress traffic is the maximum that can be processed without seeing packet drops at the MDA ingress.
  • Page 80 QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 81: Network Qos Policies

    For information about the tasks and commands necessary to access the CLI and to configure and maintain router devices, refer to the CLI Usage chapter in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide. Issue: 01...
  • Page 82: Network Ingress Tunnel Qos Override

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 83: Network Ingress Ip Match Criteria

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.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 84: Storing Match-Criteria Entries

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 85 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 3.2.1.4.1 FP4-based Cards To optimize both scale and performance, policy match-criteria entries configured by the operator are compressed by each FP4 line card prior to being installed in hardware. This compression can result, in an unexpected scenario typically only achieved in a lab environment, in an overload condition where entries for a line card QoS policy on a line card FP are not programmed.
  • Page 86: Tunnel Termination Qos Override Operation

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 To identify the affected policy, the system logs the overload event providing slot number, FP number, and impacted memory bank. Based on this information, the tools>dump>qos>match-criteria-overload command allows the operator to identify the affected policy and policy entries in the system.
  • Page 87: Egress Packet Reclassification Based On Ipv4/Ipv6 Criteria

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 3.3 Egress Packet Reclassification Based on IPv4/IPv6 Criteria The user enables IP precedence or DSCP based egress re-classification by applying the following command in the context of the network QoS policy applied to the egress context of a spoke-SDP.
  • Page 88 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 When the redirection command fails in CLI, the PW uses the network QoS policy assigned to the network IP interface, however any reclassification in the network QoS policy applied to the network interface will be ignored. 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 89: Qos For Self-Generated (Cpu) Traffic On Network Interfaces

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 3.4 QoS for Self-Generated (CPU) Traffic on Network Interfaces Differentiated services code point (DSCP), forwarding class (FC), and IEEE 802.1p values can be specified to be used by protocol packets generated by the node. This enables prioritization or deprioritization of every protocol (as required).
  • Page 90 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 19 Default QoS Values for Self-Generated Traffic (Continued) Protocol DSCP Cflowd DHCP NC1, AF41, NC2 Diameter AF41 AF41 AF41 ICMP BE, NC1 IGMP IGMP Reporter IS-IS L2TP LDP/T-LDP MSC (Multichassis Support) MSDP ND (NDIS) NC1, NC2...
  • Page 91 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Table 19 Default QoS Values for Self-Generated Traffic (Continued) Protocol DSCP RADIUS RSVP sFlow SNMP Gets/Sets AF41 SNMP Traps AF41 SRRP SSH, SCP, SFTP AF41 Syslog AF41 TACACS+ AF41 Telnet AF41 TFTP AF41 Traceroute...
  • Page 92: Default Dscp Mapping Table

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Note: Some applications have multiple DSCP default values depending on the context or service. Note: Configurable values for ANCP, APS, BFD, LMP, MSC, OpenFlow, WSC, and XMPP are not supported. 3.4.1 Default DSCP Mapping Table DSCP Name DSCP Value DSCP Value...
  • Page 93: Basic Configurations

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 3.5 Basic Configurations A basic network QoS policy must conform to the following: • Each network QoS policy must have a unique policy ID. • Include the definition of at least one queue. •...
  • Page 94 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 • DSCP — The DSCP value is used for all IP packets requiring marking that egress on this forwarding class queue that are in-profile or out-of- profile. Inplus-profile traffic is marked with the same values as in-profile traffic.
  • Page 95 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 − IPv6 criteria — Creates a mapping between the possible match criteria of the network ingress traffic and the forwarding class and profile. Ingress traffic that matches the IPv6 criteria is assigned to the corresponding forwarding class and profile.
  • Page 96 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 dst-ip {ip-address/mask | ip- address ipv4-address-mask} dst-port [{lt | gt | eq} {dst- port-number | range start end}] fragment {true | false} src-ip {ip-address/mask | ip- address ipv4-address-mask} src-port [{lt | gt | eq} {src- port-number | range start end}] renum old-entry-id new-entry-id...
  • Page 97: Applying Network Qos Policies

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 exit #------------------------------------------ A:ALA-12>config>qos# 3.5.2 Applying Network QoS Policies Use the following CLI syntax to apply network policies to the router access uplink port’s IP interfaces: CLI Syntax: config>router interface interface-name qos network-policy-id The following output displays the configuration for router interface ALA-1-2 with network policy 600 applied to the interface.
  • Page 98 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 20 Network Policy Defaults (Continued) Field Default dscp fc be profile out fc ef profile in fc l2 profile in fc h1 profile in fc nc profile in af11 fc af profile in af12 fc af...
  • Page 99 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Table 20 Network Policy Defaults (Continued) Field Default egress remarking fc af dscp-in-profile af11 dscp-out-profile af12 lsp-exp-in-profile lsp-exp-out-profile fc be dscp-in-profile dscp-out-profile lsp-exp-in-profile lsp-exp-out-profile fc ef dscp-in-profile dscp-out-profile lsp-exp-in-profile lsp-exp-out-profile fc h1 dscp-in-profile dscp-out-profile lsp-exp-in-profile...
  • Page 100 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 20 Network Policy Defaults (Continued) Field Default 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 dscp-in-profile dscp-out-profile lsp-exp-in-profile lsp-exp-out-profile The following output displays the default configuration: A:ALA-49>config>qos>network# info detail ---------------------------------------------- description "Default network QoS policy."...
  • Page 101 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 dscp af41 fc h2 profile in dscp af42 fc h2 profile out dscp af43 fc h2 profile out lsp-exp 0 fc be profile out lsp-exp 1 fc l2 profile in lsp-exp 2 fc af profile out lsp-exp 3 fc af profile in lsp-exp 4 fc h2 profile in lsp-exp 5 fc ef profile in...
  • Page 102 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 dot1p-in-profile 3 dot1p-out-profile 3 exit fc l2 dscp-in-profile cs1 dscp-out-profile cs1 lsp-exp-in-profile 1 lsp-exp-out-profile 1 dot1p-in-profile 1 dot1p-out-profile 1 exit fc nc dscp-in-profile nc2 dscp-out-profile nc2 lsp-exp-in-profile 7 lsp-exp-out-profile 7 dot1p-in-profile 7 dot1p-out-profile 7 exit exit...
  • Page 103: Service Management Tasks

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 3.6 Service Management Tasks 3.6.1 Deleting QoS Policies A network policy is associated by default with router interfaces. The default policy can be replaced with a non-default policy, but cannot be removed from the configuration.
  • Page 104: Removing A Policy From The Qos Configuration

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3.6.2 Removing a Policy from the QoS Configuration To delete a network policy, enter the following commands: CLI Syntax: config>qos# no network network-policy-id 3.6.3 Copying and Overwriting Network Policies An existing network policy can be copied to a new policy ID value or overwrite an existing policy ID.
  • Page 105: Editing Qos Policies

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 network 700 create description "Default network QoS policy." scope template ingress default-action fc be profile out 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...
  • Page 106 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 107: Network Qos Policy Command Reference

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 3.7 Network QoS Policy Command Reference 3.7.1 Command Hierarchies • Configuration Commands − Multi-Class Frame Relay Profile Commands − Network QoS Policy Commands • Self-Generated Traffic Commands • Operational Commands • Show Commands •...
  • Page 108 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 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 — network network-policy-id [create] [name name] — no...
  • Page 109 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 — match [next-header next-header] — no match — dscp dscp-name — no dscp — dst-ip {ipv6-address/prefix-length | ipv6-address ipv6-address-mask} — no dst-ip — dst-port {lt | gt | eq} dst-port-number — dst-port range start end —...
  • Page 110: Self-Generated Traffic Commands

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3.7.1.2 Self-Generated Traffic Commands config — service — vprn — sgt-qos — 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 —...
  • Page 111: Debug Commands

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 3.7.1.5 Debug Commands tools — dump — qos — match-criteria-overload — match-criteria-overload card slot-number fp fp-number — match-criteria-overload card slot-number fp fp-number network network- policy-id direction direction — match-criteria-overload card slot-number fp fp-number sap-egress policy-id —...
  • Page 112 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3.7.2.1.2 Multi-Class Frame Relay Profile Commands mc-fr-profile-ingress Syntax mc-fr-profile-ingress profile-id [create] no mc-fr-profile-ingress profile-id Context config>qos Description This command creates a profile for the user to configure the ingress QoS parameters of a Multi-Link Frame Relay (MLFR) bundle.
  • Page 113 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Class 1 = 25 ms Class 2 = 100 ms Class 3 = 1000 ms Parameters timeout-value — Specifies the timeout value, in ms. Values 1 to 1000 mc-fr-profile-egress Syntax mc-fr-profile-egress profile-id [create] no mc-fr-profile-egress profile-id Context config>qos...
  • Page 114 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Syntax mir mir no mir Context config>qos>mc-fr-profile-egress>class Description This command configures the minimum information rate scheduling parameter for each Frame Relay scheduling class queue for this profile. Default 90% for all classes Parameters mir —...
  • Page 115 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Description This command creates or edits a QoS network policy. The network policy defines the treatment that IP or MPLS packets receive as they ingress and egress the network port. The QoS network policy consists of an ingress and egress component. The ingress component of the policy defines how DiffServ code points and MPLS EXP bits are mapped to internal forwarding class and profile state.
  • Page 116 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters network-policy-id — The policy-id uniquely identifies the policy on the router. Values 1 to 65535 Default create — Required parameter when creating a QoS network policy. name name — A name of the operator’s choice, up to 64 characters. The name is saved as part of the configuration data but unused by SR OS.
  • Page 117 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Network Ingress QoS Policy Commands ingress Syntax ingress Context config>qos>network Description This command is used to enter the CLI node that creates or edits policy entries that specify the DiffServ code points-to-forwarding class mapping for all IP packets and define the MPLS EXP bits-to-forwarding class mapping for all labeled packets.
  • Page 118 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description This command explicitly sets the forwarding class or enqueuing priority and profile of the packet 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 and be assigned to the forwarding class and enqueuing priority and profile of the packet, based on the parameters included in the dot1p rule.
  • Page 119 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Ingress traffic that matches the specified DSCP will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all 64 DiffServ code points to the forwarding class. For undefined code points, packets are assigned to the forwarding class specified under the default-action command.
  • Page 120 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 21 Default DSCP Names to DSCP Value Mapping (Continued) DSCP Name DSCP Value DSCP Value DSCP Value Decimal Binary Hexadecimal af12 0x0c 0b001100 af13 0x0e 0b001110 default 0x00 0b000000 Table 22 Default Class Selector Code Points to DSCP Value Mapping DSCP Name DSCP Value...
  • Page 121 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Context config>qos>network>ingress config>qos>network>egress Description This command specifies the forwarding class name. The forwarding class name represents an egress queue. The fc fc-name represents a CLI parent node that contains sub-commands or parameters describing the egress characteristics of the queue and the marking criteria of packets flowing through it.
  • Page 122 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 ip-criteria Syntax [no] ip-criteria Context config>qos>network>ingress Description IP criteria-based network ingress policies are used to select the appropriate ingress queue and corresponding forwarding class for matched traffic. This command is used to enter the context to create or edit policy entries that specify IP criteria such as IP quintuple lookup or DiffServ code point.
  • Page 123 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 This command is supported on FP2- and higher-based hardware and is otherwise ignored. entry Syntax entry entry-id [create] no entry entry-id Context config>qos>network>ingress>ip-criteria config>qos>network>ingress>ipv6-criteria Description This command is used to create or edit an IP or IPv6 criteria entry for the policy. Multiple entries can be created using unique entry-id numbers.
  • Page 124 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 action Syntax action fc fc-name profile {in | out} no action Context config>qos>network>ingress>ip-criteria>entry config>qos>network>ingress>ipv6-criteria>entry Description This mandatory command associates the forwarding class and packet profile with specific IP or IPv6 criteria entry ID. Packets that meet all match criteria within the entry have their forwarding class and packet profile set based on the parameters included in the action parameters.
  • Page 125 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 If more than one match criteria (within one match statement) are configured, then all criteria must be satisfied (AND function) before the action associated with the match is executed. A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.
  • Page 126 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 23 Protocol ID Descriptions (Continued) Protocol Protocol ID Description ipv6 IPv6 ipv6-route Routing Header for IPv6 ipv6-frag Fragment Header for IPv6 idrp Inter-Domain Routing Protocol rsvp Reservation Protocol General Routing Encapsulation ipv6-icmp ICMP for IPv6 ipv6-no-nxt...
  • Page 127 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Context config>qos>network>ingress>ipv6-criteria>entry Description This command creates a context to configure match criteria for a network QoS policy match IPv6 criteria. When the match criteria have been satisfied, the action associated with the match criteria is executed.
  • Page 128 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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. Values be, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cs1, cp9, af11, cp11, af12, cp13, af13, cp15, cs2, cp17, af21, cp19, af22, cp21, af23, cp23, cs3, cp25, af31, cp27, af32, cp29, af33, cp31, cs4, cp33, af41, c p35,...
  • Page 129 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Description This command configures a destination TCP or UDP port number or port range for a network ingress QoS policy match criterion. The no form of this command removes the destination port match criterion. Parameters lt | gt | eq dst-port-number —...
  • Page 130 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters true — Specifies to match on all fragmented IPv6 packets. A match will occur for all packets that contain an IPv6 Fragmentation Extension Header. false — Specifies to match on all non-fragmented IP packets. Non-fragmented IPv6 packets are packets that do not contain an IPv6 Fragmentation Extension Header.
  • Page 131 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 ipv6-address-mask — Specifies the eight 16-bit hexadecimal pieces representing bit match criteria. Values x:x:x:x:x:x:x (eight 16-bit pieces) src-port Syntax src-port {lt | gt | eq} src-port-number src-port range start end no src-port Context config>qos>network>ingress>ip-criteria>entry>match config>qos>network>ingress>ipv6-criteria>entry>match...
  • Page 132 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 new-entry-number — Enter the new entry number to be assigned to the old entry. Values 1 to 65535 ler-use-dscp Syntax [no] ler-use-dscp Context config>qos>network>ingress 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.
  • Page 133 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 The no form of this command removes the association of the LSP EXP bit value to the forwarding class. The default-action then applies to that LSP EXP bit pattern. Default no lsp-exp Parameters lsp-exp-value —...
  • Page 134 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 dscp Syntax dscp dscp-name fc fc-name profile {in | out | exceed | inplus} no dscp dscp-name Context config>qos>network>egress Description This command configures an IP Differentiated Services Code Point (DSCP) value that must be matched to perform the associated reclassification actions.
  • Page 135 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Parameters dscp-name — be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57, cp58, cp59, cp60, cp61, cp62, cp63...
  • Page 136 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 • for transit packets (B-SAP/B-SDP to B-SDP), the related ITAG bits are preserved, the same as for BVID. Values 0, 1 dot1p Syntax dot1p dot1p-priority no dot1p Context config>qos>network>egress>fc Description This command is used whenever the dot1p bits are set to a common value regardless of the internal profile of the packets.
  • Page 137 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 dot1p-out-profile Syntax dot1p-out-profile dot1p-priority no dot1p-out-profile Context config>qos>network>egress>fc Description This command specifies dot1p out-of-profile mappings. The exceed-profile traffic is marked with the same value as out-of-profile traffic. The no form of this command resets the configuration to the default out-profile dot1p-priority setting for policy-id 1.
  • Page 138 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 no dscp-out-profile Context config>qos>network>egress>fc Description This command specifies the out-of-profile DSCP name for the forwarding class. The corresponding DSCP value will be used for all IP packets requiring marking the egress on this forwarding class queue that are out-of-profile.
  • Page 139 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 lsp-exp-out-profile Syntax lsp-exp-out-profile lsp-exp-value no lsp-exp-out-profile Context config>qos>network>egress>fc Description This command specifies the out-of-profile LSP EXP value for the forwarding class. The EXP value will be used for all LSP labeled packets that require marking at egress on this forwarding class queue, and that are out-of-profile.
  • Page 140 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 policer id — The specified policer-id must exist within the queue-group template applied to the ingress context of the forwarding plane. Values 1 to 8 prec Syntax prec ip-prec-value fc fc-name profile {in | out | exceed | inplus} no prec ip-prec-value Context config>qos>network>egress...
  • Page 141 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Parameters ip-prec-value — 0 to 7 fc fc-name — be, l2, af, l1, h2, ef, h1, nc 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.
  • Page 142: Self-Generated Traffic Commands

    Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The remark trusted state has no effect on packets received on an ingress VPRN IP interface. Table 24 Ingress IP Interface Type and Trust State Effect on Egress Network Remarking Ingress IP Interface Type Egress Network IP Interface Trust Egress Network IP Interface and Trust State...
  • Page 143 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 144 — 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 145: Operational Commands

    QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 fc fc-name — Specifies the forwarding class name. All packets with a DSCP value or MPLS EXP bit that are not defined will be placed in this forwarding class. Values be, l2, af, l1, h2, ef, h1, nc 3.7.2.3 Operational Commands copy...
  • Page 146 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters value dscp-value — The specific DSCP value for which to display information. Values 0 to 63 Default Show all values Output The following output is an example of dscp-table information, and Table 25 describes the output fields.
  • Page 147 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 cp41 1010 0100 cp42 1010 1000 cp43 1010 1100 cp44 1011 0000 cp45 1011 0100 1011 1000 cp47 1011 1100 1100 0000 cp49 1100 0100 cp50 1100 1000 cp51 1100 1100 cp52 1101 0000 cp53...
  • Page 148 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Context show>qos Description This command displays MLFR ingress profile information. Output The following output is an example of MLFR ingress profile information. Sample Output *A:Cpm-A# show qos mc-fr-profile-ingress ======================================================================== Multi-class Frame-Relay Ingress Profiles ======================================================================== Profile-Id Description...
  • Page 149 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Description: Default egress multi-class frame-relay profile. ======================================================================== *A:Cpm-A# *A:Cpm-A# show qos mc-fr-profile-egress 1 detail ======================================================================== Multi-class FR Egress Profile (1) ======================================================================== Profile-id : 1 Description: Default egress multi-class frame-relay profile. ======================================================================== MCFR Weight Max Size...
  • Page 150 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 A:ALA-12# A:ALA-12# show qos network 1 ============================================================================== QoS Network Policy ============================================================================== Network Policy (1) ------------------------------------------------------------------------------ Policy-id Remark : True Forward Class : be Profile : Out-profile Description : Default network QoS policy. ============================================================================== A:ALA-12# A:ALA-12# show qos network 1 detail...
  • Page 151 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 ------------------------------------------------------------------------------ FC Name : af - DSCP Mapping Out-of-Profile : af12 In-Profile : af11 - LSP EXP Bit Mapping Out-of-Profile : 2 In-Profile FC Name : be - DSCP Mapping Out-of-Profile : default In-Profile : default - LSP EXP Bit Mapping...
  • Page 152 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 config>qos# show qos network 2 detail ======================================================================== QoS Network Policy ------------------------------------------------------------------------ Network Policy (2) ------------------------------------------------------------------------ Policy-id Remark : True Forward Class : be Profile : Out LER Use DSCP : False ------------------------------------------------------------------------ DSCP Forwarding Class...
  • Page 153 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 Network Policy (10) ------------------------------------------------------------------------------- Policy-id : 10 Remark : False Forward Class : be Profile : Out LER Use DSCP : False Description : (Not Specified) ------------------------------------------------------------------------------- DSCP (Ingress) Forwarding Class Profile ------------------------------------------------------------------------------- No Matching Entries...
  • Page 154 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 - LSP EXP Bit Mapping Out-of-Profile In-Profile DE Mark None Redirect Grp Q None Redirect Grp Plcr: None FC Value FC Name : af - DSCP Mapping Out-of-Profile : af12 In-Profile : af11 - dot1p Mapping Out-of-Profile...
  • Page 155 QUALITY OF SERVICE GUIDE Network QoS Policies RELEASE 15.1.R1 FC Value FC Name : h1 - DSCP Mapping Out-of-Profile : nc1 In-Profile : nc1 - 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...
  • Page 156 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 FC Value FC Name : nc Redirect UniCast Plcr : None Redirect MultiCast Plcr : None Redirect BroadCast Plcr : None Redirect Unknown Plcr : None ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Match Criteria (Ingress) ------------------------------------------------------------------------------- No Matching Entries -------------------------------------------------------------------------------...
  • Page 157 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 158 Network QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description This command displays DSCP to FC mappings. Parameters dscp-name — The specific DSCP name. be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57,...
  • Page 159: Network Queue Qos Policies

    QoS policies must be explicitly created and associated. For information about the tasks and commands necessary to access the CLI and to configure and maintain devices, refer to the CLI Usage chapter in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide.
  • Page 160: Network Queue Parent Scheduler

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 4.2 Network Queue Parent Scheduler Network queues support port-scheduler parent priority-level associations. Using a port scheduler policy definition and mapping network queues to a port parent priority level, HQoS functionality is supported providing eight levels of strict priority and weights within the same priority.
  • Page 161: Basic Configurations

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.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 162 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 163 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.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 164 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 165: Applying Network Queue Qos Policies

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.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: 4.3.2.1 XMAs and MDAs...
  • Page 166: Ethernet Ports

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 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 ---------------------------------------------- A:ALA-7>config>card>mda# 4.3.2.2 Ethernet Ports Use the following CLI syntax to apply a network queue policy to an Ethernet port.
  • Page 167: Default Network Queue Policy Values

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 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" sonet-sdh path sts3 network queue-policy "nq1" exit no shutdown exit exit no shutdown ---------------------------------------------- A:ALA-48>config>port#...
  • Page 168 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 27 Network Queue Policy Defaults (Continued) Field Default low percent-reduction- from-mbs queue 3 low percent-reduction- from-mbs queue 4 low percent-reduction- from-mbs queue 5 low percent-reduction- from-mbs queue 6 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 169 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 Table 27 Network Queue Policy Defaults (Continued) Field Default 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 multicast-queue 9 fc ef...
  • Page 170 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 27 Network Queue Policy Defaults (Continued) Field Default fc l1 queue 7 multicast-queue 12 fc l2 queue 2 multicast-queue 10 fc nc queue 8 multicast-queue 16 A:ALA-7>config>qos>network-queue# info detail ---------------------------------------------- description "Default network queue QoS policy."...
  • Page 171 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 exit exit queue 5 auto-expedite create rate 100 cir 100 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10 exit exit exit queue 6 auto-expedite create rate 100 cir 100 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10...
  • Page 172 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 exit exit exit queue 11 multipoint auto-expedite create rate 100 cir 5 mbs 50 cbs 1 drop-tail percent-reduction-from-mbs 10 exit exit exit queue 12 multipoint auto-expedite create rate 100 cir 5 mbs 25 cbs 1 drop-tail...
  • Page 173 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 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 fc ef create multicast-queue 14 queue 6 exit fc h1 create multicast-queue 15 queue 7 exit...
  • Page 174: Service Management Tasks

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 4.4 Service Management Tasks This section discusses network queue QoS policy service management tasks. 4.4.1 Deleting QoS Policies A network queue policy is associated by default with XMA or MDA network ingress ports.
  • Page 175: Editing Qos Policies

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.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 176 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 177: Network Queue Qos Policy Command Reference

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.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 178: Operational Commands

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 — hs-attachment-policy policy-name — no hs-attachment-policy — [no] hs-wrr-group group-id — adaptation-rule [pir {max | min | closest}] — no adaptation-rule — hs-class-weight weight — no hs-class-weight — rate percent —...
  • Page 179: Show Commands

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 4.5.1.3 Show Commands show — qos — network-queue [network-queue-policy-name] [detail] 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 180 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 4.5.2.1.2 Network Queue QoS Policy Commands network-queue Syntax network-queue policy-name [create] no network-queue policy-name Context config>qos Description This command creates a context to configure a network queue policy. Network queue policies define the ingress network queuing at the XMA or MDA network node level and on the Ethernet port and SONET/SDH path level to define network egress queuing.
  • Page 181 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 • Offered High Priority / In-Profile Octet Counter • Offered Low Priority / Out-of-Profile Octet Counter • Discarded High Priority / In-Profile Octet Counter • Discarded Low Priority / Out-of-Profile Octet Counter •...
  • Page 182 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 queue Syntax [no] queue queue-id Context config>qos>network-queue>egress-hsmda Description This command 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 create or dynamically assign the queue to the object to which the policy is applied.
  • Page 183 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 Description This command defines the method used by the system to derive the operational PIR settings when the HSMDA queue is provisioned in hardware. For the PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.
  • Page 184 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 bytes — Specifies 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. kilobytes —...
  • Page 185 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 Parameters percentage — Specifies the PIR percentage rate for the HSMDA queue. Values 0.10 to 100.00 slope-policy Syntax slope-policy hsmda-slope-policy-name no slope-policy Context config>qos>network-queue>egress-hsmda>queue Description This command associates an existing HSMDA slope policy with the QoS policy HSMDA queue.
  • Page 186 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 • Maximum-Probability — This is defined as a percentage of discard probability and in conjunction with maximum-utilization completes the knee coordinate where the discard probability deviates from the slope and rises to 100%. Up to 1024 HSMDA slope policies may be configured on a system.
  • Page 187 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 Parameters value — Specifies the weight for the HSMDA queue. Values 1 to 32 wrr-policy Syntax wrr-policy hsmda-wrr-policy-name no wrr-policy 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.
  • Page 188 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description This command 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 create or dynamically assign the queue to the object to which the policy is applied. The queue identified by queue-id always exists whether the command is executed or not.
  • Page 189 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 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. When the forwarding class mapping is executed, all multicast traffic using this policy is forwarded using the queue-id.
  • Page 190 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 hs-wrr-group Syntax [no] hs-wrr-group group-id Context config>qos>network-queue Description This command specifies the HS WRR group. The no form of the command removes the group ID from the configuration. Parameters group-id — Specifies the WRR group associated with this HS queue attachment policy. Values 1, 2 adaptation-rule...
  • Page 191 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 no rate Context config>qos>network-queue>hs-wrr-group Description This command specifies the PIR rate. The no form of the command reverts to the default. Parameters percent — Specifies the HSS WRR group PIR rate. Values 1 to 100 Network Queue QoS Policy Queue Commands...
  • Page 192 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The multipoint queues are for multipoint-destined service traffic. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service queue.
  • Page 193 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 best-effort — This keyword ensures that the queue is treated in a non-expedited manner independent of the forwarding classes mapped to the queue. auto-expedite — This keyword allows the system to auto-define the way the queue is serviced by the hardware.
  • Page 194 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 • Offered-Load — The offered-load of a queue is calculated by starting with the queue depth in octets, adding the received octets at the queue and subtracting queue discard octets. The result is the number of octets the queue has available to transmit. This is the packet-based offered-load.
  • Page 195 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 196 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The CBS for a queue is used to determine whether it has exhausted its reserved buffers while enqueuing packets. When 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 197 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 198 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 199 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 Context config>qos>network-queue>queue Description This command configures the class-weight override for expanded egress HS queues. The no form of the command reverts to the default. Default hs-class-weight 1 Parameters weight — Specifies the SLA profile instance class weight override for the HS class. Values 1, 2, 4, 8 hs-mbs...
  • Page 200 The configuration parameters for each queue come from the applied egress policy on the network port or channel. Forwarding class queue on egress channel applies only to the 7450 ESS and 7750 SR. 3HE 13639 AAAA TQZZA 01...
  • Page 201 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 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. This buffer pool size will dynamically fluctuate based on the port or channels egress pool size setting.
  • Page 202 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Each queue created within the system is tied to a physical port. When the policy is applied and the queue is created, the system will scan the named pools associated with the port to find the specified pool name.
  • Page 203 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.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 204: Operational Commands

    Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP ingress or SAP egress QoS policy with the queue- 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.
  • Page 205: Show Commands

    QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 overwrite — Specifies to replace the existing destination policy. Everything in the existing destination policy will be overwritten with the contents of the source policy. If overwrite is not specified, a message is generated saying that the destination policy ID exists.
  • Page 206 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 ============================================================================== QoS Network Queue Policy ============================================================================== Network Queue Policy (nq1) ------------------------------------------------------------------------------ Policy : nq1 Description : (Not Specified) ------------------------------------------------------------------------------ Queue CIR HiPrio ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ UCastQ ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ Associations ------------------------------------------------------------------------------ Port-id : 1/1/1 ============================================================================== A:ALA-12>show>qos# Table 29...
  • Page 207 QUALITY OF SERVICE GUIDE Network Queue QoS Policies RELEASE 15.1.R1 Table 29 Network Queue Labels and Descriptions (Continued) Label Description Displays the maximum burst size. HiPrio Displays the high-priority value. Displays FC-to-queue mapping. UCastQ Displays the specific unicast queue to be used for packets in the forwarding class.
  • Page 208 Network Queue QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 209: Service Ingress And Egress Qos Policies

    For information about the tasks and commands necessary to access the CLI and to configure and maintain routers, refer to the CLI Usage chapter in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide. Issue: 01...
  • Page 210: Basic Configurations

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 5.2 Basic Configurations A basic service egress QoS policy must have the following: • a unique service egress QoS policy ID • a QoS policy scope of template or exclusive •...
  • Page 211: Service Ingress Qos Policy

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 212 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 • A new queue ID value — The system will not dynamically assign a value. • Queue parameters — Ingress queues support multipoint queues, explicit and auto-expedite hardware queue scheduling, and parent virtual scheduler definition.
  • Page 213: Percent-Rate Support

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 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 #------------------------------------------ A:ALA-7>config>qos# 5.3.2 Percent-Rate Support The percent-rate command is supported for pir and cir parameters for both queues and policers.
  • Page 214: Ingress Forwarding Class (Fc)

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 <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 #------------------------------------------ fc af create queue 12 broadcast-queue 22 multicast-queue 22 unknown-queue 22...
  • Page 215: Ingress Ip Match Criteria

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 #------------------------------------------ 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. The following displays an ingress IP criteria configuration: A:ALA-7>config>qos# info #------------------------------------------...
  • Page 216: Ingress Mac Match Criteria

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 ---------------------------------------------- queue 1 create exit queue 11 multipoint create exit ip-criteria exit ipv6-criteria entry 10 create description "IPv6 SAP-ingress policy" match src-ip 2001:db8:1000::/64 dst-ip 2001:db8:2000::/64 exit action fc be priority low exit entry 20 create description "Entry 20-FC-AF"...
  • Page 217: Vlan Id Matching

    On ingress, VLAN ID matching may be used to set QoS on SAP ingress. The matching rules are the same as for VID filter (See “VID filters” in the Filter Policies section of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Router Configuration Guide) but the action allows setting of the forwarding class.
  • Page 218: Ingress Criteria Classification Directly To Policer

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 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 219: Virtual Network Identifier (Vni) Classification

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 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 220: Fc Mapping Based On Exp Bits

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 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. The following restrictions also apply: •...
  • Page 221: Storing Match Criteria Entries

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 *A:Dut-T>config>qos>sap-ingress# info ---------------------------------------------- queue 1 create exit queue 2 create exit queue 3 create exit queue 11 multipoint create exit fc "af" create queue 2 exit fc "be" create queue 1 exit fc "ef"...
  • Page 222 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Applying a QoS Policy A policy is installed for the first time on a line card FP if no router interface, service interface, SAP, spoke SDP, mesh SDP or ESM subscriber host was using the policy on this FP.
  • Page 223: Service Egress Qos Policy

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 5.4 Service Egress QoS Policy To create a service egress policy, define the following: • A new policy ID value. The system will not dynamically assign a value. •...
  • Page 224: Percent-Rate Support

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 5.4.2 Percent-Rate Support The percent-rate command is supported for pir and cir parameters for both queues and policers. Also supported for both queues and policers is the capability of specifying the rate as a percentage value of the line rate for sap-ingress and sap- egress qos policies.
  • Page 225 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 The approximate maximum delay of traffic through a queue due to the length of the queue, when the queue is not using HQoS, is relative to its administrative PIR and can be approximated as (MBS[kB] ×...
  • Page 226 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The configuration of dynamic MBS and queue depth monitoring are mutually exclusive. Dynamic MBS is configured as follows: configure queue-group-templates 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.
  • Page 227: Queue Length As A Delay Value

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Queue : accQGrp->qg1:1(5/1/1)->1 =============================================================================== FC Map : not-applicable : not-applicable Admin PIR : 50000 Oper PIR : 25000 Admin CIR Oper CIR Admin MBS : 1008 KB Oper MBS : 504 KB High-Plus Drop Tail : 1008 KB...
  • Page 228: Egress Sap Fc And Fp Overrides

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 exit ---------------------------------------------- *A:PE>cfg>qos>qgrps>egr>qgrp# exit all *A:PE# show pools access-egress 5/1/1 queue-group "qg2" instance 1 =============================================================================== Queue : accQGrp->qg2:1(5/1/1)->1 =============================================================================== FC Map : not-applicable : not-applicable Admin PIR : 50000 Oper PIR : 50000 Admin CIR...
  • Page 229: Egress Criteria Classification Directly To Policer

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 5.4.5 Egress 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 egress by configuring a policer in the action statement within an ip-criteria or ipv6-criteria statement.
  • Page 230 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 =============================================================================== Resource Usage Information for Card Slot #1 FP #1 =============================================================================== Total Allocated Free ------------------------------------------------------------------------------- Egress Qos Bypass 262143 262143 This is supported on all FP2- and higher-based hardware, excluding when a HSMDA is used.
  • Page 231: Storing Match Criteria Entries

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 5.4.6 Storing Match Criteria Entries FP2-, FP3-, and FP4-based cards store QoS policy match-criteria entries in dedicated memory banks in hardware, also referred to as CAM tables: • IP/MAC ingress •...
  • Page 232: Dot1P Egress Remarking

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The CPM QoS management task controls the maximum number of match criteria entries per FP. If the operator attempts to go over the scaling limit, the system will return an interactive error message.
  • Page 233: Dei Egress Remarking

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 • dot1p-outer used for outer tag markings • dot1p-inner used for inner tag markings • existing dot1p used for marking both tags • markings taken from packet received at ingress The configuration of qinq-mark-top-only under the SAP egress takes precedence over the use of the dot1p-inner in the policy, that is, the inner VLAN tag is not remarked when qinq-mark-top-only is configured.
  • Page 234 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 de-mark-inner [force <de-value>] de-mark-outer [force <de-value>] exit exit By default, the DE bit is set to 0 for inplus-profile and in-profile traffic and 1 for out- of-profile and exceed-profile traffic, unless explicitly forced. The precedence of these commands is summarized from highest to lowest precedence, as follows: •...
  • Page 235 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 The introduction of the DE bit allows the S-TAG to convey eight forwarding classes/ distinct priorities, each with a drop eligible indication. When DE bit is set to 0 (DE = FALSE), the related packet is not discard eligible. This is the case for the packets that are within the CIR limits and must be given priority in case of congestion.
  • Page 236 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Figure 16 DE Aware 802.1ad Access Network 7x50 PE1 7x50 PE2 802.1a/d MPLS Access I-SAP (DE aware) Access Device Fig_26 Figure 17 shows an example of the QoS processing of the DEI processing steps for the IEEE 802.1ad use case for both ingress and egress directions (from a PE1 SAP perspective).
  • Page 237: Dscp And Ip Precedence Egress Remarking

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 5.4.7.1.4 IEEE 802.1ah Use Case Figure 18 shows an example of a PBB topology where the DE feature can be used. The processing requirements highlighted in the 802.1ad use case apply to the 802.1ah BVID, format and etype, these being identical with the 802.1ad S-TAG.
  • Page 238: Queue Depth Monitoring

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Remarking the DSCP and IP precedence based on the profile result of egress policing must be enabled under the related policer configuration, as follows: CLI Syntax: sap-egress <policy-id> create policer <policer-id>...
  • Page 239 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Queue Depth Information (Ingress SAP) =============================================================================== No Matching Entries =============================================================================== =============================================================================== Queue Depth Information (Egress SAP) =============================================================================== ------------------------------------------------------------------------------- Name : 1->1/2/1->1 : Def ------------------------------------------------------------------------------- Queue Depths (percentage) ------------------------------------------------------------------------------- 0%-10% 11%-20% 21%-30% 31%-40% 41%-50% 51%-60% 61%-70% 71%-80% 81%-90% 91%-100% ------------------------------------------------------------------------------- 68.21...
  • Page 240 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 If the MBS of a queue is modified, the occupancy information is cleared and the elapsed timers reset to zero. Issuing a clear card command will also clear this information.
  • Page 241: Service Management Tasks

    • • VPLS • VPRN Refer to the Subscriber Services Overview section of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview 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 242: Ies

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 A:ALA-7>config>service# 5.5.1.2 The following output displays an IES service configuration with SAP ingress policy 100 and SAP egress 105 applied to the SAP. A:ALA-7>config>service# info ---------------------------------------------- ies 88 customer 8 vpn 88 create interface "Sector A"...
  • Page 243: Vprn

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 5.5.1.4 VPRN The following output displays a VPRN service configuration for the 7750 SR and 7950 XRS. A:ALA-7>config>service# info ---------------------------------------------- vprn 1 customer 1 create ecmp 8 autonomous-system 10000 route-distinguisher 10001:1 auto-bind-tunnel resolution-filter...
  • Page 244: Deleting Qos Policies

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 CLI Syntax: config>qos# copy {sap-ingress | sap-egress} source- policy-id dest-policy-id [overwrite] The following output displays the copied policies: A:ALA-7>config>qos# info --------------------------------------------- exit sap-ingress 100 create description "Used on VPN sap" queue 1 create exit queue 2 multipoint create...
  • Page 245: Removing A Policy From The Qos Configuration

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 A QoS policy cannot be deleted until it is removed from all SAPs where it is applied. A:ALA-7>config>qos# no sap-ingress 100 MINOR: CLI SAP ingress policy "100" cannot be removed because it is in use. A:ALA-7>config>qos# 5.5.5 Removing a Policy from the QoS Configuration CLI Syntax:...
  • Page 246 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 247: Service Ingress And Egress Qos Policy Command Reference

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 •...
  • Page 248 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 — fc-name [create] — no fc-name — 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 —...
  • Page 249 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 — no vxlan-vni — renum old-entry-id new-entry-id — type filter-type — no type — [no] ipv6-criteria — entry entry-id [create] — no entry entry-id — action [fc fc] [priority {low| high}] [policer policer-id] —...
  • Page 250 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 — etype etype-value — no etype — inner-tag value [vid-mask] — no inner-tag — outer-tag value [vid-mask] — no outer-tag — snap-oui {zero | non-zero} — no snap-oui —...
  • Page 251: Service Egress Qos Policy Commands

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 — no burst-limit — size-in-kbytes — no — drop-tail — — percent-reduction-from-mbs percent — no percent-reduction-from-mbs — size [bytes | kilobytes] — no — packet-byte-offset {add add-bytes | subtract sub-bytes} —...
  • Page 252 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 253 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 — adaptation-rule [pir adaptation-rule] — no adaptation-rule — burst-limit size [bytes | kilobytes] — no burst-limit — size [bytes | kilobytes] — no — rate pir-rate — no rate —...
  • Page 254 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 — no match — dscp dscp-name — no dscp — dst-ip {ipv6-address/prefix-length | ipv6-address ipv6- address-mask} — no dst-ip — dst-port {lt | gt | eq} dst-port-number — dst-port range start end —...
  • Page 255 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 — prec ip-prec-value [hsmda-counter-override counter-id] [fc fc-name] [profile {in | out | exceed | inplus}] — no prec ip-prec-value — queue queue-id [queue-type] [create] — no queue queue-id —...
  • Page 256: Operational Commands

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 — scope {exclusive | template} — no scope — sub-insert-shared-pccrule start-entry entry-id count count — no sub-insert-shared-pccrule config — qos — match-list — ip-prefix-list ip-prefix-list-name [create] — no ip-prefix-list ip-prefix-list-name —...
  • Page 257: Debug Commands

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 5.6.1.5 Debug Commands tools — dump — qos — match-criteria-overload — match-criteria-overload card slot-number fp fp-number — match-criteria-overload card slot-number fp fp-number network network- policy-id direction direction — match-criteria-overload card slot-number fp fp-number sap-egress policy-id —...
  • Page 258: Operational Commands

    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. 3HE 13639 AAAA TQZZA 01...
  • Page 259 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 260 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 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 261 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Description This command configures the default forwarding class for the policy. In the event that an ingress packet does not match a higher priority (more explicit) classification command, the default forwarding class or subclass will be associated with the packet.
  • Page 262 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 low — 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. When the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
  • Page 263 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 priority — This parameter overrides the default enqueuing priority for all packets received on an ingress SAP using this policy that match this rule. Specifying the priority is optional. When a packet matches the rule, the enqueuing priority is only overridden when the priority parameter is defined on the rule.
  • Page 264 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 265 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 af11 0010 1000 cp11 0010 1100 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...
  • Page 266 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 fc fc-name — The value given for fc-name 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 267 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 268 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 269 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 270 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 271 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 272 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 273 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 30 Effect of In-Remark Command on Received SAP Ingress Packets (Continued) SAP Ingress Packet State in-remark Command Effect IP Routed, Explicit In-Profile in-remark value applied to IP header ToS field IP Routed, Explicit Out-of-Profile No Effect (out-of-profile packet)
  • Page 274 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 275 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 276 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 277 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 prec ip-prec-value — Specifies that the matching packet’s precedence bits should be overridden with the value represented by ip-prec-value. The value specified by ip-prec-value is used to overwrite the precedence bits within a matching routed packets IP header ToS field.
  • Page 278 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters policer-id — When the forwarding class policer command is executed, a valid policer-id must be specified. The parameter policer-id references a policer-id that has already been created within the sap-ingress QoS policy. Values 1 to 63 fp-redirect-group —...
  • Page 279 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 out — The out keyword is mutually exclusive to the in keyword. When the profile out command is executed, all packets associated with the class will be handled as out- of-profile.
  • Page 280 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description Within a sap-ingress QoS policy forwarding class context, the unknown-policer command is used to map packets that match the forwarding class and are considered unknown in nature to the specified policer-id. The specified policer-id must already exist within the sap- ingress QoS policy.
  • Page 281 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 fp-redirect-group — Redirects a forwarding class to a forwarding plane queue-group as specified in a SAP QoS policy. unknown-queue Syntax unknown-queue queue-id [group queue-group-name] no unknown-queue Context config>qos>sap-ingress>fc Description This command overrides the default unknown unicast forwarding type queue mapping for fc fc-name.
  • Page 282 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The software implementation will exit on the first match found and execute the actions in accordance with the accompanying action command. For this reason, entries must be sequenced correctly from most to least explicit. The no form of this command deletes all the entries specified under this node.
  • Page 283 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 create — Required parameter when creating a flow entry when the system is configured to require the explicit use of the keyword to prevent accidental object creation. Objects may be accidentally created when this protection is disabled and an object name is mistyped when attempting to edit the object.
  • Page 284 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters fc fc-name — The value given for fc fc-name must be one of the predefined forwarding classes in the system. Specifying the fc fc-name is required. When a packet matches the rule, the forwarding class is only overridden when the fc fc-name parameter is defined on the rule.
  • Page 285 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 286 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 32 IP Protocol Names Protocol Protocol ID Description icmp Internet Control Message igmp Internet Group Management IP in IP (encapsulation) Transmission Control Exterior Gateway Protocol Any private interior gateway (used by Cisco for their IGRP) User Datagram Reliable Data Protocol...
  • Page 287 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 32 IP Protocol Names (Continued) Protocol Protocol ID Description Schedule Transfer Protocol Performance Transparency Protocol isis ISIS over IPv4 crtp Combat Radio Transport Protocol crudp Combat Radio User Datagram dscp Syntax dscp...
  • Page 288 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description This command configures a destination address range to be used as a SAP QoS policy match criterion. To match on the IPv4 destination address, specify the address and its associated mask, e.g., 10.1.0.0/16.
  • Page 289 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 range start end — The range of TCP or UDP port values to match, specified as between the start and end destination port values inclusive. Values 1 to 65535 (decimal) fragment Syntax fragment {true | false}...
  • Page 290 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 mask — Specifies the length in bits of the subnet mask. Values 1 to 32 ipv4-address-mask — Specifies the subnet mask in dotted decimal notation. Values a.b.c.d (dotted quad equivalent of mask length) ip-prefix-list —...
  • Page 291 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Description This command configures a VXLAN or VXLAN GPE VNI to be used as a SAP QoS policy match criterion. A range of VNIs to be matched can be specified by including the keyword range with a start and end VNI.
  • Page 292 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 type Syntax type filter-type no type Context config>qos>sap-ingress>ip-criteria config>qos>sap-ingress>ipv6-criteria Description This command sets the ip-criteria and ipv6-criteria type to control the type of match entries configurable in this context. Default type normal Parameters...
  • Page 293 RELEASE 15.1.R1 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. When ipv6- criteria entries are removed from a SAP ingress policy, the ipv6-criteria is removed from all services where that policy is applied.
  • Page 294 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 dst-ip Syntax dst-ip {ipv6-address/prefix-length | ipv6-address ipv6-address-mask} no dst-ip Context config>qos>sap-ingress>ipv6-criteria>entry>match config>qos>sap-egress>ipv6-criteria>entry>match Description This command configures a destination address range to be used as a SAP QoS policy match criterion.
  • Page 295 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Parameters true — Specifies to match on all fragmented IPv6 packets. A match will occur for all packets that contain an IPv6 Fragmentation Extension Header. false — Specifies to match on all non-fragmented IP packets. Non-fragmented IPv6 packets are packets that do not contain an IPv6 Fragmentation Extension Header.
  • Page 296 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description This command explicitly sets the forwarding class or subclass enqueuing priority when a packet is marked with a MPLS EXP bits specified. Adding a lsp-exp rule on the policy forces packets that match the MPLS LSP EXP specified to override the forwarding class and enqueuing priority based on the parameters included in the lsp-exp rule.
  • Page 297 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 298 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The no form of this command deletes all the entries specified under this node. When mac- criteria entries are removed from a SAP ingress policy, the mac-criteria is removed from all services where that policy is applied.
  • Page 299 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 This new criterion only takes effect when applied to a VPI SAP of an Apipe VLL service of type atm-vpc. The application of this criterion to the ATM SAP of any other ATM VLL service, any other VLL service, VPLS service, or IES/VPRN service has no effect.
  • Page 300 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Format Style Format Syntax Example Hexadecimal Binary 0bBBB 0b100 To select a range from 4 up to 7, specify p-value of 4 and a mask of 0b100 for value and mask.
  • Page 301 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 dst-mac Syntax dst-mac ieee-address [ieee-address-mask] no dst-mac Context config>qos>sap-ingress>mac-criteria>entry>match Description Configures a destination MAC address or range to be used as a Service Ingress QoS policy match criterion. The no form of this command removes the destination MAC address as the match criterion.
  • Page 302 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The snap-pid field, etype field, ssap, and dsap fields are mutually exclusive and cannot be part of the same match criteria. The no form of this command removes the previously entered etype field as the match criteria.
  • Page 303 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Context config>qos>sap-ingress>mac-criteria>entry>match Description This command configures the matching of the first tag that is carried transparently through the service. Service delimiting tags are stripped from the frame and the outer tag on ingress is the first tag after any service delimiting tags.
  • Page 304 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Context config>qos>sap-ingress>mac-criteria>entry>match Description Configures an IEEE 802.3 LLC SNAP Ethernet frame PID value to be used as a service ingress QoS policy match criterion. This is a 2-byte protocol id that is part of the IEEE 802.3 LLC SNAP Ethernet Frame that follows the 3-byte OUI field.
  • Page 305 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 To configure all packets with a source MAC OUI value of 00-03-FA to be subject to a match condition, the entry should be specified as: 003FA000000 0xFFFFFF000000 Values 0x00000000000000 to 0xFFFFFFFFFFFF (hex) Default 0xFFFFFFFFFFFF (hex) (exact match)
  • Page 306 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description This command sets the mac-criteria type. Default type normal Parameters filter-type — Specifies which type of entries this MAC filter can contain. Values normal — Regular match criteria are allowed; ISID match not allowed.
  • Page 307 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 The no form of this command is used to delete a policer from a sap-ingress or sap-egress QoS policy. The specified policer cannot currently have any forwarding class mappings for the removal of the policer to succeed.
  • Page 308 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The no form of this command is used to return the policer’s metering and profiling hardware adaptation rules to closest. Parameters pir {max | min | closest} — When the optional pir parameter is specified, the max, min, or closest keyword qualifier must follow.
  • Page 309 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 When a policy is created, it may be applied to a queue or policer defined within a sap-egress or sap-ingress QoS policy. It may also be applied to a queue or policer defined within an ingress or egress queue-group template.
  • Page 310 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 kilobyte high-prio-only Syntax high-prio-only percent-of-mbs no high-prio-only Context...
  • Page 311 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 The PIR bucket’s violate threshold represents the maximum burst tolerance allowed by the policer. If the policer's offered rate is equal to or less than the policer's defined rate, the PIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load.
  • Page 312 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The policer’s packet-byte-offset defined in the QoS policy may be overridden on an sla- profile or SAP where the policy is applied. Packet byte offset settings are not included in the applied rate when (queue) frame-based accounting is configured and the policer is managed by HQoS;...
  • Page 313 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 314 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 root — The root keyword specifies that the policer is intended to become a child to the root arbiter where an instance of the policer is created. If the root arbiter does not exist, the policer will be placed in the orphan state.
  • Page 315 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 cir cir-percent — The cir keyword is optional and, when defined, the required cir-percent CIR parameter expresses the policer’s CIR as a percentage of the immediate parent root policer/arbiter rate or the FP capacity. Values Percentage ranging from 0.00 to 100.00 Default...
  • Page 316 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 If a packet arrives at the policer while the bucket’s depth is less than the threshold associated with the packet, the packet is considered to be conforming to the bucket’s rate. If the bucket depth is equal to or greater than the threshold, the packet is considered to be in the exception state.
  • Page 317 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 stat-mode Syntax stat-mode {no-stats | minimal | offered-profile-no-cir | offered-priority-no-cir | offered- profile-cir | offered-priority-cir | offered-total-cir | offered-limited-profile-cir | offered- profile-capped-cir | offered-limited-capped-cir} no stat mode Context config>qos>sap-ingress>dyn-policer config>qos>sap-ingress>policer Description...
  • Page 318 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 33 Ingress Policer Stat Mode Summary (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded Minimal Single counter Single counter for — entering policer dropped/forwarded exiting policer offered-profile-no-...
  • Page 319 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 33 Ingress Policer Stat Mode Summary (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-profile- In/out/uncolored In/out exiting policer Intended for when capped-cir entering policer the policer has profile-capped...
  • Page 320 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The default stat-mode for a policer is minimal. The minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter.
  • Page 321 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 35 Ingress Accounting Statistics Collected in offered-profile-no-cir stat-mode Show Output Accounting Statistics Collected Field Field Description Off. InProf InProfilePacketsOffered InProfileOctetsOffered Off. OutProf OutOfProfilePacketsOffered OutOfProfileOctetsOffered Dro. InProf InProfilePacketsDropped InProfileOctetsDropped Dro.
  • Page 322 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 36 Ingress Accounting Statistics Collected in offered-priority-no-cir stat-mode Show Output Accounting Statistics Collected Field Field Description Off. HiPrio HighPriorityPacketsOffered HighPriorityOctetsOffered Off. LowPrio LowPriorityPacketsOffered LowPriorityOctetsOffered Dro. HiPrio HighPriorityPacketsDropped HighPriorityOctetsDropped Dro.
  • Page 323 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 37 Ingress Accounting Statistics Collected in offered-profile-cir...
  • Page 324 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 325 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 326 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 327 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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...
  • Page 328 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 When 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”...
  • Page 329 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 prec Syntax prec ip-prec-value [fc fc-name] [priority {high | low}] no prec ip-prec-value 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).
  • Page 330 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 A maximum of eight IP precedence rules are allowed on a single policy. The precedence is evaluated from the lowest to highest value. 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 331 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 queue Syntax queue queue-id [multipoint] [queue-type] [queue-mode] [create] 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 332 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The no form of this command removes the queue-id from the SAP ingress QoS policy and from any existing SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their default queues.
  • Page 333 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 queue-mode — Specifies the mode in which the queue is operating. This attribute is associated with the queue at the time of creation and cannot be modified thereafter. Values profile-mode: When the queue is operating in the profile mode (or the color aware mode), the queue tries to provide the appropriate...
  • Page 334 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 closest — The closest keyword is used to inform the system that the metering rate defined for the policer is the target rate. The system will choose a hardware supported rate that is closest to the specified rate.
  • Page 335 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Parameters size — Specifies an explicit burst limit size. The value is expressed as an integer and, by default, is interpreted as the burst limit in kilobytes. If the value is intended to be interpreted in bytes, the byte qualifier must be added following size.
  • Page 336 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters size-in-kbytes — The size parameter is an integer expression of the number of kilobytes reserved for the queue. If a value of 10 kbytes is desired, enter the value 10. A value of 0 specifies that no reserved buffers are required by the queue (a minimal reserved size can still be applied for scheduling purposes) The CBS maximum value used is constrained by the pool size in which the queue exists.
  • Page 337 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Context config>qos>sap-egress>queue>drop-tail Description This command enters the context to configure the queue highplus drop tail parameters. The highplus drop tail defines the queue depth beyond which inplus-profile packets will not be accepted into the queue and will be discarded.
  • Page 338 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters percent — Specifies the percentage reduction from the MBS for a queue drop tail. Values 0 to 100, default percent-reduction-from-mbs Syntax percent-reduction-from-mbs percent no percent-reduction-from-mbs Context config>qos>sap-ingress>queue>drop-tail>low Description This command configures the ingress SAP low drop tail as a percentage reduction from the MBS of the queue.
  • Page 339 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Parameters weight — Specifies the weight of the scheduling class. Values 1, 2, 4, 8 hs-wred-queue Syntax hs-wred-queue [policy slope-policy-name] no hs-wred-queue Context config>qos>sap-ingress>queue Description This command configures the WRED queue. The no form of the command reverts to the default.
  • Page 340 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description The Maximum Burst Size (MBS) command defines the maximum amount of buffers allowed for a specific queue. The value is given in bytes or kilobytes and overrides the default value for the context.
  • Page 341 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Description This command modifies the size of each packet handled by the queue by adding or subtracting the specified number of bytes. The actual packet size is not modified; only the size used to determine the ingress scheduling and profiling is changed.
  • Page 342 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 If the scheduler-name does not exist, the queue is placed in the orphaned operational state. The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP.
  • Page 343 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 level level — The optional level parameter defines the level of hierarchy when compared to other schedulers and queues when vying for bandwidth on the parent scheduler- name. Queues or schedulers will not receive parental bandwidth until all queues, policers, and schedulers with a higher (numerically larger) priority on the parent have reached their maximum bandwidth or are idle.
  • Page 344 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Description This command configures a queue's PIR and CIR rates as a percentage of the egress port line rate or as a percentage of its parent scheduler rate. When the rates are expressed as a port-limit, the actual rates used per instance of the queue will vary based on the port speed.
  • Page 345 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 local-limit — Specifies that the configure PIR and CIR percentages are relative to the rate of the queue’s parent scheduler rate or agg-rate rate at egress. pool Syntax [no] pool pool-name Context config>qos>sap-ingress>queue...
  • Page 346 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 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 maximum rate that the queue can transmit packets through the switch fabric (for SAP ingress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate.
  • Page 347 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 scope Syntax scope {exclusive | template} no scope Context config>qos>sap-ingress Description This command configures the Service Ingress QoS policy scope as exclusive or template. The policy’s scope cannot be changed if the policy is applied to a service. The no form of this command sets the scope of the policy to the default of template.
  • Page 348 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 count count — Specifies the number of entries in the range. Values 1 to 65535 5.6.2.2.2 Service Egress QoS Policy Forwarding Class Commands sap-egress Syntax sap-egress {policy-id | policy-name} [create] [name name] no sap-egress {policy-id | policy-name} Context config>qos...
  • Page 349 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Parameters policy-id — The policy-id uniquely identifies the policy on the router. Values 1 to 65535 policy-name — The policy-name uniquely identifies the policy. Values 64 characters maximum. create —...
  • Page 350 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 351 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 no dscp dscp-name [dscp-name...(up to 8 max)] Context config>qos>sap-egress Description This command defines IP Differentiated Services Code Point (DSCP) names that must be matched to perform the associated reclassification actions. The specified name must exist as a DSCP name.
  • Page 352 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The hsmda-counter-override keyword 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. By default, the HSMDA uses each queue’s default queue counters for packets mapped to the queue.
  • Page 353 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 af22 0101 0000 cp21 0101 0100 af23 0101 1000 cp23 0101 1100 0110 0000 cp25 0110 0100 af31 0110 1000 cp27 0110 1100 af32 0111 0000 cp29 0111 0100 af33 0111 1000 cp31...
  • Page 354 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 355 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Syntax fc fc-name [create] no fc fc-name Context config>qos>sap-egress Description The fc fc-name node within the SAP egress QoS policy is used to contain the explicitly defined queue mapping and dot1p marking commands for fc-name. When the mapping for fc-name points to the default queue and the dot1p marking is not defined, the node for fc- name is not displayed in the show configuration or save configuration output unless the detail option is specified.
  • Page 356 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters de-value — Specifies the DE marking value. Values 0 or 1 de-mark-inner Syntax de-mark-inner [force de-value] no de-mark-inner Context config>qos>sap-egress>fc Description This command is used to explicitly define the marking of the DE bit in the inner VLAN tag for fc fc-name on a QinQ SAP, according to the in- and out-of-profile status of the packet.
  • Page 357 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 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 358 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The command with the additional structure may be used on the SAP when the internal in, out, and exceed-profile status needs to be communicated to an access network or customer device that does not support the DE bit.
  • Page 359 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 The optional in-profile | dot1p-value out-profile dot1p-value parameters on the dot1p-inner command add the capability to mark the in-profile and out-of-profile status on an egress qinq SAP. The command with the additional parameters may be used on the SAP when the internal in-profile and out-of-profile status needs to be communicated to an access network or customer device that does not support the DE bit.
  • Page 360 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 no dot1p-outer Context config>qos>sap-egress>fc Description This command explicitly defines the egress outer or single VLAN tag IEEE 802.1p (dot1p) bits marking for fc-name. When the marking is set, all packets of fc-name that have either an outer or single IEEE 802.1q or IEEE 802.1p encapsulation on a qinq or a dot1p SAP, respectively, will use the explicitly defined dot1p-value.
  • Page 361 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 362 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 hsmda Syntax hsmda Context config>qos>sap-egress>fc Description This command defines how packets matching the forwarding class will be mapped to an HSMDA queue ID. The SAP QoS policies simultaneously support both standard service queue mappings and HSMDA queue mappings for the same forwarding class;...
  • Page 363 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 43 Default FC HSMDA Queue ID Mappings (Continued) Forwarding Class Default HSMDA Queue ID queue 2 queue 1 Table 44 describes how packets are mapped to queues based on the type of service and the various forwarding types.
  • Page 364 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 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. This is only used when the specific queue group instance is assigned at the time the qos policy is applied to the SAP.
  • Page 365 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 • If the policer policer-id command is successfully executed, the default egress queuing is performed for the forwarding class using the policer-output-queues queue group and the queue-id within the group based on the forwarding class map from the group template.
  • Page 366 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The no form of this command is used to restore the mapping of the forwarding class to the default queue. If all forwarding classes have been removed from the default queue, the queue will not exist on the SAPs or subscribers associated with the QoS policy and the no policer command will cause the system to attempt to create the default queue on each object.
  • Page 367 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 368 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 369 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 370 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 371 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 372 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 373 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 374 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 375 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 376 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The no form of this 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 377 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 378 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 379 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 380 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 381 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 382 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The no form of this command removes a port scheduler parent association for the policer. When 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 383 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 384 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The no form of this 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 385 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 All cir-weight values from all weighted active policers, queues, and schedulers with a common parent are added together. Then, each individual active weight is divided by the total to determine the percentage of remaining bandwidth provided to the policer, queue, or scheduler after the higher priority level children have been serviced.
  • Page 386 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 387 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 45 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 388 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 45 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 389 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 46 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 390 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 47 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 391 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 48 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 392 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 49 Egress Accounting Statistics Collected in offered-total-cir stat-...
  • Page 393 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 394 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 395 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 51 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 396 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 52 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 397 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 53 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 398 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 399 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 54 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 400 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 401 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 402 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 403 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 404 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 405 — 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 406 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Parameters default — Reverts the queue's burst limit to the system default value. size — Specifies an explicit burst limit size. The value is expressed as an integer and by default is interpreted as the burst limit in kilobytes.
  • Page 407 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Parameters add bytes — The add keyword is mutually exclusive to the subtract keyword. Either parameter must be specified. When add is defined, the corresponding bytes parameter specifies the number of bytes that is added to the size of each packet associated with the queue for scheduling and accounting purposes.
  • Page 408 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 rate parameters and will not be controlled by a virtual scheduling context. If an instance of a queue is on a port or channel that has a port scheduler configured and the sap-egress policy defines the queue as having a non-existent intermediate scheduler parent, the queue will be treated as an orphan and will be handled according to the current orphan behavior on the port scheduler.
  • Page 409 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Context config>qos>sap-egress>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 maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues).
  • Page 410 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 wred-queue Syntax wred-queue [policy slope-policy-name] [mode mode] [slope-usage slope-usage] no wred-queue Context config>qos>sap-egress>queue Description This command allows the configuration of WRED per queue with the following options: • Native hardware WRED This uses the hardware per queue WRED capabilities of the FP3 and is configured with the native keyword.
  • Page 411 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.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 to 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 is automatically moved to its own WRED pool.
  • Page 412 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.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 413 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 ip-prefix-list Syntax ip-prefix-list ip-prefix-list-name [create] no ip-prefix-list ip-prefix-list-name Context config>qos>match-list Description This command creates a list of IPv4 prefixes for match criteria in QoS policies. An ip-prefix-list must contain only IPv4 address prefixes created using the prefix command and cannot be deleted if it is referenced by a QoS policy.
  • Page 414: Show Commands

    Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 5.6.2.3 Show Commands Note: For consistency across 7950 XRS platforms, C-XMAs/XMAs are modeled in SR OS (CLI and SNMP) as MDAs. The command outputs in the following section are examples only; actual displays may differ depending on supported functionality and user configuration.
  • Page 415 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Each Q-chip based forwarding plane maintains 7 Burst Control Groups, each targeting a certain queue bucket visitation time. A 40 ms, 20 ms, 10 ms, 5 ms, 1 ms, 500 µs, and 100 µs BCG is supported.
  • Page 416 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 port port-id — Specifies that the system should find and display the BCG and calculate the slowest accurate visitation time for the queues associated with the specified port- id.
  • Page 417 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Description The show qos queue command outputs the Burst Control Group (BCG) name and slowest accurate visitation time for the specified queues. For each queue specified, the system may find multiple hardware queues. This may be true for ingress queues on multipoint services (VPLS, IES, VPRN) or for queues created on an Ethernet Link Aggregation Group (LAG).
  • Page 418 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 sap-egress Syntax sap-egress [policy-id] [association | match-criteria | hsmda | detail] Context show>qos Description This command displays SAP egress QoS policy information. Parameters policy-id — Displays information about the specific policy ID. Values 1 to 65535 detail —...
  • Page 419 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 closest closest None closest closest ------------------------------------------------------------------------------- FC Name Queue-id Explicit/Default ------------------------------------------------------------------------------- Explicit (7) ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 1 (VPRN) Customer-Id - SAP : 1/1/10:1 SLA Profiles : - test override -------------------------------------------------------------------------------...
  • Page 420 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 ip-prefix-list "ip-prefix-list-1" create description "IPv4 prefix list" prefix 10.0.0.0/8 prefix 192.168.0.0/16 exit exit exit #-------------------------------------------------- echo "QoS Policy Configuration" #-------------------------------------------------- sap-egress 10 create queue 1 create exit queue 2 create exit fc af create queue 2...
  • Page 421 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 55 Show QoS SAP Egress Output Fields Label Description Policy-Id The ID that uniquely identifies the policy. Scope Exclusive Implies that this policy can only be applied to a single SAP. Template Implies that this policy can be applied to multiple SAPs on the router.
  • Page 422 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 55 Show QoS SAP Egress Output Fields (Continued) Label Description (Continued) PIR Rule The operational PIR for the queue will be equal to or greater than the administrative rate specified using the rate command. The operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
  • Page 423 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 55 Show QoS SAP Egress Output Fields (Continued) Label Description (Continued) FC Name Specifies the forwarding class queue mapping or dot1p marking is to be edited. Queue-id Specifies the queue-id that uniquely identifies the queue within the policy.
  • Page 424 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Sample Output show qos sap-ingress =============================================================================== Sap Ingress Policies =============================================================================== Policy-Id Scope Name Description ------------------------------------------------------------------------------- Template default Default SAP ingress QoS policy. Template 3:P2 Template Auto-created pcc-rule sap-ingres* ------------------------------------------------------------------------------- Number of Policies : 3 -------------------------------------------------------------------------------...
  • Page 425 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Source IP : Undefined Dest. IP : 192.168.0.1/32 Source Port : None Dest. Port : None Protocol : tcp DSCP : cp60 Fragment : Off : h2 Priority : Default Policer : n/a...
  • Page 426 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Prio 1500 1500 VPN_video closest closest def Prio 2500 2500 VPN_voice closest closest def Prio VPN_nc closest closest def Prio 11000 VPN_be closest closest def Prio 11000 VPN_prio* closest closest def Prio...
  • Page 427 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 ------------------------------------------------------------------------------- Entry : 10 Description : Entry 10-FC-AF Source IP : 10.10.10.104/24 Source Port : None Dest. IP : Undefined Dest. Port : None Protocol DSCP : None Fragment : Off : af...
  • Page 428 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 No Dot1p-Map Entries Found. ------------------------------------------------------------------------ DSCP Priority ------------------------------------------------------------------------ No DSCP-Map Entries Found. ------------------------------------------------------------------------ Prec Value Priority ------------------------------------------------------------------------ No Prec-Map Entries Found. ------------------------------------------------------------------------ Match Criteria ------------------------------------------------------------------------ No Matching Criteria. ------------------------------------------------------------------------ Associations ------------------------------------------------------------------------...
  • Page 429 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 56 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) Priority Specifies the enqueuing priority when a packet is marked with a dot1p-value specified. Criteria-type Specifies that an IP criteria-based SAP ingress policy is used to select the appropriate ingress queue and corresponding forwarding class for matched traffic.
  • Page 430 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 56 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) PIR Rule The operational PIR for the queue will be equal to or greater than the administrative rate specified using the rate command. The operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
  • Page 431 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 56 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) Dot1p Specifies the forwarding class or enqueuing priority when a packet is marked with a dot1p-value specified. Specifies the forwarding class overrides.
  • Page 432 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 56 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) UnknownQ Specifies the default unknown unicast forwarding type queue mapping. Match Criteria Specifies an IP or MAC criteria entry for the policy. Entry Source IP Specifies a source IP address range used for an ingress SAP...
  • Page 433: Debug Commands

    QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Table 56 Show QoS SAP Ingress Output Fields (Continued) Label Description (Continued) SSAP Specifies an Ethernet 802.2 LLC DSAP value or range for an ingress SAP QoS policy match. Specifies the entry’s forwarding class.
  • Page 434 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 This command, when used with the network, sap-egress, or sap-ingress parameters, displays the match-criteria entries not programmed for a specified QoS policy due to an overload condition. Parameters card slot-number —...
  • Page 435 QUALITY OF SERVICE GUIDE Service Ingress and Egress QoS Policies RELEASE 15.1.R1 Slot Type Policy Entry ------------------------------------------------ IPv4 1001 IPv4 1002 ================================================i Issue: 01 3HE 13639 AAAA TQZZA 01...
  • Page 436 Service Ingress and Egress QoS Policies QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 437: 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 438: Queue Group Applications

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 439: Ingress Per Sap Statistics With Ingress Queue Groups

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 The preceding 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 440: Ingress Access Port Queue Group Hardware Queue Allocation

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 441: Network Port Queue Groups For Ip Interfaces

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 442 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 443: Qos On Ingress Bindings

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 444: Vxlan Vni Queue Group Redirection

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 445: Queue Group Redirect List

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 446 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 447 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 448: Queue Group Redirect List Example

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 449 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 450 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 ------------------------------------------------------------------------------- Service Associations ------------------------------------------------------------------------------- Service ID Service Type ------------------------------------------------------------------------------- 1/1/1 (Ingress/Egress) ------------------------------------------------------------------------------- =============================================================================== A:PE# 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 451: Queue Group Templates

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 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 452: Port Queue Groups

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 6.4 Port Queue Groups When an ingress or egress queue group template is defined, a port-based queue group with the same name may be created. Port queue groups are named objects that act as a container for a group of queues.
  • Page 453: Forwarding Plane Queue Groups

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 6.5 Forwarding Plane Queue Groups Ingress forwarding plane queue groups allow groups of SAPs on one or more ports, or on a LAG on the IOM, IMM, or XMA, to be bundled together from a QoS enforcement perspective with an aggregate rate limit to be enforced across all SAPs of a bundle.
  • Page 454: Redirection Models

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 6.6 Redirection Models Two models are supported for forwarding class redirection. In the first, the actual instance of a queue group to use for forwarding class redirection is named in the QoS policy.
  • Page 455: Access Sap Forwarding Class-Based Redirection

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 456 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 457: Ingress And Egress Sap Forwarding Class Redirection Association Rules

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 458 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 459 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 If the preceding 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 460: Sap-Based Provisioning Model

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 461: Access Queue Group Statistics

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 462: Forwarding Plane Queue Groups

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 463 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 6.8 Network IP Interface Forwarding Class-Based Redirection Forwarding class redirection for a network IP interface is defined in a four step process. 1. Create an ingress or egress queue group template with the appropriate queues or policers.
  • Page 464 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 • If a redirection queue ID within the policy does not exist within the egress queue group template, the QoS policy application will fail. • If the IP interface is bound to a port (or LAG) and the specified queue group name does not exist on the port, the QoS policy application will fail.
  • Page 465: Egress Network Ip Interface Statistics

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 • If the specified egress queue group does not exist on the port, the port binding will fail. If the preceding operation is successful: • The system increments the association counter for the queue group on the port. When an IP interface associated with a queue group is unbound from a port: •...
  • Page 466: Pw Shaping

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 6.9 PW Shaping 6.9.1 Ingress PW Shaping Using Spoke-SDP Forwarding Class-Based Redirection 6.9.1.1 Feature Configuration The user applies a network QoS policy to the ingress context of a spoke-SDP to redirect the mapping of a Forwarding Class (FC) to a policer defined in a queue- group template that is instantiated on the ingress Forwarding Plane (FP) where the PW packets are received.
  • Page 467: Provisioning Model

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 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). However, the queue- group is explicitly named only at the time the network QoS policy is applied to the spoke-SDP, as shown in the preceding example of the VPRN service.
  • Page 468 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 1. Only a queue-group containing policers can be instantiated in the network ingress context of an IOM/IMM FP. If the queue-group template contains policers and queues, the queues are not instantiated. 2.
  • Page 469: Ingress Packet Classification

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 a. This behavior is the same regardless of whether the ingress network IP interface from which the PW packet is received is redirected or not to a policer queue-group. 10. If no network QoS policy is applied to the ingress context of the PW, then all packets of the PW feed: a.
  • Page 470: Feature Configuration

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 471: Provisioning Model

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 config>qos>network>egress>fc>port-redirect-group policer policer-id queue queue-id 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.
  • Page 472 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 5. A user attempt to instantiate the queue-group on the network egress context of a POS port or a TDM port will fail. 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 473: Egress Marking Of Pw Packet Header

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 474 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 475: Queue Group Behavior On Lag

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 6.10 Queue Group Behavior on LAG 6.10.1 Queue Group Queue Instantiation Per Link When a port queue group is created on a Link Aggregation Group (LAG) context, it is individually instantiated on each link in the LAG. 6.10.2 Per-Link Queue Group Queue Parameters The queue parameters for a queue within the queue group are used for each port queue and are not divided or split between the port queues representing the queue...
  • Page 476: Removing A Queue Group From A Lag

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 6.10.5 Removing a Queue Group from a LAG A queue group must be removed from the primary port of the LAG. The queue group will be deleted by the system from each of the port members of the LAG. 3HE 13639 AAAA TQZZA 01 Issue: 01...
  • Page 477: Basic Configurations

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 6.11 Basic Configurations 6.11.1 Configuring an Ingress Queue Group Template The following displays an ingress queue group template configuration example: *A:Dut-T>cfg>qos>qgrps# info ---------------------------------------------- ingress queue-group "QG_ingress_1" create queue 1 best-effort create mbs 100 exit queue 2 best-effort create...
  • Page 478 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 exit queue 3 best-effort create mbs 100 exit queue 4 best-effort create mbs 100 exit exit exit ---------------------------------------------- *A:Dut-T>cfg>qos>qgrps# 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 ----------------------------------------------...
  • Page 479: Configuring Sap-Based Egress Queue Redirection

    QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 6.11.4 Applying Egress Queue Group to SAP Egress Policy The following displays a SAP egress policy configuration with group queue-group- name specified: A:Dut-T>config>qos>sap-egress# info ---------------------------------------------- queue 1 create exit fc af create queue 2 group "QG_egress_1"...
  • Page 480 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 queue 3 port-redirect-group-queue exit exit fc ef create policer 8 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue exit exit fc h1 create queue 3 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue exit exit fc h2 create queue 3 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue...
  • Page 481 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 6.11.6 Configuring Queue Group on Ethernet Access Ingress Port The provisioning steps involved in using a queue-group queue on an ingress port are: • Queue Group Template Creation − Create the queue group template in the ingress context −...
  • Page 482: Configuring Overrides

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 ---------------------------------------------- *A:Dut-T>config>port# *A:Dut-T>config>port# /configure port 9/2/2 *A:Dut-T>config>port# info ---------------------------------------------- ethernet mode access access ingress queue-group "QG_ingress_1" create exit exit egress queue-group "QG_egress_1" create exit exit exit exit no shutdown ---------------------------------------------- *A:Dut-T>config>port# 6.11.7 Configuring Overrides The following output displays a port queue group queue override example.
  • Page 483 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 access ingress queue-group "QG_ingress_1" create exit exit egress queue-group "QG_egress_1" create queue-overrides queue 3 create rate 1500000 cir 2000 exit exit exit exit exit exit no shutdown ---------------------------------------------- *A:Dut-T>config>port# 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:...
  • Page 484 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 − Identify or create the egress SAP requiring forwarding class redirection to the queue group − Assign the QoS policy to the SAP For SAP-based redirection: • Map a Forwarding Class to the queue-id within the queue group −...
  • Page 485 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 − Map the desired egress forwarding classes within the network QoS policy to the specific queue IDs and/or policer IDs within the group (the group name will be supplied when the QoS policy is applied to the IP interface). •...
  • Page 486 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 6.11.11 Using Queue Groups to Police Ingress/Egress Traffic on Network Interface An example of the provisioning steps involved in using a queue-group to police ingress and egress traffic on a network interface is as follows: config queue-group-templates ingress...
  • Page 487 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 ethernet mtu 1514 network egress queue-group "Egress_QG_1" instance 550 create exit exit exit exit no shutdown exit router interface “to-D” address 10.10.11.3/24 port 1/1/3 qos 2 egress-port-redirect-group "Egress_QG_1" egress-instance 550 ingress-fp-redirect-group "Ingress_QG_1" ingress-instance no shutdown 6.11.12 Configuring Ingress/Egress PW Shaping Using Spoke-SDP Forwarding Class-Based Redirection...
  • Page 488 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 policer 2 create exit policer 3 create exit policer 4 create exit exit exit exit exit network 10 create ingress lsp-exp 0 fc be profile out lsp-exp 1 fc be profile out lsp-exp 2 fc be profile out lsp-exp 3 fc be profile out lsp-exp 4 fc be profile out...
  • Page 489 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 exit exit exit exit exit #-------------------------------------------------- echo "Port Configuration" #-------------------------------------------------- port 3/2/1 ethernet encap-type dot1q network egress queue-group "QGEgr1" instance 1 create exit queue-group "QGEgr1" instance 2 create exit exit exit exit no shutdown...
  • Page 490: Specifying Qos Policies On Service Saps

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 static-mac 00:00:28:00:01:02 create no shutdown exit no shutdown exit router interface "ip-192.168.0.0" address 192.168.0.0/24 port 3/2/1:1 exit interface "system" address 192.168.0.1/32 exit #--------------------------------------------- 6.11.13 Specifying QoS Policies on Service SAPs The following output displays a VPLS service configuration example.
  • Page 491: Command Hierarchies

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

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 493 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 — no hs-attachment-policy — [no] hs-wrr-group group-id — adaptation-rule [pir adaptation-rule] — no adaptation-rule — hs-class-weight weight — no hs-class-weight — percent-rate percent — no percent-rate — rate rate — no rate —...
  • Page 494 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 | offered-four-profile-no- cir | offered-total-cir-four-profile} — no stat-mode — [no] queue queue-id [queue-type] [create] —...
  • Page 495: Configuring Vxlan Vni Queue Group Redirection

    [ingress | egress] [queue-group-name] [{statistics | associations}] 6.12.1.5 Monitor Commands For more information about monitor commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide for command usage and CLI syntax. Issue: 01...
  • Page 496: Command Descriptions

    Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 monitor — card slot-number fp fp-number ingress {access | network} queue-group queue-group-name instance instance-id [interval seconds] [repeat repeat] policer policer-id [absolute | percent-rate | reference-rate] — qos — arbiter-stats — card slot-number fp fp-number queue-group queue-group-name instance instance-id [ingress] [access | network] [interval seconds] [repeat repeat]...
  • Page 497 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Parameters description-string — The description character string. Allowed values are any string up to 80 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
  • Page 498 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The queue-group-name parameter is required when executing the queue-group command and identifies the name of the template to be either created or edited. Each ingress queue group template must be uniquely named within the system. Multiple ingress queue group templates may not share the same name.
  • Page 499 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Parameters policer-id — The policer-id must be specified when executing the policer command. If the specified ID already exists, the system enters that policer's context to allow the policer’s parameters to be modified. If the ID does not exist and is within the allowed range for the QoS policy type, a context for the policer ID will be created (depending on the system's current create keyword requirements, which may require the create keyword to actually add the new policer ID to the QoS policy) and the system will...
  • Page 500 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 closest — The closest parameter is mutually exclusive with the min and max parameter. When closest is defined, the operational PIR for the queue will be the rate closest to the rate specified using the rate command.
  • Page 501 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Minimum configurable non-zero value - 6 kbytes on an FP2 and 7680 bytes on an Minimum non-zero default value - maximum of 10 ms of CIR or 6 kbytes on an FP2 and 7680 bytes on an FP3 Values Policers: 0 to 16777216 or default...
  • Page 502 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The sum of the MBS for all queues on an ingress access port can oversubscribe the total amount of buffering available. When congestion occurs and buffers become scarce, access to buffers is controlled by the RED slope that a packet is associated with. A queue that has not exceeded its MBS size is not guaranteed that a buffer will be available when needed or that the packet’s RED slope will not force the discard of the packet.
  • Page 503 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Parameters size — For queues, the size parameter is an integer expression of the maximum number of bytes or kilobytes of buffering allowed for the queue. For a value of 100 kbytes, enter the value 100.
  • Page 504 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 505 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 root — The root keyword specifies that the policer is intended to become a child to the root arbiter where an instance of the policer is created. If the root arbiter does not exist, the policer will be placed in the orphan state.
  • Page 506 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 The CIR defines the rate at which the system prioritizes the queue or policer over other queues or policer competing for the same bandwidth. In-profile, then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse.
  • Page 507 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 profile-capped-cir | offered-limited-capped-cir} no stat mode Context cfg>qos>qgrps>ing>qgrp>policer Description This command is used to configure the forwarding plane counters that allow offered, forwarded, and dropped accounting to occur for the policer. An ingress policer has multiple types of offered packets (explicit in-profile, explicit out-of-profile, uncolored, high-priority or low-priority) and each of these offered types is interacting with the policer’s metering and profiling functions resulting in colored output packets (green, yellow, and red).
  • Page 508 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 57 Stat Mode Descriptions (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-profile-no- In/out entering In/out entering Intended for when policer policer the policer does not change the profile of packets.
  • Page 509 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Table 57 Stat Mode Descriptions (Continued) Stat Mode Stat Resources Traffic Counters (Packet/Octets) Comments Offered Dropped/ Forwarded offered-limited- In/uncolored In/out exiting policer Intended for when capped-cir entering policer the policer has profile-capped configured.
  • Page 510 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 58 Ingress Accounting Statistics Collected in minimal stat-mode...
  • Page 511 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Table 59 Ingress Accounting Statistics Collected in offered-profile-no-cir stat-mode (Continued) Show Output Accounting Stats Collected Field Field Description Off. OutProf OutOfProfilePacketsOffered OutOfProfileOctetsOffered Dro. InProf InProfilePacketsDropped InProfileOctetsDropped Dro. OutProf OutOfProfilePacketsDropped OutOfProfileOctetsDropped For.
  • Page 512 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 60 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 513 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 61 Ingress Accounting Statistics Collected in offered-profile-cir...
  • Page 514 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 515 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 516 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 517 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 518 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 519 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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. When created, the defined queue-id acts as a repository for the default parameters for the queue.
  • Page 520 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 521 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 522 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 523 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 524 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 525 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.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 526 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.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 527 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 528 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 queue Syntax queue queue-id no queue Context config>qos>queue-group-templates>egress>queue-group-template>fc Description This command is used to map the forwarding class to the specified queue-id. The specified queue-id must exist within the egress queue group template. When a queue is defined in a forwarding class mapping, that queue cannot be deleted unless the forwarding class mapping is moved to another queue within the template.
  • Page 529 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Parameters group-id — Specifies the HS WRR group identifier. WRR group ID 1 or 2 must be specified when executing the hs-wrr-group command. The specified group ID identifies which WRR group context will be entered for editing. Queue membership is not considered when editing WRR group parameters.
  • Page 530 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 hs-class-weight Syntax hs-class-weight weight no hs-class-weight Context cfg>qos>qgrps>egr>qgrp>hs-wrr-group Description This command specifies the class weight. The no form of the command reverts to the default value. Default hs-class-weight 1 Parameters weight —...
  • Page 531 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 packet-byte-offset Syntax packet-byte-offset {add bytes | subtract bytes} no packet-byte-offset Context config>qos>qgrps>egr>qgrp>queue config>qos>queue-group-templates>egress>queue-group>hsmda-queues cfg>qos>qgrps>egr>qgrp>policer 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 532 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 policer Syntax policer policer-id [create] no policer Context config>qos>queue-group-templates>egress>queue-group Description This command configures a QoS egress queue-group policer. Default none Parameters policer-id — This required parameter identifies the queue-group policer that will either be created or edited within the queue group template.
  • Page 533 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 forwarding plane for all possible offered packet types and output conditions. Many policers, for example, will not be configured with a CIR profiling rate and not all policers will receive explicitly reprofiled offered packets.
  • Page 534 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 67 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 exiting policer entering policer offered-limited- In/out entering In/out exiting policer Intended for when capped-cir...
  • Page 535 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Table 67 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/ Intended to be used four-profile entering policer exceed exiting when the policer can change the...
  • Page 536 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 68 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 — Counter resource allocation: 2 This stat-mode provides offered, dropped and forwarded packet and octet counters corresponding to the profile of traffic entering the policer.
  • Page 537 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 Table 69 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 538 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 Table 70 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. InProf InProfilePacketsDropped InProfileOctetsDropped Dro.
  • Page 539 QUALITY OF SERVICE GUIDE Queue Sharing and Redirection RELEASE 15.1.R1 The counters displayed in the show output and those collected when collect-stats is enabled are described in Table 71 (the actual fields collected depends on the record configured in the applied accounting policy). Table 71 Egress Accounting Statistics Collected in offered-total-cir stat- mode...
  • Page 540 Queue Sharing and Redirection QUALITY OF SERVICE GUIDE RELEASE 15.1.R1 This mode is intended to be used with profile-capped configured within the policer but without enable-exceed-pir configured as this could cause the traffic profile to be modified by the policer in a way that is not accounted for in the statistics. The counters displayed in the show output and those collected when collect-stats is enabled are described in Table 72...
  • Page 541