Page 1 7950 EXTENSIBLE ROUTING SYSTEM QUALITY OF SERVICE GUIDE RELEASE 14.0.R1 Alcatel-Lucent Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2016 © Alcatel-Lucent. All rights reserved.
Page 2 This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation.
Page 3: Table Of Contents
Table of Contents Getting Started............................15 About This Guide..............................15 Alcatel-Lucent SR-Series Router Services Configuration Process ..............15 QoS Policies ............................17 In This Chapter ..............................17 QoS Overview ..............................17 Forwarding Classes............................18 High Priority Classes ..........................19 Assured Classes ............................20 Best-Effort Classes ..........................20 Queue Parameters .............................21 Queue ID ..............................21...
Page 4 Table of Contents Scheduler Policies Applied to Applications ....................71 Scheduler Policies Applied to SAPs......................73 Customer Service Level Agreement (SLA) ....................74 Scheduler Policies Applied to Multi-Service Sites ...................74 Shared Queues .............................74 ATM Traffic Descriptor Profiles ........................75 Configuration Notes............................75 Network QoS Policies .......................... 77 In This Section..............................77 Overview................................77 Network Ingress Tunnel QoS Override ......................78...
Page 5 Table of Contents Editing QoS Policies............................160 Network Queue QoS Policy Command Reference...................161 Command Hierarchies..........................161 Configuration Commands ........................161 Operational Commands .........................162 Show Commands ...........................162 Command Descriptions ..........................162 Configuration Commands ........................162 Operational Commands .........................163 Show Commands ...........................185 Service Egress and Ingress QoS Policies..................189 In This Section..............................189 Overview................................190 Basic Configurations............................190...
Page 6 Table of Contents Service Ingress QoS Policy Commands ....................223 Service Egress QoS Policy Commands ....................227 Operational Commands .........................230 Show Commands ...........................231 Command Descriptions ..........................231 Configuration Commands ........................231 Operational Commands .........................232 Show Commands ...........................370 Queue Sharing and Redirection......................389 In This Section..............................389 Queue Sharing and Redirection ........................389 Supported Platforms............................390 Queue Group Applications ..........................390...
Page 7 Table of Contents Per Link Queue Group Queue Parameters ....................418 Adding a Queue Group to an Existing LAG....................418 Removing a Queue Group from a LAG .......................418 Adding a Port to a LAG ..........................419 Basic Configurations............................419 Configuring an Ingress Queue Group Template ..................419 Configuring Egress Queue Group Template ....................420 Applying Ingress Queue Group to SAP Ingress Policy ................420 Applying Egress Queue Group to SAP Egress Policy.................421...
Page 8 Table of Contents Limit Unused Bandwidth ........................527 Configuring Port Scheduler Policies ......................529 Port Scheduler Structure ........................529 Special Orphan Queue and Scheduler Behavior ...................529 Packet to Frame Bandwidth Conversion ....................530 Aggregate Rate Limits for Directly Attached Queues................531 SAP Egress QoS Policy Queue Parenting .....................531 Network Queue QoS Policy Queue Parenting ..................532 Egress Port Scheduler Overrides......................532 Applying a Port Scheduler Policy to a Virtual Port .................532...
Page 9 Table of Contents Default Slope Policy Values ........................625 Deleting QoS Policies..........................626 Ports ...............................626 MDA (FP1) .............................627 FP (FP2 and higher based hardware) ....................627 Remove a Policy from the QoS Configuration ..................628 Copying and Overwriting QoS Policies .......................628 Editing QoS Policies............................629 Slope QoS Policy Command Reference ......................631 Command Hierarchies..........................631 Configuration Commands ........................631...
Page 10 Table of Contents Advanced QoS Policy Command Reference....................675 Command Hierarchies..........................675 Configuration Commands ........................675 Operational Commands .........................675 Show Commands ...........................676 Command Descriptions ..........................676 Configuration Commands ........................676 Operational Commands .........................677 Show Commands ...........................690 QoS ATM Traffic Descriptor Profiles ....................691 In This Section..............................691 Overview................................691 ATM Traffic Descriptor Profiles ........................691 ATM Traffic Management........................691...
Page 11 Table of Contents Show Commands ...........................728 Command Descriptions ..........................728 Configuration Commands ........................728 Named Pool Policy Creation ........................729 Shared Queue QoS Commands ......................743 Network Queue QoS Policy Commands ....................746 Show Commands ...........................750 High Scale Ethernet MDA Capabilities ..................... 757 In This Section..............................757 HSMDA QoS Model............................757 Queue Scaling .............................758 Port-Based Scheduling..........................758...
Page 12 Table of Contents Strict Priority Level PIR ..........................789 Scheduler Maximum Rate ........................790 HSMDA Scheduler Policy Overrides ......................790 Orphan Queues............................790 Default HSMDA Scheduling Policy ......................790 Basic HSMDA Configurations ........................791 HSMDA Pool Policies..........................791 HSMDA Scheduler Policies........................792 HSMDA Slope Policies...........................793 Egress Queue Group ..........................793 Configuring HSMDA Queue Group Overrides ..................794 Applying HSMDA Policies ...........................794 HSMDA Command Reference .........................797...
Page 13 Table of Contents Explicit Arbiter Rate Limits ..........................856 CFHP with Child Policer Exceed PIR Enabled ...................856 CFHP Child Policer Definition and Creation .....................857 Policer Enabled SAP QoS Policy Applicability ....................858 Child Policer Parent Association ........................858 Profile Capped Policers ............................859 Policer Interaction with Initial Profile, Discard Eligibility, and Ingress Priority...........861 Ingress ‘Undefined’...
Page 14 Table of Contents Standards and Protocol Support ...................... 895 Quality of Service Guide...
Page 15: Getting Started
• 7950 XRS 7450 ESS applicability statements refer to the 7450 ESS when it is not running in mixed mode. 7750 SR applicability statements refer to the 7750 SR-7/12, 7750 SR-12e, 7750 SR- a4/a8 and 7750 SR-e1/e2/e3 platforms unless otherwise specified.
Page 16 Alcatel-Lucent SR-Series Router Services Configuration Process Table 1: Configuration Process Area Task Chapter Supported Platform Policy configuration Configuring QoS Policies Network Network QoS Policies Network queue Network Queue QoS Policies SAP ingress/SAP egress Service Egress and Ingress QoS Policies Scheduler...
Page 17: Qos Policies
QoS Policies In This Chapter This chapter provides information about Quality of Service (QoS) policy management. Topics in this chapter include: • QoS Overview → Forwarding Classes → Queue Parameters • QoS Policies → Service versus Network QoS → QoS Policy Entities →...
Page 18: Forwarding Classes
Alcatel Lucent service routers (such as the 7950 XRS, 7750 SR, 7750 SR MG and 7450 ESS) appear 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 19: High Priority Classes
QoS Policies Table 2: Forwarding Classes FC-ID FC Name DiffServ Class Type Notes Designatio Name Network High-Priority Intended for network control traffic Control High-1 Intended for a second network control class or delay/jitter sensitive traffic Expedited Intended for delay/jitter sensitive traffic High-2 Intended for delay/jitter sensitive traffic Low-1...
Page 20: Assured Classes
QoS Overview With a strict PHB at each network hop, service latency is mainly affected by the amount of high-priority traffic at each hop. These classes are intended to be used for network control traffic or for delay or jitter-sensitive services. If the service core network is over-subscribed, a mechanism to traffic engineer a path through the core network and reserve bandwidth must be used to apply strict control over the delay and bandwidth requirements of high-priority traffic.
Page 21: Queue Parameters
QoS Policies Queue Parameters This section describes the queue parameters provisioned on access and queues for QoS. The queue parameters are: • Queue ID • Unicast or Multipoint Queue • Queue Hardware Scheduler • Committed Information Rate • Peak Information Rate •...
Page 22: Queue Hardware Scheduler
Queue Parameters Queue Hardware Scheduler The hardware scheduler for a queue dictates how it will be scheduled relative to other queues at the hardware level. When a queue is defined in a service ingress or service egress QoS policy, it is possible to explicitly define the hardware scheduler to use for the queue when it is applied to a SAP.
Page 23: Peak Information Rate
QoS Policies 1. When defining the CIR for a queue, the value specified is the administrative CIR for the queue.The router has a number of native rates in hardware that it uses to determine the operational CIR for the queue. The user has some control over how the administrative CIR is converted to an operational CIR should the hardware not support the exact CIR and PIR combination specified.
Page 24: Adaptation Rule
Queue Parameters When defining the PIR for a queue, the value specified is the administrative PIR for the queue.The router has a number of native rates in hardware that it uses to determine the operational PIR for the queue. The user has some control over how the administrative PIR is converted to an operational PIR should the hardware not support the exact CIR and PIR values specified.
Page 25: Committed Burst Size
QoS Policies *A:PE# show pools 1/1/1 access-egress service 1 | match expression "PIR|CIR" Admin PIR : 403000 Oper PIR : 403200 Admin CIR : 401000 Oper CIR : 401600 *A:PE# *A:PE# configure qos sap-egress 10 queue 1 adaptation-rule pir max cir max *A:PE# *A:PE# show qos sap-egress 10 detail | match expression "Queue-Id|CIR Rule"...
Page 26: Maximum Burst Size
Queue Parameters Maximum Burst Size The maximum burst size (MBS) parameter specifies the maximum queue depth to which a queue can grow. This parameter ensures that a customer that is massively or continuously over-subscribing the PIR of a queue will not consume all the available buffer resources. For high-priority forwarding class service queues, the MBS can be relatively smaller than the other forwarding class queues because the high-priority service packets are scheduled with priority over other service forwarding classes.
Page 27: Hi-Low Priority Only Buffers
QoS Policies Hi-Low Priority Only Buffers Hi-low priority only buffers are defined on a queue and allow buffers to be reserved for traffic classified as high or low priority. When the queue depth reaches a specified level, only high and low priority traffic can be enqueued. The high/low priority only reservation for a queue is defined as a percentage of the MBS value.
Page 28: Native Queue Mode
Queue Parameters Table 3: WRED Per Queue Congestion Control Summary (Continued) In profile Exceed Wred- Slope Comments traffic profile profile queue usage traffic traffic Mode Pool/megapool/ High slope Low slope Exceed If slope shutdown, named-pool slope total pool size is used.
Page 29 QoS Policies slope-usage exceed-low exit exit exit exit sap-egress <policy-id> create queue <queue-id> [<queue-type>] [create] wred-queue [policy <slope-policy-name>] mode native slope-usage exceed-low exit exit Congestion control is provided by both the slope policy applied to the queue and the MBS tail drop.
Page 30 Queue Parameters CLI Config. Resv CBS : 30%(default) Resv CBS Step : 0% Resv CBS Max : 0% Amber Alarm Threshold: 0% Red Alarm Threshold : 0% ------------------------------------------------------------------------------- Queue-Groups ------------------------------------------------------------------------------- Queue-Group:Instance : policer-output-queues:1 ------------------------------------------------------------------------------- Utilization State Start-Avg Max-Avg Max-Prob ------------------------------------------------------------------------------- High-Slope Down Low-Slope...
Page 31: Pool Per Queue Mode
QoS Policies Start Average : 4680 KB Max Average : 6600 KB Max Probability : 80 % Curr Probability : 0 % ------------------------------------------------------------------------------- =============================================================================== =============================================================================== *A:PE# Pool per Queue Mode When pool per queue mode is used, the queue resides in its own pool which is located in the forwarding plane egress megapool.
Page 32 Queue Parameters 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 buffers in the Egress WRED megapool. In both cases the min and max values must be equal. The slope- policy defines the WRED slope parameters and the time average factor used on the megapool itself to handle congestion as the megapool buffers are used.
Page 33 QoS Policies • In profile maps to the high slope. • Out of profile maps to the low slope. • Exceed profile maps to the exceed slope. If the following SAP egress QoS policy is applied to SAP on an FP with the egress WRED megapool enabled: sap-egress 10 create queue 1 create...
Page 34: Packet Markings
Queue Parameters State : enabled Start Average : 8880 KB Max Average : 10800 KB Max Probability : 80 % Curr Probability : 0 % ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Low Slope Information ------------------------------------------------------------------------------- State : enabled Start Average : 7200 KB Max Average : 9120 KB Max Probability : 80 %...
Page 35: Queue Counters
QoS Policies The high/low priority feature allows a provider to offer a customer the ability to have some packets treated with a higher priority when buffered to the ingress queue. If the queue is configured with a hi-prio-only setting (setting the high priority MBS threshold higher than the queue’s low priority MBS threshold) a portion of the ingress queue’s allowed buffers are reserved for high priority traffic.
Page 36: Queue-Types
Queue Parameters • Counters for packets and octets transmitted out-of-profile Queue-Types 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. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy.
Page 37: Qos Policies
QoS Policies All non-profiled and profiled packets are forwarded through the same ingress access queue to prevent out-of-sequence forwarding. Profiled packets in-profile are counted against the total packets flowing through the queue that are marked in-profile. This reduces the amount of CIR available to non-profiled packets causing fewer to be marked in-profile.
Page 38 QoS Policies • Network queue (for ingress and egress) • ATM traffic descriptor profile • Scheduler • Shared queue • Slope Service ingress QoS policies are applied to the customer-facing Service Access Points (SAPs) and map traffic to forwarding class queues on ingress. The mapping of traffic to queues can be based on combinations of customer QoS marking (IEEE 802.1p bits, DSCP, and TOS precedence), IP and MAC criteria.
Page 39 QoS Policies Table 4: QoS Policy Types and Descriptions Policy Type Applied at… Description Page Service Ingress SAP ingress • Defines up to 32 forwarding class queues and Service queue parameters for traffic classification Ingress • Defines up to 31 multipoint service queues for Policies broadcast, multicast and destination unknown traffic in multipoint services...
Page 40: Service Versus Network Qos
QoS Policies Table 4: QoS Policy Types and Descriptions (Continued) Policy Type Applied at… Description Page Scheduler Customer multi- • Defines the hierarchy and parameters for each Scheduler service site scheduler Policies Service SAP • Defined in the context of a tier which is used to place the scheduler within the hierarchy •...
Page 41: Qos Policy Entities
QoS Policies The router supports four types of service and network QoS policies: • Service ingress QoS policies • Service egress QoS policies • Network QoS policies • Network Queue QoS policies QoS Policy Entities Services are configured with default QoS policies. Additional policies must be explicitly created and associated.
Page 42: Network Qos Policies
QoS Policies Default QoS policies maps 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 Network QoS Policies...
Page 43 QoS Policies • 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 44: Network Queue Qos Policies
QoS Policies Table 6: 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 Network Control af11 001010 - 10...
Page 45 QoS Policies • Maximum Buffer Size (MBS) as a percentage of the buffer pool • High Priority Only Buffers as a percentage of MBS • Peak Information Rate (PIR) as a percentage of egress port bandwidth • Committed Information Rate (CIR) as a percentage of egress port bandwidth Network queue policies are identified with a unique policy name which conforms to the standard router alphanumeric naming conventions.
Page 46 QoS Policies Table 7: Default Network Queue Policy Definition (Continued) Forwarding Class Queue Definition (Continued) High-2 (h2) Queue 5 • PIR = 100% • CIR = 100% • MBS = 50% • CBS = 10% • High-Prio-Only = 10% Low-1 (l1 Queue 4 •...
Page 47: Service Ingress Qos Policies
QoS Policies 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 48 QoS Policies Figure 4: Traffic Queuing Model for 3 Queues and 3 Classes Queue Depth: High Based on PIR andf FC Scheduler E E E Expedited Ingress Series - 1 B B A B A A E E E A A A Packet Match Assured...
Page 49 QoS Policies Table 8: Forwarding Class and Enqueuing Priority Classification Hierarchy Based on Rule Type Rule Forwarding Class Enqueuing Priority Comments prec ip-prec- Set when an fc-name Set when the priority Each ip-prec-value must be value exists in the policy. parameter is high or explicitly defined.
Page 50: Fc Mapping Based On Exp Bits At Vll/Vpls Sap
QoS Policies FC Mapping Based on EXP Bits at VLL/VPLS SAP Figure 5: Example Configuration — Carrier’s 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...
Page 51 QoS Policies Table 9: Forwarding Class Classification Based on Rule Type (Continued) Rule Forwarding Class Comments MAC criteria: Set when an fc-name exists in the When MAC criteria is specified, entry’s action. Otherwise, preserve entries are matched based on • Multiple entries per from the previous match.
Page 52 QoS Policies • IEEE 802.2 LLC DSAP value/mask • IEEE 802.3 LLC SNAP OUI zero or non-zero value • IEEE 802.3 LLC SNAP PID value • IEEE 802.1p value/mask • Source MAC address/mask • Destination MAC address/mask • EtherType value The MAC match criteria that can be used for an Ethernet frame depends on the frame’s format.
Page 53: Egress Forwarding Class Override
QoS Policies Note: When a SNAP header is present, the LLC header is always set to AA-AA Service ingress QoS policy ID 1 is reserved for the default service ingress policy. The default policy cannot be deleted or changed. The default service ingress policy is implicitly applied to all SAPs which do not explicitly have another service ingress policy assigned.
Page 54: Service Egress Qos Policies
QoS Policies The buffering, queuing, policing and remarking operation at the ingress and egress remain unchanged. Egress reclassification is possible. The profile processing is completely unaffected by overriding the forwarding class. When used in conjunction with QPPB (QoS Policy Propagation Using BGP), a QPPB assigned forwarding class takes precedence over both the normal ingress forwarding class classification rules and any egress forwarding class overrides.
Page 55 QoS Policies For accounting purposes, per-service statistics can be logged. When statistics from service ingress queues are compared with service egress queues, the ability to conform to per-service QoS requirements within the service core can be measured. The service core statistics are a major asset to core provisioning tools.
Page 56: Named Pool Policies
All traffic mapped to queue 1 with no marking 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 57 QoS Policies • Network pool • The number of named per-port pools is dependent on the number of ports the MDA supports which is variable per MDA type • 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 →...
Page 58: Slope Policies
QoS Policies After the IOM has been placed into named pool mode, a named pool policy must be associated with the ingress and egress contexts of the MDA or individual ports on the MDA for named pools to be created. There are no named pools that exist by default. Each time the default pool reserve, aggregate MDA pool limit or individual pool sizes is changed, buffer pool allocation must be re-evaluated.
Page 59: Red Slopes
QoS Policies Slope policies define the RED slope characteristics as a percentage of pool size for the pool on which the policy is applied. Default buffer pools exist (logically) at the port and XMA and MDA levels. Each physical port has two pool objects associated: •...
Page 60 QoS Policies When a queue depth exceeds the queue’s CBS, packets received on that queue must contend with other queues exceeding their CBS for shared buffers. To resolve this contention, the buffer pool uses two RED slopes to determine buffer availability on a packet by packet basis. A packet that was either classified as high priority or considered in-profile is handled by the high-priority RED slope.
Page 61 QoS Policies Figure 7: RED Slope Characteristics Max-Avg Probability Max-Prob Start-Avg 100% Average Utilization OSSG020 A RED slope itself is a graph with an X (horizontal) and Y (vertical) axis. The X-axis plots the percentage of shared buffer average utilization, going from 0 to 100 percent. The Y-axis plots the probability of packet discard marked as 0 to 1.
Page 62: Tuning The Shared Buffer Utilization Calculation
QoS Policies Tuning the Shared Buffer Utilization Calculation The router allows tuning the calculation of the Shared Buffer Average Utilization (SBAU) after assigning buffers for a packet entering a queue as used by the RED slopes to calculate a packet’s drop probability. The router implements a time average factor (TAF) parameter in the buffer policy which determines the contribution of the historical shared buffer utilization and the instantaneous Shared Buffer Utilization (SBU) in calculating the SBAU.
Page 63 QoS Policies Table 14: TAF Impact on Shared Buffer Average Utilization Calculation (Continued) Equates Shared Buffer Shared Buffer Average Instantaneous Utilization Portion Utilization Portion 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) 31/32 (0.96875) 1/64 (0.015625) 63/64 (0.984375) 1/128 (0.0078125)
Page 64: Slope Policy Parameters
QoS Policies Slope Policy Parameters The elements required to define a slope policy are: • A unique policy ID • The high, low, and exceed RED slope shapes for the buffer pool: the start-avg, max- avg and max-prob. • The TAF weighting factor to use for the SBAU calculation for determining RED slope drop probability.
Page 65: Scheduler Policies
QoS Policies Table 15: Default Slope Policy Definition (Continued) Parameter Description Setting Exceed (RED) Administrative state Shutdown slope start-avg 30% utilization max-avg 55% utilization max-prob 80% probability Time average factor Scheduler Policies A scheduler policy defines the hierarchy and all operating parameters for the member schedulers.
Page 66 QoS Policies Figure 9 depicts how child queues and schedulers interact with their parent scheduler to receive bandwidth. The scheduler distributes bandwidth to the children by first using each child’s CIR according to the CIR-level parameter (CIR L8 through CIR L1 weighted loops). The weighting at each CIR-Level loop is defined by the CIR weight parameter for each child.
Page 67: Virtual Hierarchical Scheduling
QoS Policies Virtual Hierarchical Scheduling Virtual hierarchical scheduling is a method that defines a bounded operation for a group of queues. One or more queues are mapped to a given scheduler with strict and weighted metrics controlling access to the scheduler. The scheduler has an optional prescribed maximum operating rate that limits the aggregate rate of the child queues.
Page 68: Tiers
QoS Policies Tiers In single tier scheduling, queues are scheduled based on the forwarding class of the queue and the operational state of the queue relative to the queue’s CIR and PIR. Queues operating within their CIR values are serviced before queues operating above their CIR values with “high-priority”...
Page 69 QoS Policies In single tier scheduling, queues are scheduled based on the Forwarding Class of the queue and the operational state of the queue relative to the queue’s Committed Information Rate (CIR) and Peak Information Rate (PIR). Queue’s operating within their CIR values are serviced before queue’s operating above their CIR values with “high-priority”...
Page 70 QoS Policies Queues associated with a single scheduler are serviced in a round robin method. If a queue reaches the configured PIR, the scheduler will not serve the queue until the transmission rate drops below the PIR. The router QoS features are flexible and allow modifications to the forwarding class characteristics and the CIR and PIR queue parameters.
Page 71: Scheduler Policies Applied To Applications
QoS Policies 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 Rate Limiting Scheduler Queue Scheduler Policies Applied to Applications A scheduler policy can be applied either on a SAP...
Page 72 QoS Policies Figure 11: Scheduler Policy on SAP and Scheduler Hierarchy Creation Hierarchical Schedulers Created Through Scheduler Policy Application To Individual SAP Scheduler Policy Ingress or Egress Forwarding Service Class Queue Weighted Rate Limiting Packet Scheduler Packet Forwarding Weighted Packet Class Rate Limiting Scheduler...
Page 73: Scheduler Policies Applied To Saps
QoS Policies 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 Forwarding Service Packet Class Queue...
Page 74: Customer Service Level Agreement (Sla)
Once a site is created, it must be assigned to the chassis slot or a port (except in the 7450 ESS- 1 model; the slot is automatically set to 1). This allows the system to allocate the resources necessary to create the virtual schedulers defined in the ingress and egress scheduler policies.
Page 75: Atm Traffic Descriptor Profiles
QoS Policies However, as a tradeoff, the total amount of traffic throughput at ingress of the node is reduced because any ingress packet serviced by a shared-queuing SAP is recirculated for further processing. When the node is only used for access SAPs, 5 Gbps ingress traffic is the maximum that can be processed without seeing packet drops at the MDA ingress.
Page 76 QoS Policies Quality of Service Guide...
Page 77: Network Qos Policies
Network QoS Policies In This Section This section provides information to configure network QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Default Network Policy Values • Service Management Tasks Overview The ingress component of the policy defines how DiffServ code points (DSCPs) and MPLS EXP bits are mapped to internal forwarding class and profile state.
Page 78: Network Ingress Tunnel Qos Override
Overview Network policy-id 1 exists as the default policy that is applied to all network interfaces by default. The network policy-id 1 cannot be modified or deleted. It defines the default DSCP- to-FC mapping and MPLS EXP-to-FC for the ingress. For the egress, it defines six forwarding classes which represent individual queues and the packet marking criteria.
Page 79 Network QoS Policies • IP ToS precedence mapping • IP ToS DSCP mapping • MPLS LSP EXP mapping The default QoS mapping always exists on an ingress IP interface and every received packet will be mapped to this default if another explicitly defined matching entry does not exist. A tunnel that terminates on the ingress IP interface (the node is the last hop for the tunnel) is evaluated based on the type of tunnel, IP GRE or MPLS LSP.
Page 80 Overview entry 10 create match dst-ip 10.0.0.1/32 exit action fc "h2" profile in exit Network Ingress IPv6 Match Criteria IPv6 match criteria classification is supported in the ingress section of a network QoS policy. The classification only applies to the outer IPv6 header of non-tunneled traffic, consequently the use of an ipv6-criteria statement in a network QoS policy is ignored for received traffic when the network QoS policy is applied on the ingress network IP interface in the following cases:...
Page 81: Qos For Self-Generated (Cpu) Traffic On Network Interfaces
Network QoS Policies Tunnel Termination QoS Override Operation Tunnel termination QoS override only applies to IP routing decisions once the tunnel encapsulation is removed. Non-IP routed packets within a terminating tunnel are ignored by the override and are forwarded as described in the Normal QoS Operation section.
Page 82 Overview The configuration of self-generated QoS is supported in the base router, VPRN, and management contexts. The default values for self-generated traffic on network interfaces are: • Routing protocols (OSPF, BGP, etc.) → Forwarding class: Network Control (NC) → DSCP value: NC1 (not applicable for ARP, IS-IS, and PPPoE) →...
Page 83 Network QoS Policies Table 18: Default QoS Values for Self-Generated Traffic (Continued) Protocol DSCP ND (NDIS) NTP/SNTP OSPF PECP PPPoE RADIUS AF41 RSVP sFlow SNMP AF41 SRRP AF41 Syslog AF41 TACACS+ AF41 Telnet AF41 TFTP AF41 Traceroute VRRP Note: ICMP echo requests (type 8) initiated from the router will use the DSCP value set by the sgt-qos command.
Page 84: Basic Configurations
Basic Configurations Default DSCP Mapping Table DSCP Name DSCP Value DSCP Value DSCP Value Label Decimal Hexadecimal Binary ============================================================= Default 0x00 0b000000 0x30 0b110000 0x38 0b111000 0x2e 0b101110 af11 0x0a 0b001010 assured af12 0x0c 0b001100 assured af13 0x0e 0b001110 assured af21 0x12 0b010010...
Page 85 Network QoS Policies • You can modify egress criteria to customize the forwarding class queues to be instantiated. Otherwise, the default values are applied. → Remarking — When enabled, this command remarks ALL packets that egress on the specified network port. The remarking is based on the forwarding class to DSCP and LSP EXP bit mapping defined under the egress node of the network QoS policy.
Page 86: Applying Network Policies
Basic Configurations dot1p dot1p-priority fc {fc-name} profile {in | out} dscp dscp-name fc {be | l2 | af | l1 | h2 | ef | h1 | nc} profile {in | out} ler-use-dscp lsp-exp lsp-exp-value fc fc-name profile {in | out} A:ALA-10:A:ALA-12>config>qos# info #------------------------------------------...
Page 87: Default Network Policy Values
Network QoS Policies Default Network Policy Values The default network policy for IP interfaces is identified as policy-id 1. Default policies cannot be modified or deleted. The following displays default network policy parameters: Table 19: Network Policy Defaults Field Default description Default network QoS policy.
Page 88 Basic Configurations Table 19: Network Policy Defaults (Continued) Field Default lsp-exp fc be profile out fc l2 profile in fc af profile out fc af profile in fc h2 profile in fc ef profile in fc h1 profile in fc nc profile in egress remarking...
Page 89 Network QoS Policies Table 19: Network Policy Defaults (Continued) Field Default lsp-exp-out-profile fc h1 dscp-in-profile dscp-out-profile lsp-exp-in-profile lsp-exp-out-profile fc h2 dscp-in-profile af41 dscp-out-profile af42 lsp-exp-in-profile lsp-exp-out-profile fc l dscp-in-profile af21 dscp-out-profile af22 lsp-exp-in-profile lsp-exp-out-profile fc l2 dscp-in-profile dscp-out-profile lsp-exp-in-profile lsp-exp-out-profile fc nc dscp-in-profile dscp-out-profile...
Page 90 Basic Configurations The following output displays the default configuration: A:ALA-49>config>qos>network# info detail ---------------------------------------------- description "Default network QoS policy." scope template ingress default-action fc be profile out no ler-use-dscp dscp be fc be profile out dscp ef fc ef profile in dscp cs1 fc l2 profile in dscp nc1 fc h1 profile in dscp nc2 fc nc profile in...
Page 91: Service Management Tasks
Network QoS Policies dot1p-out-profile 5 exit fc h1 dscp-in-profile nc1 dscp-out-profile nc1 lsp-exp-in-profile 6 lsp-exp-out-profile 6 dot1p-in-profile 6 dot1p-out-profile 6 exit fc h2 dscp-in-profile af41 dscp-out-profile af42 lsp-exp-in-profile 4 lsp-exp-out-profile 4 dot1p-in-profile 4 dot1p-out-profile 4 exit fc l1 dscp-in-profile af21 dscp-out-profile af22 lsp-exp-in-profile 3 lsp-exp-out-profile 2...
Page 92: Remove A Policy From The Qos Configuration
Service Management Tasks You can replace the default policy with a non-default policy, but you cannot remove default policies from the configuration. When you remove a non-default policy, the policy association reverts to the appropriate default network policy. CLI Syntax: config>router interface interface-name qos network-policy-id...
Page 93: Copying And Overwriting Network Policies
Network QoS Policies Copying and Overwriting Network Policies You can copy an existing network policy to a new policy ID value or overwrite an existing policy ID. The overwrite option must be specified or an error occurs if the destination policy ID exists.
Page 94: Editing Qos Policies
Service Management Tasks dscp nc2 fc nc profile in dscp af11 fc af profile in dscp af12 fc af profile out dscp af13 fc af profile out dscp af21 fc l1 profile in dscp af22 fc l1 profile out --------------------------------------------- A:ALA-12>config>qos# Editing QoS Policies You can change existing policies, except the default policies, and entries in the CLI.
Page 95: Network Qos Policy Command Reference
Multi-Class Frame-Relay Profile Commands • Operational Commands • Show Commands Configuration Commands Multi-Class Frame-Relay Profile Commands The commands listed in this section apply only to the 7450 ESS and 7750 SR. config — qos — [no] mc-fr-profile-ingress profile-id — description description-string —...
Page 96 Network QoS Policy Command Reference — [no] fc-name — de-mark [force de-value] — no de-mark — dot1p dot1p-priority — no dot1p — dot1p-in-profile dot1p-priority — no dot1p-in-profile — dot1p-out-profile dot1p-priority — no dot1p-out-profile — dscp-in-profile dscp-name — no dscp-in-profile — dscp-out-profile dscp-name —...
Page 97: Self-Generated Traffic Commands
Network QoS Policies — dst-port {lt | gt | eq} dst-port-number — dst-port range start end — no dst-port — fragment start end — no fragment — src-ip {ip-address/mask | ip-address ipv4-address- mask | ip-prefix-list prefix-list-name]} — no src-ip — src-port {lt | gt | eq} src-port-number —...
Page 98: Operational Commands
Network QoS Policy Command Reference — router — 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 — no dscp dscp-name Operational Commands config — qos —...
Page 99: Command Descriptions
Network QoS Policies Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>network policy-id Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.
Page 100 Default QoS policies are configured with template scopes. An error is generated if you try to modify the template scope parameter to exclusive scope on default policies. Multi-Link Frame Relay Commands The commands described in this section apply only to the 7450 ESS and 7750 SR. mc-fr-profile-ingress Syntax...
Page 101 Network QoS Policies 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. A maximum of 128 ingress QoS profiles may be created on the system. The no form of this command deletes the profile.
Page 102 Network QoS Policy Command Reference mc-fr-profile-egress Syntax [no] mc-fr-profile-egress profile-id Context config>qos Description This command creates a profile for the user to configure the egress QoS parameters of an MLFR bundle or an FRF.12 UNI/NNI link. A maximum of 128 egress QoS egress profile may be created on the system.
Page 103 Network QoS Policies Default 90% for all classes Parameters mir — Specifies the percentage of the available link or bundle rate. Values 1 to 100 weight Syntax weight weight no weight Context config>qos>mc-fr-profile-egress>class Description This command configures the WRR weight scheduling parameter for each Frame Relay scheduling class queue for this profile.
Page 104 Network QoS Policy Command Reference The egress component of the network QoS policy defines the queuing parameters associated with each forwarding class. Each of the forwarding classes defined within the system automatically creates a queue on each network interface. This queue gets all the parameters defined within the default network QoS policy 1 until an explicit policy is defined for the network interfaceaccess uplink port.
Page 105 Network QoS Policies 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 106 Network QoS Policy Command Reference The classification only applies to the outer IP header of non-tunneled traffic. The only exception is for traffic received on a Draft Rosen tunnel for which classification on the outer IP header only is supported. Attempting to apply a network QoS policy containing an ip-criteria statement to any object except a network IP interface will result in an error.
Page 107 Network QoS Policies 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. The action command must be executed for the match criteria to be added to the active list of entries. Each time action is executed on a specific entry ID, the previous entered values for fc fc-name and profile are overridden with the newly defined parameters.
Page 108 Network QoS Policy Command Reference The no form of this command removes the specified entry from the policy. Entries removed from the policy are immediately removed from all services where that policy is applied. Default none Parameters entry-id — The entry-id, expressed as an integer, uniquely identifies a match criterion and the corresponding action.
Page 109 Network QoS Policies Parameters protocol protocol-id — Specifies an IP protocol to be used as an ingress network QoS policy match criterion. The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), UDP(17). Values protocol-id: 0 to 255 protocol numbers accepted in DHB keywords: none, crtp, crudp, egp, eigrp, encap, ether-ip, gre, icmp,...
Page 110 Network QoS Policy Command Reference Table 20: Protocol ID descriptions (Continued) Protocol Protocol ID Description ether-ip Ethernet-within-IP Encapsulation encap Encapsulation Header pnni PNNI over IP Protocol Independent Multicast vrrp Virtual Router Redundancy Protocol l2tp Layer Two Tunneling Protocol Schedule Transfer Protocol Performance Transparency Protocol isis ISIS over IPv4...
Page 111 Network QoS Policies Parameters next-header next-header — Specifies the next header to match. The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), UDP(17). Values protocol numbers accepted in DHB: 0 to 42, 45 to 49, 52 to 59, 61 to 255 keywords: none, crtp, crudp, egp, eigrp, encap, ether-ip, gre, icmp, idrp, igmp, igp, ip, ipv6, ipv6-icmp, ipv6-no-nxt, isis, iso-ip, l2tp,...
Page 112 Network QoS Policy Command Reference The no form of this command removes the destination IP address match criterion. Parameters ip-address — The IP address of the destination IP or IPv6 interface. This address must be unique within the subnet and specified in dotted decimal notation. Values ip-address: a.b.c.d...
Page 113 Network QoS Policies The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not. Parameters true — Configures a match on all fragmented IP packets. A match will occur for all packets that have either the MF (more fragment) bit set OR have the Fragment Offset field of the IP header set to a non-zero value.
Page 114 Network QoS Policy Command Reference Default No source IP match criterion. Parameters ip-address — Specifies the source IPv4 address specified in dotted decimal notation. Values ip-address: a.b.c.d mask — Specifies the length in bits of the subnet mask. Values 1 to 32 ipv4-address-mask —...
Page 115 Network QoS Policies dot1p Syntax dot1p dot1p-priority fc fc-name profile {in | out | use-de} no dot1p dot1p-priority Context config>qos>network>ingress Description This command explicitly sets the forwarding class or enqueuing priorityand 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 be assigned to the forwarding class and enqueuing priority and profile of the packet based on the parameters included in the Dot1p rule.
Page 116 Network QoS Policy Command Reference Context config>qos>network>ingress Description This command creates a mapping between the DiffServ Code Point (DSCP) of the network ingress traffic and the forwarding class. 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 sixty-four DiffServ code points to the forwarding class.
Page 117 Network QoS Policies Table 21: Default DSCP Names to DSCP Value Mapping Table (Continued) DSCP Name DSCP Value DSCP Value DSCP Value Decimal Binary Hexadecimal af22 0x14 0b010100 af23 0x16 0b010110 af11 0x0a 0b001010 af12 0x0c 0b001100 af13 0x0e 0b001110 default 0x00 0b000000...
Page 118 Network QoS Policy Command Reference DSCP values mapping to forwarding class ‘be’ can only be set to out-of-profile. Default None, for every DSCP value defined, the profile must be indicated. If a DSCP value is not mapped, the default-action forwarding class and profile state will be used for that value. Values in, out fp-redirect-group...
Page 119 Network QoS Policies The no version of this command removes the redirection of the FC. Parameters unknown-policer 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 32 fp-redirect-group Syntax fp-redirect-group policer policer-id...
Page 120 Network QoS Policy Command Reference 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 the network- qos-policy-id is associated with. The command may be defined at anytime after the network QoS policy has been created.
Page 121 Network QoS Policies Parameters lsp-exp-value — Specify the LSP EXP values to be associated with the forwarding class. Default None, the lsp-exp command must define a value. Values 0 to 8 (Decimal representation of three EXP bit field) fc fc-name — Enter this required parameter to specify the fc-name that the EXP bit pattern will be associated with.
Page 122 Network QoS Policy Command Reference 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 123 Network QoS Policies dot1p Syntax dot1p dot1p-priority no dot1p Context config>qos>network>egress>fc Description This command will be used whenever the dot1p bits are set to a common value regardless of the internal profile of the packets. Although it is not mandatory, it is expected that this command is used in combination with the de-mark command to enable the marking of the DE bit according to the internal profile of the packet.
Page 124 Network QoS Policy Command Reference Parameters dot1p-priority — This value is a required parameter that specifies the unique IEEE 802.1p value that will match the dot1p rule. If the command is executed multiple times with the same dot1p-value, the previous forwarding class and enqueuing priority is completely overridden by the new parameters or defined to be inherited when a forwarding class or enqueuing priority parameter is missing.
Page 125 Network QoS Policies Default Policy-id 1: Factory setting Policy-id 2 to 65535: Policy-id setting Parameters dscp-name — System- or user-defined, case-sensitive dscp-name. Default none Values Any defined system- or user-defined dscp-name lsp-exp-in-profile Syntax lsp-exp-in-profile lsp-exp-value no lsp-exp-in-profile Context config>qos>network>egress>fc Description This command specifies the in-profile LSP EXP value for the forwarding class.
Page 126 Network QoS Policy Command Reference When multiple EXP values are associated with the forwarding class at network egress, the last name entered will overwrite the previous value. The no form of this command reverts to the factory default out-of-profile EXP setting. Default Policy-id 1: Factory setting...
Page 127 Network QoS Policies 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 enter that new policer’s context for possible...
Page 128 Network QoS Policy Command Reference Description This command defines a specific IP Differentiated Services Code Point (DSCP) value that must be matched to perform the associated reclassification actions. If an egress packet on the spoke-sdp the network QoS policy is applied to matches the specified IP DSCP value, the forwarding class and profile may be overridden.
Page 129 Network QoS Policies prec Syntax prec ip-prec-value [fc fc-name] [profile {in | out}] no prec ip-prec-value Context configure>qos>network>egress Description This command defines a specific IP Precedence value that must be matched to perform the associated reclassification actions. If an egress packet on the spoke-sdp the network QoS policy is applied to matches the specified IP Precedence value, the forwarding class and profile may be overridden.
Page 130 Network QoS Policy Command Reference remarking Syntax [no] remarking [force] Context config>qos>network>egress Description This command remarks both customer traffic and egress network IP interface traffic; VPRN customer traffic is not remarked. The remarking is based on the forwarding class to DSCP and LSP EXP bit mapping defined under the egress node of the network QoS policy.
Page 131 Network QoS Policies Self-Generated Traffic Commands sgt-qos Syntax sgt-qos Context config>router config>service>vprn Description This command enables the context to configure DSCP/dot1p re-marking for self-generated traffic. application Syntax application dscp-app-name dscp {dscp-value | dscp-name} application dot1p-app-name dot1p dot1p-priority no application {dscp-app-name | dot1p-app-name} Context config>router>sgt-qos config>service>vprn>sgt-qos...
Page 132 Values The following values apply to the 7450 ESS: bgp, 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 133: Show Commands
Network QoS Policies The no form of this command removes the DiffServ code point to forwarding class association. Default none Parameters dscp-name — The name of the DiffServ code point to be associated with the forwarding class. DiffServ code point can only be specified by its name and only an existing DiffServ code point can be specified.
Page 134 Network QoS Policy Command Reference Output Sample Output A:ALA-48# show qos dscp-table =========================================================== DSCP Mapping =========================================================== DSCP Name DSCP Value TOS (bin) TOS (hex) ----------------------------------------------------------- 0000 0000 0000 0100 0000 1000 0000 1100 0001 0000 0001 0100 0001 1000 0001 1100 0010 0000 0010 0100 af11...
Page 135 Network QoS Policies 1100 0000 cp49 1100 0100 cp50 1100 1000 cp51 1100 1100 cp52 1101 0000 cp53 1101 0100 cp54 1101 1000 cp55 1101 1100 1110 0000 cp57 1110 0100 cp58 1110 1000 cp59 1110 1100 cp60 1111 0000 cp61 1111 0100 cp62...
Page 136 Network QoS Policy Command Reference Profile-id : 1 Description: Default ingress multi-class frame-relay profile. ------------------------------------------------------------------------ FR Class Reassembly Timeout ------------------------------------------------------------------------ 1000 ======================================================================== Associations ------------------------------------------------------------------------ No Matching Entries mc-fr-profile-egress Syntax mc-fr-profile-egress [detail] Context show>qos Description This command displays MLFR egress profile details and only applies to the 7750 SR and 7950 XRS. Output Sample Output *A:Cpm-A# show qos mc-fr-profile-egress 1...
Page 137 Network QoS Policies network Syntax network [policy-id] [detail] Context show>qos Description This command displays network policy information. Special Cases Network QoS Policy Output Fields — The following table describes network QoS Policy output fields. Table 24: Show QoS Network Output Fields Label Description Policy-Id...
Page 138 Network QoS Policy Command Reference Table 24: Show QoS Network Output Fields (Continued) Label Description DSCP Mapping: Out-of-Profile Displays the DSCP used for out-of-profile traffic. In-Profile Displays the DSCP used for in-profile traffic. LSP EXP Bit Mapping: Out-of-Profile Displays the LSP EXP value used for out-of-profile traffic. In-Profile Displays the LSP EXP value used for in-profile traffic.
Page 139 Network QoS Policies ------------------------------------------------------------------------------ af11 af12 af13 af21 af22 af23 af31 af32 af33 af41 af42 af43 ------------------------------------------------------------------------------ LSP EXP Bit Map Fowarding Class Profile ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ Egress Forwarding Class Queuing ------------------------------------------------------------------------------ FC Name : af - DSCP Mapping Out-of-Profile : af12 In-Profile : af11 - LSP EXP Bit Mapping...
Page 140 Network QoS Policy Command Reference - LSP EXP Bit Mapping Out-of-Profile : 4 In-Profile FC Name : l1 - DSCP Mapping Out-of-Profile : af22 In-Profile : af21 - LSP EXP Bit Mapping Out-of-Profile : 2 In-Profile FC Name : l2 - DSCP Mapping Out-of-Profile : cs1 In-Profile...
Page 141 Network QoS Policies - DSCP Mapping Out-of-Profile : be In-Profile : be - Dot1p Mapping Out-of-Profile : 7 In-Profile - LSP EXP Bit Mapping Out-of-Profile : 0 In-Profile - DE Mark : Force 1 FC Value FC Name : l2 - DSCP Mapping Out-of-Profile : cs1 In-Profile...
Page 142 Network QoS Policy Command Reference No Matching Entries ------------------------------------------------------------------------------- Dot1p Bit Map Forwarding Class Profile ------------------------------------------------------------------------------- No Matching Entries ------------------------------------------------------------------------------- Egress Forwarding Class Mapping ------------------------------------------------------------------------------- FC Value FC Name : be - DSCP Mapping Out-of-Profile : be In-Profile : be - Dot1p Mapping Out-of-Profile In-Profile...
Page 143 Network QoS Policies Out-of-Profile In-Profile DE Mark None Redirect Grp Q None Redirect Grp Plcr: None FC Value FC Name : h2 - DSCP Mapping Out-of-Profile : af42 In-Profile : af41 - Dot1p Mapping Out-of-Profile In-Profile - LSP EXP Bit Mapping Out-of-Profile In-Profile DE Mark...
Page 144 Network QoS Policy Command Reference ------------------------------------------------------------------------------- Ingress Forwarding Class Mapping ------------------------------------------------------------------------------- FC Value FC Name : be Redirect UniCast Plcr Redirect MultiCast Plcr : 3 Redirect BroadCast Plcr : 4 Redirect Unknown Plcr FC Value FC Name : l2 Redirect UniCast Plcr : None Redirect MultiCast Plcr : None Redirect BroadCast Plcr : None...
Page 145 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,...
Page 146 Network QoS Policy Command Reference Quality of Service Guide...
Page 147: Network Queue Qos Policies
Network Queue QoS Policies In This Section This section provides information to configure network queue QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Default Network Queue Policy Values • Service Management Tasks Overview Network queue policies define the ingress network queuing at the XMAMDA network node level.
Page 148: Network Queue Parent Scheduler
Basic Configurations 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 149 Network Queue QoS Policies fc fc-name multicast-queue queue-id queue queue-id queue queue-id [multipoint] [queue-type] cbs percent high-prio-only percent mbs percent port-parent [weight weight] [level level] [cir- weight cir-weight] [cir-level cir-level] rate percent [cir percent] The following output displays a network queue QoS policy. A:ALA-1>config>qos# network-queue default A:ALA-1>config>qos>network-queue# info detail ----------------------------------------------...
Page 150 Basic Configurations cbs 3 high-prio-only 10 exit queue 8 create rate 100 cir 10 mbs 25 cbs 3 high-prio-only 10 exit queue 9 multipoint create mbs 50 cbs 1 high-prio-only 10 exit queue 10 multipoint create rate 100 cir 5 mbs 50 cbs 1 high-prio-only 10...
Page 151: Applying Network Queue Policies
Network Queue QoS Policies 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 fc h2 create multicast-queue 13 queue 5 exit fc l1 create multicast-queue 12 queue 4 exit...
Page 152: Ethernet Ports
Basic Configurations The following output displays XMA or MDA network ingress queue policy reverted to the default policy. A:ALA-7>config>card>mda# info ---------------------------------------------- mda-type m60-10/100eth-tx network ingress pool default resv-cbs sum slope-policy "default" exit queue-policy "default" exit egress pool default resv-cbs sum slope-policy "default"...
Page 153: Sonet/Sdh Ports
Network Queue QoS Policies ethernet network queue-policy "nq1" exit exit no shutdown ---------------------------------------------- A:ALA-49>config>port# SONET/SDH Ports Use the following CLI syntax to apply a network queue policy to a SONET/SDH port: CLI Syntax: config>port# sonet-sdh path path network queue-policy name The following output displays the port configuration.
Page 154 Default Network Queue Policy Values Table 25: Network Queue Policy Defaults (Continued) Field Default queue 1 high-prio-only queue 2 high-prio-only queue 3 high-prio-only queue 4 high-prio-only queue 5 Quality of Service Guide...
Page 155 Network Queue QoS Policies Table 25: Network Queue Policy Defaults (Continued) Field Default high-prio-only queue 6 high-prio-only queue 7 high-prio-only queue 8 high-prio-only fc af queue 3 multicast-queue 11 fc be queue 1 multicast-queue 9 Quality of Service Guide...
Page 156 Default Network Queue Policy Values Table 25: Network Queue Policy Defaults (Continued) Field Default fc ef queue 6 multicast-queue 14 fc h1 queue 67 multicast-queue 15 fc h2 queue 5 multicast-queue 13 fc l1 queue 7 multicast-queue 12 fc l2 queue 2 multicast-queue 10 fc nc...
Page 157 Network Queue QoS Policies rate 100 cir 100 mbs 50 cbs 1 high-prio-only 10 exit queue 6 auto-expedite create rate 100 cir 100 mbs 50 cbs 1 high-prio-only 10 exit queue 7 auto-expedite create rate 100 cir 10 mbs 25 cbs 3 high-prio-only 10 exit...
Page 158: Service Management Tasks
Service Management Tasks queue 15 multipoint auto-expedite create rate 100 cir 10 mbs 25 cbs 1 high-prio-only 10 exit queue 16 multipoint auto-expedite create rate 100 cir 10 mbs 25 cbs 1 high-prio-only 10 exit fc af create multicast-queue 11 queue 3 exit fc be create...
Page 159: Deleting Qos Policies
Network Queue QoS Policies • Remove a Policy from the QoS Configuration • Copying and Overwriting QoS Policies • Editing QoS Policies Deleting QoS Policies A network queue policy is associated by default with XMA or MDA network ingress ports. You can replace the default policy with a customer-configured policy, but you cannot entirely remove a QoS policy.
Page 160: Editing Qos Policies
Service Management Tasks Editing QoS Policies You can change existing policies, except the default policies, and entries in the CLI. 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, and then overwrite the original policy.
Page 161: Network Queue Qos Policy Command Reference
Network Queue QoS Policies Network Queue QoS Policy Command Reference Command Hierarchies • Configuration Commands • Operational Commands • Show Commands Configuration Commands config — qos — network-queue policy-name — description description-string — no description — egress-hsmda — [no] wrr-policy {add add-bytes | subtract sub-bytes} —...
Page 162: Operational Commands
Network Queue QoS Policy Command Reference — port-parent [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level] [cir-level level] [cir-weight weight] — no port-parent — rate percent [cir percent] — no rate Operational Commands config — qos — copy network-queue src-name dst-name [overwrite] Show Commands show —...
Page 163: Operational Commands
Network Queue QoS Policies config>qos>sap-ingress>ip-criteria>entry config>qos>sap-ingress>mac-criteria>entry config>qos>scheduler-policy config>qos>scheduler-policy>tier>scheduler Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file. The no form of this command removes any description string from the context.
Page 164 Network Queue QoS Policy Command Reference Network Queue QoS Policy Commands network-queue Syntax [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 165 Network Queue QoS Policies 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. Once the forwarding class mapping is executed, all multicast traffic using this policy is forwarded using the queue-id.
Page 166 - once for each switch fabric destination currently provisioned. Some IOM types on the 7450 ESS and 7750 SR represent one switch fabric destinations while others may represent two. XCMs on a 7950 XRS represent two switch fabric destinations, where each XMA is one destination. At egress, a single queue is created since the policy is applied at the port level.
Page 167 Present (the queue is created as non-multipoint) egress-hsmda Syntax egress-hsmda Context config>qos>network-queue Description This command enables the context to configure queue definitions for use on HSMDAs and only applies to the 7450 ESS and 7750 SR. queue Syntax [no] queue queue-id Context config>qos>network-queue>egress-hsmda config>qos>network-queue>fc Description This command is a container for the configuration parameters controlling the behavior of an HSMDA queue.
Page 168 The no form of the command restores the defined queue-id to its default parameters. All HSMDA queues having the queue-id and associated with the QoS policy are re-initialized to default parameters. This command only applies to the 7450 ESS and 7750 SR. Parameters queue-id —...
Page 169 Description This command associates an existing HSMDA weighted-round-robin (WRR) scheduling loop policy to the HSMDA queue. This command only applies to the 7450 ESS and 7750 SR. Parameters hsmda-wrr-policy-name — Specifies the existing HSMDA WRR policy name to associate to the queue.
Page 170 Network Queue QoS Policy Command Reference 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 to the QoS policy HSMDA queue. The specified hsmda-slope-policy-name must exist for the command to succeed. If the policy name does not exist, the command has no effect on the existing slope policy association.
Page 171 The command has no immediate effect for queues that have a local override defined for the slope policy. This command applies only to the 7450 ESS and 7750 SR. Parameters hsmda-slope-policy-name — Specifies an existing slope policy within the system. If a slope policy with the specified name does not exist, the slope-policy command will fail without modifying the slope behavior on the queue.
Page 172 Network Queue QoS Policy Command Reference This command only applies to the 7450 ESS and 7750 SR. Parameters adaptation-rule — Specifies the adaptation rule to be used while computing the operational PIR value. Values pir — Defines the constraints enforced when adapting the PIR rate defined.
Page 173 Description This command assigns the weight value to the HSMDA queue. This command only applies to the 7450 ESS and 7750 SR. The no form of the command returns the weight value for the queue to the default value.
Page 174 Network Queue QoS Policy Command Reference Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or non-expedited nature of the queue based on the forwarding classes mapped to it. As long as all forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue is treated as an expedited queue by the hardware schedulers.
Page 175 If the pool comes into existence, the queue will be moved from the default pool to the new named pool and the ‘pool-orphaned’ state will be cleared. The specified name must be an ASCII name string up to 16 characters long. This parameter applies only to the 7450 ESS and 7750 SR.
Page 176 Network Queue QoS Policy Command Reference adaptation-rule Syntax adaptation-rule [pir adaptation-rule] [cir adaptation-rule] no adaptation-rule Context config>qos>network-queue>queue Description This command defines the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.
Page 177 Network Queue QoS Policies Context config>qos>network-queue>queue Description This command configures the average frame overhead to define the average percentage that the offered load to a queue will expand during the frame encapsulation process before sending traffic on-the-wire. While the avg-frame-overhead value may be defined on any queue, it is only used by the system for queues that egress a SONET or SDH port or channel.
Page 178 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.
Page 179 Network Queue QoS Policies Description The Committed Burst Size (cbs) command specifies the relative amount of reserved buffers for a specific ingress network XMA or MDA forwarding class queue or egress network port forwarding class queue. The value is entered as a percentage. The CBS for a queue is used to determine whether it has exhausted its reserved buffers while enqueuing packets.
Page 180 Forwarding Class Queue on egress channel applies only to the 7450 ESS and 7750 SR. The cbs value is used to calculate the queue’s CBS size based on the total amount of buffer space allocated for the buffer pool on the egress network port or channel.
Page 181 Network Queue QoS Policies The difference between the MBS size for the queue and the high priority reserve defines the threshold where lower priority traffic will be discarded. The result is used on the queue to define a threshold where lower priority packets are discarded, leaving the rest of the default MBS size for high priority packets only.
Page 182 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. The mbs value is used to calculate the queue’s MBS size based on the total amount buffer space allocated for the buffer pool on the egress network port or channel.
Page 183 The no form of the command removes a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool. This command only applies to the 7450 ESS and 7750 SR. Default...
Page 184 Network Queue QoS Policy Command Reference Parameters weight weight — Defines the weight the queue or scheduler will use at the above-cir port priority level (defined by the level parameter). Values 0 to 100 Default level level — Defines the port priority the queue or scheduler will use to receive bandwidth for its above-cir offered-load.
Page 185: Show Commands
Network Queue QoS Policies The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler. The rate command can be executed at anytime, 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-id.
Page 186 Network Queue QoS Policy Command Reference Table 27: Network Queue Labels and Descriptions Label Description Policy The policy name that uniquely identifies the policy. Description A text string that helps identify the policy’s context in the configuration file. Port-Id Displays the physical port identifier where the network queue policy is applied. Queue Displays the queue ID.
Page 187 Network Queue QoS Policies ------------------------------------------------------------------------------ UCastQ ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ Associations ------------------------------------------------------------------------------ Port-id : 1/1/1 ============================================================================== A:ALA-12>show>qos# Quality of Service Guide...
Page 188 Network Queue QoS Policy Command Reference Quality of Service Guide...
Page 189: Service Egress And Ingress Qos Policies
Service Egress and Ingress QoS Policies In This Section This section provides information to configure SAP ingress and egress QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Service Egress QoS Policy →...
Page 190: Overview
Overview → Editing QoS Policies → Copying and Overwriting QoS Policies → Deleting QoS Policies → Remove a Policy from the QoS Configuration Overview There is one default service ingress policy and one default service egress policy. Each policy can have up to 32 ingress queues and 8 egress queues per service. The default policies can be copied and modified but they cannot be deleted.
Page 191: Service Egress Qos Policy
Service Egress and Ingress QoS Policies • Percent-Rate Support • Service Egress QoS Policy • Service Ingress QoS Policy Service Egress QoS Policy To create a service egress policy, you must define the following: • A new policy ID value. The system will not dynamically assign a value. •...
Page 192: Service Egress Qos Queue
Service Egress QoS Policy A:ALA-7>config>qos# Service Egress QoS Queue To create a service egress queue parameters, define the following: • A new queue ID value. The system will not dynamically assign a value. • Define queue parameters. Egress queues support explicit and auto-expedite hardware queue scheduling, and parent virtual scheduler definition.
Page 193: Dynamic Mbs For Egress Queue Group Queues
Service Egress and Ingress QoS Policies When the local-limit is used the percent-rate is relative to the queue’s parent scheduler rate or the agg-rate rate at egress, when the port-limit is used the percent-rate is relative to the rate of the port (including the ingress-rate/egress-rate setting) to which the queue is attached. port- limit is the default.
Page 194 Service Egress QoS Policy When any of the queue parameters are reduced, packets that are already in the queue will not be affected and will be forwarded. Reducing these parameters will constrain the latency for newly arriving packets, but those packets already in the queue before the new parameter values were set will be forwarded with the delay associated with the actual queue depth when the packet was enqueued (based on the previous parameter values).
Page 195: Queue Length As A Delay Value
Service Egress and Ingress QoS Policies mbs 1000 kilobytes dynamic-mbs exit Without any traffic in the other queues constraining the operational PIR on this queue, the MBS used is the administrative MBS. *B:PE# show pools access-egress 5/1/1 queue-group "qg1" instance 1 =============================================================================== Queue : accQGrp->qg1:1(5/1/1)->1 ===============================================================================...
Page 196: Egress Sap Forwarding Class And Forwarding Profile Overrides
Service Egress QoS Policy configure queue-group-templates egress queue-group <queue-group-name> create queue <queue-id> queue-delay <ms> The queue-delay command and the mbs command are mutually exclusive. In order to change between the mbs and queue-delay parameters, the current parameter must be removed before adding the new parameter, that is, changing from mbs to queue-delay requires a no mbs before the queue-delay is configured and changing from queue-delay to mbs requires a no queue-delay before the mbs is configured.
Page 197: Egress Criteria Classification Directly To Policer
Service Egress and Ingress QoS Policies Overrides An access egress packet’s forwarding class can be changed to redirect the packet to an alternate queue than the ingress forwarding class determination would have used. An access egress packet’s profile (in or out) can also be changed to modifying the congestion behavior within the egress queue.
Page 198 Service Egress QoS Policy • A SAP queue configured within the SAP egress QoS policy. • The queue to which the forwarding class for the traffic is mapped. This could be a queue group, SAP, or subscriber queue. This requires the use of the use-fc-mapped- queue parameter in the criteria action statement.
Page 199: Dot1P Egress Remarking
Service Egress and Ingress QoS Policies Figure 13: Egress SAP policer-output-queues queue-group Policer 1 DSCP EF Traffic FC=BE queue 1 Other Traffic al_0617 The configuration would be as follows: sap-egress 10 create queue 1 create exit policer 1 create exit ip-criteria entry 10 create match...
Page 200: Dei Egress Remarking
Service Egress QoS Policy exit exit The precedence of the above commands is summarized as, from highest to lowest precedence: • dot1p-outer used for outer tag markings • dot1p-inner used for inner tag markings • existing dot1p used for marking both tags •...
Page 201 Service Egress and Ingress QoS Policies fc <fc-name> create de-mark [force <de-value>] de-mark-inner [force <de-value>] de-mark-outer [force <de-value>] exit exit The DE bit is set to 0 for in-profile traffic and 1 for out-of-profile and exceed-profile traffic, unless explicitly forced. The precedence of the above commands is summarized as, from highest to lowest precedence: •...
Page 202 Service Egress QoS Policy 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 203 Service Egress and Ingress QoS Policies Figure 15: DE Aware 802.1ad Access Network 7x50 PE1 7x50 PE2 802.1 a/d MPLS Access I-SAP (DE aware) Access Device The following shows an example of the QoS processing in more detail. Figure 16 displays a simple example of the DEI processing steps for the IEEE 802.1ad Use Case for both ingress and egress directions (from a PE1 SAP perspective).
Page 204: Dscp/Prec Egress Remarking
Service Egress QoS Policy A combination of two access networks can be possible. If PBB encapsulation is used, the configuration used for DE in SAP and SDP policies applies to both BVID and ITAG DE bits. When both fields are used the BVID takes precedence. IEEE 802.1ah Use Case Figure 17 illustrates an example of a PBB topology where the DE feature can be used.
Page 205: Queue Depth Monitoring
Service Egress and Ingress QoS Policies in-profile <ip-prec-value> out-profile <ip-prec- value> [exceed-profile <ip-prec-value>]} exit exit Remarking the DSCP/prec based on the profile result of egress policing must be enabled as the follows under the related policer configuration: sap-egress <policy-id> create policer <policer-id>...
Page 206 Service Egress QoS Policy The queue depth can then be shown as follows: *A:PE-1# show service id 1 sap 1/2/1 queue-depth =============================================================================== Queue Depth Information (Ingress SAP) =============================================================================== No Matching Entries =============================================================================== =============================================================================== Queue Depth Information (Egress SAP) =============================================================================== ------------------------------------------------------------------------------- Name : 1->1/2/1->1 : Def...
Page 207: Service Ingress Qos Policy
Service Egress and Ingress QoS Policies There is no specific limit on the number of queues that can be monitored but the amount of each line card CPU’s resources allocated to the monitoring is bounded, consequently average polling interval will increase as more queues are monitored on the line card. If the MBS of a queue is modified, the occupancy information is cleared and the elapsed timers reset to zero.
Page 208: Service Ingress Qos Queue
Service Ingress QoS Policy sap-ingress 100 create description "Used on VPN sap" ---------------------------------------------- A:ALA-7>config>qos>sap-ingress# Service Ingress QoS Queue To create service ingress queues parameters, define the following: • A new queue ID value — The system will not dynamically assign a value. •...
Page 209: Percent-Rate Support
Service Egress and Ingress QoS Policies parent VPN_be rate 11000 exit queue 22 multipoint create parent VPN_priority rate 11000 exit queue 23 multipoint create parent VPN_reserved rate 1 exit queue 25 multipoint create parent VPN_video rate 1500 cir 1500 exit queue 26 multipoint create parent VPN_voice rate 2500 cir 2500...
Page 210: Service Ingress Forwarding Class (Fc)
Service Ingress QoS Policy *B:Dut-A>config>qos>sap-ingress# queue 1 percent-rate - no percent-rate - percent-rate <pir-percent> [cir <cir-percent>] [port-limit | local-limit] - percent-rate <pir-percent> police [port-limit | local-limit] <pir-percent> : [0.01..100.00] <cir-percent> : [0.00..100.00] <police> : keyword <port-limit | local-*> : keyword *B:Dut-A>config>qos>sap-ingress# policer 1 percent-rate - no percent-rate - percent-rate <pir-percent>...
Page 211: Service Ingress Ip Match Criteria
Service Egress and Ingress QoS Policies fc nc create queue 17 broadcast-queue 27 multicast-queue 27 unknown-queue 27 exit prec 0 fc be prec 2 fc af prec 3 fc ef prec 5 fc h1 prec 6 fc h2 prec 7 fc nc #------------------------------------------ A:ALA-7>config>qos# Service Ingress IP Match Criteria...
Page 212: Service Ingress Ipv6 Match Criteria
Service Ingress QoS Policy Service Ingress IPv6 Match Criteria When specifying SAP ingress match criteria, only one match criteria type (IP/IPv6 or MAC) can be configured in the SAP ingress QoS policy. This feature applies only to the 7750 SR and 7950 XRS.
Page 213: Vlan Id Matching
Service Egress and Ingress QoS Policies • Match criteria for ingress SAP QoS policy. Optionally, specify an IP protocol to be used as an ingress SAP QoS policy match criterion. The following displays an ingress MAC criteria configuration: A:ALA-7>config>qos# info #------------------------------------------ echo "QoS Policy Configuration"...
Page 214: Ingress Criteria Classification Directly To Policer
Service Ingress QoS Policy exit exit 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 when using one of the following statements: ip-criteria, ipv6-criteria or mac-criteria.
Page 215: Virtual Network Identifier (Vni) Classification
Service Egress and Ingress QoS Policies action policer 1 exit exit exit 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 216: Fc Mapping Based On Exp Bits
Service Ingress QoS Policy 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: • Source and destination port matching on a SAP on which a SAP ingress QoS policy is applied that has ip-criteria or ipv6-criteria statements with type vxlan-vni, is not available for:...
Page 217: Service Management Tasks
Apply SAP ingress and egress policies to the following service SAPs: • Epipe • • VPLS • VPRN Refer to the Subscriber Services Overview section of the Services Guide for information about configuring service parameters on the 7750 SR and 7450 ESS. Quality of Service Guide...
Page 218: Epipe
Service Management Tasks Epipe The following output displays an Epipe service configuration with SAP ingress policy 100 and SAP egress 105 applied to the SAP. A:ALA-7>config>service# info ---------------------------------------------- epipe 6 customer 6 vpn 6 create description "Distributed Epipe service to west coast" sap 1/1/10:010 create ingress qos 100...
Page 219: Vpls
Service Egress and Ingress QoS Policies VPLS The following output displays a VPLS service configuration with SAP ingress policy 100. The SAP egress policy 1 is applied to the SAP by default. A:ALA-7>config>service# info ---------------------------------------------- vpls 700 customer 7 vpn 700 create description "test"...
Page 220: Editing Qos Policies
Service Management Tasks exit ---------------------------------------------- A:ALA-7>config>service# Editing QoS Policies You can change QoS existing policies and entries. The changes are applied immediately to all services where this policy is applied. To prevent configuration errors copy the policy to a work area, make the edits, and then write over the original policy. Copying and Overwriting QoS Policies You can copy an existing service egress or ingress policy, rename it with a new policy ID value, or overwrite an existing policy ID.
Page 221: Deleting Qos Policies
Service Egress and Ingress QoS Policies description "Used on VPN sap" queue 1 create exit queue 2 multipoint create exit queue 10 create parent "VPN_be" rate 11000 exit --------------------------------------------- A:ALA-7>config>qos# Deleting QoS Policies Every service SAP is associated, by default, with the appropriate egress or ingress policy (policy-id 1).
Page 222 Service Management Tasks Quality of Service Guide...
Page 223: Service Sap Qos Policy Command Reference
Service Egress and Ingress QoS Policies Service SAP QoS Policy Command Reference Command Hierarchies • Service Ingress QoS Policy Commands • Service Egress QoS Policy Commands • Operational Commands • Show Commands Service Ingress QoS Policy Commands config — qos —...
Page 224 Service SAP QoS Policy Command Reference — out-remark prec ip-prec-value — no out-remark — queue queue-id {group queue-group-name [instance instance-id] | port- redirect-group-queue]} — no queue — unknown-policer policer-id [fp-redirect-group] — no unknown-policer — unknown-queue queue-id [group queue-group-name] — no unknown-queue —...
Page 225 Service Egress and Ingress QoS Policies — fragment {true | false | first-only | non-first-only} — no fragment — src-ip {ipv6-address/prefix-length | ipv6-address/ipv6- address-mask} — no src-ip — src-port {lt | gt | eq} src-port-number — src-port range start end —...
Page 226 Service SAP QoS Policy Command Reference — description description-string — no description — {size [bytes | kilobytes] | default} — no — high-prio-only percent-of-mbs — no high-prio-only — {size [bytes | kilobytes] | default} — no — packet-byte-offset {add bytes | subtract bytes} —...
Page 227: Service Egress Qos Policy Commands
Service Egress and Ingress QoS Policies — no sub-insert-shared-pccrule Service Egress QoS Policy Commands config — qos — [no] sap-egress policy-id | policy-name — description description-string — no description — dot1p dot1p-value [fc fc-name] [profile {in | out | use-de}] —...
Page 228 Service SAP QoS Policy Command Reference — no adaptation-rule — burst-limit size [bytes | kilobytes] — no burst-limit — {[0 to 2625] kilobytes | [0 to 2688000] bytes | default} — no — rate pir-rate {max | kilobits-per-second} — no rate —...
Page 229 Service Egress and Ingress QoS Policies — no dst-ip — dst-port {lt | gt | cq} dst-port-number — dst-port range start end — no dst-port — src-ip {ipv6-address/prefix-length | ipv6-address ipv6- address-mask} — no src-ip — src-port {lt | gt | cq} dst-port-number —...
Page 230: Operational Commands
Service SAP QoS Policy Command Reference — avg-frame-overhead percent — no avg-frame-overhead — burst-limit — no burst-limit — size-in-kbytes — no — high-prio-only percent — no high-prio-only — size [bytes | kilobytes] — no — packet-byte-offset add add-bytes — packet-byte-offset subtract sub-bytes —...
Page 231: Show Commands
Service Egress and Ingress QoS Policies — copy named-pool-policy src-name dst-name [overwrite] Show Commands show — qos — sap-ingress [policy-id] [association | match-criteria | hsmda | detail] — sap-egress[policy-id] [association | match-criteria | hsmda | detail] Command Descriptions Configuration Commands Generic Commands description Syntax...
Page 232: Operational Commands
ID are HSMDA slope policy IDs. 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.
Page 233 Service Egress and Ingress QoS Policies 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, an error will occur if the destination policy ID exists. SR>config>qos# copy sap-egress 1 1010 MINOR: CLI Destination "1010"...
Page 234 Service SAP QoS Policy Command Reference 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 can be modified but not deleted. The no sap-ingress command restores the factory default settings when used on policy-id 1.
Page 235 Service Egress and Ingress QoS Policies 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 236 Service SAP QoS Policy Command Reference default-fc Syntax default-fc fc-name Context config>qos>sap-ingress 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 sub-class will be associated with the packet.
Page 237 Service Egress and Ingress QoS Policies Parameters high — Setting the enqueuing parameter to high for a packet increases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing, once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
Page 238 Service SAP QoS Policy Command Reference class[.sub-class] class: be, l2, af, l1, h2, ef, h1, nc sub-class: 29 characters max Default None (Each sub-class-name must be explicitly defined) policer Syntax policer policer-id [fp-redirect-group] no policer Context config>qos>sap-ingress>fc Description Within a sap-ingress QoS policy forwarding class context, the policer command is used to map packets that match the forwarding class and are considered unicast in nature to the specified policer-id.
Page 239 Service Egress and Ingress QoS Policies 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 Default None...
Page 240 Service SAP QoS Policy Command Reference The no form of this command is used to restore the mapping of the broadcast forwarding type within the forwarding class to the default multipoint queue. If all forwarding class forwarding types had been removed from the default multipoint queue, the queue will not exist on the SAPs or subscribers or multi-service site associated with the QoS policy and the no broadcast-policer command will cause the system to attempt to create the default multipoint queue on each object.
Page 241 Service Egress and Ingress QoS Policies A policer defined within the sap-ingress policy is not actually created on an ingress SAP or a subscriber using an sla-profile where the policy is applied until at least one forwarding type (unicast, broadcast, unknown or multicast) from one of the forwarding classes is mapped to the policer. If insufficient policer resources exist to create the policer for a SAP or subscriber or multi-service site or ingress policing is not supported on the port associated with the SAP or subscriber or multi-service site, the initial forwarding class forwarding type mapping will fail.
Page 242 Service SAP QoS Policy Command Reference Unknown forwarding type packets are mapped to either an ingress multipoint queue (using the unknown queue-id or unknown queue-id group ingress-queue-group commands) or an ingress policer (unknown-policer policer-id). The unknown and unknown-policer commands within the forwarding class context are mutually exclusive.
Page 243 Service Egress and Ingress QoS Policies Description This command explicitly sets the forwarding class or sub-class or enqueuing priority when a packet is marked with a dot1p-priority specified. Adding a dot1p rule on the policy forces packets that match the dot1p-priority specified to override the forwarding class and enqueuing priority based on the parameters included in the dot1p rule.
Page 244 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 245 Service Egress and Ingress QoS Policies A maximum of 64 DSCP rules are allowed on a single policy and a maximum of 8 dscp- names can be specified in a single statement. The specified name must exist as a dscp-name. SR OS software provides names for the well- known code points these can be shown using the command below: A:PE# show qos dscp-table ============================================================...
Page 246 Service SAP QoS Policy Command Reference 1100 0000 cp49 1100 0100 cp50 1100 1000 cp51 1100 1100 cp52 1101 0000 cp53 1101 0100 cp54 1101 1000 cp55 1101 1100 1110 0000 cp57 1110 0100 cp58 1110 1000 cp59 1110 1100 cp60 1111 0000 cp61...
Page 247 Service Egress and Ingress QoS Policies high — This parameter is used in conjunction with the priority parameter. Setting the enqueuing parameter to high for a packet increases the likelihood of enqueuing the packet when the ingress queue is congested. Ingress enqueuing priority only affects ingress SAP queuing. Once the packet is placed in a buffer on the ingress queue, the significance of the enqueuing priority is lost.
Page 248 Service SAP QoS Policy Command Reference The reclassification actions from a dscp reclassification rule may be overridden by an IP flow match event. The fc keyword is optional. When specified, the egress classification rule will overwrite the forwarding class derived from ingress. The new forwarding class is used for egress remarking and queue mapping decisions.
Page 249 Service Egress and Ingress QoS Policies 0001 1100 0010 0000 0010 0100 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 250 Service SAP QoS Policy Command Reference fc fc-name: — The fc reclassification action is optional. When specified, packets matching the IP DSCP value corresponding to a specified dscp-name will be explicitly reclassified to the forwarding class specified as fc-name regardless of the ingress classification decision. The explicit forwarding class reclassification may be overwritten by an ip-criteria reclassification match.
Page 251 Service Egress and Ingress QoS Policies 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 252 Service SAP QoS Policy Command Reference ip-criteria Syntax [no] ip-criteria Context config>qos>sap-ingress Description IP criteria-based SAP 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 253 For this reason entries must be sequenced correctly from most to least explicit. This is supported on FP2- and higher-based line cards and requires mixed-mode for the 7450 ESS. The no form of this command deletes all the entries specified under this node. Once ipv6-criteria entries are removed from a SAP ingress policy, the ipv6-criteria is removed from all services where that policy is applied.
Page 254 Service SAP QoS Policy Command Reference Description This command sets the ip-criteria and ipv6-criteria type to control the type of match entries configurable in this context. Default normal Parameters filter-type — Specifies which type of entries that the ip-criteria and ipv6-criteria statements can contain.
Page 255 Service Egress and Ingress QoS Policies Context config>qos>sap-ingress Description This command explicitly sets the forwarding class or sub-class 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 256 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 257 Service Egress and Ingress QoS Policies policer Syntax policer policer-id [create] no policer policer-id Context config>qos>sap-ingress Description This command is used in the sap-ingress and sap-egress QoS policies to create, modify or delete a policer. Policers are created and used in a similar manner to queues. The policer ID space is separate from the queue ID space, allowing both a queue and a policer to share the same ID.
Page 258 Service SAP QoS Policy Command Reference description Syntax description description-string no description Context config>qos>sap-ingress>policer Description The description command is used to define an informational ASCII string associated with the policer control policy. The string value can be defined or changed at any time once the policy exists. The no form of this command is used to remove an explicit description string from the policer.
Page 259 Service Egress and Ingress QoS Policies adaptation-rule Syntax adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}] no adaptation-rule Context config>qos>sap-ingress>policer Description This command is used to define how the policer’s configuration parameters are translated into the underlying hardware capabilities used to implement each policer instance.
Page 260 Service SAP QoS Policy Command Reference max — The max keyword is used to inform the system that the profiling rate defined for the policer is the maximum allowed rate. The system will choose a hardware supported rate that is closest but not exceeding the specified rate. min —...
Page 261 Service Egress and Ingress QoS Policies high-prio-only Syntax high-prio-only percent-of-mbs no high-prio-only Context config>qos>sap-ingress>policer Description This command is used to configure the percentage of the policer’s PIR leaky bucket's MBS (maximum burst size) that is reserved for high priority traffic. While the mbs value defines the policer’s high priority violate threshold, the percentage value defined is applied to the mbs value to derive the bucket’s low priority violate threshold.
Page 262 Service SAP QoS Policy Command Reference Parameters size [bytes | kilobytes] — The size parameter is required when specifying mbs and is expressed as an integer representing the required size in either bytes or kilobytes. The default is kilobytes. The optional byte and kilobyte keywords are mutually exclusive and are used to explicitly define whether size represents bytes or kilobytes.
Page 263 This functionality is available only for the 7450 ESS and 7750 SR. Executing the parent command will fail if: •...
Page 264 Service SAP QoS Policy Command Reference config>qos>sap-ingress>policer Description The percent-rate command within the SAP ingress and egress QOS policy enables supports for a policer’s PIR and CIR rate to be configured as a percentage of the immediate parent root policer/arbiter rate or the FP capacity.
Page 265 Service Egress and Ingress QoS Policies • At egress, soft-in-profile packets (packets received from ingress as in-profile) are treated the same as explicit in-profile (unless explicitly reclassified as out-of-profile) and have an initial policer state of in-profile. • At both ingress and egress, any packet output from the policer with a non-conforming CIR state are treated as out-of-profile (out-of-profile state is ignored for initial in-profile packets when profile capped mode is not enabled) Default...
Page 266 Service SAP QoS Policy Command Reference The policer’s adaptation-rule command settings are used by the system to convert the specified rates into hardware timers and decrement values for the policer’s buckets. By default, the policer’s metering rate is max and the profiling rate is 0 Kbps (all packets out-of- profile).
Page 267 Service Egress and Ingress QoS Policies Description This command is used to configure the forwarding plane counters that allow offered, output and discard accounting to occur for the policer. An ingress policer has multiple types of offered packets (explicit in-profile, explicit out-of-profile, 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 268 Service SAP QoS Policy Command Reference Counter 0 indicates that the accounting statistic returns a value of zero. minimal — Counter resource allocation: 1 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 269 Service Egress and Ingress QoS Policies 4. dropped-out = Same as 2 5. forwarded-in = Derived from 1 - 3 6. forwarded-out = Derived from 2 - 4 When collect-stats is enabled, the counters are used by the system to generate the following statistics: a.
Page 270 Service SAP QoS Policy Command Reference With offered-priority-no-cir enabled as the policer stat-mode, the SAP offered stats for the policer returned via MIB query and CLI show commands will return the following values: i. offered-high = 1 ii. offered-low = 2 iii.
Page 271 Service Egress and Ingress QoS Policies The offered-profile-cir mode allocates four forwarding plane offered counters and four traffic manager discard counters. The offered-profile-cir mode is most useful when the policer is receiving trusted out-of- profile and in-profile traffic and is also receiving untrusted packets that are being applied to a defined CIR profiling rate.
Page 272 Service SAP QoS Policy Command Reference The offered-priority-cir mode is most useful when the policer is receiving only untrusted packets that are being classified as high priority or low priority and are being applied to a defined CIR profiling rate. This mode differs from offered-profile-cir mode in that it does not expect trusted in-profile and out-of-profile packets but does not exclude the ability of the policer to receive them.
Page 273 Service Egress and Ingress QoS Policies The counters are used in the following manner: 1. offered-that-turned-green = profile in/out, priority high/low 2. offered- that-turned-yellow-or-red = profile in/out, priority high/low 3. dropped-offered-that-turned-green = Same as 1 4. dropped-offered-that-turned-yellow-or-red = Same as 2 5.
Page 274 Service SAP QoS Policy Command Reference 8.‘dropped-soft-out-that-turned-green’ = Same as 3 9.‘dropped-soft-out-that-turned-yellow-or-red’ = Same as 4 10.‘dropped-out-that-turned-yellow-or-red’ = Same as 5 11.‘forwarded-in-that-stayed-green’ = Derived from 1 - 6 12.‘forwarded-in-that-turned-yellow’ = Derived from 2 - 7 13.‘forwarded-soft-out-that-turned-green’ = Derived from 3 - 8 14.‘forwarded-soft-out-that-turned-yellow’...
Page 275 Service Egress and Ingress QoS Policies When collect-stats is enabled, the counters are used by the system to generate the following statistics: a. ‘offered-in’ = 1 + 2 b.‘offered-out’ = 3 + 4 c.‘discard-in’ = 5 + 7 d.‘discard-out’ = 6 + 8 e.‘forward-in’...
Page 276 Service SAP QoS Policy Command Reference The no form of the command removes the explicit IP precedence classification rule from the SAP ingress policy. Removing the rule on the policy immediately removes the rule on all ingress SAPs using the policy. Parameters ip-prec-value —...
Page 277 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 precedent bits used to match against prec reclassification rules come from the Type of Service (ToS) field within the IPv4 header.
Page 278 Service SAP QoS Policy Command Reference 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. By default, the HSMDA uses each queues default queue counters for packets mapped to the queue.
Page 279 Service Egress and Ingress QoS Policies hsmda-counter-override counter-id — The hsmda-counter-override reclassification action is optional and only has significance on SAPs which are created on an HSMDA. When specified, packets matching the IP precedence value will be mapped to the defined HSMDA exception counter-id for the packets queue group.
Page 280 Service SAP QoS Policy Command Reference When an ingress SAP QoS policy with multipoint queues is applied to an Epipe SAP, the multipoint queues are not created. When an ingress SAP QoS policy with multipoint queues is applied to an IES SAP, a multipoint queue will be created when PIM is enabled on the IES interface.
Page 281 Service Egress and Ingress QoS Policies auto-expedite — This keyword allows the system to auto-define the way the queue is serviced by the hardware. When auto-expedite is defined on the queue, the queue is treated in an expedited manner when all forwarding classes mapped to the queue are configured as expedited types nc, ef, h1 or h2.
Page 282 Service SAP QoS Policy Command Reference pool-name — The specified pool-name identifies a named pool where the policy will be applied. 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 283 Service Egress and Ingress QoS Policies group queue-group-name — This optional parameter is used to redirect the forwarding type within the forwarding class to the specified queue-id within the queue-group-name. When the policy is applied, all packets matching the forwarding class and forwarding type will be redirected to the queue within the specified queue group.
Page 284 Service SAP QoS Policy Command Reference no egress-fc Context config>qos>sap-ingress>fc Description This command configures the forwarding class to be used by the egress QOS processing. It overrides the forwarding class determined by ingress classification but no0t the QOS Policy Propagation via BGP.
Page 285 Service Egress and Ingress QoS Policies SAP Ingress Packet State ‘in-remark’ Command Effect Non-Routed, Explicit Out-of-Profile No Effect (non-routed packet) IP Routed, Policed In-Profile in-remark value applied to IP header ToS field IP Routed, Policed Out-of-Profile No Effect (out-of-profile packet) IP Routed, Explicit In-Profile in-remark value applied to IP header ToS field IP Routed, Explicit Out-of-Profile...
Page 286 Service SAP QoS Policy Command Reference The multicast forwarding type includes the unknown unicast forwarding type and the broadcast forwarding type unless each is explicitly defined to a different multipoint queue. When the unknown and broadcast forwarding types are left as default, they will track the defined queue for the multicast forwarding type.
Page 287 Service Egress and Ingress QoS Policies Table 28: Out-remark command effect SAP Ingress Packet State ’out-remark’ Command Effect Non-Routed, Policed In-Profile No Effect (non-routed packet) Non-Routed, Policed Out-of-Profile No Effect (non-routed packet) Non-Routed, Explicit In-Profile No Effect (non-routed packet) Non-Routed, Explicit Out-of-Profile No Effect (non-routed packet) IP Routed, Policed In-Profile No Effect (in-profile packet)
Page 288 Service SAP QoS Policy Command Reference The value specified by prec-value is used to overwrite the Precedence bits within a matching routed packets IP header ToS field. Values 0 to 7 Default None (an explicit Precedence value must be specified) An explicit dscp name or prec value must be specified for out-of-profile remarking to be applied.
Page 289 Service Egress and Ingress QoS Policies 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. The specified queue-id must exist within the policy as a multipoint queue before the mapping can be made.
Page 290 Service SAP QoS Policy Command Reference Parameters queue-id — Specifies the SAP egress queue-id to be associated with the forwarding class. The queue-id must be an existing queue defined in sap-egress policy-id. Values 1 — 8 Default group queue-group-name — This optional parameter is used to redirect the forwarding type within the forwarding class to the specified queue-id within the queue-group-name.
Page 291 Service Egress and Ingress QoS Policies 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 which the policy is applied.
Page 292 Service SAP QoS Policy Command Reference port-redirect-group — 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. This redirection model is known as SAP based redirection.
Page 293 Service Egress and Ingress QoS Policies As inferred above, the variable accounting size offered by the packet-byte-offset command is targeted at the queue and queue group level. When the queue group represents the last-mile bandwidth constraints for a subscriber, the offset allows the HSMDA queue group to provide an accurate accounting to prevent overrun and underrun conditions for the subscriber.
Page 294 Service SAP QoS Policy Command Reference Description This command assigns the low burst maximum class to associate with the HSMDA queue. The no form of the command returns the class id for the queue to the default value. Parameters class-id — Specifies the class identifier of the low burst max class for the HSMDA queue. Values 1 to 32 wrr-weight...
Page 295 Service Egress and Ingress QoS Policies 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). This is the maximum depth of the queue specified in bytes where all packets start to discard. The high and low priority RED slopes provide congestion control mechanisms that react to the current depth of the queue and start a random discard that increases in probability as the queue depth increases.
Page 296 Service SAP QoS Policy Command Reference Parameters hsmda-slope-policy-name — Specifies an existing slope policy within the system. If a slope policy with the specified name does not exist, the slope-policy command will fail without modifying the slope behavior on the queue. Once a slope policy is associated with an HSMDA queue, the policy cannot be deleted.
Page 297 Service Egress and Ingress QoS Policies 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 298 Service SAP QoS Policy Command Reference action Syntax action [fc fc-name] [hsmda-counter-override counter-id] [profile {in | out}] [policer policer- id [{port-redirect-group-queue queue queue-id | queue queue-id | use-fc-mapped- queue}]] no action Context config>qos>sap-egress>ip-criteria>entry 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.
Page 299 Service Egress and Ingress QoS Policies 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 queues default queue counters for packets mapped to the queue.
Page 300 Service SAP QoS Policy Command Reference hsmda-counter-override counter-id — The hsmda-counter-override reclassification action is optional and only has significance on SAPs which are created on an HSMDA. When specified, packets matching the IP precedence value will be mapped to the defined HSMDA exception counter-id for the packets queue group.
Page 301 Service Egress and Ingress QoS Policies The list of flow criteria is evaluated in a top down fashion with the lowest entry ID at the top and the highest entry ID at the bottom. If the defined match criteria for an entry within the list matches the information in the egress packet, the system stops matching the packet against the list and performs the matching entries reclassification actions.
Page 302 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,...
Page 303 Service Egress and Ingress QoS Policies Table 29: IP Protocol Names (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 No Next Header for IPv6 ipv6-opts...
Page 304 Service SAP QoS Policy Command Reference config>qos>sap-egress>ipv6-criteria>entry Description This command creates a context to configure match criteria for ingress SAP QoS policy match IPv6 criteria. When the match criteria have been satisfied the action associated with the match criteria is executed.
Page 305 This command configures a VCI based filter entry in the SAP ingress QoS policy. This command applies only to the 7450 ESS and 7750 SR. This new criterion has only take affect when applied to a VPI SAP of an apipe VLL service of type atm-vpc.
Page 306 Service SAP QoS Policy Command Reference It is strongly recommended that the user does not enable cell-concatenation on the spoke-SDP when a VCI QoS filter is applied to the SAP. The filter will match against the VCI in the header of the first cell in the concatenated packet.
Page 307 Service Egress and Ingress QoS Policies 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 ESDMA queue mappings for the same forwarding class and the hsmda node is used to separate the HSMDA mappings from the standard mappings This allows the same QoS policy to be used on a standard MDA attached SAP and an HSMDA attached SAP.
Page 308 Service SAP QoS Policy Command Reference Table 31: Ingress HSMDA Queue Mapping Behavior Based on Forwarding Type Queue Mappings For Each Forwarding Type Service Type Queue Broadcast Multicast Unknown Epipe All packets matching None None None the FC All packets matching Packets with Broadcast IP Multicast Packets None...
Page 309 Service Egress and Ingress QoS Policies Description This command is used to configure the policer’s PIR leaky bucket’s high priority violate threshold. The high-prio-only command is applied to the MBS value to derive the bucket’s low priority violate threshold. For egress, trusted in-profile packets and untrusted high priority packets use the policer’s high priority violate threshold while trusted out-of-profile and untrusted low priority packets use the policer's low priority violate threshold.
Page 310 Service SAP QoS Policy Command Reference To match on the IPv4 or IPv6 destination address, specify the address and its associated mask, e.g., 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 can also be used for IPv4. The no form of this command removes the destination IPv4 or IPv6 address match criterion. Default No destination IP match criteria Parameters...
Page 311 Service Egress and Ingress QoS Policies Description This command configures a destination TCP or UDP port number or port range for a SAP QoS policy match criterion. The no form of this command removes the destination port match criterion. Default none Parameters lt | gt | eq dst-port-number —...
Page 312 Service SAP QoS Policy Command Reference The no form of this command removes the match criterion and matches all packets regardless of whether they are fragmented or not. Default no fragment Parameters true — Specifies to match on all fragmented IPv6 packets. A match will occur for all packets that contain an IPv6 Fragmentation Extension Header.
Page 313 Service Egress and Ingress QoS Policies ipv6-address — Specifies the IPv6 prefix for the IP match criterion in hex digits. Values ipv6-address: x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x: [0 to FFFF]H d: [0 to 255]D prefix — Specifies the IPv6 prefix length for the ipv6-address expressed as a decimal integer. Values 1 to 128 mask —...
Page 314 Service SAP QoS Policy Command Reference 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 315 Service Egress and Ingress QoS Policies 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. Default 7 (decimal) (exact match) Values 1 to 7 (decimal) dsap...
Page 316 Service SAP QoS Policy Command Reference dst-mac Syntax dst-mac ieee-address [ieee-address-mask] no dst-mac Context config>qos>sap-ingress>mac-criteria>entry 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. Default none Parameters...
Page 317 Service Egress and Ingress QoS Policies 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. Default None Parameters...
Page 318 Service SAP QoS Policy Command Reference 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 outer tag on ingress is the first tag after any service delimiting tags.
Page 319 Service Egress and Ingress QoS Policies 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 two-byte protocol id that is part of the IEEE 802.3 LLC SNAP Ethernet Frame that follows the three-byte OUI field.
Page 320 Service SAP QoS Policy Command Reference To configure all packets with a source MAC OUI value of 00-03-FA are subject to a match condition, then the entry should be specified as: 003FA000000 0xFFFFFF000000 Default 0xFFFFFFFFFFFF (hex) (exact match) Values 0x00000000000000 to 0xFFFFFFFFFFFF (hex) ssap Syntax ssap ssap-value [ssap-mask]...
Page 321 Service Egress and Ingress QoS Policies Service Egress QoS Policy Forwarding Class Commands Syntax fc fc-name 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.
Page 322 Service SAP QoS Policy Command Reference When the sap-egress policy is applied to a SAP, the parent schedulers of the queues need to be configured in the scheduler-policy applied to the SAP or the multi-service site. sla — When the sap-egress policy is applied to an sla-profile for a subscriber, the parent schedulers of the queues need to be configured in the scheduler-policy applied to the same sla-profile.
Page 323 Service Egress and Ingress QoS Policies • 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 324 Service SAP QoS Policy Command Reference 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-egress QoS policy. Values 1 to 63 Default none...
Page 325 Service Egress and Ingress QoS Policies description Syntax description description string no description Context config>qos>sap-egress>policer Description The description command is used to define an informational ASCII string associated with the policer control policy. The string value can be defined or changed at any time once the policy exists. The no form of this command is used to remove an explicit description string from the policer.
Page 326 Service SAP QoS Policy Command Reference The hardware also needs to adapt the given mbs and cbs values into the PIR bucket violate threshold (discard) and the CIR bucket exceed threshold (out-of-profile). The hardware may not have an exact threshold match which it can use. In R8.0, the system treats the mbs and cbs values as minimum threshold values.
Page 327 Service Egress and Ingress QoS Policies Description This command is used to configure the policer’s CIR leaky bucket’s exceed threshold. The CIR bucket’s exceed threshold represents the committed burst tolerance allowed by the policer. If the policer’s forwarding rate is equal to or less than the policer's defined CIR, the CIR bucket depth hovers around the 0 depth with spikes up to the maximum packet size in the offered load.
Page 328 Service SAP QoS Policy Command Reference Description This command enables the forwarding of traffic exceeding the PIR for a SAP egress or a network egress queue group (configured in the egress queue group template) policer. This traffic is forwarded as exceed-profile instead of being dropped. Default no enable-exceed-pir high-prio-only...
Page 329 Service Egress and Ingress QoS Policies The policer’s mbs size defined in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. The no form of this command returns the policer to its default MBS size. Default None Parameters...
Page 330 Service SAP QoS Policy Command Reference Parameters add bytes — The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the policer for rate metering, profiling and accounting purposes.
Page 331 On the 7450 ESS and 7750 SR, for subscribers, the policer control hierarchy is created through the policer-control-policy applied to the sub-profile used by the subscriber. A unique policer control hierarchy is created for each subscriber associated with the sub-profile.
Page 332 Service SAP QoS Policy Command Reference rate Syntax rate {max | kilobits-per-second} [cir {max | kilobits-per-second}] no rate Context config>qos>sap-egress>policer Description This command is used to configure the policer’s metering and optional profiling rates. The metering rate is used by the system to configure the policer’s PIR leaky bucket’s decrement rate while the profiling rate configures the policer’s CIR leaky bucket’s decrement rate.
Page 333 Service Egress and Ingress QoS Policies cir {max | kilobits-per-second} — The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit kilobits-per-second parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket.
Page 334 Service SAP QoS Policy Command Reference The stat-mode setting defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied. If insufficient policer counter resources exist to implement the override, the stat-mode override command will fail. The previous stat-mode setting active for the policer will continue to be used by the policer.
Page 335 Service Egress and Ingress QoS Policies offered-profile-no-cir — Counter resource allocation: 2 The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters. The offered-profile-no-cir mode is most useful when profile based offered, discard and forwarding stats are required from the egress policer, but a CIR is not being used to recolor the soft in-profile and out-of-profile packets.
Page 336 Service SAP QoS Policy Command Reference When collect-stats is enabled, the counters are used by the system to generate the following statistics: offered-in = 1 offered-out = 4 offered-undefined = 2+3 discard-in = 5 + 6 discard-out = 7 + 8 forward-in (includes forward-exceed that were in) = 9+10 forward-out (includes forward-exceed that were soft or out) = 11+12 offered-total-cir —...
Page 337 Service Egress and Ingress QoS Policies The impact of using offered-limited-capped-cir stat-mode while profile-capped mode is disabled are 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 338 Service SAP QoS Policy Command Reference dropped-in-that-stayed-green = Same as 1 dropped-in-that-turned-yellow-or-red = Same as 2 dropped-soft-that-turned-green = Same as 3 dropped-soft-that-turned-yellow-or-red = Same as 4 10. dropped-out-that-stayed-yellow-or-turned-red = Same as 5 11. forwarded-in-that-stayed-green = Derived from 1 - 6 12.
Page 339 FC. If the optional exceed/in/out-profile is specified, the command will remark different DSCP code points depending on whether the packet was classified to be exceed, in, or out- of-profile ingress to the node. This is supported on FP2- and higher-based line cards for the 7450 ESS. Default not enabled Parameters dscp-name —...
Page 340 Service SAP QoS Policy Command Reference Description This command defines a value to be used for remarking packets for the specified FC. If the optional in/out/exceed-profile is specified, the command will remark different PREC values depending on whether the packet was classified to be in, exceed, or out-of-profile. Parameters ip-prec-value —...
Page 341 Service Egress and Ingress QoS Policies Context config>qos Description This command is used to create or edit a Service Egress QoS policy. The egress policy defines the Service Level Agreement (SLA) for service packets as they egress on the SAP. Policies in effect are templates that can be applied to multiple services as long as the scope of the policy is template.
Page 342 Service SAP QoS Policy Command Reference Parameters policy-id — The policy-id uniquely identifies the policy on the router. Default none Values 1 to 65535 policy-name — The policy-name uniquely identifies the policy. Values Valid names consist of any string up to 64 characters long. Policies must first be created with a policy-id, after which a policy-name can be assigned and used as an alias to reference the policy during configuration changes.
Page 343 Service Egress and Ingress QoS Policies Context config>qos>sap-egress>fc Description This command explicitly defines the egress IEEE 802.1p (dot1p) bits marking for fc-name. When the marking is set, all packets of fc-name that have either an IEEE 802.1q or IEEE 802.1p encapsulation use the explicitly defined dot1p-value.
Page 344 Service SAP QoS Policy Command Reference de-mark-inner Syntax [no] de-mark-inner [force de-value] 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. If no de-value is present, the default values are used for the marking of the DE bit: for example, 0 for in-profile packets, 1 for out-of-profile ones–...
Page 345 Service Egress and Ingress QoS Policies This command takes precedence over the de-mark command if both are specified in the same policy and over the default action. If no de-mark commands are used, the DE bit is preserved if an ingress outer or single tag exists, or set to zero otherwise.
Page 346 Service SAP QoS Policy Command Reference Parameters dot1p-value — Specifies the 802.1p value to set for in-profile frames in this forwarding class. Values 0 to 7 in-profile dot1p-value — Specifies the 802.1p value to set for in-profile frames in this forwarding class.
Page 347 Service Egress and Ingress QoS Policies This command is supported on FP2 and higher based hardware, and is otherwise ignored. Default Parameters dot1p-value — Specifies the 802.1p value to set for in-profile frames in this forwarding class. Values 0 to 7 in-profile dot1p-value —...
Page 348 Service SAP QoS Policy Command Reference 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 349 Service Egress and Ingress QoS Policies Service Queue QoS Policy Commands adaptation-rule Syntax adaptation-rule [pir adaptation-rule] [cir adaptation-rule] no adaptation-rule Context config>qos>sap-ingress>queue config>qos>sap-egress>queue Description This command defines the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware.
Page 350 For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint. This command applies only to the 7450 ESS and 7750 SR. The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy.
Page 351 Sonet or SDH port or channel. Queues operating on egress Ethernet ports automatically calculate the frame encapsulation overhead based on a 20 byte per packet rule (8 bytes for preamble and 12 bytes for Inter-Frame Gap). This command applies only to the 7450 ESS and 7750 SR.
Page 352 Service SAP QoS Policy Command Reference 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 353 — 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 354 Service SAP QoS Policy Command Reference size — When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and by default is interpreted as the burst limit in Kilobytes.
Page 355 Service Egress and Ingress QoS Policies 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 356 Service SAP QoS Policy Command Reference hi-low-prio-only Syntax hi-low-prio-only percent no hi-low-prio-only Context config>qos>sap-egress>queue config>qos>qgrps>egr>qgrp>queue Description The hi-low-prio-only command configures the percentage of buffer space for the queue, used exclusively by higher priority (in-profile and out-of-profile) packets. The specified value overrides the default value for the context.
Page 357 Service Egress and Ingress QoS Policies Syntax mbs size [bytes | kilobytes] no mbs Context config>qos>sap-egress>queue config>qos>sap-ingress>queue Description The Maximum Burst Size (MBS) command provides the explicit definition of 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 358 Service SAP QoS Policy Command Reference Description This command is used to modify the size of each packet handled by the queue by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the bucket depth impact is changed.
Page 359 Service Egress and Ingress QoS Policies Description This command is used to modify the size of each packet handled by the queue by adding or subtracting a number of bytes. The actual packet size is not modified; only the size used to determine the ingress scheduling and profiling is changed.
Page 360 Service SAP QoS Policy Command Reference containing the scheduler-name being directly or indirectly applied (through a multi-service customer site) to the egress SAP. 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 361 Service Egress and Ingress QoS Policies All weight values from all weighted active queues and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the queue or scheduler after the strict children are serviced.
Page 362 Service SAP QoS Policy Command Reference config>qos>sap-ingress>queue Description The percent-rate command within the SAP ingress and egress QOS policy enables supports for a queue’s PIR and CIR rate to be configured as a percentage of the egress port’s line rate or of its parent scheduler’s rate.
Page 363 The no pool command is used to remove a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool. This command only applies to the 7450 ESS and 7750 SR. Default...
Page 364 Service SAP QoS Policy Command Reference In this context, the port-parent command is mutually exclusive to the parent command (used to create a parent/child association between a queue and an intermediate scheduler). Executing a port- parent command when a parent definition is in place causes the current intermediate scheduler association to be removed and replaced by the defined port-parent association.
Page 365 Service Egress and Ingress QoS Policies cir-level cir-level — Defines the port priority the queue or scheduler will use to receive bandwidth for its within-cir offered-load. If the cir-weight parameter is set to a value of 0 (the default value), the queue or scheduler does not receive bandwidth during the port schedulers within-cir pass and the cir-level parameter is ignored.
Page 366 Service SAP QoS Policy Command Reference The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned. Values [1 to 200000000 | max] kbps Default cir-rate — The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional.
Page 367 The cir keyword is used to configure the rate threshold between the in-profile and out- of-profile state of the queue during scheduling from the queue. This command only applies to the 7450 ESS and 7750 SR. Since the CIR leaky bucket is updated during scheduling events and not enqueuing events. The profiling function is not based on packet arrival.
Page 368 Service SAP QoS Policy Command Reference The no form of the command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0). Parameters pir-rate — Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined.
Page 369 Service Egress and Ingress QoS Policies Pool-per-queue WRED When the wred-queue mode pool-per-queue command is defined and the queue ID is created on FP2 or higher based hardware, a buffer pool is created specifically for the queue and the queue obtains all buffers from that pool.
Page 370: Show Commands
Service SAP QoS Policy Command Reference mode {native | pool-per-queue} — The mode species whether the WRED per queue is using the native FP3 WRED capabilities or the FP2 and later hardware pool per queue. Values native - use the hardware per queue WRED capabilities of the FP3 and requires slope-usage exceed-low.
Page 371 Service Egress and Ingress QoS Policies Label Description (Continued) Template Implies that this policy can be applied to multiple SAPs on the router. Description A text string that helps identify the policy’s context in the configuration file. Default FC Specifies the default forwarding class for the policy. Priority Specifies the enqueuing priority when a packet is marked with a dot1p- value specified.
Page 372 Service SAP QoS Policy Command Reference Label Description (Continued) closest The operational PIR for the queue will be the rate closest to the rate specified using the rate command. Specifies the default CBS value for the queue. value Specifies the value to override the default reserved buffers for the queue. Specifies the default MBS value.
Page 373 Service Egress and Ingress QoS Policies Label Description (Continued) Priority This parameter specifies the default enqueuing priority overrides for all packets received on an ingress SAP using this policy that match this rule. High Specifies that the high enqueuing parameter for a packet increases the likelihood of enqueuing the packet when the ingress queue is congested.
Page 374 Service SAP QoS Policy Command Reference Label Description (Continued) ESnap-oui-zero Specifies an IEEE 802.3 LLC SNAP Ethernet Frame OUI zero or non- zero value to be used as a Service Ingress QoS policy match. DSAP Specifies an Ethernet 802.2 LLC DSAP value or range for an ingress SAP QoS policy match.
Page 375 Service Egress and Ingress QoS Policies Policy-id : 3:P2 Scope : Template Default FC : be Priority : Low Criteria-type : IP Name : (Not Specified) Description : Auto-created pcc-rule sap-ingress qos policy ------------------------------------------------------------------------------- Dynamic Configuration Information ------------------------------------------------------------------------------- PccRule Insert Point : 40000 (size 100* DynPlcr Insert Point : 20 (size 20) Shared Policies : Def : Def...
Page 376 Service SAP QoS Policy Command Reference Fragment : Off : Default Priority : Default Policer : 20 … ------------------------------------------------------------------------------- IPv6 Match Criteria ------------------------------------------------------------------------------- No Match Criteria Entries found. =============================================================================== QoS Sap Ingress =============================================================================== Sap Ingress Policy (100) ------------------------------------------------------------------------------- Policy-id : 100 Scope : Template Default FC...
Page 377 Service Egress and Ingress QoS Policies ------------------------------------------------------------------------------- SubFC Profile In-Remark Out-Remark ------------------------------------------------------------------------------- None None None None None None None None None None None None None None None None None None ------------------------------------------------------------------------------- Dot1p Priority ------------------------------------------------------------------------------- High High ------------------------------------------------------------------------------- DSCP Priority ------------------------------------------------------------------------------- af41 High -------------------------------------------------------------------------------...
Page 378 Service SAP QoS Policy Command Reference - SAP : 1/1/9:0 override =============================================================================== *A:ALA-48>config>qos# config>qos# show qos sap-ingress 2 detail ======================================================================== QoS Sap Ingress ------------------------------------------------------------------------ Sap Ingress Policy (2) ------------------------------------------------------------------------ Policy-id Scope : Template Default FC : be Priority : Low Criteria-type : None ------------------------------------------------------------------------...
Page 379 Service Egress and Ingress QoS Policies Policy-Id Scope Name Description ------------------------------------------------------------------------------- Template default Default SAP ingress QoS policy. Template Template ------------------------------------------------------------------------------- Number of policies : 3 ------------------------------------------------------------------------------- =============================================================================== *A:# sap-egress Syntax sap-egress [policy-id] [association | match-criteria | hsmda | detail] Context show>qos Description...
Page 380 Service SAP QoS Policy Command Reference Label Description (Continued) The operational CIR for the queue will be equal to or less than the administrative rate specified using the rate command. closest The operational PIR for the queue will be the rate closest to the rate specified using the rate command without exceeding the operational PIR.
Page 381 Service Egress and Ingress QoS Policies 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. Explicit/Default Explicit Specifies the egress IEEE 802.1p (dot1p) bits marking for fc-name. Default Specifies that the default dot1p value (0) is used.
Page 382 Service SAP QoS Policy Command Reference ------------------------------------------------------------------------------- Policy-id : 1010 Scope : Template =============================================================================== A:ALA-49# A:ALA-49# show qos sap-egress 1010 detail =============================================================================== QoS Sap Egress =============================================================================== ------------------------------------------------------------------------------- Sap Scheduler Policy (1010) ------------------------------------------------------------------------------- Policy-id : 1010 Scope : Template ------------------------------------------------------------------------------- Queue CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt...
Page 383 Service Egress and Ingress QoS Policies Default None ------------------------------------------------------------------------ Associations ------------------------------------------------------------------------ No Associations Found. ------------------------------------------------------------------------ Mirror SAPs ------------------------------------------------------------------------ No Mirror SAPs Found. ======================================================================== config>qos# configure #-------------------------------------------------- echo "QoS Policy Configuration" #-------------------------------------------------- match-list 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...
Page 384 Service SAP QoS Policy Command Reference Description : IPv4 prefix list ------------------------------------------------------------------------------- IP Prefixes ------------------------------------------------------------------------------- 10.0.0.0/8 192.168.0.0/16 ------------------------------------------------------------------------------- No. of Prefixes : 2 ------------------------------------------------------------------------------- =============================================================================== *A:PE# queue Syntax queue from {sap sap-id | queue-group port-id queue-group-name | subscriber subscriber- id | network {mda-id | port-id} | system {card slot-number | mda mda-id port port-id}} {ingress | egress} [id queue-id] Context show>qos...
Page 385 If the specified subscriber-id does not exist, the system should return ‘The specified subscriber does not exist’. This parameter applies to the 7450 ESS and 7750 SR only. network {mda-id | port-id} — The network keyword is used to specify that the system should find and display the queue information for the queues associated with the specified mda-id or port-id.
Page 386 Service SAP QoS Policy Command Reference amount decremented from the bucket is a function of the amount of time that has elapsed since the last bucket update and the queue’s shaping rate (PIR). If the queue’s shaping rate is configured as 1Mbps and 1ms has elapsed since the last bucket update, the system will decrement the PIR bucket by 125 bytes.
Page 387 Service Egress and Ingress QoS Policies member-queues [at-risk-only] — The member-queues optional keyword is used to include a list of all queues attached to the specified burst-control-group-name. The optional at-risk-only keyword may be added to limit the displayed queues to only include queues that are considered ‘at-risk’...
Page 388 Service SAP QoS Policy Command Reference Quality of Service Guide...
Page 389: Queue Sharing And Redirection
Queue Sharing and Redirection In This Section This section provides information to configure queue groups using the command line interface. Topics in this section include: • Queue Sharing and Redirection → Pseudowire Shaping for Layer 2 and Layer 3 Services •...
Page 390: Supported Platforms
Queue Sharing and Redirection • Network ingress supports the creation of multiple queue groups at the ingress forwarding plane level of the IOM/IMM/XMA. These queue groups may only contain policers. • Network egress supports the creation of multiple queue groups per egress port. These queue groups may contain queues only, or queues and policers.
Page 391: Ingress Access Port Queue Group Hardware Queue Allocation
Queue Sharing and Redirection The situation is different for a shared or port-queuing model that is based on policing color packets that conform or exceed a static rate before the single queue and that use WRED or drop tail functions to essentially reserve room for the conforming packets. In this model, there is no way for the conforming packets to go to the head of line in the view of the port scheduler.
Page 392: Network Port Queue Groups For Ip Interfaces
Queue Sharing and Redirection 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. If sufficient hardware queues are unavailable, the XCM provisioning will fail. Adding queues to the queue group template or adding additional ingress access port queue groups will continue to require more hardware queue to be allocated, with the configurations failing if there are not sufficient available.
Page 393: Qos On Ingress Bindings
Queue Sharing and Redirection 2. Apply the queue-group template to the network ingress forwarding plane where there exists a network IP interface that the PW packets can be received on. This creates one instance of the template on the ingress of the FP. One or more instances of the same template can be created.
Page 394 Queue Sharing and Redirection Figure 19: Ingress QoS Control on VPRN Bindings auto-bind or spoke-sdp bindings VPRN MPLS/IP VPRN VPRN Ingress QoS Control al_0647 An ingress queue group must be configured and applied to the ingress network FP where the traffic is received for the VPRN.
Page 395: Queue Group Templates And Port Queue Groups
Queue Sharing and Redirection This is supported for all available transport tunnel types and is independent of the label mode (vrf or next-hop) used within the VPRN. It is also supported for Carrier-Supporting-Carrier VPRNs. The ingress network interfaces on which the traffic is received must be on FP2- and higher- based hardware.
Page 396: Port Queue Groups
Queue Sharing and Redirection Port Queue Groups Once 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 397: Redirection Models
Queue Sharing and Redirection Once an ingress queue group template is defined, a forwarding plane queue group with the same name may be created on an ingress forwarding plane of an IOM, IMM, or XMA. Forwarding plane queue groups are named objects that act as a container for a group of policers.
Page 398: Access Sap Forwarding Class Based Redirection
Queue Sharing and Redirection 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 399 Queue Sharing and Redirection 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 400: Ingress And Egress Sap Forwarding Class Redirection Association Rules
Queue Sharing and Redirection 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. On ingress: config>service>epipe>sap sap-id ingress...
Page 401 Queue Sharing and Redirection When a SAP ingress QoS policy forwarding class redirection is removed from a queue group queue ID: • If the forwarding class is being moved to another queue group queue ID that does not exist within an ingress queue group template, the redirection removal from the current queue group queue ID will fail.
Page 402: Sap-Based Provisioning Model
Queue Sharing and Redirection • The system decrements the queue ID association counter within the queue group template for the queue ID previously specified in the forwarding class redirection. • The system decrements the port queue group association counter for each egress port queue group where the SAP egress QoS policy is applied to a SAP.
Page 403 Queue Sharing and Redirection • If a redirected policer ID in the SAP ingress QoS policy does not match a policer ID in the named ingress queue group template, the redirection will fail. • If the SAP ingress QoS policy is currently applied to a non-Ethernet port or an Ethernet port where the specified ingress queue group instance does not exist on the forwarding plane, the redirection will fail.
Page 404: Access Queue Group Statistics
Queue Sharing and Redirection • If an egress QoS policy containing one or more redirections is applied to a SAP, but either no queue group instance is specified at association time, or a named queue group instance is specified and either the queue group name or the instance identifier does not correspond to a queue group that has been created on the egress port, then the association will be rejected.
Page 405: Network Ip Interface Forwarding Class-Based Redirection
Queue Sharing and Redirection This means that it is not possible to perform accounting within a queue group based on the source SAPs feeding packets to the queue. That is, the statistics associated with the SAP will not include packets redirected to a queue group queue. If the user enables the packet-byte-offset {add bytes | subtract bytes} option under the ingress queue-group policer, the byte counters of that policer will reflect the adjusted packet size.
Page 406 Queue Sharing and Redirection The system keeps an association counter for each queue group template and an association counter for each queue ID within the template. The system also keeps an association counter for each queue group created on a port. When a network QoS policy is applied to an IP interface with the queue group parameter specified: •...
Page 407: Egress Network Ip Interface Statistics
Queue Sharing and Redirection • If removing, the queue ID association counter is decremented within each queue group template based on the queue ID removed from the policy. • If adding, the queue ID association counter is incremented within each queue group template based on the queue ID added to the policy.
Page 408: Feature Configuration
Queue Sharing and Redirection Based Redirection 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 which is instantiated on the ingress Forwarding Plane (FP) where the PW packets are received.
Page 409: Provisioning Model
Queue Sharing and Redirection 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. Provisioning Model Operationally, the provisioning model in the case of the ingress PW shaping feature consists of the following steps: 1.
Page 410 Queue Sharing and Redirection 6. When a PW FC is redirected to use a policer in a named policer queue-group and the queue-group name does not exist, the association is failed at the time the user associates the ingress context of a spoke-SDP to the named queue-group. In such a case, the PW packet feeds directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the MDA/FP.
Page 411: Ingress Packet Classification
Queue Sharing and Redirection Ingress Packet Classification When a PW is redirected to use a policer queue-group, the classification of the packet for the purpose of FC and profile determination is performed according to default classification rule or the QoS filters defined in the ingress context of the network QoS policy applied to the PW. This is true regardless if an instance of the named policer queue-group exists on the ingress FP the PW packet is received on.
Page 412: Provisioning Model
Queue Sharing and Redirection config>qos>network>egress>fc>port-redirect-group {queue queue-id | policer policer-id [queue queue-id]} There are three possible outcomes when executing this command. • The user can redirect a FC to use a queue in a queue-group and in which case there are no policers used.
Page 413 Queue Sharing and Redirection b. One or more spoke-sdps can have their FCs redirected to use queues only or queues and policers in the same queue-group instance. The following are the constraints and rules of this provisioning model: 1. Queue-groups containing queues only or policers and queues can be instantiated in the network egress context of an Ethernet port on IOM3/IMM.
Page 414: Egress Marking Of Pw Packet Header
Queue Sharing and Redirection b. When a PW packet for that FC is forwarded and an instance of the referenced queue-group name does not exist on that egress port, the PW packet is fed directly to the corresponding egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.
Page 415: Ingress Per Sap Statistics With Ingress Queue Groups
Queue Sharing and Redirection If the packet does not have an IP header, DSCP or IP-precedence based matching is not performed. The IP precedence and DSCP based re-classification are only supported on a PW used in an IES or VPRN spoke-interface. The CLI blocks the application of a network QoS policy with the egress re-classification commands to a network IP interface or to a spoke-SDP part of L2 service.
Page 416 Queue Sharing and Redirection A:PE1# show service id 100 sap 1/1/3 sap-stats =============================================================================== Service Access Points(SAP) =============================================================================== Service Id : 100 : 1/1/3 Encap : null Description : (Not Specified) Admin State : Up Oper State : Up Flags : None Multi Svc Site : None Last Status Change : 04/04/2014 11:45:25...
Page 417: Ingress And Egress Pw Statistics
Queue Sharing and Redirection For. All =============================================================================== A:PE1# Ingress and Egress PW Statistics The PW forwarded packet and octet statistics (SDP binding statistics) are currently supported for both ingress and egress and are available via show command, monitor command, and accounting file.
Page 418: Queue Group Behavior On Lag
Queue Sharing and Redirection Queue Group Behavior on LAG 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. 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 group queue.
Page 419: Basic Configurations
Queue Sharing and Redirection Adding a Port to a LAG When adding a port to a LAG group, the port must have the same queue groups defined as the existing ports on the LAG before it will be allowed as a member. This includes all queue group override parameters.
Page 420: Configuring Egress Queue Group Template
Basic Configurations mbs 100 exit exit exit ---------------------------------------------- *A:Dut-T>cfg>qos>qgrps# Note: To fully use the queue group feature to save queues, you must explicitly map all forwarding classes to queue group queues. This rule is applicable to SAP ingress, SAP egress and network QoS policies. Configuring Egress Queue Group Template The following displays an egress queue group template configuration example: *A:Dut-T>cfg>qos>qgrps# info...
Page 421: Applying Egress Queue Group To Sap Egress Policy
Queue Sharing and Redirection ---------------------------------------------- queue 1 create exit queue 11 multipoint create exit fc "af" create queue 2 group "QG_ingress_1" exit fc "be" create queue 1 group "QG_ingress_1" exit fc "ef" create queue 3 group "QG_ingress_1" exit fc "nc" create queue 4 group "QG_ingress_1"...
Page 422: Sap-Based Egress Queue Re-Direction
Basic Configurations SAP-based Egress Queue Re-direction The following displays a SAP egress policy configuration with port-redirect-group-queue construct (shown for both regular and HS-MDA egress queues) and the actual queue-group- name is determined by the SAP egress QoS configuration: *A:Dut-A# configure qos sap-egress 3 *A:Dut-A>config>qos>sap-egress# info ---------------------------------------------- queue 1 create...
Page 423: Configuring Queue Group On Ethernet Access Ingress Port
Queue Sharing and Redirection exit exit fc nc create queue 3 port-redirect-group-queue hsmda queue 3 port-redirect-group-queue exit exit ---------------------------------------------- This is to be in-conjunction with: *A:Dut-A# configure service vpls 1 *A:Dut-A>config>service>vpls# info ---------------------------------------------- shutdown exit sap 9/1/2:1 create egress qos 3 port-redirect-group qg1 instance 101 exit exit Configuring Queue Group on Ethernet Access Ingress Port...
Page 424: Configuring Overrides
Basic Configurations → Assign the QoS policy to the SAP The following displays an Ethernet access ingress port queue-group configuration example: *A:Dut-T>config>port# /configure port 9/2/1 *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...
Page 425: Configuring Queue Group On Ethernet Access Egress Port
Queue Sharing and Redirection ingress queue-group "QG_ingress_1" create queue-overrides queue 2 create rate 800000 cir 20000 exit exit exit exit egress queue-group "QG_egress_1" create exit exit exit exit no shutdown ---------------------------------------------- *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"...
Page 426: Configuring Queue Group For Network Egress Traffic On Port
Basic Configurations → Identify which egress port (or ports) on which the queue group will be needed (for LAG use the primary port member) → Create a queue group instance with the same name as the template on the port or ports •...
Page 427: Configuring Queue Group For Network Ingress Traffic On Forwarding Plane
Queue Sharing and Redirection → Create the queues and/or policers within the queue group template. • Queue Group Creation: → Identify the egress port (or ports) on which the queue group will be needed (for LAG use the primary port member). →...
Page 428: Using Queue Groups To Police Ingress/Egress Traffic On Network Interface
Basic Configurations → Map the desired ingress forwarding classes within the network QoS policy to the specific policer IDs within the group (the group name will be supplied when the QoS policy is applied to the IP interface). • Apply the network QoS policy: →...
Page 429: Configuring Ingress/Egress Pw Shaping Using Spoke-Sdp Forwarding Class-Based Redirection
Queue Sharing and Redirection fp 1 ingress network queue-group "Ingress_QG_1" instance 550 create exit exit exit exit no shutdown port 1/1/3 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"...
Page 430 Basic Configurations exit exit egress queue-group "QGEgr1" create queue 1 best-effort create exit policer 1 create exit 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...
Page 431 Queue Sharing and Redirection #-------------------------------------------------- card 3 fp 1 ingress network queue-group "QGIng1" instance 1 create exit queue-group "QGIng1" instance 2 create 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"...
Page 432: Specifying Qos Policies On Service Saps
Basic Configurations spoke-sdp 1:101 vc-type vlan create description "Description for Sdp Bind 1 for Svc ID 1" ingress qos 10 fp-redirect-group "QGIng1" instance 1 exit egress qos 10 port-redirect-group "QGEgr1" instance 1 exit static-mac 00:00:28:00:01:02 create no shutdown exit no shutdown exit router interface "ip-12.1.1.1"...
Page 433: Qos Queue Group Template Command Reference
Queue Sharing and Redirection QoS Queue Group Template Command Reference Command Hierarchies • Configuring Egress Queue Group Templates • Configuring Ingress Queue Group Templates • Show Commands • Monitor Commands Configuring Egress Queue Group Templates config — qos — queue-group-templates —...
Page 434: Configuring Ingress Queue Group Templates
QoS Queue Group Template Command Reference — 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 [queue-type] [create] — no queue queue-id —...
Page 435 Queue Sharing and Redirection — no queue-group queue-group-name — policer policer-id [create] — [no] policer — adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}] — no adaptation-rule — {size [bytes | kilobytes] | default} — no —...
Page 436: Show Commands
QoS Queue Group Template Command Reference Show Commands show — qos — queue-group [queue-group-name] [ingress | egress] [association | detail] — queue-group summary — sap-egress [policy-id] [association | match-criteria| hsmda | detail] — sap-ingress [policy-id] [association | match-criteria| hsmda | detail] show —...
Page 437: Command Descriptions
Queue Sharing and Redirection Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context cfg>qos>qgrps>egr>qgrp cfg>qos>qgrps>ing>qgrp cfg>qos>qgrps>ing>qgrp>policer Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the content in the configuration file.
Page 438 QoS Queue Group Template Command Reference egress Syntax egress Context cfg>qos>qgrps Description This command enables the context to configure QoS egress queue groups. Egress queue group templates can be applied to egress Ethernet ports to create an egress queue group. Default none queue-group...
Page 439 Queue Sharing and Redirection Policers are created and used in a similar manner to queues. The policer ID space is separate from the queue ID space, allowing both a queue and a policer to share the same ID. The ingress queue-group template may have up to 32 policers (numbered 1 through 32) and may be defined, while the egress queue-group template supports a maximum of 8 (numbered 1 through 8).
Page 440 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 which when exist are used to identify the egress port queue group.
Page 441 Queue Sharing and Redirection Once a policer is created, it cannot be deleted from the queue-group template unless any forwarding classes that are redirected to the policer are first removed. The no form of this command deletes the policer. Parameters policer-id —...
Page 442 QoS Queue Group Template Command Reference Description This command is used to redirect the FC of a packet of a pseudowire or network IP interface to an ingress forwarding plane queue-group. It defines the mapping of a FC to a policer-id and redirects the lookup of the policer of the same ID in some ingress forwarding plane queue-group instance.
Page 443 Queue Sharing and Redirection Description This command creates a queue for use in a queue group template. Once created, the defined queue-id acts as a repository for the default parameters for the queue. The template queue is created on each queue-group object which is created with the queue group template name.
Page 444 QoS Queue Group Template Command Reference min — The min (minimum) option is mutually exclusive with the max and closest options. When min is defined, the operational PIR for the queue will be equal to or greater than the administrative rate specified using the rate command. closest —...
Page 445 Queue Sharing and Redirection size — When a numeric value is specified (size), the system interprets the value as an explicit burst limit size. The value is expressed as an integer and by default is interpreted as the burst limit in Kilobytes.
Page 446 QoS Queue Group Template Command Reference dynamic-mbs Syntax [no] dynamic-mbs Context config>qos>qgrps>egr>qgrp>queue Description This command enables support for dynamically modifying the MBS size of a queue using H-QoS in order to maintain the maximum latency for traffic in the queue based on the queue’s configured MBS and the ratio of its operational PIR to its administrative PIR.
Page 447 Queue Sharing and Redirection The hi-low-prio-only drop tail exists also for egress network queues in a network queue policy, however, in these policies it is not configurable and has a default of an additional 10% of the MBS value on top of the high priority only. Default Parameters percent —...
Page 448 QoS Queue Group Template Command Reference Parameters percent-of-mbs — The percent-of-mbs parameter is required when specifying high-prio-only and is expressed as a percentage. Values 0 to 100 Default Syntax mbs size [bytes | kilobytes] no mbs Context config>qos>qgrps>egr>qgrp>queue config>qos>qgrpid>ing>qgrp>queue config>qos>qgrpid>egr>qgrp>policer config>qos>qgrpid>ing>qgrp>policer Description The Maximum Burst Size (MBS) command specifies the default maximum buffer size for the template...
Page 449 Queue Sharing and Redirection The PIR bucket’s violate threshold represent 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. If the offered rate increases beyond the metering rate, the amount of data allowed above the rate is capped by the threshold.
Page 450 QoS Queue Group Template Command Reference Parameters add bytes — The add keyword is mutually exclusive to the subtract keyword. Either add or subtract must be specified. When add is defined the corresponding bytes parameter specifies the number of bytes that is added to the size each packet associated with the queue for scheduling, profiling and accounting purposes.
Page 451 Queue Sharing and Redirection The parent scheduler can be made unavailable due to the removal of a scheduler policy or scheduler. When an existing parent scheduler is removed or inoperative, the queue enters the orphaned state mentioned above and automatically return to normal operation when the parent scheduler is available again.
Page 452 QoS Queue Group Template Command Reference Children of the parent scheduler with a lower strict priority or that are weighted will not receive bandwidth until all children with a higher strict priority have either reached their maximum bandwidth or are idle. Children with the same strict level are serviced in a round robin fashion.
Page 453 MDA named pool. If named pool mode is not enabled where the template queue is created, the defined pool name is ignored. The no form of the command removes the pool name from the configuration. This command only applies to the 7450 ESS and 7750 SR. Default none Parameters pool-name —...
Page 454 QoS Queue Group Template Command Reference port-parent Syntax port-parent [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-level] no port-parent Context config>qos>qgrps>egr>qgrp>queue Description This command defines the port scheduling parameters used to control the queues behavior when a virtual egress port scheduling is enabled where the egress queue group template is applied. The port- parent command follows the same behavior and provisioning characteristics as the parent command in the SAP egress QoS policy.
Page 455 Queue Sharing and Redirection Context config>qos>qgrps>egr>qgrp>queue Description This command configures the target queue delay for packets forwarded through the queue. It is used to determine the related queue parameters based on the administrative PIR of the queue. This command and the mbs command are mutually exclusive. In order to change between the mbs and queue-delay parameters, the current parameter must be removed before adding the new parameter, that is, changing from mbs to queue-delay requires a no mbs before the queue-delay is configured and changing from queue-delay to mbs requires a no...
Page 456 QoS Queue Group Template Command Reference The rate command can be executed at anytime, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id or policer-id. The no form of the command returns all queues or policer created with the queue-id or policer-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).
Page 457 Queue Sharing and Redirection The packet-byte-offset command is meant to be an arbitrary mechanism that can be used to either add downstream frame encapsulation or remove portions of packet headers. When a packet-byte-offset value is applied to a queue instance, it adjusts the immediate packet size. This means that the queue rates (i.e., operational PIR and CIR) and queue bucket updates use the adjusted packet size.
Page 458 QoS Queue Group Template Command Reference This implements each queue in its own pool and uses the WRED capabilities of the pool to provide WRED per queue. This is supported on both FP2 and later hardware and is configured with the pool-per-queue keyword. Native Hardware WRED When the wred-queue mode native command is configured, the queue uses the WRED capabilities of the FP3.
Page 459 Queue Sharing and Redirection As packets attempt to enter the egress queue, they are associated with the high, low, or exceed WRED slope based on the packets’ profile. If the packet is in-profile, the high slope is used. If the packet is out-of-profile, the low slope is used, and, if the packet is exceed-profile, then exceed slope is used.
Page 460 QoS Queue Group Template Command Reference 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. Once 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 461 Queue Sharing and Redirection The no form of the command removes a template queue from the queue group template. If the queue is specified as a forwarding class redirection target in any SAP ingress QoS policy, the command will fail. Default none Parameters...
Page 462 QoS Queue Group Template Command Reference rate Syntax rate pir-rate [cir cir-rate] rate pir-rate police no rate Context config>qos>qgrpid>ing>qgrp>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 through the switch fabric (for SAP ingress queues).
Page 463 Queue Sharing and Redirection police — Specifies that the out of profile traffic feeding into the physical queue instance should be dropped. Using this keyword will override the bandwidth specified by the SAP ingress queue’s administrative CIR. If the police keyword is not specified, the individual queue group overrides may override both the defined shaping rate and the cir defined profiling rate.
Page 464 QoS Queue Group Template Command Reference Parameters add bytes — Specifies an number of bytes to add as the offset amount. Values 0 to 31 subtract bytes — Specifies an number of bytes to add as the offset amount. Values 1 to 32 parent Syntax...
Page 465 Queue Sharing and Redirection All weight values from all weighted active queues and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the queue or scheduler after the strict children are serviced.
Page 466: Show Commands
QoS Queue Group Template Command Reference offered-profile-capped-cir — Selects offered profile capped statistics as the statistics mode. offered-limited-capped-cir — Selects offered limited capped statistics as the statistics mode. Show Commands The command outputs in the following section are examples only; actual displays may differ depending on supported functionality and user configuration.
Page 467 Queue Sharing and Redirection ------------------------------------------------------------------------------- Group-Name : QG_egress_1 Description : Egress queue group ------------------------------------------------------------------------------- Queue CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent CIR Rule PIR Rule CIR Lvl/Wt Named-Buffer Pool ------------------------------------------------------------------------------- None closest closest (not-assigned) None closest closest (not-assigned) None closest...
Page 468 QoS Queue Group Template Command Reference Description : Egress queue group =============================================================================== Queue Group Ports (access) =============================================================================== Port Sched Pol Acctg Pol Stats Description ------------------------------------------------------------------------------- 9/2/1 9/2/2 ------------------------------------------------------------------------------- =============================================================================== Queue Group Ports (network) =============================================================================== Port Sched Pol Acctg Pol Stats Description ------------------------------------------------------------------------------- 6/1/1...
Page 469 Queue Sharing and Redirection ------------------------------------------------------------------------------- QoS Queue Group ------------------------------------------------------------------------------- Group-Name : QG_ingress_1 Description : Ingress queue-group ------------------------------------------------------------------------------- Queue Mode CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent CIR Rule PIR Rule CIR Lvl/Wt Named-Buffer Pool ------------------------------------------------------------------------------- Prio None closest closest 100 (not-assigned) Prio...
Page 470 QoS Queue Group Template Command Reference Port Sched Pol Acctg Pol Stats Description ------------------------------------------------------------------------------- 9/2/1 9/2/2 ------------------------------------------------------------------------------- =============================================================================== Queue Group Sap FC Maps =============================================================================== Sap Policy FC Name Queue (id type) ------------------------------------------------------------------------------- (2 Unicast) (1 Unicast) (3 Unicast) (4 Unicast) ------------------------------------------------------------------------------- Entries found: 4 -------------------------------------------------------------------------------...
Page 471 Queue Sharing and Redirection Packets Octets Ing. Policer: Grp: QGIng1 (Stats mode: minimal) Off. All 91836202 91465530792 Dro. All 6678807 6649127172 For. All 85157395 84816403620 Ing. Policer: Grp: QGIng1 (Stats mode: minimal) Off. All 93584703 90933906888 Dro. All 8320200 6106644900 For.
Page 472 QoS Queue Group Template Command Reference Dro. All For. All Ing. Policer: 13 Grp: QGIng1 (Stats mode: minimal) Off. All Dro. All For. All Ing. Policer: 14 Grp: QGIng1 (Stats mode: minimal) Off. All Dro. All For. All Ing. Policer: 15 Grp: QGIng1 (Stats mode: minimal) Off.
Page 473 Queue Sharing and Redirection Oper Thresh Unfair:311296 Oper Thresh Fair:425984 Association count:0 Priority 4 Oper Thresh Unfair:311296 Oper Thresh Fair:425984 Association count:0 Priority 3 Oper Thresh Unfair:311296 Oper Thresh Fair:425984 Association count:0 Priority 2 Oper Thresh Unfair:311296 Oper Thresh Fair:425984 Association count:4 Priority 1 Oper Thresh Unfair:102400...
Page 474 QoS Queue Group Template Command Reference |--(P) : Policer Net-FPQG-1-T3:1->2 MaxPIR:max MaxCIR:0 CBS:0 MBS:20480 HiPrio:2048 Depth:18944 OperPIR:128 OperCIR:0 OperFIR:128 PacketByteOffset:0 StatMode: minimal [Level 1 Weight 1] Assigned PIR:125 Offered:9967 Consumed:125 Assigned FIR:125 |--(P) : Policer Net-FPQG-1-T3:1->1 MaxPIR:max MaxCIR:0 CBS:0 MBS:20480 HiPrio:2048 Depth:19024 OperPIR:128...
Page 475 Queue Sharing and Redirection Consumed:250 Assigned FIR:250 |--(P) : Policer Net-FPQG-1-T3:1->7 MaxPIR:max MaxCIR:0 CBS:0 MBS:20480 HiPrio:2048 Depth:21065 OperPIR:250 OperCIR:0 OperFIR:250 PacketByteOffset:0 StatMode: minimal [Level 1 Weight 1] Assigned PIR:250 Offered:9967 Consumed:250 Assigned FIR:250 |--(P) : Policer Net-FPQG-1-T3:1->6 MaxPIR:max MaxCIR:0 CBS:0 MBS:20480 HiPrio:2048 Depth:21353...
Page 476 QoS Queue Group Template Command Reference *A:Dut-T# show qos policer port 9/2/4 network egress queue-group "QGEgr1" instance 1 =============================================================================== Policer Information (Summary), Slot 9 =============================================================================== ------------------------------------------------------------------------------- Name FC-Maps HP-Only A.PIR A.CIR Direction Depth O.PIR O.CIR O.FIR ------------------------------------------------------------------------------- Net-PQG-9/2/4-QGEgr1:1->8 Egress 64 KB 8 KB 0 KB 1026...
Page 477 Queue Sharing and Redirection Consumed : 0 Kbps ------------------------------------------------------------------------------- =============================================================================== =============================================================================== Policer Info (Net-PQG-9/2/4-QGEgr1:1->7), Slot 9 =============================================================================== Policer Name : Net-PQG-9/2/4-QGEgr1:1->7 Direction : Egress Fwding Plane Depth PIR : 1026 Bytes Depth CIR : 0 Bytes Depth FIR : 1026 Bytes : 64 KB : 0 KB Hi Prio Only...
Page 478 QoS Queue Group Template Command Reference Oper PIR : Max Oper CIR : 0 Kbps Oper FIR : Max Stat Mode : minimal Parent Arbiter Name: (Not Specified) ------------------------------------------------------------------------------- Arbiter Member Information ------------------------------------------------------------------------------- Offered Rate : 0 Kbps Level Weight Parent PIR : 0 Kbps Parent FIR...
Page 479 Queue Sharing and Redirection ============================================================================== =============================================================================== Policer Info (Net-PQG-9/2/4-QGEgr1:1->2), Slot 9 =============================================================================== Policer Name : Net-PQG-9/2/4-QGEgr1:1->2 Direction : Egress Fwding Plane Depth PIR : 1026 Bytes Depth CIR : 0 Bytes Depth FIR : 1026 Bytes : 64 KB : 0 KB Hi Prio Only : 8 KB Pkt Byte Offset...
Page 480 QoS Queue Group Template Command Reference Policer Info (1->5:105->10), Slot 9 Policer Info (1->6:106->10), Slot 9 Policer Info (1->7:107->10), Slot 9 Policer Info (1->8:108->10), Slot 9 Policer Info (1->9:109->10), Slot 9 Policer Info (1->10:110->10), Slot 9 Policer Info (1->11:111->10), Slot 9 Policer Info (1->12:112->10), Slot 9 Policer Info (1->13:113->10), Slot 9 Policer Info (1->14:114->10), Slot 9...
Page 481 Queue Sharing and Redirection Dro. All For. All : 22133355 22708822230 Egress Policer: Group: QGEgr1 Instance-Id: 1 Stats mode: minimal Off. All : 22133355 22708822230 Dro. All For. All : 22133355 22708822230 Egress Policer: Group: QGEgr1 Instance-Id: 1 Stats mode: minimal Off.
Page 482 QoS Queue Group Template Command Reference =============================================================================== Card Num Fp Num Instance Type ------------------------------------------------------------------------------- Network Network Network Network Network Network Network Network Network Network clear card 4 fp 1 ingress mode network queue-group "QGIng1" instance 1 statistics *A:Dut-T# monitor card 9 fp 1 ingress queue-group "QGIng1" network instance 1 policer 1 ======================================================================== Monitor Card: 9 Ingress Network Queue-Group: QGIng1 Statistics ========================================================================...
Page 483 Queue Sharing and Redirection No queues found ------------------------------------------------------------------------------- Statistics ------------------------------------------------------------------------------- Packets Octets Ing. Policer: Grp: QGIng3 (Stats mode: offered-profile-capped-cir) Off. InProf Off. OutProf Off. Uncolor 22159073 1506816964 Dro. InProf Dro. OutProf For. InProf 215642 14663656 For. OutProf 21943431 1492153308 Ing. Policer: Grp: QGIng3 (Stats mode: offered-profile-capped-cir) Off.
Page 484 QoS Queue Group Template Command Reference Ing. Policer: Grp: Ingress_QG_1 (Stats mode: minimal) Off. All 53982387 6909745536 Dro. All 50861158 6510228224 For. All 3121229 399517312 =============================================================================== *A:Dut-A# show card 9 fp 1 ingress mode access queue-group "Ingress_QG_1" instance 2838 =============================================================================== Card:9 Acc.QGrp: Ingress_QG_1 Instance: 2838...
Page 485 Queue Sharing and Redirection =============================================================================== *A:Dut-A# monitor card 9 fp 1 ingress access queue-group "Ingress_QG_1" instance 2838 policer 2 ======================================================================== Monitor Card: 9 Ingress Access Queue-Group: Ingress_QG_1 Statistics ======================================================================== ------------------------------------------------------------------------------- At time t = 0 sec (Base Statistics) ------------------------------------------------------------------------------- Packets Octets Ing.
Page 486 QoS Queue Group Template Command Reference At time t = 55 sec (Mode: Delta) ------------------------------------------------------------------------------- Packets Octets Ing. Policer: Grp: Ingress_QG_1 (Stats mode: minimal) Off. All : 9291543 1189317504 Dro. All : 8754385 1120561280 For. All : 537158 68756224 ------------------------------------------------------------------------------- At time t = 66 sec (Mode: Delta) ------------------------------------------------------------------------------- Packets...
Page 487 — Displays the entities associated with the specified policy ID. match-criteria — Displays match criteria when this keyword is specified. hsmda — Displays HSMDA properties (applies only to the 7450 ESS and 7750 SR). detail — Displays detailed information about the specified SAP egress policy.
Page 488 QoS Queue Group Template Command Reference ------------------------------------------------------------------------------- Associations ------------------------------------------------------------------------------- Service-Id : 1 (VPLS) Customer-Id - SAP : 9/2/1 - SAP : 9/2/2 ------------------------------------------------------------------------------- Mirror SAPs ------------------------------------------------------------------------------- No Mirror SAPs Found. ------------------------------------------------------------------------------- HSMDA CIR Admin PIR Admin Packet Slope Policy Queue CIR Rule PIR Rule Offset -------------------------------------------------------------------------------...
Page 489 — Displays the entities associated with the specified policy ID. match-criteria — Displays match criteria when this keyword is specified. hsmda — Displays HSMDA properties (applies only to the 7450 ESS and 7750 SR). detail — Displays detailed information about the specified SAP egress policy.
Page 490 QoS Queue Group Template Command Reference ------------------------------------------------------------------------------- UCastQ/QGrp MCastQ/QGrp BCastQ/QGrp UnknownQ/QGrp ------------------------------------------------------------------------------- 1/QG_ingress_1 def/ def/ def/ 2/QG_ingress_1 def/ def/ def/ 3/QG_ingress_1 def/ def/ def/ 4/QG_ingress_1 def/ def/ def/ ------------------------------------------------------------------------------- DE-1-out-profile Profile In-Remark Out-Remark ------------------------------------------------------------------------------- None None None None None None None None None...
Page 491 Queue Sharing and Redirection closest closest add 0 default closest closest add 0 default closest closest add 0 default closest closest add 0 default closest closest ------------------------------------------------------------------------------- HSMDA UCastQ HSMDA MCastQ HSMDA BCastQ ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- HSMDA Associations ------------------------------------------------------------------------------- No Associations Found. =============================================================================== *A:Dut-T>config>port# pools...
Page 492 QoS Queue Group Template Command Reference *A:PE# show pools access-egress 5/1/1 queue-group "qg1" instance 1 =============================================================================== Pool Information =============================================================================== Port : 5/1/1 Application : Acc-Egr Pool Name : default CLI Config. Resv CBS : 30%(default) Resv CBS Step : 0% Resv CBS Max : 0% Amber Alarm Threshold: 0%...
Page 493 Queue Sharing and Redirection ------------------------------------------------------------------------------- Utilization State Start-Avg Max-Avg Max-Prob ------------------------------------------------------------------------------- High-Slope Down Low-Slope Down Time Avg Factor Pool Total : 168960 KB Pool Shared : 116736 KB Pool Resv : 52224 KB Pool Total In Use : 0 KB Pool Shared In Use : 0 KB Pool Resv In Use...
Page 494 QoS Queue Group Template Command Reference 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->1 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000...
Page 495 Queue Sharing and Redirection QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->2 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3...
Page 496 QoS Queue Group Template Command Reference QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->3 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4...
Page 497 Queue Sharing and Redirection 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 QGrp->QG_ingress_1(9/2/1)->4 1000000 =============================================================================== *A:Dut-T>config>port# port Syntax port port-id queue-group [ingress | egress] [queue-group-name] [{statistics | associations}] Context show>port Description This command displays physical port information for the port’s queue group. Parameters port-id —...
Page 498 QoS Queue Group Template Command Reference Group Name : QG_ingress_1 Description : (Not Specified) Sched Policy : None Acct Pol : None Collect Stats : disabled Queues ------------------------------------------------------------------------------- Ing. QGroup : QG_ingress_1 Queue-Id : 1 (Unicast) (Priority) Description : Ingress queue-group Admin PIR : max* Admin CIR: 0*...
Page 499 Queue Sharing and Redirection Description : Egress queue group Admin PIR : max* Admin CIR: 0* PIR Rule : closest* CIR Rule : closest* : def* : 100* Hi Prio : def* Egr. QGroup : QG_egress_1 Queue-Id : 3 Description : Egress queue group Admin PIR : 1500000...
Page 500: Monitor Commands
QoS Queue Group Template Command Reference Monitor Commands card Syntax 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] Context monitor Description This command monitors policer statistics in an ingress FP queue group. Parameters card slot-number —...
Page 501 Queue Sharing and Redirection reference-rate — When a reference-rate value is specified, the rate-per-second for each statistic is displayed as a percentage based on the reference rate specified. Values 100M, 1G, 10G, 40G, 100G, 400G card Syntax card slot-number fp fp-number queue-group queue-group-name instance instance-id [ingress] [access | networks] [interval seconds] [repeat repeat] [absolute | percent-rate | reference-rate] [arbiter root | name] Context...
Page 502 QoS Queue Group Template Command Reference reference-rate — When a reference-rate value is specified, the rate-per-second for each statistic is displayed as a percentage based on the reference rate specified. Values 100M, 1G, 10G, 40G, 100G, 400G arbiter name — Specify the name of the policer control policy arbiter. Values An existing arbiter-name in the form of a string up to 32 characters long composed of printable, 7-bit ASCII characters.
Page 503 Queue Sharing and Redirection repeat repeat — Configures how many times the command is repeated. Default Values 1 to 999 absolute — When the absolute keyword is specified, the raw statistics are displayed, without processing. No calculations are performed on the delta or rate statistics. rate —...
Page 504 QoS Queue Group Template Command Reference interval seconds — Configures the interval for each display in seconds. Default 11 seconds Values 11 to 60 repeat repeat — Configures how many times the command is repeated. Default Values 1 to 999 absolute —...
Page 505: Qos Scheduler Policies
QoS Scheduler Policies In This Section This section provides information to configure QoS scheduler and port scheduler policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Service Management Tasks Overview Scheduler Policies Virtual schedulers are created within the context of a scheduler policy that is used to define the hierarchy and parameters for each scheduler.
Page 506: Egress Port-Based Schedulers
Overview Egress Port-Based Schedulers In previous releases, HQoS root (top tier) schedulers always assumed that the configured rate was available, regardless of egress port level oversubscription and congestion. This resulted in the possibility that the aggregate bandwidth assigned to queues was not actually available at the port level.
Page 507 QoS Scheduler Policies The priority 1 “above-cir” scheduling loop has a special two tier strict distribution function. The high priority level 1 “above-cir” distribution is weighted between all queues and schedulers attached to level 1 for “above-cir” bandwidth. The low priority distribution for level 1 “above-cir”...
Page 508: Service/Subscriber Or Multi-Service Site Egress Port Bandwidth Allocation
Overview When a queue is inactive or has a limited offered load that is below its fair share (fair share is based on the bandwidth allocation a queue would receive if it was registering adequate activity), its operational PIR must be set to some value to handle what would happen if the queues offered load increased prior to the next iteration of the port virtual scheduling algorithm.
Page 509 QoS Scheduler Policies Figure 20: Port Level Virtual Scheduler Bandwidth Allocation Based on Priority and CIR Priority 8 “Within-CIR” Weighted Distribution Level Rate Limit Priority 8 “Above-CIR” Weighted Distribution Highest Priority Priority 7 “Within-CIR” Within-CIR Weighted Strict Distribution Level Distribution Rate Limit Lowest Priority...
Page 510: Service Or Subscriber Or Multi-Service Site Scheduler Child To Port Scheduler Parent
Overview Service or Subscriber or Multi-service site Scheduler Child to Port Scheduler Parent The service or subscriber or multi-service site scheduler to port scheduler association model allows for multiple services or subscriber or multi-service site to have independent scheduler policy definitions while the independent schedulers receive bandwidth from the scheduler at the port level.
Page 511 QoS Scheduler Policies preferentially allocate bandwidth within a service or subscriber or multi-service site context through the service or subscriber or multi-service site level policy without affecting the overall bandwidth allocation to each service or subscriber or multi-service site. Figure 22 shows a per-service bandwidth allocation using the two scheduler policy model.
Page 512 Overview provides an aggregate bandwidth allocation model, it does not inhibit per service or per subscriber or multi-service site queuing. Figure 23 demonstrates the single, port scheduler policy model. Figure 23 also demonstrates the optional aggregate rate limiter at the SAP, multi-service site or subscriber or multi-service site level.
Page 513: Frame And Packet-Based Bandwidth Allocation
QoS Scheduler Policies Figure 23: Direct Service or Subscriber or Multi-service site Association to Port Scheduler Model Queue Rate Queue Limit or MSS Queue Priority 1 Weighted Rate Limiting Queue Scheduler Rate Queue Limit or MSS Priority 2 Port Queue Weighted Strict Rate Rate Limiting...
Page 514 Overview means that an Ethernet packet will consume 20 bytes more bandwidth on the wire than what the queue accounted for. When considering HDLC encoded PoS or SDH ports on the 7750 SR, the overhead is variable based on ‘7e’ insertions (and other TDM framing issues). The HDLC and SONET/SDH frame overhead is not included for queues forwarding on PoS and SDH links.
Page 515: Queue Parental Association Scope
QoS Scheduler Policies Figure 24: Port Bandwidth Distribution for Service and Port Scheduler Hierarchies Rate Limiting Port Priority Rate Limiting Level Port Scheduler MSS/SAP/Sub (Frame Provisioned) (Frame Provisioned) Scheduler Hierarchy (Packet Provisioned) Highest Highest Strict Strict/ Egress Weighted Priority Weighted Port Rate Limiting Rate Limiting...
Page 516: Service Or Subscriber Or Multi-Service Site-Level Scheduler Parental Association Scope
Overview The port-parent command only accepts a child/parent association to the eight priority levels on a port scheduler hierarchy. Similar to the local parent command, two associations are supported, one for “within-cir” bandwidth (cir-level) and a second one for “above-cir” bandwidth (level).
Page 517: Network Queue Parent Scheduler
QoS Scheduler Policies 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 518: Congestion Monitoring On Egress Port Scheduler
Overview • Within-CIR weight = 0 • Above-CIR priority = 1 • Above-CIR weight = 0 The above-CIR weight = 0 value is only used for orphaned queues and schedulers on port scheduler enabled egress ports. The system interprets weight=0 as priority level 0 and will only distribute bandwidth to level 0 once all other properly parented queues and schedulers have received bandwidth.
Page 519 QoS Scheduler Policies Figure 27: GPON Bandwidth Control through Vport GPON 1 2.4gbps GPON 2 2.4gbps • • • 2.4gbps GPON n 2.4gbps GPONn Vport-n GPON1 Vport-1 GPON2 Vport-2 al_0740 There are no forward/drop counters directly associated with the EPS. Instead, the counters are maintained on a per queue level.
Page 520 Overview Figure 28: Exceed Counts Vport Offered Load Vport configured bandwidth [kbps] Monitor-threshold [%] Time Read Read Samples above the threshold: 2 Total samples: al_0741 Figure 29: Exceed Counts (Severe Congestion) Vport Offered Load Vport configured bandwidth [kbps] Monitor-threshold [%] Time Read Read...
Page 521 QoS Scheduler Policies The reduced ability to determine the time of congestion if the reading interval is too long is shown in Figure Figure 31, and Figure 32. It can be seen that the same readings (in the 3 examples) can represent different congestion patterns that occur at different times between the two consecutive reads.
Page 522 Overview Figure 31: Determining the Time of Congestion Example 2) Vport Offered Load Vport configured bandwidth [kbps] Monitor-threshold [%] Time 1 Day Read Read Samples above the threshold: 20K Total samples: 100K al_0744 Figure 32: Determining the Time of Congestion (Example 3) Vport Offered Load Vport configured bandwidth [kbps]...
Page 523 QoS Scheduler Policies Each statistics gathering operation requires a show or read followed by a clear. The shorter the time between the two, the more accurate the information about the congestion state of the EPS will be. If the clear operation is not executed after the show or read operation, the external statistics gathering entity (external server) would need to perform additional operations (such as, subtract statistics between the two consecutive reads) in order the obtain the delta between the two reads.
Page 524: Frame-Based Accounting
Overview Frame-Based Accounting The standard accounting mechanism uses ‘packet based’ rules that account for the DLC header, any existing tags, Ethernet payload and the 4 byte CRC. The Ethernet framing overhead which includes the Inter-Frame Gap (IFG) and preamble (20 bytes total) are not included in packet based accounting.
Page 525: Existing Egress Port Based Virtual Scheduling
QoS Scheduler Policies Existing Egress Port Based Virtual Scheduling The port based virtual scheduling mechanism takes the native packet based accounting results from the queue and adds 20 bytes to each packet to derive the queue’s frame based offered load. The ratio between the frame based offered load and the packet based offered load is then used to determine the effective frame based CIR and frame based PIR thresholds for the queue.
Page 526: Virtual Scheduling Unused Bandwidth Distribution
Overview Similarly, the rates defined in the scheduling policy with frame based accounting enabled will automatically be interpreted as frame based rates. The port based scheduler aggregate rate limit command always interprets its configured rate limit value as a frame based rate. Setting the frame based accounting parameter on the aggregate rate limit command only affects the queues managed by the aggregate rate limit and converts them from packet based to frame based accounting mode.
Page 527: Limit Unused Bandwidth
QoS Scheduler Policies • The above-offered-cap command within the adv-config-policy provides control of each queue’s operational PIR to prevent aggregate rate overrun. This is accomplished by defining how much a queue’s operational PIR is allowed to exceed the queue’s current allocated bandwidth. •...
Page 528 Overview • Else if a queue has accumulated work then its LUB-weight is set to 50. The work is determined by the queue having built up a depth of packets, or its offered rate is increasing since last sample period. The aim is to assign more of the unused bandwidth to queues needing more capacity.
Page 529: Configuring Port Scheduler Policies
QoS Scheduler Policies Figure 34: Resulting Bandwidth Distribution No Traffic Traffic in Q5 & Q3 Offered Default Second Offered Default Second Traffic H-Qos Pass (LUB) Traffic H-Qos Pass (LUB) 59.39=40+19.39 0.39=0+0.39 39.42=20+19.42 0.39=0+0.39 0.39=0+0.39 Each queue can Each queue can Each queue Each queue can burst to the full...
Page 530: Packet To Frame Bandwidth Conversion
Packet over SONET (PoS) and SDH queues on the 7450 ESS and 7750 SR also operate based on packet sizes and do not include on-the-wire frame overhead. Unfortunately, the port based virtual scheduler algorithm does not have access to all the frame encapsulation overhead occurring at the framer level.
Page 531: Aggregate Rate Limits For Directly Attached Queues
QoS Scheduler Policies required for proper bandwidth allocation between queues and service schedulers. If this value is not attainable, another approach is to artificially lower the maximum rate of the port scheduler to represent the average port framing overhead. This, in conjunction with a zero or low value for avg-frame-overhead, will ensure that the allocated queue bandwidth will control forwarding behavior instead of the low level hardware schedulers.
Page 532: Network Queue Qos Policy Queue Parenting
The vport operates exactly like a port scheduler except multiple vport objects can be configured on the egress context of an Ethernet port. This feature applies to the 7450 ESS and 7750 SR only. Figure 35 illustrates the use of the vport on an Ethernet port of a Broadband Network Gateway (BNG).
Page 533 QoS Scheduler Policies Figure 35: Applying a Port Scheduler Policy to a Vport Weighted Scheduler Group C-VLAN1 Residential Subscriber agg-rate-limit Virtual Port for S- VLAN=20 (provides Residential Weight X BE Q 1 destination agg-rate Weight Y support) L2 Q 2 Weight Z Prio=3 L1 Q 3...
Page 534: Applying Aggregate Rate Limit To A Vport
1 schedulers in a scheduler policy applied to the egress of a subscriber or SLA profile, or to a PW SAP in an IES or VPRN service. This feature applies only to the 7450 ESS and 7750 SR.
Page 535 QoS Scheduler Policies Bandwidth distribution from an egress port scheduler to a VPORT configured with a scheduler policy can be performed based on the level/cir-level and weight/cir-weight configured under the scheduler’s port parent. The result is in allowing multiple VPORTs, for example representing different DSLAMs, to share the port bandwidth capacity in a flexible way that is under the control of the user.
Page 536: Weighted Scheduler Group In A Port Scheduler Policy
A group has a rate and optionally a cir-rate and inherits the highest scheduling priority of its member levels. For example, the scheduler group for the 7450 ESS and 7750 SR shown in the vport in Figure 35 consists of level priority 3 and level priority 4.
Page 537: Create A Qos Scheduler Policy
QoS Scheduler Policies A basic QoS port scheduler policy must conform to the following: • Each QoS port scheduler policy must have a unique policy name. Create a QoS Scheduler Policy Configuring and applying QoS policies is optional. If no QoS policy is explicitly applied to a SAP or IP interface, a default QoS policy is applied.
Page 538: Applying Scheduler Policies
Overview rate 11000 exit scheduler "Voice" create description "Any voice traffic from VPN and Internet use this scheduler" parent All_traffic level 2 cir-level 2 rate 5500 exit exit tier 3 scheduler "Internet_be" create parent NonVoice cir-level 1 exit scheduler "Internet_priority" create parent NonVoice level 2 cir-level 2 exit scheduler "Internet_voice"...
Page 539 QoS Scheduler Policies • • VPLS • VPRN Customer Use the following CLI syntax to associate a scheduler policy to a customer’s multiservice site: CLI Syntax: config>customer customer-id multiservice-site customer-site-name egress scheduler-policy scheduler-policy-name ingress scheduler-policy scheduler-policy-name Epipe Use the following CLI syntax to apply QoS policies to ingress and/or egress Epipe SAPs: CLI Syntax: config>service# epipe service-id [customer customer-id] sap sap-id...
Page 540 Overview exit egress scheduler-policy "SLA2" qos 1010 exit exit ---------------------------------------------- A:SR>config>service# Use the following CLI syntax to apply scheduler policies to ingress and/or egress IES SAPs: CLI Syntax: config>service# ies service-id [customer customer-id] interface ip-int-name sap sap-id egress scheduler-policy scheduler-policy-name ingress scheduler-policy scheduler-policy-name The following output displays an IES service configuration with scheduler policy SLA2...
Page 541 QoS Scheduler Policies CLI Syntax: config>service# vpls service-id [customer customer-id] sap sap-id egress scheduler-policy scheduler-policy-name ingress scheduler-policy scheduler-policy-name The following output displays an VPLS service configuration with scheduler policy SLA2 applied to the SAP ingress and egress. A:SR>config>service# info ---------------------------------------------- vpls 700 customer 7 vpn 700 create description "test"...
Page 542: Creating A Qos Port Scheduler Policy
Overview The following output displays a VPRN service configuration with the scheduler policy SLA2 applied to the SAP ingress and egress. A:SR7>config>service# info ---------------------------------------------- vprn 1 customer 1 create ecmp 8 autonomous-system 10000 route-distinguisher 10001:1 auto-bind-tunnel resolution-filter resolution-filter ldp vrf-target target:10001:1 interface "to-ce1"...
Page 543: Configuring Port Parent Parameters
QoS Scheduler Policies orphan-override [level priority-level] [weight weight] [cir-level priority-level] [cir-weight cir-weight] The following displays a scheduler policy configuration example: *A:ALA-48>config>qos>port-sched-plcy# info ---------------------------------------------- description "Test Port Scheduler Policy" orphan-override weight 50 cir-level 4 cir-weight 50 ---------------------------------------------- *A:ALA-48>config>qos>port-sched-plcy# Configuring Port Parent Parameters The port-parent command defines a child/parent association between an egress queue and a port based scheduler or between an intermediate service scheduler and a port based scheduler.
Page 544: Above-Cir Priority Level Parameters
Overview Above-CIR Priority Level Parameters The above-cir parameters define which port priority level the queue or scheduler should be associated with when receiving bandwidth for the queue’s or scheduler’s above-cir offered load. The above-cir offered load is the amount of bandwidth the queue or scheduler could use that is equal to or less than its defined PIR value (based on the queue or schedulers rate command) less any bandwidth that was given to the queue or scheduler during the above-cir scheduler pass.
Page 545 QoS Scheduler Policies *B:ALU-A>config>port# info ---------------------------------------------- ethernet mode access egress-scheduler-policy "psp" autonegotiate limited exit no shutdown ---------------------------------------------- *B:ALU-A>config>port# /configure lag 30 *B:ALU-A>config>lag# info ---------------------------------------------- description "Description For LAG Number 30" mode access port 2/1/6 port 2/1/10 port 3/2/1 port 3/2/2 no shutdown *B:ALU-A>config>service>ies>if>sap# /configure qos port-scheduler-policy "psp"...
Page 546 Overview AdminPIR:2000000(w) AdminCIR:0(w) [Within CIR Level 0 Weight 0] Assigned:0(w) Offered:0(w) Consumed:0(w) [Above CIR Level 1 Weight 0] Assigned:413202(w) Offered:2000000(w) <----without dist-lag-rate-shared 413MB is assigned to slot 2 Consumed:413202(w) TotalConsumed:413202(w) OperPIR:406494 [As Parent] OperPIR:406494 OperCIR:0 ConsumedByChildren:406494 |--(Q) : 1->lag-30(2/1/6)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*)
Page 547 QoS Scheduler Policies PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false | slot(3) |--(S) : Tier0Egress:1->lag-30:0.0->1 (Port lag-30 Orphan) AdminPIR:2000000 AdminCIR:0(sum) Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) AdminPIR:2000000(w) AdminCIR:0(w) [Within CIR Level 0 Weight 0] Assigned:0(w) Offered:0(w) Consumed:0(w) [Above CIR Level 1 Weight 0] Assigned:413202(w) Offered:2000000(w) <----without dist-lag-rate-shared 413MB is assigned to slot 3 Consumed:413202(w)
Page 548 Overview [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:203247 Offered:1000000 Consumed:203247 OperPIR:203125 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false The following output shows dist-lag-rate-shared enabled. *B:ALU-A>config>qos>port-sched-plcy# dist-lag-rate-shared *B:ALU-A>config>qos>port-sched-plcy# info ---------------------------------------------- dist-lag-rate-shared max-rate 413202 ---------------------------------------------- *B:ALU-A>config>qos>port-sched-plcy# !/show *B:ALU-A>config>qos>port-sched-plcy# /show qos scheduler-hierarchy sap lag-30 egress\ detail =============================================================================== Scheduler Hierarchy - Sap lag-30...
Page 549 QoS Scheduler Policies TotalConsumed:206601(w) OperPIR:203247 [As Parent] OperPIR:203247 OperCIR:0 ConsumedByChildren:203247 |--(Q) : 1->lag-30(2/1/6)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) CBS:0 B MBS:1310720 B Depth:1045760 B HiPrio:262144 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:101624 Offered:1000000 Consumed:101624 OperPIR:102000 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false...
Page 550 Overview [Within CIR Level 0 Weight 0] Assigned:0(w) Offered:0(w) Consumed:0(w) [Above CIR Level 1 Weight 0] Assigned:206601(w) Offered:2000000(w) <----with dist-lag-rate-shared 206 Mb is assigned to slot 3 Consumed:206601(w) TotalConsumed:206601(w) OperPIR:203247 [As Parent] OperPIR:203247 OperCIR:0 ConsumedByChildren:203247 |--(Q) : 1->lag-30(3/2/2)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) CBS:0 B...
Page 551 QoS Scheduler Policies OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false =============================================================================== *B:ALU-A>config>qos>port-sched-plcy# If one of the member links of the LAG goes down, then the max-rate is divided among the remaining lag members. Card 2 is assigned 137734 (1/3 of max-rate 413202) Card 3 is assigned 275468 (2/3 of max-rate 413202) *B:ALU-A>config>qos>port-sched-plcy# /show lag 30 detail =============================================================================== LAG Details...
Page 552 Overview (*) real-time dynamic value (w) Wire rates Bytes ------------------------------------------------------------------------------- Root (Egr) | slot(2) |--(S) : Tier0Egress:1->lag-30:0.0->1 (Port lag-30 Orphan) AdminPIR:1000000 AdminCIR:0(sum) Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) AdminPIR:1000000(w) AdminCIR:0(w) [Within CIR Level 0 Weight 0] Assigned:0(w) Offered:0(w) Consumed:0(w) [Above CIR Level 1 Weight 0] Assigned:137734(w) Offered:1000000(w) Consumed:137734(w)
Page 553 QoS Scheduler Policies [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:135498 Offered:1000000 Consumed:135498 OperPIR:135000 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false | slot(3) |--(S) : Tier0Egress:1->lag-30:0.0->1 (Port lag-30 Orphan) AdminPIR:2000000 AdminCIR:0(sum) Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) AdminPIR:2000000(w) AdminCIR:0(w) [Within CIR Level 0 Weight 0] Assigned:0(w) Offered:0(w) Consumed:0(w)
Page 554 Overview OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false |--(Q) : 1->lag-30(3/2/1)->1 AdminPIR:1000000 AdminCIR:0 Parent Limit Unused Bandwidth: not-found AvgFrmOv:101.65(*) CBS:0 B MBS:1253376 B Depth:1105728 B HiPrio:147456 B [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:135498 Offered:1000000 Consumed:135498 OperPIR:135625 OperCIR:0 PktByteOffset:add 0* OnTheWireRates:false ATMOnTheWireRates:false LastMileOnTheWireRates:false =============================================================================== *B:ALU-A>config>qos>port-sched-plcy# The following output shows the max-rate percent value.
Page 555 QoS Scheduler Policies level 6 percent-rate 60.00 percent-cir 60.00 level 7 percent-rate 70.00 percent-cir 70.00 level 8 percent-rate 80.00 percent-cir 80.00 Port scheduler-Overrides Both max-rate and level can be overridden if they are of the same type as in the policy being overridden.
Page 556: Service Management Tasks
Service Management Tasks Orphan CIR-Lvl : default Orphan CIR-Weight : default --snip-- ------------------------------------------------------------------------------- Egr Port Sched Override ------------------------------------------------------------------------------- Max Rate : max* Max Rate Percent : 50.00 Lvl1 PIR : max* Lvl1 CIR : max* Lvl1 PIR Percent : 10.00 Lvl1 CIR Percent : 10.00 Lvl2 PIR : max*...
Page 557: Removing A Qos Policy From A Customer Multi-Service Site
QoS Scheduler Policies SR7>config>qos# no scheduler-policy SLA2 MINOR: QOS #1003 The policy has references SR7>config>qos# Removing a QoS Policy from a Customer Multi-Service Site CLI Syntax: config>service>customer customer-id multi-service-site customer-site-name egress no scheduler-policy ingress no scheduler-policy Example: config>service>customer# multi-service-site “Test” config>service>cust>multi-service-site# ingress config>service>cust>multi-service-site>ingress# no scheduler-policy...
Page 558: Removing A Policy From The Qos Configuration
Service Management Tasks sap sap-id egress no scheduler policy ingress no scheduler policy Example: config>service# vprn 1 config>service>vprn# interface "to-ce1" config>service>vprn>if# sap 1/1/10:1 config>service>vprn>if>sap# ingress config>service>vprn>if>sap>ingress# no scheduler-policy config>service>vprn>if>sap>ingress# exit config>service>vprn>if>sap# egress config>service>vprn>if>sap>egress# no scheduler-policy config>service>vprn>if>sap>egress# exit config>service>vprn>if>sap# Removing a Policy from the QoS Configuration To delete a scheduler policy, enter the following commands: CLI Syntax: config>qos# no scheduler-policy network-policy-id...
Page 559 QoS Scheduler Policies A:SR>config>qos# #------------------------------------------ echo "QoS Policy Configuration" #------------------------------------------ scheduler-policy "SLA1" create description "NetworkControl(3), Voice(2) and NonVoice(1) have strict priorities" tier 1 scheduler "All_traffic" create description "All traffic goes to this scheduler eventually" rate 11000 exit exit tier 2 scheduler "NetworkControl"...
Page 560: Editing Qos Policies
Service Management Tasks parent "All_traffic" cir-level 1 rate 11000 exit scheduler "Voice" create description "Any voice traffic from VPN and Internet use this scheduler" parent "All_traffic" level 2 cir-level 2 rate 5500 exit exit tier 3 scheduler "Internet_be" create parent "NonVoice" cir-level 1 exit scheduler "Internet_priority"...
Page 561: Qos Scheduler Policy Command Reference
QoS Scheduler Policies QoS Scheduler Policy Command Reference Command Hierarchies • Scheduler Policy Configuration Commands • Port Scheduler Policy Configuration Commands • Operational Commands • Show Commands • Clear Commands Scheduler Policy Configuration Commands config — qos — [no] scheduler-policy scheduler-policy-name —...
Page 562: Operational Commands
QoS Scheduler Policy Command Reference — [no] dist-lag-rate-shared — group name [create] — no group name — percent-rate pir-percent [cir cir-percent] — no percent-rate — rate pir-rate [cir cir-rate] — no rate — level priority-level rate pir-rate [cir cir-rate] group name [weight weight] [monitor- threshold percent] —...
Page 563: Clear Commands
QoS Scheduler Policies — scheduler-name scheduler-name — scheduler-policy scheduler-name [association | sap-ingress policy-id | sap-egress policy-id] — scheduler-stats customer customer-id site customer-site-name [scheduler scheduler-name] [ingress | egress] — scheduler-stats sap sap-id [scheduler scheduler-name] [ingress | egress] — scheduler-stats subscriber sub-ident-string [scheduler scheduler-name] [ingress | egress] show —...
Page 564: Command Descriptions
QoS Scheduler Policy Command Reference Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>scheduler-policy config>qos>scheduler-policy>tier>scheduler config>qos>port-scheduler-policy Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.
Page 565: Scheduler Policy Commands
QoS Scheduler Policies If overwrite is not specified, an error will occur if the destination policy exists. Parameters scheduler-policy src-name dst-name — Indicates that the source policy and the destination policy are scheduler policy. Specify the source policy that the copy command will attempt to copy from and specify the destination policy to which the command will copy a duplicate of the policy.
Page 566 QoS Scheduler Policy Command Reference When the maximum number of scheduler policies has been exceeded a configuration error occurs, the command will not execute, and the CLI context will not change. If the provided scheduler-policy-name is invalid according to the criteria below, a name syntax error occurs, the command will not execute, and the CLI context will not change.
Page 567 QoS Scheduler Policies Description This command determines the expected location of the parent schedulers for the tier 1 schedulers configured with a parent command within the scheduler-policy. The parent schedulers must be configured within a scheduler-policy applied at the location corresponding to the parent-location parameter.
Page 568 QoS Scheduler Policy Command Reference The save config and show config commands only display information on scheduler tiers that contain defined schedulers. When all schedulers have been removed from a level, that level ceases to be included in output from these commands. Parameters tier —...
Page 569 QoS Scheduler Policies If the provided scheduler-name is invalid according to the criteria below, a name syntax error will occur, the command will not execute, and the CLI context will not change. Parameters scheduler-name — The name of the scheduler. Values Valid names consist of any string up to 32 characters long composed of printable, 7-bit ASCII characters.
Page 570 QoS Scheduler Policy Command Reference The no form of the command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. Once a parent association has been removed, the former child scheduler attempts to operate based on its configured rate parameter.
Page 571 QoS Scheduler Policies A 0 (zero) cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level. Values 0 to 100 Default cir-level cir-level — The cir-level keyword defines the strict priority CIR level of this scheduler in comparison to other child schedulers and queues vying for bandwidth on the parent scheduler-name during the ‘within CIR’...
Page 572 QoS Scheduler Policy Command Reference Changing the parent context on a SAP egress policy queue may cause a SAP or subscriber context of the queue (policy associated with a SAP or subscriber profile) to enter an orphaned state. If an instance of a queue is created on a port or channel that does not have a port scheduler enabled and the sap-egress policy creating the queue has a port-parent association, the queue will be allowed to run according to its own rate parameters and will not be controlled by a virtual scheduling context.
Page 573: Port Scheduler Policy Commands
QoS Scheduler Policies no rate Context config>qos>scheduler-policy>tier>scheduler config>qos>port-scheduler-policy>max-rate Description The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler.
Page 574 QoS Scheduler Policy Command Reference Description When a port scheduler has been associated with an egress port, it is possible to override the following parameters: • The max-rate allowed for the scheduler • The maximum rate for each priority level (8 through 1) •...
Page 575 QoS Scheduler Policies Up to eight groups can be defined within each port scheduler policy. One or more levels can map to the same group. A group has a rate and optionally a cir-rate and inherits the highest scheduling priority of its member levels.
Page 576 QoS Scheduler Policy Command Reference 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.
Page 577 QoS Scheduler Policies The first pass is called the within-cir pass and consists of providing the available port bandwidth to each of the 8 priority levels starting with level 8 and moving down to level 1. Each level takes the offered load and distributes it to all child members that have a port-parent cir-level equal to the current priority level.
Page 578 This command can be used on channels only on the 7450 ESS and 7750 SR. The max-rate command may be executed at anytime for an existing port-scheduler-policy. When a new max-rate is given for a policy, the system evaluates all instances of the policy to see if the configured rate is smaller than the available port or channel bandwidth.
Page 579 QoS Scheduler Policies The max-rate value defined in the policy may be overridden on each scheduler instance. If the maximum rate is explicitly defined as an override on a port or channel, the policies max-rate value has no effect. The no form of this command removes an explicit rate value from the port scheduler policy. Once removed, all instances of the scheduler policy on egress ports or channel are allowed to run at the available line rate unless the instance has a max-rate override in place.
Page 580 QoS Scheduler Policy Command Reference Description This command override the default orphan behavior for port schedulers created using the port scheduler policy. The default orphan behavior is to give all orphan queues and schedulers bandwidth after all other properly parented queues and schedulers. Orphans by default do not receive any within- cir bandwidth and receive above-cir bandwidth after priority levels 8 through 1 have been allocated.
Page 581: Show Commands
QoS Scheduler Policies The no form of the command removes the orphan override port parent association for the orphan queues and schedulers on port schedulers created with the port scheduler policy. Any orphan queues and schedulers on a port associated with the port scheduler policy will revert to default orphan behavior.
Page 582 QoS Scheduler Policy Command Reference Parameters scheduler-name — The name of a scheduler configured in the config>qos>scheduler-policy context. association — Display the associations related to the specified scheduler name. sap-ingress policy-id — Specify the SAP ingress QoS policy information. sap-egress policy-id — Specify the SAP egress QoS policy information. Customer Scheduler-Policy Output Output The following table describes the customer scheduler hierarchy fields.
Page 583 QoS Scheduler Policies Table 32: Show QoS Scheduler-Policy Output Fields (Continued) Label Description Orphan Queues Specifies the number of queues in an orphaned state. Hierarchy Displays the scheduler policy tree structure. Sample Output A:ALA-12# show qos scheduler-policy SLA1 ============================================================================== QoS Scheduler Policy ============================================================================== Policy-Name : SLA1...
Page 584 QoS Scheduler Policy Command Reference - SAP : 1/1/3.1:0 (Egress) Service-Id : 7000 (VPLS) Customer-Id - SAP : 1/1/5:0 (Egress) - Multi Service Site : west (Ingress) ============================================================================== A:ALA-12# A:ALA-12# show qos scheduler-policy SLA1 sap-ingress 100 ============================================================================= Compatibility : Scheduler Policy SLA1 & Sap Ingress 100 ============================================================================= Orphan Queues : None Found...
Page 585 QoS Scheduler Policies |---(S) : Voice |---(S) : Internet_voice |---(S) : VPN_voice |---(Q) : 16 |---(Q) : 26 |---(Q) : 1 |---(Q) : 2 ============================================================================= A:ALA-12# A:ALA-12# show qos scheduler-policy SLA1 sap-egress 101 ============================================================================== Compatibility : Scheduler Policy SLA1 & Sap Egress 101 ============================================================================== Orphan Queues : None Found...
Page 586 QoS Scheduler Policy Command Reference scheduler-hierarchy customer Syntax scheduler-hierarchy customer customer-id site customer-site-name [scheduler scheduler-name] [ingress | egress] [detail] Context show>qos Description This command displays the scheduler hierarchy per customer multi-service-site. Parameters customer customer-id — Specifies the ID number associated with a particular customer. Values 1 to 2147483647 site customer-site-name —...
Page 587 QoS Scheduler Policies Table 33: Show QoS Scheduler-Hierarchy Customer Output Fields (Continued) Label Description (Continued) Specifies the CIR rate. Parent Specifies the parent scheduler that governs the available bandwidth given the queue aside from the queue’s PIR setting. Service-Id The ID that uniquely identifies the policy. Customer-Id The ID that uniquely identifies the customer.
Page 588 QoS Scheduler Policy Command Reference Context show>qos Description This command displays scheduler hierarchy information per port. Parameters port-id — Specifies the port ID. port-id slot/mda/port [.channel] eth-sat-id esat-id/slot/port esat keyword 1 to 20 pxc-id pxc-id.sub-port keyword 1 to 64 sub-port a, b detail —...
Page 589 QoS Scheduler Policies =============================================================================== Scheduler Hierarchy - Port 1/2/1 =============================================================================== Port-scheduler-policy p1 Port Bandwidth : 10000000 Max Rate : max Consumed : 0 Offered : 0 [Within CIR Level 8] Rate : max Consumed : 0 Offered : 0 [Within CIR Level 7] Rate : max Consumed : 0 Offered : 0...
Page 590 QoS Scheduler Policy Command Reference Consumed : 0 Offered : 0 [Above CIR Level 7] Rate : max Consumed : 0 Offered : 0 [Above CIR Level 6] Rate : max Consumed : 0 Offered : 0 [Above CIR Level 5] Rate : max Consumed : 0 Offered : 0...
Page 591 QoS Scheduler Policies Parameters sap sap-id — Specifies the SAP assigned to the service. Values The following values apply to the 7750 SR and 7950 XRS: sap-id null [port-id | lag-id] dot1q [port-id | lag-id]:qtag1 qinq [port-id | bundle-id | bpgrp-id | lag-id]:qtag1.qtag2 port-id slot/mda/port [.channel] esat-id/slot/port...
Page 592 QoS Scheduler Policy Command Reference sap-id null [port-id | bundle-id | bpgrp-id | lag-id | aps-id] dot1q [port-id | bundle-id | bpgrp-id | lag-id | aps-id]:qtag1 qinq [port-id | bundle-id | bpgrp-id | lag-id]:qtag1.qtag2 [port-id | aps-id][:vpi/vci | vpi | vpi1.vpi2] frame [port-id | aps-id]:dlci cisco-hdlc...
Page 593 QoS Scheduler Policies Values The following values apply to the 7450 ESS only: sap-id null [port-id | lag-id] dot1q [port-id | lag-id]:qtag1 qinq [port-id | lag-id]:qtag1.qtag2 frame [port-id]:dlci port-id slot/mda/port[.channel] aps-id aps-group-id[.channel] keyword group-id 1 to 64 ccag-id ccag-id.path-id[cc-type]:cc-id ccag...
Page 594 QoS Scheduler Policy Command Reference Table 35: Show QoS Scheduler-Hierarchy SAP Output Fields Label Description Legend Admin CIR/PIR: Specifies the configured value of CIR/PIR. Assigned CIR/PIR: Specifies the PIR/CIR rate given to a member by that parent level. Offered CIR/PIR: Specifies the offered load on that member. Consumed CIR/PIR: Specifies the amount of scheduler bandwidth used by this member.
Page 595 QoS Scheduler Policies [Above CIR Level 1 Weight 1] Assigned:960000 Offered:120000 Consumed:0 TotalConsumed:120000 OperPIR:960000 [As Parent] Rate:960000 ConsumedByChildren:120000 |--(S) : AccessIngress:2->1/2/1:1->3 AdminPIR:max AdminCIR:max(sum) [Within CIR Level 0 Weight 1] Assigned:960000 Offered:0 Consumed:0 [Above CIR Level 1 Weight 1] Assigned:960000 Offered:120000 Consumed:120000 TotalConsumed:120000 OperPIR:960000...
Page 596 QoS Scheduler Policy Command Reference |--(S) : vod AdminPIR:max AdminCIR:max(sum) [Within CIR Level 2 Weight 75] Assigned:840000 Offered:2400000 Consumed:840000 [Above CIR Level 2 Weight 75] Assigned:840000 Offered:2400000 Consumed:0 TotalConsumed:840000 OperPIR:840000 [As Parent] Rate:840000 ConsumedByChildren:840000 |--(S) : AccessIngress:2->1/2/1:1->2 AdminPIR:max AdminCIR:max(sum) [Within CIR Level 0 Weight 1] Assigned:840000 Offered:0 Consumed:0...
Page 597 QoS Scheduler Policies Assigned:420000 Offered:0 Consumed:0 [PIR] Assigned:420000 Offered:0 Consumed:0 OperPIR:420000 OperCIR:420000 |--(S) : hsi AdminPIR:max AdminCIR:0(sum) [Within CIR Level 2 Weight 5] Assigned:0 Offered:0 Consumed:0 [Above CIR Level 1 Weight 1] Assigned:0 Offered:961000 Consumed:0 TotalConsumed:0 OperPIR:0 [As Parent] Rate:0 ConsumedByChildren:0 |--(S) : AccessIngress:2->1/2/1:1->1 AdminPIR:max...
Page 598 QoS Scheduler Policy Command Reference OperPIR:0 OperCIR:0 |--(Q) : 2->1/2/1:1->1 1/2 AdminPIR:10000000 AdminCIR:0 CBS:0 MBS:0 Depth:0 HiPrio:0 [CIR] Assigned:0 Offered:0 Consumed:0 [PIR] Assigned:0 Offered:0 Consumed:0 OperPIR:0 OperCIR:0 =============================================================================== *A:Dut-R# *A:Dut-R# show qos scheduler-hierarchy sap 5/1/1:1 egress detail =============================================================================== Scheduler Hierarchy - Sap 5/1/1:1 =============================================================================== Legend : (*) real-time dynamic value...
Page 599 QoS Scheduler Policies Consumed:3000 TotalConsumed:6000 OperPIR:946339 [As Parent] Rate:946339 ConsumedByChildren:6000 |--(Q) : 2->5/1/1:1->1 AdminPIR:6000 AdminCIR:3000 CBS:4 MBS:64 Depth:56 HiPrio:8 [Within CIR Level 0 Weight 1] Assigned:3000 Offered:0 Consumed:0 [Above CIR Level 1 Weight 1] Assigned:6000 Offered:6000 Consumed:6000 TotalConsumed:6000 OperPIR:6000 OperCIR:3000 |--(S) : vod AdminPIR:max AdminCIR:16000(sum)
Page 600 QoS Scheduler Policy Command Reference |--(S) : voice AdminPIR:max AdminCIR:768(sum) [Within CIR Level 6 Weight 1] Assigned:768 Offered:561 Consumed:561 [Above CIR Level 1 Weight 1] Assigned:940900 Offered:561 Consumed:0 TotalConsumed:561 OperPIR:940900 [As Parent] Rate:940900 ConsumedByChildren:561 |--(Q) : 2->5/1/1:1->3 AdminPIR:786 AdminCIR:768 CBS:8 MBS:64 Depth:0 HiPrio:8...
Page 601 QoS Scheduler Policies Show QoS Scheduler-Hierarchy Subscriber Output Output The following table describes the QoS scheduler hierarchy subscriber fields. Table 36: Show QoS Scheduler-Hierarchy Subscriber Output Fields Label Description Legend Admin CIR/PIR: Specifies the configured value of CIR/PIR. Assigned CIR/PIR: Specifies the PIR/CIR rate given to a member by that parent level.
Page 602 QoS Scheduler Policy Command Reference |--(S) : AccessIngress:Sub=1:1 200->1/2/5:1->5 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->5 1/2 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->5 2/1 |--(S) : AccessIngress:Sub=1:1 200->1/2/5:1->4 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->4 1/2 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->4 2/1 |--(S) : AccessIngress:Sub=1:1 200->1/2/5:1->3 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->3 1/2 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->3 2/1 |--(S) : AccessIngress:Sub=1:1 200->1/2/5:1->2 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->2 1/2...
Page 603 QoS Scheduler Policies |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->5 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->7 |--(S) : rbs |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->6 |--(Q) : Sub=RoutedCoHost1:adsl-hsi 200->1/2/5:1->8 show qos scheduler-hierarchy subscriber x detail |--(Q) : Sub=hpolSub43:hpolSlaProf1 2000->2/1/5:2000->2 (Port 2/1/5) AdminPIR:100000 AdminCIR:0 AvgFrmOv:0.00 AdminPIR:100000(w) AdminCIR:0(w) CBS:0 MBS:125952 Depth:0 HiPrio:15360...
Page 604 QoS Scheduler Policy Command Reference Scheduler Policy : SLA1 Scheduler Policy : alpha Scheduler Policy : beta ================================================================== A:ALA-12# scheduler-stats customer Syntax scheduler-stats customer customer-id site customer-site-name [scheduler scheduler- name] [ingress | egress] Context show>qos Description This command displays scheduler statistics information. Parameters customer customer-id —...
Page 605 QoS Scheduler Policies scheduler-stats sap Syntax scheduler-stats sap sap-id [scheduler scheduler-name] [ingress | egress] Context show>qos Description Display the scheduler stats per SAP. Parameters sap sap-id — The port number and encapsulation value used to identify the SAP. Values The following values apply to the 7750 SR and 7950 XRS: sap-id null [port-id | lag-id]...
Page 606 QoS Scheduler Policy Command Reference sap-id null [port-id | bundle-id | bpgrp-id | lag-id | aps-id] dot1q [port-id | bundle-id | bpgrp-id | lag-id | aps-id]:qtag1 qinq [port-id | bundle-id | bpgrp-id | lag-id]:qtag1.qtag2 [port-id | aps-id][:vpi/vci | vpi | vpi1.vpi2] frame [port-id | aps-id]:dlci cisco-hdlc...
Page 607 QoS Scheduler Policies Values The following values apply to the 7450 ESS: sap-id null [port-id | lag-id] dot1q [port-id |lag-id]:qtag1 qinq [port-id |lag-id]:qtag1.qtag2 frame [port-id]:dlci port-id slot/mda/port[.channel] aps-id aps-group-id[.channel] keyword group-id 1 to 64 ccag-id ccag-id.path-id[cc-type]:cc-id ccag keyword 1 to 8...
Page 608 QoS Scheduler Policy Command Reference Table 38: Show QoS Scheduler-Stats SAP Output Fields (Continued) Label Description Forwarded Octet Displays the number of octets forwarded. Ingress Schedulers Displays the egress scheduler name(s). Egress Schedulers Displays the ingress scheduler name(s). Sample Output A:ALA-12# show qos scheduler-stats sap 1/1/4.1:0 ============================================================================== Scheduler Stats...
Page 609 [scheduler scheduler-name] [ingress | egress] Context show>qos Description This command displays scheduler statistics information and applies only to the 7450 ESS and 7750 SR. Parameters subscriber sub-ident-string — Specifies an existing SLA profile string. scheduler scheduler-name — Specifies an existing scheduler name.
Page 610 QoS Scheduler Policy Command Reference =============================================================================== *A:D# agg-rate customer Syntax customer customer-id site customer-site-name [egress] [detail] Context show>qos Description This command displays the HQoS aggregate rate limit per customer multi-service-site. Parameters customer customer-id — Specifies the ID number associated with a particular customer. Values 1 to 2147483647 site customer-site-name —...
Page 611 QoS Scheduler Policies egress — Displays egress queue group information. access — Displays HQoS aggregate rate limit information on an access port. network — Displays HQoS aggregate rate limit information on a network port. instance instance-id — Specifies the identification of a specific instance of the queue-group. Values 1 to 65535 vport name —...
Page 612 QoS Scheduler Policy Command Reference bpgrp-num 1 to 2000 aps-id aps-group-id[.channel] keyword group-id 1 to 64 ccag-id ccag-id.path-id[cc-type]:cc-id ccag keyword 1 to 8 path-id a, b cc-type .sap-net, .net-sap cc-id 0 to 4094 eth-tunnel eth-tunnel-id[:eth-tun-sap-id] 1 to 128 eth-tun-sap-id 0 to 4094 lag-id lag-id keyword...
Page 613 QoS Scheduler Policies agg-rate subscriber Syntax subscriber sub-indent-string [egress] [detail] Context show>qos Description This command displays the HQoS aggregate rate limit per subscriber. Parameters sub-indent-string — Specifies the subscriber identification string of the subscriber. egress — Displays egress SAP customer scheduler stats. detail —...
Page 614 QoS Scheduler Policy Command Reference Table 40: Show QoS Port Scheduler Output Fields (Continued) Label Description (Continued) Max Rate Displays the explicit maximum frame-based bandwidth limit of this port scheduler. Lvlx PIR Displays the total bandwidth limit, PIR, for the specified priority level. Lvlx CIR Displays the within-cir bandwidth limit for the specified priority level.
Page 615 QoS Scheduler Policies - Port : 5/1/1 =============================================================================== *A:Dut-R# Sample Output The following configuration displays dist-lag-rate-shared and percent-rate for level, group and max-rate in a port-scheduler-policy *B:vineshDut-A>config>qos>port-sched-plcy# info ---------------------------------------------- dist-lag-rate-shared max-rate percent 30.00 group "test" create percent-rate 20.00 cir 20.00 exit level 1 percent-rate 10.00 percent-cir 10.00 level 2 percent-rate 20.00 percent-cir 20.00...
Page 616 QoS Scheduler Policy Command Reference Description : (Not Specified) Max Rate : max Max Rate Percent : 30.00 Dist LAG Rate : True Last changed : 07/16/2014 21:31:51 Group : test Group PIR : max Group CIR : max Group PIR Percent : 20.00 Group CIR Percent : 20.00 Lvl1 PIR : max...
Page 617: Clear Commands
QoS Scheduler Policies Clear Commands Syntax sap sap-id [scheduler scheduler-name] [ingress | egress] Context clear>qos>scheduler-stats Description This command clears scheduler statistics. Parameters sap-id — Specifies the SAP assigned to the service. Values The following values apply to the 7750 SR and 7950 XRS: sap-id null [port-id | lag-id]...
Page 618 QoS Scheduler Policy Command Reference sap-id null [port-id | bundle-id | bpgrp-id | lag-id | aps-id] dot1q [port-id | bundle-id | bpgrp-id | lag-id | aps-id]:qtag1 qinq [port-id | bundle-id | bpgrp-id | lag-id]:qtag1.qtag2 [port-id | aps-id][:vpi/vci | vpi | vpi1.vpi2] frame [port-id | aps-id]:dlci cisco-hdlc...
Page 619 QoS Scheduler Policies Values The following values apply to the 7450 ESS: sap-id : null [port-id | lag-id] dot1q [port-id | lag-id]:qtag1 qinq [port-id | lag-id]:qtag1.qtag2 frame [port-id]:dlci port-id slot/mda/port[.channel] aps-id aps-group-id[.channel] keyword group-id 1 to 64 ccag-id ccag-id.path-id[cc-type]:cc-id ccag...
Page 620 QoS Scheduler Policy Command Reference Quality of Service Guide...
Page 621: Slope Qos Policies
Slope QoS Policies In This Section This section provides information to configure slope QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Default Slope Policy Values • Deleting QoS Policies Overview Default buffer pools exist (logically) at the port, FP or MDA and node levels.
Page 622: Basic Configurations
Overview • Acc-Ing MC Path Mgmt • Network ingress pool • Network egress pool By default, each pool is associated with slope-policy default which has the slopes within the pool shutdown. Slope policies are also applied when WRED is applied per queue and to the associated megapools, see WRED Per Queue.
Page 623: Applying Slope Policies
Slope QoS Policies start-avg percent max-avg percent max-prob percent no shutdown low-slope start-avg percent max-avg percent max-prob percent no shutdown exceed-slope start-avg percent max-avg percent max-prob percent no shutdown time-average-factor taf The following displays the slope policy configuration: A:ALA-7>config>qos# info #------------------------------------------ echo "QoS Slope/Queue Policies Configuration"...
Page 624 Overview Ports The following CLI syntax examples may be used to apply slope policies to port pools: CLI Syntax: config>port>access>ingress>pool>slope-policy name config>port>access>egress>pool>slope-policy name config>port>network>egress>pool>slope-policy name MDA (FP1) The following CLI syntax examples may be used to apply slope policies to MDA pools: CLI Syntax: config>card>mda>access>ingress>pool>slope-policy name config>card>mda>access>egress>pool>slope-policy name...
Page 625: Default Slope Policy Values
Slope QoS Policies CLI Syntax: config>mcast-mgmt>bw-plcy> mcast-pool percent-of-total <percent-of-buffers> resv-cbs <percent-of-pool> slope- policy <policy-name> Default Slope Policy Values The default access ingress and egress policies are identified as policy-id 1. The default policies cannot be edited or deleted. The following displays default policy parameters: Table 41: Slope Policy Defaults Field Default...
Page 626: Deleting Qos Policies
Overview A:ALA-7>config>qos>slope-policy# info detail ---------------------------------------------- description "Default slope policy." high-slope shutdown start-avg 70 max-avg 90 max-prob 80 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 80 exit exceed-slope shutdown start-avg 30 max-avg 55 max-prob 80 exit time-average-factor 7 ---------------------------------------------- A:ALA-7>config>qos>slope-policy# Deleting QoS Policies A slope policy is associated by default with XMAs and MDAs and port access and network egress pools.
Page 627: Mda (Fp1)
Slope QoS Policies MDA (FP1) The following CLI syntax examples can be used to remove slope policies from MDAs: CLI Syntax: config>card>mda>access>ingress>pool# no slope-policy name config>card>mda>access>egress>pool# no slope-policy name config>card>mda>network>egress>pool# no slope-policy name For the MC Path Mgmt, the mcast-pool can be removed from the bandwidth policy or the bandwidth-policy can be removed from under the MDA ingress multicast-path-management.
Page 628: Remove A Policy From The Qos Configuration
Overview Remove a Policy from the QoS Configuration To delete a slope policy, enter the following command: CLI Syntax: config>qos# no slope-policy policy-id Example: config>qos# no slope-policy slopePolicy1 Copying and Overwriting QoS Policies You can copy an existing slope policy, rename it with a new policy ID value, or overwrite an existing policy ID.
Page 629: Editing Qos Policies
Slope QoS Policies max-prob 80 exit low-slope shutdown start-avg 50 max-avg 75 max-prob 80 exit exceed-slope shutdown start-avg 30 max-avg 55 max-prob 80 exit time-average-factor 7 exit slope-policy "slopePolicy2" create description "Default slope policy." high-slope shutdown start-avg 70 max-avg 90 max-prob 80 exit low-slope...
Page 630 Overview Quality of Service Guide...
Page 631: Slope Qos Policy Command Reference
Slope QoS Policies Slope QoS Policy Command Reference Command Hierarchies Configuration Commands config — qos — [no] slope-policy name — description description-string — no description — [no] exceed-slope — max-avg percent — no max-avg — max-prob percent — no max-prob —...
Page 632: Show Commands
Slope QoS Policy Command Reference Show Commands show — qos — slope-policy [slope-policy-name] [detail] Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>slope-policy Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.
Page 633 Slope QoS Policies Context config>qos Description This command copies existing QoS policy entries for a QoS policy-id to another QoS policy-id. The copy command is a configuration level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword. Parameters slope-policy —...
Page 634 Slope QoS Policy Command Reference Description This command sets a weighting factor to calculate the new shared buffer average utilization after assigning buffers for a packet entering a queue. To derive the new shared buffer average utilization, the buffer pool takes a portion of the previous shared buffer average and adds it to the inverse portion of the instantaneous shared buffer utilization.
Page 635 Slope QoS Policies high-slope Syntax [no] high-slope Context config>qos>slope-policy Description The high-slope context contains the commands and parameters for defining the high Random Early Detection (RED) slope graph. Each buffer pool supports a high RED slope for managing access to the shared portion of the buffer pool for in-profile packets.
Page 636 Slope QoS Policy Command Reference Description Sets the exceed, low, or high Random Early Detection (RED) slope position for the shared buffer average utilization value where the packet discard probability rises directly to one. The percent parameter is expressed as a percentage of the shared buffer size. The no form of this command restores the max-avg value to the default setting.
Page 637 Slope QoS Policies config>qos>slope-policy>high-slope config>qos>slope-policy>low-slope Description This command enables or disables the administrative status of the Random Early Detection slope. By default, all slopes are shutdown and have to be explicitly enabled (no shutdown). The no form of this command administratively enables the RED slope. Default shutdown - RED slope disabled implying a zero (0) drop probability start-avg...
Page 638: Show Commands
Slope QoS Policy Command Reference Show Commands slope-policy Syntax slope-policy [slope-policy-name] [detail] Context show>qos Description This command displays slope policy information. Parameters slope-policy-name — The name of the slope policy. detail — Displays detailed information about the slope policy. Slope QoS Policy Output Fields Output The following table describes slope QoS policy output fields.
Page 639 Slope QoS Policies A:C# show qos slope-policy “2” =============================================================================== QoS Slope Policy =============================================================================== Policy Time Avg ------------------------------------------------------------------------------- High Slope Parameters ------------------------------------------------------------------------------- Start Avg : 70 Admin State : Enabled Max Avg : 90 Max Prob. : 100 ------------------------------------------------------------------------------- Low Slope Parameters ------------------------------------------------------------------------------- Start Avg : 30...
Page 640 Slope QoS Policy Command Reference WRED Slot/FP Associations ------------------------------------------------------------------------------- Slot ------------------------------------------------------------------------------- No Matching Entries ------------------------------------------------------------------------------- WRED SAP Queue Associations ------------------------------------------------------------------------------- Policy-Id Queue-Id ------------------------------------------------------------------------------- No Matching Entries ------------------------------------------------------------------------------- WRED QoS Queue-Group Associations ------------------------------------------------------------------------------- Queue-Group Queue-Id ------------------------------------------------------------------------------- No Matching Entries =============================================================================== A:C# Quality of Service Guide...
Page 641: Shared-Queue Qos Policies
Shared-Queue QoS Policies In This Section This section provides information to configure shared-queue QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Default Shared Queue Policy Values Overview Shared-queue QoS policies can be implemented to facilitate queue consumption on the router.
Page 642: Multipoint Shared Queuing
Overview Multipoint Shared Queuing Multipoint shared queuing is supported to minimize the number of multipoint queues created for ingress VPLS, IES or VPRN SAPs or ingress subscriber SLA profiles. Normally, ingress multipoint packets are handled by multipoint queues created for each SAP or subscriber SLA profile instance.
Page 643 Shared-Queue QoS Policies When multiple hardware queues represent a single logical service queue, the system automatically monitors the offered load and forwarding rate of each hardware queue. Based on the monitored state of each hardware queue, the system imposes an individual CIR and PIR rate for each queue that provides an overall aggregate CIR and PIR reflective of what is provisioned on the service queue.
Page 644 Overview When the first SAP or SLA profile instance is configured for shared queuing on an ingress forwarding plane, the system allocates eight hardware queues per available destination forwarding plane, one queue per forwarding class. Twenty-four hardware queues are also allocated for multipoint shared traffic, but that is discussed in the following section.
Page 645 Shared-Queue QoS Policies Figure 38: Multipoint Queue Behavior with Shared Queuing Enabled Multipoint Service Queue is representated by a single Hardware Queue (Single Pass) Unicast Service Queue is Multicast representated by a single Queue Hardware Queue But Dual Pass through the Forwarding Plane Service Queue SF Egress...
Page 646 Overview overall subscriber density on the ingress forwarding plane. Multipoint shared queuing eliminates the multipoint queues sparing hardware queues for better subscriber density. Figure 39 demonstrates multipoint shared queuing. One caveat of enabling multipoint shared queuing is that multipoint packets are no longer managed per service (although the unicast forwarding queues may provide limit benefit in this area).
Page 647: Basic Configurations
Shared-Queue QoS Policies • Apipe (applies to the 7750 SR and 7950 XRS) • Fpipe (applies to the 7750 SR and 7950 XRS) • Ipipe • Routed CO For information about the tasks and commands necessary to access the command line interface and to configure and maintain your router, refer to CLI Usage chapter in the Basic System Configuration Guide.
Page 648: Applying Shared-Queue Policies
Overview cbs 2 high-prio-only 20 exit ---------------------------------------------- A:ALA-48>config>qos>shared-queue# Applying Shared-Queue Policies The default shared queue policy is applied at the SAP level just as sap-ingress and sap-egress QoS policies are specified. If the shared-queuing keyword is not specified in the qos policy- id command then the SAP is assumed to use single-pass queuing.
Page 649 Shared-Queue QoS Policies IES Services Use the following CLI syntax to apply the default policy to an IES service: CLI Syntax: config>service# ies service-id interface interface-name sap sap-id ingress qos policy-id [shared-queuing |multipoint-shared] The following output displays an IES service configuration with SAP ingress policy 100 applied to the SAP with shared-queuing enabled.
Page 650: Default Shared Queue Policy Values
Overview exit exit exit ---------------------------------------------- A:SR>config>service# VPRN Services Use the following CLI syntax to apply QoS policies to ingress VPRN SAPs on the 7750 SR and 7950 XRS: CLI Syntax: config>service# vprn service-id [customer customer-id] interface ip-int-name sap sap-id ingress qos policy-id [shared-queuing | multipoint-shared] The following output displays a VPRN service configuration.
Page 651 Shared-Queue QoS Policies Table 43: Shared Queue Policy Defaults Field Default description “Default Shared Queue Policy” queue 1 auto-expedite rate high-prio-only queue 2 auto-expedite rate high-prio-only queue 3 auto-expedite rate high-prio-only queue 4 auto-expedite rate high-prio-only queue 5 auto-expedite Quality of Service Guide...
Page 652 Overview Table 43: Shared Queue Policy Defaults (Continued) Field Default rate high-prio-only queue 6 auto-expedite rate high-prio-only queue 7 auto-expedite rate high-prio-only queue 8 auto-expedite rate high-prio-only The fc-to-shared-queue mappings that cannot be modified are: fc af queue 3 Quality of Service Guide...
Page 653 Shared-Queue QoS Policies Table 43: Shared Queue Policy Defaults (Continued) Field Default fc be queue 1 fc h1 queue 6 fc h2 queue 5 fc l1 queue 4 fc l2 queue 2 fc nc queue 8 The following output displays the default configuration: ALA-7>config>qos>shared-queue# info detail ---------------------------------------------- description "Default Shared Queue Policy"...
Page 654 Overview queue 7 auto-expedite create rate 100 cir 10 mbs 25 cbs 3 high-prio-only 10 exit queue 8 auto-expedite create rate 100 cir 10 mbs 25 cbs 3 high-prio-only 10 exit fc af create queue 3 exit fc be create queue 1 exit fc ef create...
Page 655: Shared-Queue Qos Policy Command Reference
Shared-Queue QoS Policies Shared-Queue QoS Policy Command Reference Command Hierarchies Configuration Commands config — qos — shared-queue policy-name — description description-string — no description — [no] {be | l2 | af | l1 | h2 | ef | h1 | nc} —...
Page 656: Command Descriptions
Shared-Queue QoS Policy Command Reference Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>shared-queue Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.
Page 657 Shared-Queue QoS Policies Syntax [no] fc fc-name Context config>qos>shared-queue 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 658 Shared-Queue QoS Policy Command Reference Description This command configures the 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. Once the forwarding class mapping is executed, all multicast traffic on a SAP using this policy is forwarded using the queue-id.
Page 659: Show Commands
The expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. On the 7450 ESS, the expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. The hardware status of the queue must be defined at the time of queue creation within the policy.
Page 660 Shared-Queue QoS Policy Command Reference 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 661 Shared-Queue QoS Policies The unknown forwarding type usually tracks the multicast forwarding type definition. This command overrides that default behavior. The no form of this command sets the unknown forwarding type queue-id back to the default of tracking the multicast forwarding type queue mapping. Parameters queue-id —...
Page 662 Shared-Queue QoS Policy Command Reference Table 44: CBS Forwarding Class Default Values Forwarding Class Fowarding Class Label Default CBS Network-Control High-1 Expedited High-2 Low-1 Assured Low-2 Best-Effort Parameters percent — The percent of buffers reserved from the total buffer pool space, expressed as a decimal integer.
Page 663 Shared-Queue QoS Policies Default Parameters percent — The amount of queue buffer space, expressed as a decimal percentage of the MBS. Values 0 to 100 | default Syntax mbs percent no mbs Context config>qos>shared-queue>queue Description This command specifies the relative amount of the buffer pool space for the maximum buffers for a specific ingress network XMA or MDA forwarding class queue or egress network port forwarding class queue.
Page 664 Shared-Queue QoS Policy Command Reference Parameters percent — The percent of buffers from the total buffer pool space for the maximum amount of buffers, expressed as a decimal integer. If 10 MB is the total buffers in the buffer pool, a value of 10 would limit the maximum queue size to 1MB (10%) of buffer space for the forwarding class queue.
Page 665 Shared-Queue QoS Policies The CIR defines the percentage 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. In-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse.
Page 666 Shared-Queue QoS Policy Command Reference Shared-Queue QoS Policy Output Fields Output Table 46 describes shared-queue QoS policy output fields. Table 46: Show QoS Shared Queue Output Fields Label Description Policy The ID that uniquely identifies the policy. Description A text string that helps identify the policy’s context in the configuration file.
Page 667 Advanced QoS Policies In This Section This section provides information to configure advanced QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configurations • Default Advanced Policy Values • Deleting QoS Policies Overview The adv-config-policy contains queue and policer configuration parameters that are not expected to be useful to most users.
Page 668 Overview For information about the tasks and commands necessary to access the command line interface and to configure and maintain your router, refer to CLI Usage chapter in the System Basic Configuration Guide. Basic Configurations A advanced QoS policy must conform to the following: •...
Page 669: Advanced Qos Policies
Advanced QoS Policies ALA-7>config>qos# Applying Advanced Policies Apply advanced policies to the following entities: • Queue Group • SAP Ingress • SAP Egress Queue Group Use the following CLI syntax to apply advanced policies to ingress queue groups. CLI Syntax: config>...
Page 670: Overview
Overview Default Advanced Policy Values The default policies cannot be edited or deleted. Table 47 displays default advanced policy parameters. Table 47: Advanced Policy Parameter Defaults Field Default offered-measurement high-rate-hold-time time-average-factor sample-interval Deleting QoS Policies Delete advanced policies from the following entities: •...
Page 671: Sap Ingress
Advanced QoS Policies SAP Ingress Use the following CLI syntax to delete advanced policies from an ingress SAP. CLI Syntax: qos sap-ingress 11 policer 1 adv-config-policy child1 queue 1 no adv-config-policy SAP Egress Use the following CLI syntax to delete advanced policies from an egress SAP. CLI Syntax: qos sap-egress 11 policer 1 adv-config-policy child1 queue 1 no adv-config-policy...
Page 672 Overview Quality of Service Guide...
Page 673 Advanced QoS Policies Advanced QoS Policy Command Reference Command Hierarchies Configuration Commands config — qos — [no] adv-config-policy policy-name — description description-string — no description — child-control — offered-measurement — [no] {percent percent-of-admin-pir | rate rate-in-kilobits-per- second} [min-only | active-min-only] —...
Page 674 Advanced QoS Policy Command Reference Show Commands show — qos — adv-config-policy [policy-name] [detail] Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>adv-config-policy Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.
Page 675: Operational Commands
Advanced QoS Policies Operational Commands copy Syntax copy adv-config-policy src-name dst-name [overwrite] Context config>qos Description This command copies existing QoS policy entries for a QoS policy-id to another QoS policy-id. The copy command is a configuration level maintenance tool used to create new policies using existing policies.
Page 676 Advanced QoS Policy Command Reference While the system maintains default values for the advanced configuration parameters, no default adv- config-policy exists. The no form of this command removes the specified advanced policy. Default None Parameters policy-name — The name of the advanced QoS policy. A policy-name must be specified and conform to the policy naming guidelines.
Page 677 Advanced QoS Policies min-only] Context config>qos>adv-config-policy>child-control>offered-measurement Description This command is used to increase the measured rate of the policer or queue associated with the policy. The offered rate (capped by the administrative PIR configured on the queue or policer) is usually used unaltered by the parent virtual scheduler.
Page 678 Advanced QoS Policy Command Reference Parameters percent-of-admin-pir — When the percent qualifier is used, this parameter specifies the percentage of the child’s administrative PIR that should be added to the child’s offered rate. The new offered rate result is capped by the child’s PIR. If a value of 0 or 0.00 is used, the system interprets this equivalent to no add.
Page 679 Advanced QoS Policies If the granularity command is used with a percent based value, the sensitivity is a function of the configured PIR value on the policer or queue. In this case, care should be taken that the child is either configured with an explicit PIR rate (other than max) or the child’s administrative PIR is defined using the percent-rate command with the local parameter enabled if an explicit value is not desired.
Page 680 Advanced QoS Policy Command Reference A possible reason to define a maximum decrement limit is to allow a child queue or policer to hold on to a portion of bandwidth that has been distributed by the parent virtual scheduler in case the child’s offered rate fluctuates in an erratic manor.
Page 681 Advanced QoS Policies high-rate-hold-time Syntax [no] high-rate-hold-time seconds [active-min-only] Context config>qos>adv-config-policy>child-control>offered-measurement Description This command sets a time period that the current offered rate should be maintained for a child policer or queue once it is seen that the offered rate is decreasing. The offered measurement that triggers the hold time is used when the hold timer expires unless a higher offered rate is seen in the interim.
Page 682 Advanced QoS Policy Command Reference The adjustment to the offered rate is performed using the following formula when taf-value is not set to ‘0’: Adjusted_Rate = ((Prev_Offered_Rate x (taf-value – 1)) + New_Offered_Rate) / taf-value If the dec-only option is specified, the adjustment is only applied when New_Offered_Rate is less than the Prev_Offered_Rate.
Page 683 Advanced QoS Policies fast-start Syntax [no] fast-start Context config>qos>adv-config-policy>child-control>offered-measurement Description This command is used to enable fast detection of initial bandwidth on a child policer or queue associated with the policy. Multiple offered rate counter reads may be performed per the sampling interval.
Page 684 Advanced QoS Policy Command Reference Context config>qos>adv-config-policy>child-control Description This command modifies or controls the bandwidth distribution phase of the parent virtual scheduler. This command edits the parameters that control the child given bandwidth for all policers and queues associated with the policy. above-offered-cap Syntax [no] above-offered-cap {percent percent-of-admin-pir | rate rate-in-kilobits-per-second}...
Page 685 Advanced QoS Policies Parameters percent-of-admin-pir — When the percent qualifier is used, the following percent-of-admin-pir parameter specifies the percentage of the child’s administrative PIR that used as the fair share increase limit. The new operational PIR result is capped by the child’s PIR. If a value of 0 or 0.00 is used, the system will disable the fair share increase function and only configure the actual distribution rate.
Page 686 Advanced QoS Policy Command Reference Description This command is used to create a stepped like behavior where the operational PIR will round up to the nearest increment of the specified granularity before being applied to the child. The only exception is when the distributed bandwidth is less than 1% above a lower step value in which case the lower step value is used.
Page 687 Advanced QoS Policies limit-pir-zero-drain Syntax [no] limit-pir-zero-drain Context config>qos>adv-config-policy>child-control>offered-measurement Description This command is used to configure the system to use the minimum configurable PIR instead of an HQoS derived zero operational PIR. The default behavior is to allow the operational PIR of the queue to remain the last configured value while setting the queue MBS to zero (preventing queuing of newly arriving packets).
Page 688 Advanced QoS Policy Command Reference Show Commands The command outputs in the following section are examples only; actual displays depend on supported functionality and user configuration. adv-config-policy Syntax adv-config-policy [policy-name] [detail] Context show>qos Description This command displays advanced QoS policy information. Parameters policy-name —...
Page 689 QoS ATM Traffic Descriptor Profiles In This Section This section provides information to configure QoS Traffic Descriptor Profiles using the command line interface. • Overview • Basic Configurations • Default ATM-TD-Profile Policy Values • Service Management Tasks Overview ATM Traffic Descriptor Profiles This section provides a description of support ATM QoS policy features.
Page 690 Overview QoS Model for ATM-Based Services Figure 40: Hierarchical Scheduling for ATM-Based Services Cell Level Per-VC Queues Packet Level Forwarding (ATM SAR) Class Queues CBR High Strict Priority Strict Priority Shaping CBR Low Basic/HQoS Shaped VC 1 Scheduler VC 1 Packet VLL/VPLS/ Switch Queues...
Page 691: Qos Atm Traffic Descriptor Profiles
QoS ATM Traffic Descriptor Profiles Any discard decision are performed exclusively at the packet level where the context for the frame forwarding class and for the 802.1p bit mapping to a forwarding class is known. When a per-VC queue backs up, a back pressure scheme is applied such that the frames are held in the per-forwarding class packet queues dedicated to this VC.
Page 692: Overview
Overview Policing The policing option, when enabled, applies only for ingress traffic. Similarly, the shaping option, if enabled, applies only for egress traffic. For example, if a traffic descriptor has both options, policing and shaping enabled, the policing option is enforced for the ingress traffic, while the shaping option is enforced for the egress traffic.
Page 693: Congestion Avoidance
QoS ATM Traffic Descriptor Profiles • nrt-VBR unshaped VCs and UBR VCs are scheduled as a common class. Scheduling among these VCs is done using a WRR scheduler where the weight of each VC is determined by the configured SIR for nrt-VBR and by the MIR for UBR VCs. The scheduling is work-conserving, so each VC has access to excess bandwidth in proportion to its SIR/MIR.
Page 694: Shaping
Overview • Assign a policy ID (policy number). The system will not dynamically assign an ID. • Include a description. The description provides a brief overview of policy features. • Configure traffic attributes of the ATM traffic profile. • Determine whether egress shaping should occur. The following displays an atm-td-profile policy configuration: *A:ALA-48>config>qos>atm-td-profile# info ----------------------------------------------...
Page 695 QoS ATM Traffic Descriptor Profiles Epipe SAPs Use the following CLI syntax to apply ATM QoS traffic descriptor profile policies to Epipe SAPs on ingress and egress. CLI Syntax: config>service>epipe>sap# atm egress traffic-desc traffic-desc-profile-id ingress traffic-desc traffic-desc-profile-id IES SAPs Use the following CLI syntax to apply ATM QoS traffic descriptor profile policies to IES SAPs on ingress and egress.
Page 696 Overview VPLS SAPs Use the following CLI syntax to apply ATM QoS traffic descriptor profile policies to VPLS SAPs on ingress and egress. CLI Syntax: config>service>vpls>sap# atm egress traffic-desc traffic-desc-profile-id ingress traffic-desc traffic-desc-profile-id Default ATM-TD-Profile Policy Values The default ATM QoS traffic descriptor profile is identified as default. The default profile cannot be edited or deleted.
Page 697 QoS ATM Traffic Descriptor Profiles descriptor-type P0_1 no shaping exit atm-td-profile 2 create ---------------------------------------------- A:ALA-48>config>qos# Service Management Tasks This section discusses the following service management tasks: • Removing a Profile from the QoS Configuration • Copying and Overwriting Profile • Editing QoS Policies Removing a Profile from the QoS Configuration The default ATM traffic descriptor profile cannot be deleted.
Page 698 Service Management Tasks CLI Syntax: config>qos> copy atm-td-profile src-prof dst-prof [overwrite] Example: A:ALA-48>config>qos# copy atm-td-profile 2 3 MINOR: CLI destination (3) exists use {overwrite}. A:ALA-48>config>qos# copy atm-td-profile 2 3 overwrite A:ALA-48>config>qos# Editing QoS Policies You can change existing policies and entries in the CLI. The changes are applied immediately to all services where this policy is applied.
Page 699: Configuration Commands
QoS ATM Traffic Descriptor Profiles ATM QoS Policy Command Reference Command Hierarchies Configuration Commands config — qos — [no] atm-td-profile traffic-desc-profile-id — [no] clp-tagging — description description-string — no description — descriptor-type type — [no] policing — service-category service-category — [no] shaping —...
Page 700: Operational Commands
ATM QoS Policy Command Reference — port [port-id] atm pvt [vpi-range] [detail] Command Descriptions Configuration Commands Generic Commands description Syntax description description-string no description Context config>qos>atm-td-profile Description This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the context in the configuration file.
Page 701 QoS ATM Traffic Descriptor Profiles The copy command is a configuration level maintenance tool used to create new profiles using existing profiles. It also allows bulk modifications to an existing profile with the use of the overwrite keyword. Parameters atm-td-profile src-prof dst-prof — Indicates that the source profile ID and the destination profile ID are atm-td-profile IDs.
Page 702 ATM QoS Policy Command Reference When many changes are required on a profile, it is recommended that the profile be copied to a work area profile ID. That work-in progress profile can be modified until complete and then written over the original profile-id.
Page 703 QoS ATM Traffic Descriptor Profiles Table 50: Descriptor Type Default Values (Continued) Service Category Default Descriptor Type P0_1 UBR with MIR P0_1 rt-VBR or nrt-VBR P0_1andS0_1 Parameters type — defines interpretation of traffic parameters that are specified for this profile Values P0_1, P0_1andS0_Tag, P0_1andS0, P0_1andS0_1 Table 51...
Page 704: Atm Service Categories
ATM QoS Policy Command Reference service-category Syntax service-category service-category Context config>qos>atm-td-profile Description This command is used to configure an ATM service category attribute of an ATM traffic descriptor profile per ATM Forum Traffic Management Specification Version 4.1. The router supports the ATM service categories on ATM-capable MDAs listed in Table Table 52: ATM Service Categories Service Category...
Page 705 QoS ATM Traffic Descriptor Profiles Table 53: Default Shaping Values Applicable Service Default Shaping Comments Category Value disabled Shaping cannot be enabled enabled Shaping cannot be disabled when the profile is applied to ATM SAP on ATM MDA rt-VBR enabled Shaping cannot be disabled when applied to ATM SAP on ATM MDA...
Page 706 ATM QoS Policy Command Reference Table 54: Traffic Descriptor Parameter Support by Service Category (Continued) Service Category CDVT UBR with MIR Y (must be Y (non- >= MIR zero MIR specified) Configuring PIR for traffic descriptor profiles for UBR and UBR with MIR service categories has no impact on a traffic contract when a PVCC using that profile resides on an m4-atmoc12/3-sfp XMA or MDA.
Page 707: Show Commands
QoS ATM Traffic Descriptor Profiles Table 55: ATM Traffic Parameter Defaults Service Category Traffic Parameter Defaults CBR: rt-VBR and nrt-VBR UBR (by default UBR is without MIR) Parameters sir value — Sustained Information Rate (including cell overhead) in kilobits per second. Values 0 to 4294967295 pir value —...
Page 708 ATM QoS Policy Command Reference atm-td-profile Syntax atm-td-profile [traffic-desc-profile-id] [detail] Context show>qos Description This command displays ATM traffic descriptor profile information. Parameters traffic-desc-profile-id — Displays the ATM traffic descriptor profile. Values 1 to 1000 detail — Displays detailed policy information including policy associations. Output ATM TD Profile Output —...
Page 709 QoS ATM Traffic Descriptor Profiles =============================================================================== Maximum Supported Profiles : 1000 Currently Configured Profiles ------------------------------------------------------------------------------- TDP-id Description Service Category SCR ------------------------------------------------------------------------------- Default Traffic Descriptor ------------------------------------------------------------------------------- Default Traffic Descriptor NRT_VBR 4000 5000 ------------------------------------------------------------------------------- Default Traffic Descriptor NRT_VBR 4000 5000 =============================================================================== A:ALA-48>config>qos>atm-td-profile# A:ALA-48>config>qos>atm-td-profile# show qos atm-td-profile 10 detail =============================================================================== Traffic Descriptor Profile (10)
Page 710 ATM QoS Policy Command Reference qos-policy qos-policy-id — The ingress or egress QoS Policy ID for which to display matching SAPs. Values 1 to 65535 filter filter-id — The ingress or egress Filer Policy ID for which to display matching SAPs. Values 1 to 65535 sap-id —...
Page 711 *, 0 to 4094 NNI: 0 to 4095 UNI: 0 to 255 1, 2, 5 to 65535 dlci 16 to 1022 The following values apply to the 7450 ESS: Values sap-id null [port-id | lag-id] dot1q [port-id | lag-id]:qtag1 qinq [port-id | lag-id]:qtag1.qtag2...
Page 712 ATM QoS Policy Command Reference Table 57: SAP Output Fields Label Description Port ID The ID of the access port where the SAP is defined. Svc ID The service identifier. SapMTU The SAP MTU value. I.QoS The SAP ingress QoS policy number specified on the ingress SAP. I.MAC/IP The MAC or IP filter policy ID applied to the ingress SAP.
Page 713 7750 SR7: 1 - 5 • 7750 SR1: 1 • 7750 SR-c12 Values The following slot values apply to the 7450 ESS: • 7450 ESS7: 1 - 5 • 7450 ESS1: 1 MDA Values: 1, 2 Port Values: 1 to 60 (depending on the MDA)
Page 714 ATM QoS Policy Command Reference Table 58: Show Port ATM PVC VPI/VCI Detail Output Fields Label Description Port Id Displays the port ID. VPI/VCI Displays the VPI/VCI values. Admin State Displays the administrative state of the interface connection. Oper State Indicates the status of the ATM interface.
Page 715 QoS ATM Traffic Descriptor Profiles Table 58: Show Port ATM PVC VPI/VCI Detail Output Fields (Continued) Label Description CRC-32 Errors Displays the number of valid AAL-5 SDUs and AAL-5 SDUs with CRC-32 errors received by the AAL-5 VCC. Reassembly Timeouts Displays the number of reassembly timeout occurrences.
Page 716 ATM QoS Policy Command Reference =============================================================================== Input Output ------------------------------------------------------------------------------- Loopback CRC-10 Errors Other =============================================================================== A:ALA-1# Quality of Service Guide...
Page 717: Basic Configurations
Named Pools In This Section This section provides information to configure Named Pools QoS policies using the command line interface. Topics in this section include: • Overview • Basic Configuration Overview The named buffer pool feature allows for the creation of named buffer pools at the XMA, MDA and port level.
Page 718 Overview The named pool policy is applied at the XMA or MDA ingress and egress level and at the ingress and egress port level. Each XMA or MDA within the system is associated with a forwarding plane traffic manager that has support for a maximum of 57 buffer pools. The following circumstances affect the number of named pools that can be created per XMA or MDA (these circumstances may be different between ingress and egress for the XMA or MDA):...
Page 719: Named Pools
Named Pools When buffer pools are being created or deleted, individual queues may need to be moved to or from the default pools. When a queue is being moved, the traffic destined to the queue is first moved temporarily to a ‘fail-over’ queue. Then the queue is allowed to drain. Once the queue is drained, the statistics for the queue are copied.
Page 720: Overview
Overview Buffer allocation rate modification is supported for both standard and named pool mode buffer allocation methods. The system allocates buffers based on the following criteria: • “named-pool-mode” setting on the IOM. • Amount of path bandwidth on channelized ports. •...
Page 721: Basic Configuration
Named Pools Ingress Q1 Named Pools Egress Q1 Named Pools *A:PE# Basic Configuration A basic named pool QoS policy must conform to the following: • Default values can be modified but parameters cannot be deleted. Create a Named Pool QoS Policy To create a new named pool policy, the following must be defined: •...
Page 722 Overview CLI Syntax: config# network queue configure qos copy network-queue default 15 network-queue 15 queue 1 pool p1 exit all Step 3: Configure the above queue profile to be used by the respective applications or port. Configure the named pool policy. CLI Syntax: config# configure card 1 mda 2 network ingress queue- policy 15...
Page 723: Allocation Steps
Named Pools A:SR7-10# Allocation Steps Whether one or multiple MDAs share the same buffer space, the buffer space is portioned out on a per port basis. Each port gets an amount of buffering which is its fair-share based on the port’s bandwidth compared to the overall active bandwidth.
Page 724 Overview port named pools are created, the XMA or MDA weight should be set to ‘0’. Setting the default weight to ‘0’ should be done with care as any queues without named pool definitions or queues with non-existent pool names use the default pools. The weights are summed and then each individual weight is divided by the sum.
Page 725: Command Hierarchies
Named Pools Named Pools QoS Policy Command Reference Command Hierarchies Configuration Commands config — qos — [no] named-pool-policy policy-name [create] — description description-string — no description — q1-pools — [no] pool pool-name [create] — amber-alarm-threshold percentage — no amber-alarm-threshold — application-weights —...
Page 726: Show Commands
Named Pools QoS Policy Command Reference Show Commands show — qos — named-pool-policy — named-pool-policy policy-name [detail] — named-pool-policy policy-name association — network-queue policy-id detail — sap-egress policy-id detail — sap-ingress policy-id detail — shared-queue default detail — slope-policy slope-name detail show —...
Page 727: Named Pool Policy Creation
Named Pools Parameters description-string — The description-string parameter defines the ASCII description string for the named pool policy. If the string contains spaces, it must be placed within beginning and ending double quotation marks. Beginning and ending quotation marks are not considered part of the description string.
Page 728 Named Pools QoS Policy Command Reference Pools in the policy may be added or removed at anytime. If the policy is currently associated with an XMA, MDA, or port, the system will first check to ensure necessary resources exist on the port, XMA, or MDA before allowing the pool creation within the policy to proceed.
Page 729 Named Pools q1-pools Syntax q1-pools Context config>qos>named-pool-policy Description The q1-pools command is used to enter the configuration node for Q1 oriented named buffer pools. The named pool policy will support contexts for configuring pools of other types when other pool types exist.
Page 730 Named Pools QoS Policy Command Reference port weight — The port keyword is used to identify the weight value for the port where the policy is applied used in the calculation of the amount of buffer space given to the local port named pools by the port.
Page 731 Named Pools create — The create keyword is required if creating a new named pool within the policy 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 732 Named Pools QoS Policy Command Reference application-weights Syntax application-weights Context config>qos>named-pool-policy>q1-pools>pool Description The application-weights CLI node context contains the network and access allocation weights. The network and access application weights are used to divide the network and access buffer space available to the pools between each named pool.
Page 733 Named Pools access-allocation-weight Syntax access-allocation-weight buffer-allocation-weight no access-allocation-weight Context config>qos>named-pool-policy>q1-pools>pool>application-weights Description The access-allocation-weight command is used to define the weight used when dividing access associated buffer space between the named pools. When the named pool is created on an XMA or MDA, the access associated buffer space is summed from all ports.
Page 734 Named Pools QoS Policy Command Reference The slope policy contains the High and Low WRED slope definitions that will be used by the pool on each XMA or MDA on which the pool is created. If the slope-policy command is not executed or the no slope-policy command is executed, the default slope policy will be associated with the pool.
Page 735 Named Pools max maximum — Specifies the maximum percentage for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, max value must be set to non-default value along with the step percent. When reserved CBS is default adaptive CBS sizing cannot be enabled.
Page 736 Named Pools QoS Policy Command Reference 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 can be modified but not deleted. The no sap-ingress command restores the factory default settings when used on policy-id 1.
Page 737 Named Pools The queue command allows the creation of multipoint queues. Only multipoint queues can receive ingress packets that need flooding to multiple destinations. By separating the unicast for multipoint traffic at service ingress and handling the traffic on separate multipoint queues special handling of the multipoint traffic is possible.
Page 738 Named Pools QoS Policy Command Reference 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. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy.
Page 739 Named Pools priority-mode: The queue is capable of handling traffic differently with two distinct priorities. These priorities are assigned by the stages preceding the queueing framework in the system. In priority mode, the queue does not have the functionality to support the profiled traffic and in such cases the queue will have a degraded performance.
Page 740 Named Pools QoS Policy Command Reference Parameters pool-name — The specified pool-name identifies a named pool where the policy will be applied. 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 741 Named Pools Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all egress SAPs where this policy is applied. For this reason, when many changes are required on a policy, it is highly recommended that the policy be copied to a work area policy-id. That work-in- progress policy can be modified until complete and then written over the original policy-id.
Page 742 On the 7950 XRS, the expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. On the 7450 ESS, the expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. The hardware status of the queue must be defined at the time of queue creation within the policy.
Page 743 Named Pools auto-expedite — This keyword allows the system to auto-define the way the queue is serviced by the hardware. When auto-expedite is defined on the queue, the queue is treated in an expedited manner when all forwarding classes mapped to the queue are configured as expedited types nc, ef, h1 or h2.
Page 744: Network Queue Qos Policy Commands
Named Pools QoS Policy Command Reference The no form of the command removes a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool. Default None Parameters pool-name — The specified pool-name identifies a named pool where the policy will be applied. Each queue created within the system is tied to a physical port.
Page 745: Show Commands
Named Pools Description This command creates the context to configure a QoS network-queue policy queue. Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or non-expedited nature of the queue based on the forwarding classes mapped to it.
Page 746 Named Pools QoS Policy Command Reference The queue’s pool association may only be removed by either re-executing the queue command without the pool keyword or by executing the no pool command within the queue’s CLI context. When the pool name is removed, the queue will be placed on the appropriate default pool. Parameters queue-id —...
Page 747 Named Pools 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 bandwidth to the packets with different profiles.
Page 748 Named Pools QoS Policy Command Reference Parameters pool-name — The specified pool-name identifies a named pool where the policy will be applied. 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 749 Named Pools sap-ingress Syntax sap-ingress policy-id detail Context show>qos Description This command displays pools associated/configured to a queue. Output Sample Output B:SR7-10# show qos sap-ingress 2 detail =============================================================================== QoS Sap Ingress ------------------------------------------------------------------------------- Sap Ingress Policy (2) ------------------------------------------------------------------------------- Policy-id Scope : Template Default FC : be Priority...
Page 750 Named Pools QoS Policy Command Reference Description This command displays pools associated/configured to a queue. shared-queue Syntax shared-queue default detail Context show>qos Description This command displays pool name details pertaining to a shared-queue. Output Sample Output A:ALA-A>show>qos# shared-queue default detail =============================================================================== QoS Shared Queue Policy -------------------------------------------------------------------------------...
Page 751 Named Pools testOrig =============================================================================== A:ALA-A>show>qos# card Syntax card card-slot detail | match “Named Pool Mode” Context show Description This command checks the card specified named pool mode. Output Sample Output show card 1 detail | match "Named Pool Mode" ====================================================== Named Pool Mode : Configured (Enabled) ======================================================...
Page 752 Named Pools QoS Policy Command Reference =============================================================================== Port Percent Total Bw Total Buffer Default % Mda % Port % ------------------------------------------------------------------------------- 1/2/1 1000000 12260 1/2/2 1000000 12260 1/2/3 1000000 12260 1/2/4 1000000 12260 1/2/5 1000000 12260 1/2/6 1000000 12260 1/2/7 1000000 12260 1/2/8 1000000...
Page 753 Named Pools 1/2/9 1000000 12260 Access Network 1000000 12260 2042 4086 6130 1/2/10 1000000 12260 Access Network 1000000 12260 2042 4086 6130 =============================================================================== Named Pool Information =============================================================================== Mda/Port Pool Name Pool Size Access Network Weight Total Buffer Space Weight Total Buffer Space ------------------------------------------------------------------------------- 11093...
Page 754 Named Pools QoS Policy Command Reference pools Syntax pools port-id Context show Description This command displays XMA, MDA, or port pools. If the pool size is zero, there are no queues associated with the pool and the pool is not in use (configured but not instantiated). To display details about an ingress/egress named pool, use the command show pools 1/2 ingress | egress p2.
Page 755 High Scale Ethernet MDA Capabilities In This Section This section provides information to configure HSMDA QoS policies using the command line interface. Topics in this section include: • HSMDA QoS Model • SAP Ingress and SAP Egress QoS Policies • Subscriber Queuing Differences •...
Page 756: Queue Scaling
HSMDA QoS Model • Hardware implemented provider style port based scheduling • Elimination of ingress dual pass queuing at the ingress hardware • Egress intermediate destination (such as DSLAM) shaping using secondary shapers • Expanded counters at ingress and egress •...
Page 757: High Scale Ethernet Mda Capabilities
High Scale Ethernet MDA Capabilities Figure 41: HSMDA Queue Mapping to Scheduler Class Service Lists Scheduler Service List (Per Egress Port Scheduler or Single Ingress Scheduler) Scheduling Class 8 Service List Queue 8 Scheduling Class 7 Service List Queue 7 Scheduling Class 6 Service List Queue 6...
Page 758: Hsmda Qos Model
HSMDA QoS Model Figure 42: Scheduler Class Mapping to Strict Level or Weighted Group Example Service List Group 1 Service List Group 2 (Maximum of 3 (Maximum of 3 Consecutive Service Consecutive Service Class Lists) Class Lists) Strict Level 8 Scheduling Class 8 Group 1 Weight...
Page 759 High Scale Ethernet MDA Capabilities Figure 44: Scheduler Class and Weighed Group Scheduling Priority Mapping Example 8 Strict Byte Fair Scheduling of Priority Service List Members Levels Scheduling Class 8 Service List Class Weighted Group 1 Class Weighted Group 2 Scheduling Class 7 Service List Class Weighted Group 1 Class Weighted Group 2...
Page 760: Dual Pass Queuing
HSMDA QoS Model • Intermediate destination shaper (egress) • Per queue-group shaper • Per queue shaper Dual Pass Queuing In the standard queuing model, the ingress hardware performs both per service ingress SLA enforcement as well as per switch fabric destination based virtual output queuing. Due to the requirement that each queue on ingress be mapped to a single switch fabric destination, when a SAP for a service type that forwards to multiple switch fabric destinations (such as VPLS, IES and VPRN services), a single ingress service queue is created as multiple hardware...
Page 761 High Scale Ethernet MDA Capabilities In other systems, the downstream destination is represented as a scheduler in a tiered hierarchical scheduler. This means that bandwidth is allocated on a per DSLAM basis without regard to the class of packets being forwarded to that DSLAM. In this model, a set of subscribers on one DSLAM receiving packets for a premium service are treated equally to subscribers on other DLSAMs receiving packets associated with best-effort type services.
Page 762: Packet And Octet Counting
HSMDA QoS Model Figure 45: HSMDA Egress Queue Group and Secondary Destination Shaper Behavior Egress Port Secondary Other Queu Groups Destination Associated With Same Shaper Secondary Destination Stop servicing all queues Shaper associated with secondary destination shaper when destination PIR is exceeded. Queue 8 Class 8 Service List Queue 7...
Page 763 High Scale Ethernet MDA Capabilities • Discarded out-of-profile (low priority) packet • Discarded out-of-profile (low priority) octet • Discarded in-profile (high priority) packet • Discarded in-profile (high priority) octet • Forwarded out-of-profile packet • Forwarded out-of-profile octet • Forwarded in-profile packet •...
Page 764: Above Cir Discard With Pir Bypass
HSMDA QoS Model Since the HSMDA only updates a single counter set per packet, overriding the counter for a packet causes that packet not to be represented within the default counter-id for the queue. If the queue counter-id is being used to determine CIR or PIR accuracy or basic throughput for a queue, any packets forwarded through the queue using a counter override is considered.
Page 765 High Scale Ethernet MDA Capabilities • Ensure that the policing queue is not stalled by the queue groups configured aggregate rate limit. If the queue is not the highest scheduling priority, the sum of the allowed scheduling for the queues with higher scheduling priority may cause the queue groups PIR to be exceeded and thus scheduling for the policing queue will stall.
Page 766: Hsmda Buffer Utilization Controls
HSMDA QoS Model HSMDA Buffer Utilization Controls The HSMDA has 1 million ingress and 1 million egress 168-byte buffers available for packet queuing purposes. The average of approximately six buffers per queue when all 163,480 are active. Certain queues need more than 6 buffers while other queues require very shallow buffering based on the type of traffic the queue is servicing and the scheduling priority of the queue.
Page 767: Provisioned And System Port Class Pools
High Scale Ethernet MDA Capabilities Figure 46: Queue Group ID Mapping Table 20479 OSSG154 Provisioned and System Port Class Pools The HSMDA uses a second table called the port class buffer pools table (Figure 47) that represents a set of 180 buffer pools. Pools 0 through 79 are used by queues within group P and 80 through 179 are used by queues within group S.
Page 768: Aggregate Pools For Type And Class Separation
HSMDA QoS Model Figure 47: Port Class Buffer Pools Table Buffers-Available (21bits) Agg-Pool-Ptr-1 (5bits) Agg-Pool-Ptr-2 (5bits) Buffers-Available (21bits) Agg-Pool-Ptr-1 (5bits) Agg-Pool-Ptr-2 (5bits) Buffers-Available (21bits) Agg-Pool-Ptr-1 (5bits) Agg-Pool-Ptr-2 (5bits) Group P Buffers-Available (21bits) Agg-Pool-Ptr-1 (5bits) Agg-Pool-Ptr-2 (5bits) Buffers-Available (21bits) Agg-Pool-Ptr-1 (5bits) Agg-Pool-Ptr-2 (5bits) Buffers-Available (21bits) Agg-Pool-Ptr-1 (5bits)
Page 769: Use Of Aggregate Control Buffer Pools
High Scale Ethernet MDA Capabilities Figure 48: Aggregate Control Buffer Pools Table Buffers-Available (21bits) Buffers-Available (21bits) Buffers-Available (21bits) Buffers-Available (21bits) Buffers-Available (21bits) Buffers-Available (21bits) OSSG156 Use of Aggregate Control Buffer Pools The aggregate control buffer pools are separated into two sets. The first 16 pools (0 through 15) are used by the provisioned group (group P) port class pools.
Page 770 HSMDA QoS Model Figure 49: Buffer Pool Hierarchy Provisioned Buffers Available Root-Pools Arbitrary Mapping Class-Pools Port 1 Port-Class Pools Port 2 Port-Class Pools Port 10 Port-Class Pools Class-Pools Arbitrary Mapping 1 Million 168 Byte Buffers Divided between ‘System’ Root-Pools and ‘Provisioned’ based on ‘System-Reserve’...
Page 771: Hsmda Buffer Pool Policy
High Scale Ethernet MDA Capabilities HSMDA Buffer Pool Policy HSMDA buffer pool policies contain information the system uses to configure the individual pool sizes and the root pools used by the class pools. The division between total provisioned and total system buffers is based on the system-reserve parameter that defines the percentage of buffers reserved for system use.
Page 772 HSMDA QoS Model Table 59: Default Policy Parameters (Continued) System Reserve Root-Pool 7 Weight: Root-Pool 8 Weight: The class pool parameters are listed in Table Table 60: Class Pool Parameters Class Pools Class-Pool 1 Parent: Root-Pool 1 Percentage: Class-Pool 2 Parent: Root-Pool 1 Percentage:...
Page 773: Port Class Pool Sizing
High Scale Ethernet MDA Capabilities Port Class Pool Sizing The port class pools are sized based on the port’s active bandwidth, provisioned use of the port and the port bandwidth rate modifier percentages defined on the port. For the HSMDA, a port’s active bandwidth is simply the current speed provisioned for the port.
Page 774: Hsmda Queue Congestion And Buffer Utilization Controls
HSMDA QoS Model less, every packet has access to the remaining pool since the maximum size packet requires less than 64 buffers. While this scheme allows for fair access to the buffer pool, some buffers will not be used by the HSMDA. This is considered inconsequential due to the limited number of buffer pools.
Page 775: Maximum Hsmda Queue Depth
High Scale Ethernet MDA Capabilities • The random number is multiplied by the inverse slope value and then added to the slope Start-Buffer to derive the random fill depth which is the number of buffers that need to be full in order for the slope discard threshold to cross the random number. •...
Page 776: Hsmda Slope Policy Mbs Parameter
HSMDA QoS Model Figure 50: High and Low RED Slopes High Slope Slope Discard Probability 100% Queue Depth Utilization OSSG158 HSMDA Slope Policy MBS Parameter Unlike standard queues, HSMDA queues do not have a configured maximum buffer size (MBS) parameter. Instead the high and low RED slopes are used for all queue congestion control functions by the queue.
Page 777 High Scale Ethernet MDA Capabilities • The MBS value is multiplied by the starting-depth percentage to derive the number of bytes at which the slope will start. This value is then converted to buffers by dividing the resulting byte value by the buffer size (168 bytes) and rounding to the nearest integer value.
Page 778 HSMDA QoS Model Table 61: HSMDA Inverse Slope Fixed Point Binary Values (Continued) Inverse Slope Fixed Point Binary Format (23 22 21 20. 2-1 2-2 2-3 2-4) Whole Number Decimal Value Corresponding Binary Value (23 22 21 20) 1010 1011 1100 1101 1110...
Page 779 High Scale Ethernet MDA Capabilities For instance, if the MBS value is defined as 16,800 bytes and the low slope was configures with a starting depth set to 75 percent, a maximum depth set to 100 percent and a maximum discard probability set to 80 percent: •...
Page 780: Hsmda Slope Shutdown Behavior
HSMDA QoS Model HSMDA Slope Shutdown Behavior HSMDA slope policies allow the high or low RED slope to be shutdown. This effectively configures the HSDMA internal slope to have a Start-buffer and end-buffer equal to the buffer value closest to the configured policy MBS value. Packets matching the slope will still be discarded based on the slope, but it will appear that the MBS value is being enforced within the queue.
Page 781: Hsmda Queue Congestion Or Pool Congestion Discard Stats
High Scale Ethernet MDA Capabilities 16,800 bytes (100 buffers) High Slope Start-depth 100% Max-depth 100% Max-probability 100% Shutdown Low Slope Start-depth 90% Max-depth 90% Max-probability 100% No shutdown HSMDA Queue Congestion or Pool Congestion Discard Stats When a packet is discarded, the high priority or low priority packet and octet discard counter is incremented.
Page 782: Egress Queue Cir Based Dot1P Remarking
SAP Ingress and SAP Egress QoS Policies Egress Queue CIR Based Dot1P Remarking The HSMDA adds the capability to perform remarking of one dot1p value within a dot1q or qinq- tagged packet based on the dynamic CIR state of the egress queue at the time the packet is scheduled out the egress port.
Page 783 High Scale Ethernet MDA Capabilities The standard ingress service queues are separated into two types, point-to-point and multipoint. point-to-point queues are used either for VLL services such as Epipe or for unicast traffic within a VPLS, VPRN or IES service. Multipoint queues are used by VPLS, VPRN and IES services for packets that must be replicated by the switch fabric.
Page 784: Sap Ingress And Sap Egress Qos Policies
Subscriber Queuing Differences Another modification is the ability to define egress HSMDA counter override criteria which relies on an egress TCAM lookup based on IP flow criteria match entries. Egress IP flow based HSMDA counter overrides are ignored when applied to a SAP not on an HSMDA. Egress counter overrides are ignored when a SAP is a member of an efficient multicast group.
Page 785: Sap Egress Qos Policy
High Scale Ethernet MDA Capabilities To negate the issue between SAP type and LAG port membership, the config>lag>port-type {standard | hsmda-ports} command has must be executed prior to adding any ports to the LAG. This command allows the type ports that will be added to the LAG to be predefined. Without executing this command, HSMDA ports cannot be added to the LAG and after execution, the LAG may only be populated with HSMDA ports.
Page 786: Hsmda Features
HSMDA Features HSMDA Queue Groups A fundamental concept on an HSMDA is the queue group. Queue groups are not directly managed by the provisioner, they are indirectly assigned when creating SAPs or subscribers on the XMA and MDA. A queue group has eight queue members. The queues within the group are numbered from 1 through 8.
Page 787 High Scale Ethernet MDA Capabilities Scheduling Class Weighted Groups As indicated above, an HSMDA scheduler handles groups of queues based on each queues identifier. All queues numbered 1 are automatically placed in scheduler class 1, queues numbered 2 are placed in scheduler class 2 through queues numbered 8 being placed in scheduler class 8.
Page 788 HSMDA Features Scheduler Maximum Rate A maximum scheduling rate may be defined for the scheduler. The rate is specified in megabits per second and the default rate is max which allows the scheduler to operate without a set limit. When the HSMDA scheduling policy is applied to an egress port, the maximum scheduling rate may be used to define a rate less then the available line rate of the port.
Page 789 High Scale Ethernet MDA Capabilities Table 62: HSMDA Scheduling Policy Default Values (Continued) Command Default group group 1 rate max group 2 rate max scheduling-class scheduling-class 1 rate max scheduling-class 2 rate max scheduling-class 3 rate max scheduling-class 4 rate max scheduling-class 5 rate max scheduling-class 6 rate max scheduling-class 7 rate max...
Page 790 HSMDA Features class-pool 6 root-parent 2 allocation-percent 50.00 class-pool 7 root-parent 2 allocation-percent 40.00 class-pool 8 root-parent 2 allocation-percent 30.00 exit ---------------------------------------------- A:ALA-48>config>qos>hsmda-pool-policy# HSMDA Scheduler Policies HSMDA scheduler policies can be assigned to an egress HSMDA port or as the ingress control scheduler between the HSMDA and the ingress forwarding plane.
Page 791 High Scale Ethernet MDA Capabilities *A:ALA-48>config>qos# HSMDA Slope Policies The following displays details of the default HSMDA slope policy configuration. A:ALA-48>config>qos# -------------------------------------------------- hsmda-slope-policy "default" create description "Default hsmda slope policy." queue-mbs 16800 high-slope start-depth 100.00 max-depth 100.00 max-prob 100.00 no shutdown exit low-slope start-depth 90.00...
Page 792: Hsmda Queue Groups
HSMDA Features Configuring HSMDA Queue Group Overrides When a queue group template is instantiated at the port, queue group queues can be overridden at the instance level using hsmda-queue-overrides. The following display output displays a hsmda-queue-group and overrides example configuration at the port level. *A:Dut-A>config>port>ethernet# /configure port 4/1/1 *A:Dut-A>config>port# info ----------------------------------------------...
Page 793 High Scale Ethernet MDA Capabilities — packet-byte-offset {add add-bytes | subtract sub- bytes} — no packet-byte-offset — queue queue-id [create] — no queue queue-id — mbs {[0 to 2625] kilobytes | [0 to 2688000] bytes | default} — no mbs —...
Page 794 HSMDA Features Quality of Service Guide...
Page 795 High Scale Ethernet MDA Capabilities HSMDA Command Reference Command Hierarchies config — qos — hsmda-pool-policy policy-name [create] — no hsmda-pool-policy policy-name — class-tier — class-pool class-pool-id root-parent root-pool-id allocation-percent percent- of-parent-pool — no class-pool class-pool-id — description description-string — no description —...
Page 796 HSMDA Command Reference — no start-depth — no hsmda-wrr-policy scheduler-policy-name — description description-string — no description — include-queues {1-2 | 1-3} — no include-queues — schedule-using-class {1 | 2 | 3} — no schedule-using-class — class-agg-weight {1 | 2 | 4 | 8} —...
Page 797 High Scale Ethernet MDA Capabilities Default No description is associated with the configuration context. Parameters description-string — A text string describing the entity. Allowed values are any string up to 80 characters long 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 798 HSMDA Command Reference class-tier Syntax class-tier Context config>qos>hsmda-pool-policy Description This class enables the context to configure class pool tier parameters. Within the class-tier context, class pools may be associated with a root pool and are sized as a percentage of the root pool’s size. class-pool Syntax class-pool class-pool-id root-parent root-pool-id allocation-percent percent-of-parent-pool...
Page 799 High Scale Ethernet MDA Capabilities root-parent root-pool-id — Specifies the parent root pool to which the class pool will be associated. All class pool parent associations are output when save config or show config is executed regardless of whether the default value is currently set. The root-parent keyword is required and must precede the root-pool-id parameter.
Page 800 HSMDA Command Reference Description This command defines the buffer allocation weight for a specific root pool. Eight root pools exist and do not need to be created. The allocation-weight parameter is used to specify the weight that will be applied to the pool and is divided by the sum of all root pool weights to derive the pool’s buffer allocation factor.
Page 801 High Scale Ethernet MDA Capabilities Table 64: Pool Weight Values (Continued) Unit: Integer Range root-pool 2 0 — 100 Range root-pool 3 0 — 100 Range root-pool 4 0 — 100 Range root-pool 5 0 — 100 Range root-pool 6 0 —...
Page 802 HSMDA Command Reference HSMDA Scheduler QoS Policy Commands hsmda-scheduler-policy Syntax hsmda-scheduler-policy scheduler-policy-name [create] no hsmda-scheduler-policy scheduler-policy-name Context config>qos Description This command configures HSMDA scheduler policy parameters. HSMDA scheduler policies can be assigned to an egress HSMDA port or as the ingress control scheduler between the HSMDA and the ingress forwarding plane.
Page 803 High Scale Ethernet MDA Capabilities The no form of the command reverts the specified weighted scheduling class group rate limit to the default setting. Parameters group-id — Defines the maximum rate allowed for the scheduling classes mapped to the specified group-id.
Page 804: Scheduling Class Weighted Groups
HSMDA Command Reference scheduling-class class rate rate no scheduling-class class Context config>qos>hsmda-scheduler-policy Description This command configures the behavior of a specific scheduling class on all HSMDA schedulers associated with the policy. The scheduling-class command performs one of two operations, configure a maximum rate for the scheduling class or place the scheduling class into one of the two available weighted scheduling groups.
Page 805 High Scale Ethernet MDA Capabilities The scheduling-class command will also fail using the group keyword when a rate override for the scheduling class exists on an HSMDA scheduler instance associated with the policy. The rate override for the scheduling class indicates the class is directly attached to a strict priority level, conflicting with the policy group keyword trying to place the class in the specified group.
Page 806 HSMDA Command Reference The configured priority level rate limits can be overridden at the egress port or channel using the egress-scheduler-override level priority-level command. When a scheduler instance has an override defined for a priority level, both the rate and cir values are overridden even when one of them is not explicitly expressed in the override command.
Page 807 High Scale Ethernet MDA Capabilities no hsmda-slope-policy policy-name Context config>qos Description This command creates an HSMDA RED slope policy. The policy may be assigned to an ingress or egress HSMDA queue. The policy contains the Maximum Buffer Size (MBS) that will be applied to the queue and the high and low priority RED slope definitions.
Page 808 HSMDA Command Reference Parameters policy-name — Specifies a HSMDA slope policy. Each HSMDA slope policy must be uniquely named within the system. Names of up to 32 ASCII characters are supported with the normal character restrictions. An HSMDA slope policy must be exist prior to applying the policy name to an HSMDA queue.
Page 809 High Scale Ethernet MDA Capabilities The defined percent-of-queue-depth value for the start-depth command is defined as a percentage of the queue-mbs value. The value defined for the start depth must be less than or equal to the current percentage value for max-depth. If the defined value is greater than max-depth, the start-depth command will fail with no change to the current value.
Page 810 HSMDA Command Reference The defined percent-of-queue-depth for max-depth is defined as a percentage of the queue-mbs value. The value defined as the maximum depth must be greater than or equal to the current percentage value for start-depth. If the defined value is less than start-depth, the max-depth command will fail with no change to the current value.
Page 811 High Scale Ethernet MDA Capabilities Context config>qos Description This command creates an HSMDA weighed-round-robin (WRR) scheduling loop policy. The policy may be assigned to an egress HSMDA queue. The no form of the command removes the specified HSMDA WRR policy from the configuration. If the HSMDA WRR policy is currently associated with an HSMDA queue, the command will fail.
Page 812 HSMDA Command Reference 2 — Specifies scheduling class 2 for the HSMDA WRR policy. 3 — Specifies scheduling class 3 for the HSMDA WRR policy. class-agg-weight Syntax class-agg-weight {1 | 2 | 4 | 8} no class-agg-weight Context config>qos>hsmda-wrr-policy config>qos>hsmda-wrr-policy Description This command specifies the aggregate weight within the scheduling class for the HSMDA WRR scheduling loop policy.
Page 813 High Scale Ethernet MDA Capabilities Qos HSMDA Pool Policy =============================================================================== Policy Name Description ------------------------------------------------------------------------------- default Default hsmda Pool policy. =============================================================================== *A:ALA-48>show>qos# *A:Dut-A# show qos hsmda-pool-policy ingPoolPol detail ============================================================================= Qos HSMDA Pool Policy ============================================================================= Policy Name : ingPoolPol ============================================================================= Description : (Not Specified) Sys.
Page 814 HSMDA Command Reference Qos HSMDA Pool Policy ============================================================================= Policy Name : ingPoolPol ============================================================================= Description : (Not Specified) ----------------------------------------------------------------------------- Associations ----------------------------------------------------------------------------- - MDA Ingress: 4/1 ============================================================================= *A:Dut-A# hsmda-pools Syntax hsmda-pools mda mda-id {ingress | egress} [detail] Context show>qos Description This command displays HSMDA pool information. Parameters detail —...
Page 815 High Scale Ethernet MDA Capabilities ------------------------------------------------------------------------------- 117891 117891 117891 117891 117891 117891 117891 117891 117891 117891 117891 117891 117891 117890 117891 117891 =============================================================================== Port Class Pools =============================================================================== Port ID Class ID Size Remaining ------------------------------------------------------------------------------- 117891 117884 117891 117891 117891 117891 117891 117891 117891...
Page 816 HSMDA Command Reference 117891 117891 117891 117886 117891 117891 117891 117891 117891 117891 117891 117891 117891 117891 =============================================================================== *A:Dut-A# *A:Dut-A# show qos hsmda-pools ingress mda 4/1 detail Buffer Pools HSMDA 4/1 Port Allocation Factors Port Act-BW: 10 Gbps Modifier: Actual Factor: 10000 Root Pools Percentage of Total: 89.99 Actual Total Size 943128...
Page 817 High Scale Ethernet MDA Capabilities Class-pool 4 Percentage of Root: 100.00 Size: 117891 Remaining: 117891 Port-class-pool Factor-Size: 117891 Remaining: 117891 Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size:...
Page 818 HSMDA Command Reference Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool Factor-Size: Remaining: Port-class-pool 10 Factor-Size: Remaining: *A:Dut-A# hsmda-scheduler-hierarchy Syntax hsmda-scheduler-hierarchy port port-id [{shapers | shaper shaper-name}] hsmda-scheduler-hierarchy mda mda-id hsmda-scheduler-hierarchy sap sap-id [ingress | egress] hsmda-scheduler-hierarchy subscriber sub-id [ingress | egress] Context show>qos Description...
Page 819 High Scale Ethernet MDA Capabilities sap sap-id — Displays information about the specified SAP ID. Values sap-id null port-id | lag-id dot1q port-id | lag-id:qtag1 qinq port-id | lag-id:qtag1.qtag2 port-id slot/mda/port[.channel] esat-id/slot/port esat keyword 1 to 20 pxc-id.sub-port keyword 1 to 64 sub-port a, b lag-id...
Page 820 HSMDA Command Reference Scheduler Priority 4 Rate: 113963360 Scheduler Class 4 Rate: 113963360 Scheduler Priority 3 Rate: 0 Scheduler Class 3 Rate: 0 Scheduler Priority 2 Rate: 0 Scheduler Class 2 Rate: 0 Scheduler Priority 1 Rate: 0 Scheduler Class 1 Rate: 0 Secondary Shaper secShaper Rate 4999785760...
Page 821 High Scale Ethernet MDA Capabilities Scheduler Priority 8 Rate: 1221455600 Scheduler Class 8 Rate: 1221455600 Scheduler Priority 7 Rate: 1221455600 Scheduler Class 7 Rate: 1221455600 Scheduler Priority 6 Rate: 1221455600 Scheduler Class 6 Rate: 1221455600 Scheduler Priority 5 Rate: 1221539520 Scheduler Class 5 Rate: 1221539520 Scheduler Priority 4...
Page 822 HSMDA Command Reference Scheduler Priority 1 Rate: 1221539520 Scheduler Class 1 Rate: 1221539520 [4/1/1:1] Queue 1 Rate 14982240 *A:Dut-A# *A:Dut-A# show qos hsmda-scheduler-hierarchy sap 4/1/1:1 egress HSMDA Scheduler Policy egrSchedPol Port Bandwidth: 10 Gbps Max Rate : 5000373200 Scheduler Priority 8 Rate: 1221623440 Scheduler Class 8 Rate: 1221623440...
Page 823 High Scale Ethernet MDA Capabilities Scheduler Priority 6 Rate: 1018748800 Scheduler Class 6 Rate: 1018748800 [4/2/1:41] Queue 6Rate 0 Scheduler Priority 5 Rate: 1006536000 Scheduler Class 5 Rate: 1006536000 [4/2/1:41] Queue 5Rate 0 Scheduler Priority 4 Rate: 1002505600 Scheduler Class 4 Rate: 1002505600 [4/2/1:41] Queue 4Rate 0 Scheduler Priority 3...
Page 824 HSMDA Command Reference Group 1 Rate: max No classes assigned to group Group 2 Rate: max No classes assigned to group No Group Class 1 - Rate: max Class 2 - Rate: max Class 3 - Rate: max Class 4 - Rate: max Class 5 - Rate: max Class 6 - Rate: max Class 7 - Rate: max...
Page 825 High Scale Ethernet MDA Capabilities Sample Output *A:Dut-A# show qos hsmda-slope-policy slopePol detail =============================================================================== Qos HSMDA Slope Policy =============================================================================== Policy Name : slopePol =============================================================================== Description : (Not Specified) Provisioned Queue MBS : 168000 ------------------------------------------------------------------------------- High Slope Parameters ------------------------------------------------------------------------------- Start Depth : 100.00 Admin State : Enabled...
Page 826 HSMDA Command Reference Policy ID Queues ------------------------------------------------------------------------------- 1000 1 2 3 4 5 6 7 8 ------------------------------------------------------------------------------- SAP-Egress Associations ------------------------------------------------------------------------------- Policy ID Queues ------------------------------------------------------------------------------- No Association Found. ------------------------------------------------------------------------------- SAP Override Associations ------------------------------------------------------------------------------- SAP ID Direction Queues ------------------------------------------------------------------------------- No Association Found. ------------------------------------------------------------------------------- Sub-Profile Override Associations -------------------------------------------------------------------------------...
Page 827 QoS in MC-MLPPP In This Section This section provides information to configure MC-MLPPP using the command line interface. Topics in this section include: • Overview • Basic Configurations • QoS in MLFR and FRF.12 Fragmentation Overview If the user enables the multiclass option under an MLPPP bundle, the XMA or MDA egress data path provides a queue for each of the 4 classes of MLPPP.
Page 828 Overview Table 66: Default Packet Forwarding Class to MLPPP Class Mapping (Continued) FC ID FC Name Scheduling Priority MLPPP Class 4- MLPPP Class 3- MLPPP Class (Default) class bundle class bundle 2-class bundle Non-Expedited Non-Expedited Non-Expedited Non-Expedited Table 67 shows a different mapping enabled when the user applies one of three predefined egress QoS profiles in the 4-class bundle configuration only.
Page 829: Qos In Mc-Mlppp
QoS in MC-MLPPP Table 68: MLPPP Class Queue Threshold Parameters Class 0 Class 1 Class 2 Class 3 Queue Threshold (in ms @ Available bundle rate) 2-Class Bundle Default Egress QoS Profile 3-Class Bundle Default Egress QoS Profile 4-Class Bundle Default Egress QoS Profile 4-Class Bundle 1000...
Page 830: Overview
Overview Table 69: MLPPP Class Queue Scheduling Parameters (Continued) WRR Parameters Profile 3 <1% Figure 52: MLPPP Class Queue Scheduling Scheme Class0 > 100% Class1 > MIR Strict Priority Class2 Class3 al_0193 All queue threshold and queue scheduling parameters are adjusted to the available bundle rate.
Page 831: Ingress Mlppp Class Reassembly
QoS in MC-MLPPP Ingress MLPPP Class Reassembly For a MLPPP bundle with the multi-class option enabled, there is a default profile for setting the re-assembly timer value for each class. When the predefined MLPPP ingress QoS profile 1 is applied to a 4-class bundle, the values of the timers are modified as shown in Table Table 70: MLPPP Ingress QoS Profile: Reassembly Timers (msec) Class 0...
Page 832: Basic Configurations
Basic Configurations Table 68, or Table 69 for the egress QoS Profile #1. This is regardless of the parameter value the edited profiles have at that point in time. • A maximum of 128 ingress QoS profiles and 128 egress QoS profiles can be created on the system.
Page 833 QoS in MC-MLPPP The following displays the profile configuration examples: A:ALA-12>config>qos# info #------------------------------------------ mlppp-profile-ingress 2 [create] description my-4-class-bundle-ingress-profile class class 0 reassembly-timeout 10 class class 1 reassembly-timeout 100 class class 2 reassembly-timeout 500 class class 3 reassembly-timeout 1000 mlppp-profile-egress 4 [create] description my-4-class-bundle-egress-profile fc be mlppp-class 3 fc l2 mlppp-class 2...
Page 834: Configuring Mc-Mlppp
QoS in MLFR and FRF.12 Fragmentation member 1/1/1.1.4.1 minimum-links 2 Configuring MC-MLPPP Use the following CLI syntax to create an MC-MLPPP: CLI Syntax: config>qos# mlppp-profile-ingress 2 [create] description dmy-4-class-bundle-ingress-profile class class 0 reassembly-timeout 10 class class 1 reassembly-timeout 100 class class 2 reassembly-timeout 500 class class 3 reassembly-timeout 1000...
Page 835 QoS in MC-MLPPP Table 71 Figure 53 provide the details of the class queue threshold parameters. Packets that are marked with high drop precedence, for example, out-of-profile, by the service or network ingress QoS policy will be discarded when any class queue reaches the OOP threshold.
Page 836: Qos In Mlfr And Frf.12 Fragmentation
QoS in MLFR and FRF.12 Fragmentation Figure 54: FR Class Queue Scheduling for an MLFR Bundle Class0 > 100% Class1 > MIR Strict Priority Class2 Class3 al_0195 The minimum information rate, referred to as MIR in Figure 54 and MIR in CLI, applies to Class 1 queues only.
Page 837: Qos In Frf.12 End-To-End Fragmentation
QoS in MC-MLPPP • Changes of parameters in the currently assigned ingress and egress QoS profiles. QoS in FRF.12 End-to-End Fragmentation When end-to-end fragmentation is enabled on an FR SAP, the queuing and scheduling on the XMA or MDA is reusing the existing FR SAP high and low priority queues are show in Figure Figure 55: DLC Egress Channel Queue Scheduling Channel SAP Queue Prioritization on MDA...
Page 838 QoS in MLFR and FRF.12 Fragmentation Quality of Service Guide...
Page 839: Mlppp Command Reference
QoS in MC-MLPPP MLPPP Command Reference Command Hierarchies Configuration Commands config — qos — mlppp-profile-egress profile-id [create] — no mlppp-profile-egress profile-id — class class-id — max-queue-size queue-size — no max-queue-size — mir-value — no — weight weight-value — no weight —...
Page 840: Command Descriptions
MLPPP Command Reference Command Descriptions Configuration Commands MC-MLPPP Commands mlppp-profile-ingress Syntax [no] mlppp-profile-ingress profile-id [create] Context config>qos Description This command creates a profile for the user to configure the ingress QoS parameters of a multiclass MLPPP bundle. A maximum of 128 ingress QoS profiles can be created on the system. The no form of this command deletes the profile.
Page 841 QoS in MC-MLPPP Description This command configures the value of the MLPPP bundle ingress per class reassembly timer for this profile. Parameters timeout-value — Specifies a a reassembly timeout for this policy. Values 1 to 1000 in milliseconds description Syntax description description-string no description Context...
Page 842 MLPPP Command Reference max-queue-size Syntax max-queue-size queue-size no max-queue-size Context config>qos>mlppp-profile-egress>class Description This command configures the maximum queue size for each MLPPP class queue for this profile. Parameters queue-size — Specifies the maximum queue size. Values 1 to 1000 in milliseconds of buffer space Syntax mir mir-value no mir...
Page 843 QoS in MC-MLPPP Description This command configures the mapping of the system forwarding class to the MLPPP classes for this profile. There is a many-to-one relationship between the system forwarding class and an MLPPP class. Parameters fc-name — Specifies the forwarding class name. Values b3, l2, af, l1, h2, ef, h1, nc class-id —...
Page 844 MLPPP Command Reference Quality of Service Guide...
Page 845 Class Fair Hierarchical Policing (CFHP) In This Section This section provides information to configure CFHP QoS policies using the command line interface. Topics in this section include: • Introduction • Parent Policer Priority and Unfair Sensitive Discard Thresholds • CFHP Ingress and Egress Use Cases •...
Page 846 Introduction Below are the capabilities and limitations for CFHP under a multi-service-site: • Support for SAP only (no subscriber support) • Assignment is for port only (not for card) • Supported both in Ingress and Egress • Policer Overrides are not supported under a multi-service-site. *A:Dut-A>config>service>cust>multi-service-site# pwc ------------------------------------------------------------------------------- Present Working Context :...
Page 847: Class Fair Hierarchical Policing (Cfhp)
Class Fair Hierarchical Policing (CFHP) Parent Policer Priority and Unfair Sensitive Discard Thresholds Priority level bandwidth control is managed on the parent policer through the use of progressively higher discard thresholds for each in use priority level. Up to eight priority levels are supported and are individually enabled per parent policer instance based on child policer priority level association.
Page 848: Parent Policer Priority And Unfair Sensitive Discard Thresholds
Parent Policer Priority and Unfair Sensitive Discard Thresholds Figure 56: Policer Bucket Rate and Packet Flow Interaction with Bucket Depth packet Offered packets Current burst level Below MBS, so white tokens go into CIR bucket Current burst level Below CBS, so green tokens go into FIR bucket Current burst level...
Page 849: Cfhp Ingress And Egress Use Cases
Class Fair Hierarchical Policing (CFHP) CFHP Ingress and Egress Use Cases While ingress CFHP seems a natural fit based on how policers are typically used in today’s networks, CFHP may also be used at egress. The reasons for utilizing egress CFHP may be to provide a non-jitter or latency inducing aggregate SLA for multiple ingress flows or simply to provide higher scale in the number of egress aggregate SLAs supported.
Page 850: Egress Cfhp Queuing
Post-CFHP Queuing and Scheduling multicast path to be used. Each table entry maintains a bandwidth counter that is used to monitor the aggregate traffic per multicast path. This can be optimized by enabling IMPM on any forwarding complex which allows the system to redistribute this traffic across the IMPM paths on all forwarding complexes to achieve a more even capacity distribution.
Page 851: Egress Subscriber Cfhp Queuing
When a subscriber packet is mapped to a child policer through the SAP egress QoS policy. The actual egress queue group is derived from the subscriber host identification process within the subscriber management module, otherwise the default queue-group is used. This feature applies to the 7450 ESS only. Quality of Service Guide...
Page 852: Subscriber Destination String Queue Group Identification
When a subscriber is identified, a special destination string may optionally exist for the subscriber that is typically used to identify the subscriber’s destination aggregation node. This feature applies only to the 7450 ESS and 7950 SR. On the subscriber’s egress Ethernet port, the default policer-output-queues and other explicitly created queue groups may be configured to represent a destination node by defining the same destination string on the queue group.
Page 853: Cfhp Policer Control Policy
Class Fair Hierarchical Policing (CFHP) CFHP Policer Control Policy Provisioning CFHP entails creating policer control policies (policer-control-policy), applying a policer control policy to the ingress or egress context of a SAP or to the ingress or egress context of a subscriber profile (sub-profile) much the same way scheduler policies (scheduler-policy) are applied.
Page 854: Tier 1 And Tier 2 Explicit Arbiters
CFHP Policer Control Policy Tier 1 and Tier 2 Explicit Arbiters Other arbiters may be explicitly created in the policy for the purpose of creating an arbitrary bandwidth distribution hierarchy. The explicitly created arbiters must be defined within tier 1 or tier 2 on the policy. Tier 1 arbiters must always be parented by the root arbiter and thus becomes a child of the root arbiter.
Page 855: Cfhp Child Policer Definition And Creation
Class Fair Hierarchical Policing (CFHP) • Traffic exceeding the operational PIR of the child policer is reprofiled to be exceed profile, where the operational PIR is determined by the H-pol algorithm from the configuration of the policer parent and the associated arbiters (root and/or intermediate).
Page 856: Policer Enabled Sap Qos Policy Applicability
Policing is supported only on Ethernet SAPs or Ethernet based subscribers. Policing is also only supported on FlexPath2 based systems or IOMs with the exception of CCAG and HSMDA SAPs or subscribers. This feature applies to the 7450 ESS and 7750 SR only. Child Policer Parent Association Each policer configured within a SAP ingress or SAP egress QoS policy may be configured to be child policer by defining a parent arbiter association using the parent command.
Page 857: Profile Capped Policers
Class Fair Hierarchical Policing (CFHP) Profile Capped Policers Profile capped mode has been introduced to enforce an overall in-profile burst limit to the CIR bucket for ingress undefined, ingress explicit in-profile, egress soft-in-profile and egress explicit in-profile packets. The default behavior when profile-capped mode is not enabled is to ignore the CIR output state when an explicit in-profile packet is handled by an ingress or egress policer.
Page 858 Profile Capped Policers Table 74: Effect of Profile-Capped Mode on CIR Output CIR Setting Initial Profile State Normal Mode Capped Notes Profile Mode CIR=0 Ingress Undefined Always Yellow Always Yellow CIR = 0 forces all packets to be yellow when profile-capped Ingress Profile In Always Green Always Yellow...
Page 859: Policer Interaction With Initial Profile, Discard Eligibility, And Ingress Priority
Class Fair Hierarchical Policing (CFHP) Table 74: Effect of Profile-Capped Mode on CIR Output (Continued) CIR Setting Initial Profile State Normal Mode Capped Notes Profile Mode Egress Soft-In- Green below Green below Profile 2xCBS Yellow at or Yellow at or above CBS above 2xCBS Egress Soft-Out-Of-...
Page 860 Policer Interaction with Initial Profile, Discard Eligibility, and Ingress Priority Priority high and low are used in the child policer’s PIR leaky bucket to choose one of two discard thresholds (threshold-be-low and threshold-be-high) which are derived from the child policer’s mbs and high-priority-only parameters. The high threshold is directly generated by the mbs value.
Page 861: Ingress 'Undefined' Initial Profile
Class Fair Hierarchical Policing (CFHP) Ingress ‘Undefined’ Initial Profile Access ingress packets have one of three initial profile states prior to processing by the policer: • Undefined • profile in • profile out The SAP ingress QoS policy classification rules map each packet to either a forwarding class or a sub-class within a forwarding class.
Page 862: Ingress Explicitly 'In-Profile' State Packet Handling With Profile-Capped Mode
Policer Interaction with Initial Profile, Discard Eligibility, and Ingress Priority Explicit in-profile packets do not automatically use the high priority threshold (‘threshold-be- high’) within the child policer’s PIR bucket. If preferential burst tolerance is desired for explicit in-profile packets, the packets should also be classified as priority high. Ingress Explicitly ‘In-Profile’...
Page 863: Preserving Out Of Profile State At Egress Policer
Class Fair Hierarchical Policing (CFHP) Preserving Out of Profile State at Egress Policer Traffic sent through an egress policer with a non zero CIR will be reprofiled by default based on the CIR threshold of the egress policer. To accommodate designs where traffic is set to be out of profile at ingress, and the out of profile state is required to be maintained by an egress policer, the parameter profile-out-preserve can be configured under the egress policer.
Page 864: Forwarding Traffic Exceeding Pir In Egress Policers
Policer Interaction with Initial Profile, Discard Eligibility, and Ingress Priority Third, when the policer has a CIR = 0 rate (the default rate), all profile capped packets are treated as out-of-profile independent of the initial profile state. Forwarding Traffic Exceeding PIR in Egress Policers An egress policer can be configured to forward traffic which exceeds its oper PIR instead of dropping it.
Page 865 Class Fair Hierarchical Policing (CFHP) For ingress policing, each offered packet has a priority and a profile state. The priority is used by the policer to choose either the high or low priority PIR threshold-be. Every offered packet is either priority high or priority low. The offered profile state defines how a packet will interact with the policers CIR bucket state.
Page 866 Policer Interaction with Initial Profile, Discard Eligibility, and Ingress Priority resources exist, the change in the mode will fail without any change to the existing counters currently applied to the existing policers. If the QoS policy is being applied to a SAP or subscriber or multi-service site context and insufficient counter resources exist to implement the configured modes for the policers within the policy, the QoS policy will not be applied.
Page 867: Egress Child Policer Stat-Mode
Class Fair Hierarchical Policing (CFHP) Make sure to use the correct stat-mode if the policer’s CIR is explicitly not set or is set to 0. The no-cir version of the stat-mode must be used and when the CIR has a non-zero value. Also when overriding the policer’s cir mode, make sure you override the stat-mode instance (cir override can be performed using snmp access).
Page 868 Profile Preferred Mode Root Policers Egress supported stat-modes are: • no-stats • minimal - default • offered-profile-no-cir • offered-profile-cir • offered-total-cir • offered-limited-capped-cir • offered-profile-capped-cir • offered-total-cir-exceed Details of the output showing the stat-modes for ingress and egress child policers can be found in the Class Fair Hierarchical Policing for SAPs section of the SR OS Advanced Configuration Guide.
Page 869 Class Fair Hierarchical Policing (CFHP) The net result is that explicit in-profile packets stay blue up to the high CBS threshold, undefined profile packets would stay blue up to the low CBS threshold (1x CBS) and explicit out-of-profile packets would always be orange due to a 0 CBS threshold. Orange packets would be discarded by the parent policer within the child policer’s priority level before the blue packets, preferring blue packets over orange once the discard-orange threshold is crossed.
Page 870: Profile Preferred Mode Root Policers
Profile Preferred Mode Root Policers Quality of Service Guide...
Page 871: Class Fair Hierarchical Policing (Cfhp) Policy Command Reference
Class Fair Hierarchical Policing (CFHP) Class Fair Hierarchical Policing (CFHP) Policy Command Reference Command Hierarchies Class Fair Hierarchical Policing Commands config — qos — policer-control-policy policy-name [create] — no policer-control-policy — description description string — no description — root — max-rate {kilobits-per-second | max} —...
Page 872: Command Descriptions
Class Fair Hierarchical Policing (CFHP) Policy Command Reference Command Descriptions Configuration Commands Generic Commands policer-control-policy Syntax policer-control-policy policy-name [create] no policer-control-policy Context config>qos Description This command is used to create, delete, or modify policer control policies. The policer-control-policy controls the aggregate bandwidth available to a set of child policers. Once created, the policy can be applied to ingress or egress SAPs.
Page 873 SAP, or subscriber instance for the 7450 ESS and 7750 SR, or multi-service site instance for the 7950 XRS. Packets that are not discarded by the child policers associated with the SAP or subscriber or multi-service site instances are evaluated against the parent policer’s PIR leaky bucket.
Page 874 Class Fair Hierarchical Policing (CFHP) Policy Command Reference For each packet, the bucket is first decremented by the correct amount based on the decrement rate to derive the current bucket depth. The current depth is then compared to one of two discard thresholds associated with the packet.
Page 875 Class Fair Hierarchical Policing (CFHP) priority-mbs-thresholds Syntax priority-mbs-thresholds Context config>qos>policer-control-policy>root Description The priority-mbs-thresholds command contains the root arbiter parent policer’s min-thresh- separation command and each priority level’s mbs-contribution command that is used to internally derive each priority level’s shared-portion and fair-portion values. The system uses each priority level’s shared-portion and fair-portion value to calculate each priority level’s discard-unfair and discard-all MBS thresholds that enforce priority sensitive rate-based discards within the root arbiter’s parent policer.
Page 876 Class Fair Hierarchical Policing (CFHP) Policy Command Reference • When a parent policer instance's priority level has two or more child policers associated, the fair-portion will be equal to the maximum of the following: → min-thresh-separation value → The priority level’s mbs-contribution value less min-thresh-separation value When the mbs-contribution command’s optional fixed keyword is defined for a priority level within the policy, the system will treat the defined mbs-contribution value as an explicit definition of the priority level’s MBS.
Page 877 Setting this value has no effect on parent policer instances where the min-thresh-separation value has been overridden. Values 0 to 4194304 or default (applies to the 7450 ESS) 0 to 16777216 or default (applies to the 7750 SR or 7950 XRS) Default 1536 [bytes | kilobytes] —...
Page 878 The mbs-contribution command is used to configure the policy-based burst tolerance for a parent policer instance created when the policy is applied to a SAP, or a subscriber context for the 7450 ESS and 7750 SR, or a 7950 XRS multi-service site. The system uses the parent policer’s min-thresh- separation value, the priority level’s mbs-contribution value and the number of child policers...
Page 879 Class Fair Hierarchical Policing (CFHP) of burst tolerance before marking its packets as unfair, the current parent policer bucket depth may at times rise above the discard-unfair threshold. The mbs-contribution value provides a means to define how much separation is provided between the priority level’s discard-unfair and discard-all threshold to allow the parent policer to absorb some amount of FIR burst before reaching the priority’s discard- all threshold.
Page 880 The defined mbs-contribution value may be overridden on a subscriber sla-profile for the 7450 ESS and 7750 SR, or on a multi-service site for the 7950 XRS, or on a SAP instance, but the fixed nature of the contribution cannot be overridden.
Page 881 Setting this value has no effect on parent policer instances where the priority level’s mbs- contribution value has been overridden. Values 0 to 4194304 or default (applies to the 7450 ESS) 0 to 16777216 or default (applies to the 7750 SR and 7950 XRS) Default 8 kilobytes bytes | kilobytes: —...
Page 882 Class Fair Hierarchical Policing (CFHP) Policy Command Reference Description This command is used to create an arbiter within the context of tier 1 or tier 2. An arbiter is a child policer bandwidth control object that manages the throughput of a set of child policers. An arbiter allows child policers or other arbiters to parent to one of eight strict levels.
Page 883 Class Fair Hierarchical Policing (CFHP) Default None. Parameters description-string — This parameter defines the ASCII description string for the tiered arbiter. If the string contains spaces, it must be placed within beginning and ending double quotation marks. Beginning and ending quotation marks are not considered part of the description string.
Page 884 Class Fair Hierarchical Policing (CFHP) Policy Command Reference Description This command is used to define from where the tiered arbiter receives bandwidth. Both tier 1 and tier 2 arbiters default to parenting to the root arbiter. Tier 2 arbiters may be modified to parent to a tier 1 arbiter.
Page 885: In This Chapter
Frequently Used QoS Terms In This Chapter This chapter provides definitions for frequently used QoS terminology. The following terms are used in router Hierarchical QoS to describe the operation and maintenance of a virtual scheduler hierarchy and are presented for reference purposes: •...
Page 886 Above CIR Distribution Above CIR Distribution ‘Above CIR’ distribution is the second phase of bandwidth allocation between a parent scheduler and its child queues and child schedulers. The bandwidth that is available to the parent scheduler after the ‘within CIR’ distribution is distributed among the child members using each child’s level (to define strict priority for the above CIR distribution), Weight (the ratio at a given level with several children) and the child’s rate value.
Page 887: Frequently Used Qos Terms
Frequently Used QoS Terms The CIR rate for ingress queues controls the in-profile and out-of-profile policing and ultimately egress in-profile and out-of-profile marking. Queue CIR rates also define the hardware fairness threshold at which the queue is no longer prioritized over other queues.
Page 888: Above Cir Distribution
Child Child Child is a logical state of a queue or scheduler that has been configured with a valid parent scheduler association. The child/parent association is used to build the hierarchy among the queues and schedulers. Level The level parameter defines the strict priority level for a child queue or scheduler with regards to bandwidth allocation during the above CIR distribution phase on the child’s parent scheduler.
Page 889 Frequently Used QoS Terms Offered Load Offered load is evaluated per child in the scheduler hierarchy. The offered load is the amount of bandwidth a child queue or scheduler can use to accommodate the data passing through the child. It is separated into two portions; within CIR and above CIR. Within CIR offered load is the portion of bandwidth required to meet the child’s CIR value.
Page 890: Available Bandwidth
Queue Queue A queue is where packets that will be forwarded are buffered before scheduling. Packets are not actually forwarded through the schedulers; they are forwarded from the queues directly to ingress or egress interfaces. The association between the queue and the virtual schedulers is intended to accomplish bandwidth allocation to the queue.
Page 891: Level
Frequently Used QoS Terms Scheduler Policy A scheduler policy represents a particular grouping of virtual schedulers that are defined in specific scheduler tiers. The tiers and internal parent associations between the schedulers establish the hierarchy among the virtual schedulers. A scheduler policy can be applied to either a multi-service site or to a service Service Access Point (SAP).
Page 892: Cir Level
Within CIR Distribution Within CIR Distribution Within the CIR distribution process is the initial phase of bandwidth allocation between a parent scheduler and its child queues and child schedulers. The bandwidth that is available to the parent scheduler is distributed first among the child members using each child’s CIR level (to define a strict priority for the CIR distribution), CIR weight (the ratio at a given CIR level with several children), and the child’s CIR value.
Page 893: Rate
Standards and Protocol Support Note: The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. ANCP/L2CP draft-ietf-ancp-protocol-02, Protocol for Access Node Control Mechanism in Broadband Networks RFC 5851, Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks AF-ILMI-0065.000, Integrated Local Management Interface (ILMI) Version 4.0...
Page 894 Standards and Protocol Support draft-ietf-idr-bgp-gr-notification-01, Notification Message support for BGP Graceful Restart draft-ietf-idr-error-handling-03, Revised Error Handling for BGP UPDATE Messages RFC 1772, Application of the Border Gateway Protocol in the Internet RFC 1997, BGP Communities Attribute RFC 2385, Protection of BGP Sessions via the TCP MD5 Signature Option RFC 2439, BGP Route Flap Damping RFC 2545, Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing RFC 2858, Multiprotocol Extensions for BGP-4...
Page 895 Standards and Protocol Support RFC 5287, Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks Ethernet IEEE 802.1AB, Station and Media Access Control Connectivity Discovery IEEE 802.1ad, Provider Bridges IEEE 802.1ag, Connectivity Fault Management IEEE 802.1ah, Provider Backbone Bridges IEEE 802.1ak, Multiple Registration Protocol IEEE 802.1aq, Shortest Path Bridging IEEE 802.1ax, Link Aggregation...
Page 896: Frame Relay
Standards and Protocol Support draft-snr-bess-evpn-proxy-arp-nd-00, Proxy-ARP/ND function in EVPN networks RFC 7432, BGP MPLS-Based Ethernet VPN RFC 7623, Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN) Frame Relay ANSI T1.617 Annex D, DSS1 - Signalling Specification For Frame Relay Bearer Service FRF.1.2, PVC User-to-Network Interface (UNI) Implementation Agreement FRF.12, Frame Relay Fragmentation Implementation Agreement FRF.16.1, Multilink Frame Relay UNI/NNI Implementation Agreement...
Page 897 Standards and Protocol Support RFC 2349, TFTP Timeout Interval and Transfer Size Options RFC 2428, FTP Extensions for IPv6 and NATs RFC 2865, Remote Authentication Dial In User Service (RADIUS) RFC 2866, RADIUS Accounting RFC 2867, RADIUS Accounting Modifications for Tunnel Protocol Support RFC 2868, RADIUS Attributes for Tunnel Protocol Support RFC 3046, DHCP Relay Agent Information Option (Option 82) RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Page 898 Standards and Protocol Support RFC 3590, Source Address Selection for the Multicast Listener Discovery (MLD) Protocol RFC 3618, Multicast Source Discovery Protocol (MSDP) RFC 3810, Multicast Listener Discovery Version 2 (MLDv2) for IPv6 RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches RFC 4601, Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification...
Page 899 Standards and Protocol Support RFC 2401, Security Architecture for Internet Protocol RFC 3021, Using 31-Bit Prefixes on IPv4 Point-to-Point Links IP — Version 6 RFC 2460, Internet Protocol, Version 6 (IPv6) Specification RFC 2464, Transmission of IPv6 Packets over Ethernet Networks RFC 2529, Transmission of IPv6 over IPv4 Domains without Explicit Tunnels RFC 3587, IPv6 Global Unicast Address Format RFC 3633, IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6...
Page 900 Standards and Protocol Support RFC 3706, A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) Peers RFC 3947, Negotiation of NAT-Traversal in the IKE RFC 3948, UDP Encapsulation of IPsec ESP Packets RFC 4210, Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP) RFC 4211, Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)
Page 901 Standards and Protocol Support RFC 5308, Routing IPv6 with IS-IS RFC 5309, Point-to-Point Operation over LAN in Link State Routing Protocols RFC 5310, IS-IS Generic Cryptographic Authentication RFC 6213, IS-IS BFD-Enabled TLV RFC 6232, Purge Originator Identification TLV for IS-IS RFC 6233, IS-IS Registry Extension for Purges RFC 6329, IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging Management...
Page 902 Standards and Protocol Support RFC 2494, Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type RFC 2514, Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management RFC 2515, Definitions of Managed Objects for ATM Management RFC 2571, An Architecture for Describing SNMP Management Frameworks RFC 2572, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) RFC 2573, SNMP Applications...
Page 903 Standards and Protocol Support RFC 3877, Alarm Management Information Base (MIB) RFC 3895, Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types RFC 3896, Definitions of Managed Objects for the DS3/E3 Interface Type RFC 4001, Textual Conventions for Internet Network Addresses RFC 4022, Management Information Base for the Transmission Control Protocol (TCP) RFC 4113, Management Information Base for the User Datagram Protocol (UDP) RFC 4220, Traffic Engineering Link Management Information Base...
Page 904 Standards and Protocol Support RFC 5332, MPLS Multicast Encapsulations RFC 6790, The Use of Entropy Labels in MPLS Forwarding MPLS — GMPLS draft-ietf-ccamp-rsvp-te-srlg-collect-04, RSVP-TE Extensions for Collecting SRLG Information RFC 3471, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions RFC 4204, Link Management Protocol (LMP) RFC 4208, Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface...
Page 905 Standards and Protocol Support MPLS — MPLS-TP RFC 5586, MPLS Generic Associated Channel RFC 5921, A Framework for MPLS in Transport Networks RFC 5960, MPLS Transport Profile Data Plane Architecture RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers RFC 6378, MPLS Transport Profile (MPLS-TP) Linear Protection RFC 6426, MPLS On-Demand Connectivity and Route Tracing RFC 6427, MPLS Fault Management Operations, Administration, and Maintenance (OAM) RFC 6428, Proactive Connectivity Verification, Continuity Check and Remote Defect...
Page 906 Standards and Protocol Support RFC 4875, Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs) RFC 4950, ICMP Extensions for Multiprotocol Label Switching RFC 5151, Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions RFC 5712, MPLS Traffic Engineering Soft Preemption RFC 5817, Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering...
Page 907 Standards and Protocol Support RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/ MPLS IP Virtual Private Networks (VPNs) RFC 4577, OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) RFC 4970, Extensions to OSPF for Advertising Optional Router Capabilities RFC 5185, OSPF Multi-Area Adjacency RFC 5187, OSPFv3 Graceful Restart (Helper Mode)
Page 908 Standards and Protocol Support RFC 2153, PPP Vendor Extensions RFC 2516, A Method for Transmitting PPP Over Ethernet (PPPoE) RFC 2615, PPP over SONET/SDH RFC 2661, Layer Two Tunneling Protocol "L2TP" RFC 2686, The Multi-Class Extension to Multi-Link PPP RFC 2878, PPP Bridging Control Protocol (BCP) RFC 4951, Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover"...
Page 909: Quality Of Service
Standards and Protocol Support RFC 6575, Address Resolution Protocol (ARP) Mediation for IP Interworking of Layer 2 VPNs RFC 6718, Pseudowire Redundancy RFC 6829, Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6 RFC 6870, Pseudowire Preferential Forwarding Status bit RFC 7023, MPLS and Ethernet Operations, Administration, and Maintenance (OAM) Interworking RFC 7267, Dynamic Placement of Multi-Segment Pseudowires...
Page 910 Standards and Protocol Support ITU-T G.813, Timing characteristics of SDH equipment slave clocks (SEC), issued 03/2003 ITU-T G.8261, Timing and synchronization aspects in packet networks, issued 04/2008 ITU-T G.8262, Timing characteristics of synchronous Ethernet equipment slave clock (EEC), issued 08/2007 ITU-T G.8264, Distribution of timing information through packet networks, issued 10/2008 ITU-T G.8265.1, Precision time protocol telecom profile for frequency synchronization, issued 10/2010...
Page 911 Customer Documentation and Product Support Customer Documentation http://documentation.alcatel-lucent.com Technical Support http://support.alcatel-lucent.com Documentation Feedback documentation.feedback@alcatel-lucent.com...

This manual is also suitable for:

7950 7750

Alcatel-Lucent 7450 Quality Of Service Manual

Getting Started

Qos Policies

Network Qos Policies

Network Queue Qos Policies

Service Egress and Ingress Qos Policies

Queue Sharing and Redirection

Qos Scheduler Policies

Slope Qos Policies

Shared-Queue Qos Policies

Advanced Qos Policies

Qos ATM Traffic Descriptor Profiles

Named Pools

High Scale Ethernet MDA Capabilities

Quick Links

Related Manuals for Alcatel-Lucent 7450

Summary of Contents for Alcatel-Lucent 7450