FP and Port Queue Groups
This chapter provides information about FP and port queue groups.
Topics in this chapter include:
Applicability
This chapter is applicable to the 7950 XRS-16c/20, 7750 SR-7/12, 7750 SR-a4/8, 7750 SR-c4/12, and 7450 ESS-6/6v/7/12 platforms and assumes only FP2- and higher-based line cards are used.
Port queue groups can be configured on FP1 line cards but not all functions described in this chapter are supported on FP1 line cards. FP queue groups are not supported on FP1 line cards because FP queue groups rely on hardware policing.
The configuration was tested on Release 13.0.R7. There are no other specific prerequisites for this configuration.
Overview
Queue groups provide flexible QoS control beyond that available by default for SAPs and network interfaces.
Many applications require detailed QoS control for SAPs, with aggregated QoS control across the core on network interfaces. Queue groups allow the reverse, specifically aggregated QoS control for multiple SAPs and per-network interface QoS control. This is summarized in Default QoS and Queue Group Comparison .
Default |
Queue group |
|
|---|---|---|
SAPs |
|
|
Network interfaces |
|
|
Queue groups were introduced in SR OS Release 7 as a mechanism of grouping a set of queues and enhanced in subsequent Releases. Release 10 added the ability to configure policers within queue groups and introduced a more flexible configuration where the queue group template could be applied multiple times with different instances. The term queue groups was retained even though they can now contain queues, policers, or both. This chapter describes this new configuration.
Queue groups can be used for other applications than those listed in Default QoS and Queue Group Comparison ; for example:
Pseudowire (PW) QoS
Providing QoS control for spoke SDPs in the various pipe services, different types of VPLS services, and associated IES/VPRN interfaces (see chapter Pseudowire QoS ).
Carrier Supporting Carrier (CSC) services
Providing QoS control for CSC network interfaces in VPRN services.
Ingress QoS control on VPRN network interfaces
Providing for ingress QoS control of unicast traffic into a VPRN over automatically created or manually created bindings in a VPRN service.
Network egress QoS
Providing queue rates in kbps instead of the percentage of the port rate, and queue CBS/MBS in kbytes instead of a fractional percentage of the pool size.
When egress queue groups are used for SAPs, the groups provide a similar functionality to multi-service sites in that both can provide an overall rate for a set of SAPs. However, multi-service sites also provide per-SAP QoS control, whereas the queue groups do not.
Queue groups are not applicable to subscriber management except when egress policing is used.
The queue groups described in this chapter are different from those that are configured when using a high-scale Ethernet MDA (HS-MDAv2).
Configuration
Following the description of the overall configuration of queue groups, their configuration is illustrated using examples on a SAP, a network interface, and with egress subscriber policing.
The steps required to configure a queue group are summarized as follows:
Create a queue group template:
Ingress or egress
Apply an instance of the queue group template to:
FP ingress
Access or network
Ethernet egress port
Access or network
Redirect traffic to a policer or queue in the FP or port queue group instance per forwarding class (FC) within a:
SAP ingress or egress QoS policy
Network QoS policy for both ingress and egress
Consider post-egress policer queuing
Creating Queue Group Templates
Queue group templates are configured separately for ingress and egress; an ingress queue group template with the same name as an egress queue group template is a different object.
Ingress queue group templates can contain policers or queues, but not both.
Egress queue group templates can contain policers or queues, or both; queue 1 is created by default and cannot be deleted. A forwarding class (FC) can also be configured to determine the queue mapping of the FC for forwarded SAP egress post-policer traffic.
To summarize the use of policers with respect to queue groups:
Ingress FP queue groups can only use policers.
Port egress access queue groups cannot use policers.
Network ingress and egress applications can only use policers in a queue group.
The configuration of an ingress and egress queue group template is as follows:
configure
qos
queue-group-templates
ingress
queue-group <queue-group-name> [create]
description <description-string>
policer <policer-id> [create]
queue <queue-id> [multipoint] [<queue-type>]
[<queue-mode>] [create]
egress
queue-group <queue-group-name> [create]
description <description-string>
fc <fc-name> [create]
queue <queue-id>
policer <policer-id> [create]
queue <queue-id> [<queue-type>] [create]
The configuration of the policer and queue is similar to the configuration in a SAP ingress and egress QoS policy. However, the SAP ingress QoS policy allows the configuration of a percent-rate and the SAP egress QoS policy allows the configuration of an avg-frame-overhead, neither of which is available in a queue group template. An ingress queue group template supports the creation of up to 32 queues and 32 policers, while an egress queue group template supports the creation of up to 8 queues and 8 policers.
Because an egress queue group template uses kbps for the CIR/PIR rates and bytes/kbytes for the CBS/MBS, unlike a network-queue QoS policy, a network egress interface can use them when an egress queue group template is applied.
The system instantiates the following queue group templates by default. Queue Group Templates - Egress shows the ingress queue group templates:
Group name |
Description |
|---|---|
_tmnx_nat_ing_q_grp _tmnx_nat_ing_q_grp_v2 _tmnx_lns_esm_ing_q_grp |
NAT/LNS Ingress Queue Group Template NAT/LNS Ingress Queue Group Template for ISAv2 LNS ESM Ingress Queue Group Template |
Queue Group Templates - Egress shows the egress queue group templates:
Group name |
Description |
|---|---|
_tmnx_nat_egr_q_grp policer-output-queues _tmnx_nat_egr_q_grp_v2 _tmnx_lns_esm_egr_q_grp |
NAT/LNS Egress Queue Group Template Default egress policer output queues NAT/LNS Egress Queue Group Template for ISAv2 LNS ESM Egress Queue Group Template |
This chapter will only discuss the policer-output-queues queue group from the preceding table, an instance of which is created on all egress access and hybrid ports, to be used for egress policed traffic.
Applying Queue Group Templates
Ingress
An ingress queue group template containing only policers can be applied to an FP ingress. When applied, an instance identifier must be specified, which represents the instantiated instance of the related queue group template.
If an attempt is made to configure a queue group template containing queues for an FP ingress, the following error message appears:
*A:PE-1>config# card 5 fp 1 ingress access queue-group "qg2" instance 1 create
MINOR: CHMGR #1164 Cannot attach a Queue Group containing queues
Because 7750 SR-a4/8 platforms do not support SAP or network hardware policers, FP ingress queue groups are not supported on those platforms.
Queue group templates containing only queues can be applied to port ingress. However, only one such queue group can be applied per ingress port.
An ingress template can be applied to an FP ingress as either an ingress access queue group or an ingress network queue group, or both. In each case:
An accounting policy can be applied.
Statistics collection can be enabled.
A description can be configured.
A policer control policy can be applied, containing parent arbiters for the queue group policers, and its parameters can be overridden.
Policer parameters configured within the queue group template can also be overridden.
When the queue group applies to a tunnel object that can move between different network interfaces, and consequently different network ingress FPs (for example, PW QoS), a network ingress queue group instance must be applied to each FP ingress that could be used.
The configuration of ingress queue group templates for ingress FPs is as follows:
configure
card <slot-number>
fp [<fp-number>]
ingress
access
queue-group <queue-group-name>
instance <[1..65535]> [create]
accounting-policy <acct-policy-id>
collect-stats
description <description-string>
policer-control-override [create]
max-rate {<rate> | max}
priority-mbs-thresholds
min-thresh-separation <size> [bytes | kilobytes]
priority <level>
mbs-contribution <size> [bytes | kilobytes]
policer-control-policy
<policer-control-policy-name>
policer-override
policer <policer-id> [create]
network
queue-group <queue-group-name>
instance <[1..65535]> [create]
accounting-policy <acct-policy-id>
collect-stats
description <description-string>
policer-control-override [create]
max-rate {<rate> | max}
priority-mbs-thresholds
min-thresh-separation <size> [bytes | kilobytes]
priority <level>
mbs-contribution <size> [bytes | kilobytes]
policer-control-policy
<policer-control-policy-name>
policer-override
policer <policer-id> [create]
Configure FP ingress access and network queue group instances consistently across FPs relating to a LAG.
A single ingress template containing only queues can also be applied to an Ethernet port ingress, which can be used only for access ingress:
An accounting policy can be applied.
Statistics collection can be enabled.
A description can be configured.
Queue parameters configured within the queue group template can be overridden.
A scheduler policy can be applied containing parent schedulers for the queue group queues.
The configuration of an ingress queue group template for an ingress port is as follows:
configure
port <port-id>
ethernet
access
ingress
queue-group <queue-group-name> [create]
accounting-policy <acct-policy-id>
collect-stats
description <description-string>
queue-overrides
queue <queue-id> [create]
scheduler-policy <scheduler-policy-name>
Egress
An egress queue group template containing policers or queues, or both, can be applied to an Ethernet port network egress. Only queue group templates containing queues (not policers) can be applied to an Ethernet port access egress. When applied, an instance identifier can be specified, which represents the instantiated instance of the related queue group template; the default being 1.
If an attempt is made to configure a queue group template containing policers for an Ethernet port access egress, the following error message appears:
*A:PE-1# configure port 5/1/5 ethernet access egress queue-group "qg1" instance 1 create
MINOR: CLI Could not create/change "qg1".
MINOR: PMGR #1324 Cannot attach a Queue Group containing policers
An egress template can be applied as either an egress access queue group or an egress network queue group, or both. In each case:
An accounting policy can be applied.
Statistics collection can be enabled.
A description can be configured.
Queue parameters configured within the queue group template can be overridden.
A scheduler policy can be applied containing parent schedulers for the queue group queues.
When applied to the Ethernet access egress, a host-match can be configured, which is used to select a queue group for subscriber egress policed traffic; see later in this chapter for details.
When applied to the Ethernet network egress, a policer control policy can be applied, which contains parent arbiters for the queue group policers.
When the queue group applies to a tunnel object that can move between different network interfaces, and consequently different network egress ports (for example, PW QoS), a network egress queue group instance must be applied to each network egress port that could be used.
The configuration of egress queue group templates for egress ports is as follows:
configure
port <port-id>
ethernet
access
egress
queue-group <queue-group-name> [create]
[instance <instance-id>]
accounting-policy <acct-policy-id>
agg-rate
limit-unused-bandwidth
queue-frame-based-accounting
rate <kilobits-per-second>
collect-stats
description <description-string>
host-match dest <destination-string> [create]
queue-overrides
queue <queue-id> [create]
scheduler-policy <scheduler-policy-name>
network
queue-group <queue-group-name> [create]
[instance <instance-id>]
accounting-policy <acct-policy-id>
agg-rate
limit-unused-bandwidth
queue-frame-based-accounting
rate <kilobits-per-second>
collect-stats
description <description-string>
policer-control-policy
<policer-control-policy-name>
queue-overrides
queue <queue-id> [create]
scheduler-policy <scheduler-policy-name>
When port egress queue groups are used with a LAG, the system enforces a consistent configuration between the ports (based on only the configuration of the primary LAG port).
Redirecting Traffic to a Queue Group Queue or Policer
There are multiple ways to redirect traffic to a queue group queue or policer. The redirection is always on a per-FC basis so that different FCs within the same policy can use a mix of a local SAP policer, a local SAP or network queue, or a queue group policer or queue (where applicable).
Redirection to a queue group queue or policer is not supported for subscribers; attempting to do so will display the following errors:
*A:PE-1>config>qos>sap-ingress# fc "af" policer 1 fp-redirect-group
MINOR: QOS #1489 Cannot assign a queue-group because SLA profile references to this policy exist
*A:PE-1>config>qos>sap-egress# fc af policer 1 port-redirect-group-queue
MINOR: QOS #1628 Cannot assign a queue-group because SLA profile references to this policy exist
*A:PE-1>config>qos>sap-egress# fc af queue 1 port-redirect-group-queue
MINOR: QOS #1628 Cannot assign a queue-group because SLA profile references to this policy exist
*A:PE-1>config>subscr-mgmt>sla-prof>ingress# qos 40
MINOR: SUBMGR #1110 Cannot assign Qos Policy, QOS Plcy contains queue-group references
*A:PE-1>config>subscr-mgmt>sla-prof>egress# qos 40
MINOR: SUBMGR #1110 Cannot assign Qos Policy, QOS Plcy contains queue-group references
SAP Ingress Redirection
Traffic can be redirected per FC to a policer in an FP ingress access queue group, using the fp-redirect-group parameter in the SAP ingress QoS policy, as follows:
configure
qos
sap-ingress <policy-id> [create]
fc <fc-name> [create]
policer <policer-id> fp-redirect-group
The policer-id is referencing a policer in the FP ingress queue group.
The queue group name and instance to be used is not yet configured, allowing this QoS policy to be applied to objects using different FP ingress queue group instances, which results in greater flexibility.
Compare this preferred configuration to the original configuration used for ingress port queue groups, as follows, where the queue group name is specified within the SAP ingress QoS policy and the instance is not available:
configure
qos
sap-ingress <policy-id> [create]
fc <fc-name> [create]
queue <queue-id> group <queue-group-name>
In the preferred configuration, redirection is completed by applying the SAP ingress QoS policy to the SAP with the queue group name and instance to be used, as follows:
configure
service
{apipe|cpipe|epipe|fpipe|ipipe} <service-id>
sap <sap-id>
ingress
qos <policy-id> fp-redirect-group <queue-group-name>
instance <instance-id>
{ies|vprn} <service-id>
interface <ip-int-name>
sap <sap-id>
ingress
qos <policy-id>
fp-redirect-group <queue-group-name>
instance <instance-id>
SAP Egress Redirection
Traffic can be redirected per FC to a queue in a port egress access queue group, using the port-redirect-group parameter, as follows:
configure
qos
sap-egress <policy-id> [create]
fc <fc-name> [create]
queue <queue-id> port-redirect-group-queue
The queue-id is referencing a queue in the port egress queue group.
The queue group name and instance to be used is not yet configured, allowing this QoS policy to be applied to objects using different port egress queue groups.
Compare this preferred configuration to the original configuration, which allows the queue group name with an instance to be specified:
queue <id> {group <grp-name> [instance instance-id]}
In the preferred configuration, redirection is completed by applying the SAP egress QoS policy to the SAP with the queue group name and instance to be used, as follows:
configure
service
{apipe|cpipe|epipe|fpipe|ipipe} <service-id>
sap <sap-id>
egress
qos <policy-id>
port-redirect-group <queue-group-name>
instance <instance-id>
{ies|vprn} <service-id>
interface <ip-int-name>
sap <sap-id>
egress
qos <policy-id>
port-redirect-group <queue-group-name>
instance <instance-id>
Network Ingress Redirection
Traffic can be redirected per FC to a policer in an FP ingress network queue group, using the fp-redirect-group parameter, as follows:
configure
qos
network <network-policy-id> [create]
ingress
fc <fc-name>
fp-redirect-group <policer-type> <policer-id>
The policer-id is referencing a policer in the FP ingress queue group.
The traffic usage for each policer type for the supported services is shown in Table 4.
Policer Type |
Usage |
|---|---|
broadcast-policer |
Broadcast traffic for PW QoS in a VPLS service |
mcast-policer |
Multipoint traffic (except for ingress QoS control on VPRN network interfaces and CSC services where the IP multicast traffic uses the ingress network queues or queue group related to the network interface) Multicast traffic for PW QoS in a VPLS service |
unknown-policer |
Unknown traffic for PW QoS in a VPLS service |
policer |
Unicast traffic |
The queue group name and instance to be used is not yet configured, allowing this QoS policy to be applied to objects using different FP ingress queue group instances.
The redirection is completed by applying the network QoS policy to the required object with the queue group name and instance to be used, as follows (only the network interface redirection is shown):
configure
router
interface <interface-name>
qos <network-policy-id>
ingress-fp-redirect-group <queue-group-name>
ingress-instance <instance-id>
Network Egress Redirection
Traffic can be redirected per FC to a policer or a queue in a port egress network queue group, using the port-redirect-group parameter, as follows:
configure
qos
network <network-policy-id> [create]
egress
fc <fc-name>
port-redirect-group {queue <queue-id> |
policer <plcr-id> [queue <queue-id>]}
The queue-id and policer-id are referencing a queue and a policer in the port egress queue group.
The queue group name and instance to be used are not yet configured, allowing this QoS policy to be applied to objects using different port egress queue groups.
The redirection is completed by applying the network QoS policy to the required object with the queue group name and instance to be used, as follows (only the network interface redirection is shown):
configure
router
interface <interface-name>
qos <network-policy-id>
egress-fp-redirect-group <queue-group-name>
egress-instance <instance-id>
Non-IPv4/non-IPv6/non-MPLS packets are not subject to the redirection to an egress queue group instance and will remain on the regular port network egress queues. When using an egress port scheduler, parent the related regular network port queues to appropriate port scheduler priority levels, to ensure the required operation under port congestion. This is important for protocol traffic, such as LACP, EFMOAM, ETH-CFM, ARP, and IS-IS, which by default use the FC nc regular network port queue.
Post-egress Policer Queuing
The queuing of traffic exiting an egress policer is described as follows for SAP egress and network egress.
SAP egress policed traffic exits a port, using either a local queue or an egress queue group instance queue. If an egress queue group instance queue is to be used, the policed traffic can be mapped to the queue in the following ways, listed in reverse preference order (first is lowest preference):
By default, SAP egress policed traffic exits using a queue in the policer-output-queues queue group instance when only a policer is configured:
configure qos sap-egress <policy-id> [create] fc <fc-name> [create] policer <policer-id>The system always creates this egress queue group template and applies it to all access and hybrid ports (for use by the access part of the hybrid port) as instance 1. The queue group template contains the mapping for all FCs to one of the two created queues to determine which queue is to be used.
The default configuration of the policer-output-queues group template is as follows (without the queue details):
configure qos queue-group-templates egress queue-group "policer-output-queues" create description "Default egress policer output queues." queue 1 best-effort create exit queue 2 expedite create exit fc af create queue 1 exit fc be create queue 1 exit fc ef create queue 2 exit fc h1 create queue 2 exit fc h2 create queue 2 exit fc l1 create queue 1 exit fc l2 create queue 1 exit fc nc create queue 2 exit exitThis queue group template cannot be deleted, but its configuration can be modified. The configuration commands under a port access egress queue group instance are also available under the policer-output-queues queue group instance.
The FC in the SAP egress QoS policy can be mapped to a policer with its traffic redirected to a port access egress queue group, as follows:
configure qos sap-egress <policy-id> [create] fc <fc-name> [create] policer <policer-id> port-redirect-group-queueThe QoS policy must be applied to the SAP with a redirection to a queue group instance. By default, queue 1 in the queue group will be used, but other queues can be created and used by creating an FC-to-queue mapping to them.
Similar to step 2, the FC in the SAP egress QoS policy can be mapped to a policer with its traffic redirected to a port access egress queue group instance and the queue within that queue group instance to be used, as follows:
configure qos sap-egress <policy-id> [create] fc <fc-name> [create] policer <policer-id> port-redirect-group-queue queue <id>The QoS policy must again be applied to the SAP with a redirection to a queue group instance. In this case, the queue specified with the port-redirect-group-queue will be used.
Network egress can only use policers that are created within an egress queue group instance, and this requires the egress FC to have the port-redirect-group parameter configured.
With the following configuration, traffic exits the port on the network egress queue to which its FC is mapped (not on a queue group queue):
configure
qos
network <network-policy-id> [create]
egress
fc <fc-name>
port-redirect-group policer <plcr-id>
If a queue is specified on the port-redirect-group statement, as follows, the traffic exits on the referenced queue within the port network egress queue group instance:
configure
qos
network <network-policy-id> [create]
egress
fc <fc-name>
port-redirect-group policer <plcr-id> queue <queue-id>
Configuration Examples
The following configuration examples are for the use of queue groups with a SAP, network interface, and egress policed traffic subscriber traffic. Different queue group templates and instances have been used to highlight the flexibility of the configuration.
SAP Configuration Example
In this example, a SAP is created in an IES service using ingress queue group qg1 instance 1 and egress queue group qg1 instance 1.
First, the queue group templates are configured, as follows:
configure
qos
queue-group-templates
ingress
queue-group "qg1" create
policer 1 create
exit
policer 2 create
exit
exit
exit
egress
queue-group "qg1" create
queue 1 best-effort create
exit
queue 2 expedite create
exit
exit
queue-group "policer-output-queues" create
queue 3 best-effort create
exit
fc l2 create
queue 3
exit
exit
The policer-output-queues queue group template has been modified to add an extra queue and map FC l2 to it. This is used by the traffic mapped to policer 1 in the SAP egress QoS policy.
The ingress template is applied to card 5 fp 1 to create an FP access queue group instance, as follows:
configure
card 5
fp 1
ingress
access
queue-group "qg1" instance 1 create
exit
exit
The egress template is applied to port 5/1/5 to create a port access queue group instance, as follows:
configure
port 5/1/5
ethernet
mode hybrid
encap-type dot1q
access
egress
queue-group "qg1" instance 1 create
exit
exit
The SAP ingress QoS policy is created to redirect FC af to policer 1 and FC ef to policer 2 in the FP ingress queue group. To emphasize that the redirection is per FC and can coexist with locally mapped queues or policers, FC be is mapped to the local queue 1 and FC l2 to local queue 2, as follows:
configure
qos
sap-ingress 10 create
queue 1 create
exit
queue 2 create
exit
queue 11 multipoint create
exit
fc "af" create
policer 1 fp-redirect-group
exit
fc "be" create
queue 1
exit
fc "ef" create
policer 2 fp-redirect-group
exit
fc "l2" create
queue 2
exit
dot1p 0 fc "be"
dot1p 1 fc "l2"
dot1p 2 fc "af"
dot1p 3 fc "ef"
exit
The SAP egress QoS policy is created to redirect FC af to queue 1 in the port egress queue group and FC ef to local policer 2, with its traffic exiting through queue 2 in the port egress queue group. FC be is mapped to the local queue 1 and FC l2 to local policer 1. The policer 1 traffic will exit using queue 3 of the policer-output-queues queue group, because the mapping for FC l2 has been modified in its template, as follows:
configure
qos
sap-egress 10 create
queue 1 create
exit
policer 1 create
exit
policer 2 create
exit
fc af create
queue 1 port-redirect-group-queue
exit
fc be create
queue 1
exit
fc ef create
policer 2 port-redirect-group-queue queue 2
exit
fc l2 create
policer 1
exit
exit
The IES service is created with an interface on SAP 5/1/5:1, using the preceding ingress and egress QoS policies and queue group instances. A second interface (not shown) is used to forward the traffic to and from this interface, as follows:
configure
service
ies 1 customer 1 create
interface "PE-1-int1-2" create
address 10.1.2.1/24
sap 5/1/5:1 create
ingress
qos 10 fp-redirect-group "qg1" instance 1
exit
egress
qos 10 port-redirect-group "qg1" instance 1
exit
exit
exit
no shutdown
exit
The following output shows the configuration and the QoS state after sending traffic through the service.
The traffic statistics are either counted in the SAP queues and policers, or in the queue group instance queues and policers, but not in both. However, summary statistics per SAP are available when using FP ingress queue groups, as shown.
The queue group templates can be shown. The output shows the details related to the ingress queue group template:
*A:PE-1# show qos queue-group "qg1" ingress detail
===============================================================================
QoS Queue-Group Ingress
===============================================================================
-------------------------------------------------------------------------------
QoS Queue Group
-------------------------------------------------------------------------------
Group-Name : qg1
Description : (Not Specified)
-------------------------------------------------------------------------------
Q Mode CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent
CIR Rule PIR Rule MBS CIR Lvl/Wt BurstLimit(B)
Named-Buffer Pool Pkt Bt Ofst Adv Config Policy Name
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group Ports
===============================================================================
Port Sched Pol Acctg Pol Stats Description
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group Sap FC Maps
===============================================================================
Sap Policy FC Name Queue (id type)
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group FP Maps
===============================================================================
Card Num Fp Num Instance Type
-------------------------------------------------------------------------------
5 1 1 Access
-------------------------------------------------------------------------------
Entries found: 1
-------------------------------------------------------------------------------
===============================================================================
Queue Group Policer
===============================================================================
Policer Id : 1
Description : (Not Specified)
PIR Adptn : closest CIR Adptn : closest
Parent : none Level : 1
Weight : 1 Adv. Cfg Plcy: none
Admin PIR : max Admin CIR : 0
CBS : def MBS : def
Hi Prio Only : def Pkt Offset : 0
Profile Capped : Disabled
StatMode : minimal
===============================================================================
Policer Id : 2
Description : (Not Specified)
PIR Adptn : closest CIR Adptn : closest
Parent : none Level : 1
Weight : 1 Adv. Cfg Plcy: none
Admin PIR : max Admin CIR : 0
CBS : def MBS : def
Hi Prio Only : def Pkt Offset : 0
Profile Capped : Disabled
StatMode : minimal
===============================================================================
*A:PE-1#
The following output shows the details related to the egress queue group template:
*A:PE-1# show qos queue-group "qg1" egress detail
===============================================================================
QoS Queue-Group Egress
===============================================================================
-------------------------------------------------------------------------------
QoS Queue Group
-------------------------------------------------------------------------------
Group-Name : qg1
Description : (Not Specified)
-------------------------------------------------------------------------------
Q CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent BurstLimit(B)
CIR Rule PIR Rule MBS CIR Lvl/Wt Wred-Queue Slope
Named-Buffer Pool Pkt Bt Ofst Adv Config Policy Name
-------------------------------------------------------------------------------
1 0 max def def 1/1 None default
closest closest def 0/1 disabled default
(not-assigned) add 0 (not-assigned)
2 0 max def def 1/1 None default
closest closest def 0/1 disabled default
(not-assigned) add 0 (not-assigned)
===============================================================================
Queue Group FC Mapping
===============================================================================
FC Name Queue-Id
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
===============================================================================
Queue Group Ports (access)
===============================================================================
Port Sched Pol Acctg Pol Stats Description QGrp-Instance
-------------------------------------------------------------------------------
5/1/5 0 No 1
-------------------------------------------------------------------------------
===============================================================================
Queue Group Ports (network)
===============================================================================
Port Sched Pol Policer-Ctrl-Pol Acctg Pol Stats Description QGrp-Instance
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Qos Sap-Egress FC Group-Queue References
===============================================================================
Sap Policy FC Name Queue Id
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Qos Sap-Egress FC Port-Redirect-Group-Queue References
===============================================================================
Sap Policy FC Name Queue Id
-------------------------------------------------------------------------------
10 af 1
10 ef 2
-------------------------------------------------------------------------------
Entries found: 2
-------------------------------------------------------------------------------
===============================================================================
Queue Group Policer
===============================================================================
No Matching Entries
-------------------------------------------------------------------------------
HSMDA PIR Admin Packet WRR MBS Slope Plcy WRR Plcy
Queue PIR Rule Offset Weight Max Class Burst Lmt
-------------------------------------------------------------------------------
1 max add 0 1 default default n/a
closest 8 default
2 max add 0 1 default default n/a
closest 8 default
3 max add 0 1 default default n/a
closest 8 default
4 max add 0 1 default default n/a
closest 8 default
5 max add 0 1 default default n/a
closest 8 default
6 max add 0 1 default default n/a
closest 8 default
7 max add 0 1 default default n/a
closest 8 default
8 max add 0 1 default default n/a
closest 8 default
-------------------------------------------------------------------------------
===============================================================================
*A:PE-1#
The preceding output shows that the ingress template has an instance 1, which is applied to card 5 fp 1, and the egress template has an instance 1, which is applied to port 5/1/5.
The remapping of FC l2 to queue 3 in the policer-output-queues queue group template is as follows:
*A:PE-1# show qos queue-group "policer-output-queues" egress detail | match post-lines 12 "Queue Group FC Mapping"
Queue Group FC Mapping
===============================================================================
FC Name Queue-Id
-------------------------------------------------------------------------------
af 1
be 1
ef 2
h1 2
h2 2
l1 1
l2 3
nc 2
===============================================================================
*A:PE-1#
For SAP ingress QoS policy 10, the redirection is true for FC af using policer 1 and FC ef using policer 2 to an FP ingress queue group, as follows:
*A:PE-1# show qos sap-ingress 10 detail | match post-lines 5 expression "af Unicast|ef Unicast"
FC : af Unicast
-------------------------------------------------------------------------------
Policer : 1 Queue : def
Queue-Group : None
FP Queue-Group : True
FC : ef Unicast
-------------------------------------------------------------------------------
Policer : 2 Queue : def
Queue-Group : None
FP Queue-Group : True
In the following output for SAP egress QoS policy 10:
The redirection is true for FC af using queue 1 in the queue group instance, to be specified when the policy is applied to a SAP.
The redirection is true for FC ef using local policer 2 with its traffic exiting queue 2 in the queue group instance, to be specified when the policy is applied to a SAP.
FC l2 is using local policer 1 with its traffic exiting using queue 3 in the policer-output-queues port access egress queue group.
*A:PE-1# show qos sap-egress 10 detail | match post-lines 6 expression "Queue-Group"
FC Queue Queue-Group InstanceId SapBReDir Plcr
-------------------------------------------------------------------------------
be 1 n/a n/a False None
l2 3 policer-output-queues 1 False 1
af 1 n/a n/a True None
ef 2 n/a n/a True 2
The QoS information, including the queue group instances being used for the IES service SAP, is shown as follows:
*A:PE-1# show service id 1 sap 5/1/5:1 detail | match post-lines 4 QOS
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 10 Egress qos-policy : 10
Ingress FP QGrp : qg1 Egress Port QGrp : qg1
Ing FP QGrp Inst : 1 Egr Port QGrp Inst: 1
In the following output for the egress SAP, FC ef is using policer 2 and its traffic exits using queue 2 in queue group qg1 instance 1, while FC l2 is using policer 1 and its traffic exits using queue 3 of the policer-output-queues queue group instance 1:
*A:PE-1# show qos policer sap 5/1/5:1 egress detail | match post-lines 4 "Policer Info"
Policer Info (1->5/1/5:1->1), Slot 5
===============================================================================
Policer Name : 1->5/1/5:1->1
Direction : Egress Fwding Plane : 1
FC->[QGrp:Inst->]Q : l2->policer-output-queues:1->3
Policer Info (1->5/1/5:1->2), Slot 5
===============================================================================
Policer Name : 1->5/1/5:1->2
Direction : Egress Fwding Plane : 1
FC->[QGrp:Inst->]Q : ef->qg1:1->2
The associations of the port access egress queue group are shown as follows:
*A:PE-1# show port 5/1/5 queue-group "qg1" instance 1 egress access associations
===============================================================================
Ethernet port 5/1/5 Access Egress queue-group
===============================================================================
Queue-Group Name : qg1
Instance-Id : 1
-------------------------------------------------------------------------------
Subscriber-Host Queue-Group Associations
-------------------------------------------------------------------------------
No associations
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
SAP Based Queue-Group Association
-------------------------------------------------------------------------------
Service-Id SAP Qos Policy-Id
-------------------------------------------------------------------------------
1 (IES) 5/1/5:1 10
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Qos Policy Based Queue-Group Association
-------------------------------------------------------------------------------
FC Name Qos Policy-Id Local Policer-Id Local Queue-Id QGrp-Q
-------------------------------------------------------------------------------
No associations
-------------------------------------------------------------------------------
===============================================================================
===============================================================================
*A:PE-1#
After traffic is sent through the service, the FP ingress access queue group policer statistics are as follows:
*A:PE-1# show card 5 fp 1 ingress queue-group "qg1" instance 1 mode access statistics
===============================================================================
Card:5 Acc.QGrp: qg1 Instance: 1
===============================================================================
Group Name : qg1
Description : (Not Specified)
Pol Ctl Pol : None Acct Pol : None
Collect Stats : disabled
-------------------------------------------------------------------------------
Statistics
-------------------------------------------------------------------------------
Packets Octets
Ing. Policer: 1 Grp: qg1 (Stats mode: minimal)
Off. All : 1000 128000
Dro. All : 0 0
For. All : 1000 128000
Ing. Policer: 2 Grp: qg1 (Stats mode: minimal)
Off. All : 1000 128000
Dro. All : 0 0
For. All : 1000 128000
===============================================================================
*A:PE-1#
The traffic sent through the port egress access queue group queues is as follows:
*A:PE-1# show port 5/1/5 queue-group "qg1" instance 1 egress access statistics
-------------------------------------------------------------------------------
Ethernet port 5/1/5 Access Egress queue-group
-------------------------------------------------------------------------------
Packets Octets
Egress Queue: 1 Group: qg1 Instance: 1
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
Egress Queue: 2 Group: qg1 Instance: 1
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
-------------------------------------------------------------------------------
*A:PE-1#
Finally, the FC l2 traffic using the egress policer 1 is in queue 3, in the policer-output-queues queue group instance statistics, as follows:
*A:PE-1# show port 5/1/5 queue-group "policer-output-queues" instance 1 egress access statistics
-------------------------------------------------------------------------------
Ethernet port 5/1/5 Access Egress queue-group
-------------------------------------------------------------------------------
Packets Octets
Egress Queue: 1 Group: policer-output-queues Instance: 1
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 0 0
Out Profile dropped : 0 0
Egress Queue: 2 Group: policer-output-queues Instance: 1
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 0 0
Out Profile dropped : 0 0
Egress Queue: 3 Group: policer-output-queues Instance: 1
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
-------------------------------------------------------------------------------
*A:PE-1#
The number of valid ingress packets received on a SAP, or subscribers on that SAP, in the sap-stats output, are shown as follows. The received valid counter includes both the local SAP counters and the counters from the related FP ingress queue group instance. This is useful to display SAP-level traffic statistics when forwarding classes in a SAP ingress policy have been redirected to an ingress queue group.
*A:PE-1# show service id 1 sap 5/1/5:1 sap-stats | match post-lines 6 "Forwarding Engine Stats"
Forwarding Engine Stats
Dropped : 0 0
Received Valid : 4000 512000
Off. HiPrio : 0 0
Off. LowPrio : 2000 256000
Off. Uncolor : 0 0
Off. Managed : 0 0
Traffic forwarded through FP ingress access, port ingress access, and port egress access queue groups can be monitored, as follows:
monitor card <slot-number> fp <fp-number> ingress {access|network} queue-group <queue-group-name> instance <instance-id> [interval <seconds>][repeat<repeat>] policer <policer-id> [absolute | percent-rate [<reference-rate>]]
monitor port queue-group <queue-group-name> ingress <access> ingress-queue <ingress-queue-id> [interval <seconds>] [repeat <repeat>] [absolute|rate]
monitor port queue-group <queue-group-name> egress <access> [instance <instance-id>] [egress-queue <egress-queue-id>] [interval <seconds>] [repeat <repeat>] [absolute|rate]
The summary of the queue groups applied to a port is shown as follows:
*A:PE-1# show port 5/1/5 queue-group summary
===============================================================================
Port queue-group summary
===============================================================================
Access-egress queue groups:
----------------------------
qg1
policer-output-queues
Total number of access-egress queue groups : 2
Network-egress queue groups:
----------------------------
Total number of network-egress queue groups : 0
Access-ingress queue groups:
----------------------------
Total number of access-ingress queue groups : 0
===============================================================================
*A:PE-1#
The total usage of queue groups is shown as follows:
*A:PE-1# show qos queue-group summary
===============================================================================
Queue-group instances per card
===============================================================================
card port-acc-ing port-acc-egr port-nw-egr fp-acc-ing fp-nw-ing
-------------------------------------------------------------------------------
1 0 0 0 0 0
2 0 0 0 0 0
3 0 0 0 0 0
4 0 0 0 0 0
5 0 3 0 1 0
-------------------------------------------------------------------------------
Total ingress QG templates per system : 4
Total egress QG templates per system : 5
===============================================================================
*A:PE-1#
The preceding output includes the created ingress template plus the three system-created ingress templates (making four in total), and the created egress template plus the four system-created egress templates (making five in total). There is one applied FP access ingress queue group instance on card 5. There are three port access egress queue group instances (the applied queue group instance and two instances of the policer-output-queues queue group), one on each access port used for IES service interfaces.
Network Interface Configuration Example
A network interface is created using ingress queue group qg2 instance 2 and egress queue group qg2 instance 2. If the goal is to provide per-network interface QoS on a single port, each network interface would be configured on a separate VLAN.
First, the queue group templates are configured, as follows:
configure
qos
queue-group-templates
ingress
queue-group "qg2" create
policer 1 create
exit
policer 2 create
exit
exit
exit
egress
queue-group "qg2" create
queue 1 best-effort create
exit
queue 2 expedite create
exit
policer 1 create
exit
policer 2 create
exit
exit
exit
The ingress template is applied to card 5 fp 1 to create an FP network queue group instance, as follows:
configure
card 5
fp 1
ingress
network
queue-group "qg2" instance 2 create
exit
exit
The egress template is applied to port 5/1/5 to create a port network queue group instance, as follows:
configure
port 5/1/5
ethernet
mode hybrid
encap-type dot1q
network
egress
queue-group "qg2" instance 2 create
exit
exit
The network QoS policy is created to:
Ingress
Redirect FC af to policer 1 and FC ef to policer 2 in the FP ingress queue group. FC be and FC l2 continue to use their default mapping to the local network ingress queues 1 and 2, respectively.
Egress
Redirect FC af to queue 1 in the port egress queue group and FC ef to policer 2 in the port egress queue group, with its traffic exiting through queue 2 of the port egress queue group. FC l2 is redirected to policer 1 in the port egress queue group, with its traffic exiting through the default network egress queue mapped by FC l2; that is, queue 2. FC be continues to use the default network egress queue 1.
configure
qos
network 10 create
ingress
dot1p 0 fc be profile out
dot1p 1 fc l2 profile out
dot1p 2 fc af profile out
dot1p 3 fc ef profile in
fc af
fp-redirect-group policer 1
exit
fc ef
fp-redirect-group policer 2
exit
exit
egress
fc af
port-redirect-group queue 1
exit
fc ef
port-redirect-group policer 2 queue 2
exit
fc l2
port-redirect-group policer 1
exit
exit
exit
The network interface is created on port 5/1/5:2 using the preceding network QoS policy with the ingress and egress being redirected to created queue group instances. A second interface (not shown) is used to forward the traffic to and from this network interface.
configure
router Base
interface "PE-1-int2-2"
address 10.2.2.1/24
port 5/1/5:2
qos 10 egress-port-redirect-group "qg2" egress-instance 2
ingress-fp-redirect-group "qg2" ingress-instance 2
no shutdown
exit
The following output shows the details of the configuration and the QoS state after sending traffic through the network interface.
The traffic statistics are either counted in the network interface queues or in the queue group instance queues and policers, but not in both.
The queue group templates can be shown. The output shows the details related to the ingress queue group template:
*A:PE-1# show qos queue-group "qg2" ingress detail
===============================================================================
QoS Queue-Group Ingress
===============================================================================
-------------------------------------------------------------------------------
QoS Queue Group
-------------------------------------------------------------------------------
Group-Name : qg2
Description : (Not Specified)
-------------------------------------------------------------------------------
Q Mode CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent
CIR Rule PIR Rule MBS CIR Lvl/Wt BurstLimit(B)
Named-Buffer Pool Pkt Bt Ofst Adv Config Policy Name
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group Ports
===============================================================================
Port Sched Pol Acctg Pol Stats Description
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group Sap FC Maps
===============================================================================
Sap Policy FC Name Queue (id type)
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group FP Maps
===============================================================================
Card Num Fp Num Instance Type
-------------------------------------------------------------------------------
5 1 2 Network
-------------------------------------------------------------------------------
Entries found: 1
-------------------------------------------------------------------------------
===============================================================================
Queue Group Policer
===============================================================================
Policer Id : 1
Description : (Not Specified)
PIR Adptn : closest CIR Adptn : closest
Parent : none Level : 1
Weight : 1 Adv. Cfg Plcy: none
Admin PIR : max Admin CIR : 0
CBS : def MBS : def
Hi Prio Only : def Pkt Offset : 0
Profile Capped : Disabled
StatMode : minimal
===============================================================================
Policer Id : 2
Description : (Not Specified)
PIR Adptn : closest CIR Adptn : closest
Parent : none Level : 1
Weight : 1 Adv. Cfg Plcy: none
Admin PIR : max Admin CIR : 0
CBS : def MBS : def
Hi Prio Only : def Pkt Offset : 0
Profile Capped : Disabled
StatMode : minimal
===============================================================================
*A:PE-1#
The following output shows the details related to the egress queue group template:
*A:PE-1# show qos queue-group "qg2" egress detail
===============================================================================
QoS Queue-Group Egress
===============================================================================
-------------------------------------------------------------------------------
QoS Queue Group
-------------------------------------------------------------------------------
Group-Name : qg2
Description : (Not Specified)
-------------------------------------------------------------------------------
Q CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent BurstLimit(B)
CIR Rule PIR Rule MBS CIR Lvl/Wt Wred-Queue Slope
Named-Buffer Pool Pkt Bt Ofst Adv Config Policy Name
-------------------------------------------------------------------------------
1 0 max def def 1/1 None default
closest closest def 0/1 disabled default
(not-assigned) add 0 (not-assigned)
2 0 max def def 1/1 None default
closest closest def 0/1 disabled default
(not-assigned) add 0 (not-assigned)
===============================================================================
Queue Group FC Mapping
===============================================================================
FC Name Queue-Id
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
===============================================================================
Queue Group Ports (access)
===============================================================================
Port Sched Pol Acctg Pol Stats Description QGrp-Instance
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group Ports (network)
===============================================================================
Port Sched Pol Policer-Ctrl-Pol Acctg Pol Stats Description QGrp-Instance
-------------------------------------------------------------------------------
5/1/5 No 2
-------------------------------------------------------------------------------
===============================================================================
Qos Sap-Egress FC Group-Queue References
===============================================================================
Sap Policy FC Name Queue Id
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Qos Sap-Egress FC Port-Redirect-Group-Queue References
===============================================================================
Sap Policy FC Name Queue Id
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
Queue Group Policer
===============================================================================
Policer Id : 1
Description : (Not Specified)
PIR Adptn : closest CIR Adptn : closest
Parent : none Level : 1
Weight : 1 Adv. Cfg Plcy: none
Admin PIR : max Admin CIR : 0
CBS : def MBS : def
Hi Prio Only : def Pkt Offset : 0
Profile Capped : Disabled
StatMode : minimal
===============================================================================
Policer Id : 2
Description : (Not Specified)
PIR Adptn : closest CIR Adptn : closest
Parent : none Level : 1
Weight : 1 Adv. Cfg Plcy: none
Admin PIR : max Admin CIR : 0
CBS : def MBS : def
Hi Prio Only : def Pkt Offset : 0
Profile Capped : Disabled
StatMode : minimal
-------------------------------------------------------------------------------
HSMDA PIR Admin Packet WRR MBS Slope Plcy WRR Plcy
Queue PIR Rule Offset Weight Max Class Burst Lmt
-------------------------------------------------------------------------------
1 max add 0 1 default default n/a
closest 8 default
2 max add 0 1 default default n/a
closest 8 default
3 max add 0 1 default default n/a
closest 8 default
4 max add 0 1 default default n/a
closest 8 default
5 max add 0 1 default default n/a
closest 8 default
6 max add 0 1 default default n/a
closest 8 default
7 max add 0 1 default default n/a
closest 8 default
8 max add 0 1 default default n/a
closest 8 default
-------------------------------------------------------------------------------
===============================================================================
*A:PE-1#
The preceding output shows that the ingress template has an instance 2, which is applied to card 5 fp 1, and the egress template has an instance 2, which is applied to port 5/1/5.
The details of network QoS policy 10 shows the redirection to the ingress and egress queue groups, as follows:
*A:PE-1# show qos network 10 detail | match expression "Egress Forwarding Class Mapping|Ingress Forwarding Class Mapping|FC Value|Redirect"
Egress Forwarding Class Mapping
FC Value : 0 FC Name : be
Redirect Grp Q : None Redirect Grp Plcr: None
FC Value : 1 FC Name : l2
Redirect Grp Q : None Redirect Grp Plcr: 1
FC Value : 2 FC Name : af
Redirect Grp Q : 1 Redirect Grp Plcr: None
FC Value : 3 FC Name : l1
Redirect Grp Q : None Redirect Grp Plcr: None
FC Value : 4 FC Name : h2
Redirect Grp Q : None Redirect Grp Plcr: None
FC Value : 5 FC Name : ef
Redirect Grp Q : 2 Redirect Grp Plcr: 2
FC Value : 6 FC Name : h1
Redirect Grp Q : None Redirect Grp Plcr: None
FC Value : 7 FC Name : nc
Redirect Grp Q : None Redirect Grp Plcr: None
Ingress Forwarding Class Mapping
FC Value : 0 FC Name : be
Redirect UniCast Plcr : None Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
FC Value : 1 FC Name : l2
Redirect UniCast Plcr : None Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
FC Value : 2 FC Name : af
Redirect UniCast Plcr : 1 Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
FC Value : 3 FC Name : l1
Redirect UniCast Plcr : None Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
FC Value : 4 FC Name : h2
Redirect UniCast Plcr : None Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
FC Value : 5 FC Name : ef
Redirect UniCast Plcr : 2 Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
FC Value : 6 FC Name : h1
Redirect UniCast Plcr : None Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
FC Value : 7 FC Name : nc
Redirect UniCast Plcr : None Redirect MultiCast Plcr : None
Redirect BroadCast Plcr : None Redirect Unknown Plcr : None
*A:PE-1#
The preceding output shows that:
Ingress
FC af is redirected to unicast policer 1 in the queue group instance, to be specified when the policy is applied to a network interface.
FC ef is redirected to unicast policer 2 in the queue group instance, to be specified when the policy is applied to a network interface.
Egress
FC af is redirected to queue 1 in the queue group instance, to be specified when the policy is applied to a network interface.
FC ef is redirected to policer 2 and queue 2 in the queue group instance, to be specified when the policy is applied to a network interface, so that the policer 2 traffic exits using queue 2 in the port network egress queue group instance.
The queue group instances used by the network interface are shown as follows:
*A:PE-1# show router interface "PE-1-int2-2" detail | match post-lines 3 "QoS Queue-Group Redirection Details"
QoS Queue-Group Redirection Details
-------------------------------------------------------------------------------
Ingress FP QGrp : qg2 Egress Port QGrp : qg2
Ing FP QGrp Inst : 2 Egr Port QGrp Inst: 2
After traffic is sent through the network, it can be shown in the FP ingress network queue group policers, as follows:
*A:PE-1# show card 5 fp 1 ingress queue-group "qg2" instance 2 mode network statistics
===============================================================================
Card:5 Net.QGrp: qg2 Instance: 2
===============================================================================
Group Name : qg2
Description : (Not Specified)
Pol Ctl Pol : None Acct Pol : None
Collect Stats : disabled
-------------------------------------------------------------------------------
Statistics
-------------------------------------------------------------------------------
Packets Octets
Ing. Policer: 1 Grp: qg2 (Stats mode: minimal)
Off. All : 1000 128000
Dro. All : 0 0
For. All : 1000 128000
Ing. Policer: 2 Grp: qg2 (Stats mode: minimal)
Off. All : 1000 128000
Dro. All : 0 0
For. All : 1000 128000
===============================================================================
*A:PE-1#
The traffic sent through the port egress network queue group queues can also be shown, as follows:
*A:PE-1# show port 5/1/5 queue-group "qg2" instance 2 egress network statistics
-------------------------------------------------------------------------------
Ethernet port 5/1/5 Network Egress queue-group
-------------------------------------------------------------------------------
Packets Octets
Egress Queue: 1 Group: qg2 Instance-Id: 2
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
Egress Queue: 2 Group: qg2 Instance-Id: 2
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
Egress Policer: 1 Group: qg2 Instance-Id: 2
Stats mode: minimal
Off. All : 1000 128000
Dro. All : 0 0
For. All : 1000 128000
Egress Policer: 2 Group: qg2 Instance-Id: 2
Stats mode: minimal
Off. All : 1000 128000
Dro. All : 0 0
For. All : 1000 128000
-------------------------------------------------------------------------------
*A:PE-1#
In the preceding output, the traffic on queue 1 is FC af, on policer 1 is FC l2, and on policer 2 is FC ef, with the post-policed traffic on queue 2.
Finally, the FC l2 traffic using the network egress queue group policer 1 can be shown in queue 2 of the default network egress queues, as follows:
*A:PE-1# show port 5/1/5 detail | match post-lines 4 "Egress Queue 2"
Egress Queue 2 Packets Octets
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
Traffic forwarded through both FP ingress network and port egress network queue groups can be monitored, as follows:
monitor card <slot-number> fp <fp-number> ingress {access|network} queue-group <queue-group-name> instance <instance-id> [interval <seconds>][repeat<repeat>] policer <policer-id> [absolute | percent-rate [<reference-rate>]]
monitor port queue-group <queue-group-name> egress <access> [instance <instance-id>] [egress-queue <egress-queue-id>] [interval <seconds>] [repeat <repeat>] [absolute|rate]
The summary of the queue groups applied to a port is shown as follows:
*A:PE-1# show port 5/1/5 queue-group summary
===============================================================================
Port queue-group summary
===============================================================================
Access-egress queue groups:
----------------------------
policer-output-queues
Total number of access-egress queue groups : 1
Network-egress queue groups:
----------------------------
qg2
Total number of network-egress queue groups : 1
Access-ingress queue groups:
----------------------------
Total number of access-ingress queue groups : 0
===============================================================================
*A:PE-1#
The total usage of queue groups is shown as follows:
*A:PE-1# show qos queue-group summary
===============================================================================
Queue-group instances per card
===============================================================================
card port-acc-ing port-acc-egr port-nw-egr fp-acc-ing fp-nw-ing
-------------------------------------------------------------------------------
1 0 0 0 0 0
2 0 0 0 0 0
3 0 0 0 0 0
4 0 0 0 0 0
5 0 2 1 0 1
-------------------------------------------------------------------------------
Total ingress QG templates per system : 4
Total egress QG templates per system : 5
===============================================================================
*A:PE-1#
The preceding output includes the created ingress template plus the three system-created ingress templates (making four in total), and the created egress template plus the four system-created egress templates (making five in total). There is the one applied FP network ingress queue group instance on card 5. There is the one created port network egress queue group instance. There are also two port access egress queue group instances, which are the policer-output-queues queue group instances associated with the access port used for IES service interface (not discussed) and the access side of the hybrid port 5/1/5.
Egress Policed Subscriber Configuration Example
Queue groups are only applicable to subscribers for egress policed traffic. By default, subscriber egress policed traffic exits the port using a queue in the egress access policer-output-queues queue group instance. The queue used is determined by the FC mapping in the policer-output-queues queue group template. This is the same default operation as in the SAP example.
The subscriber policed traffic can be sent to a different queue group instance using the inter-dest-id and a host-match (described when applying an egress access queue group template to a port), which represent an intermediate destination, such as a downstream DSLAM or GPON OLT. The inter-dest-id can be associated with a subscriber host when it is created; this would usually be received from the DHCP, or RADIUS server, or Diameter Gx (Policy and Rule Charging Function), or the local user database, or configured under a static host.
An alternative to host matching on an inter-dest-id is to match on the top VLAN tag when a QinQ SAP is configured using a default inter-dest-id.
A default inter-dest-id can be configured in IES, VPRN, and VPLS services, and under an MSAP policy, as follows:
configure
service
{ies|vprn} <service-id>
subscriber-interface <ip-int-name>
group-interface <ip-int-name> [create]
sap <sap-id>
sub-sla-mgmt
def-inter-dest-id {<inter-dest-string>|use-top-q}
configure
service
vpls <service-id>
sap <sap-id>
sub-sla-mgmt
def-inter-dest-id {<inter-dest-string>|use-top-q}
configure
subscriber-mgmt
msap-policy <msap-policy-name> [create]
sub-sla-mgmt
def-inter-dest-id {<inter-dest-string>|use-top-q}
The egress queue group template is configured as follows:
configure
qos
queue-group-templates
egress
queue-group "qg3" create
queue 1 best-effort create
exit
queue 2 expedite create
exit
fc af create
queue 1
exit
fc ef create
queue 2
exit
exit
exit
The egress template is applied to port 5/1/5 to create a port access queue group instance. A host match is configured under the created queue group instance on an egress access port. In the following, the host match dslam-1 is used:
configure
port 5/1/5
ethernet
mode hybrid
encap-type dot1q
access
egress
queue-group "qg3" instance 1 create
host-match dest "dslam-1" create
exit
exit
A host-match can only be configured under instance 1 of a port access egress queue group; if its configuration is attempted on a different instance, the following error is displayed:
*A:PE-1# configure port 5/1/5 ethernet access egress queue-group "qg3" instance 3 create host-match dest another-dslam create
MINOR: PMGR #1337 Host match entries only supported on port access egress queue groups with system default instance 1
*A:PE-1#
The subscriber host uses a SAP egress QoS policy in an egress SLA profile to map FCs to egress queue and policers. The SAP egress QoS policy is created with FC af using policer 1 and FC ef using policer 2, as follows:
configure
qos
sap-egress 30 create
queue 1 create
exit
queue 2 create
exit
policer 1 create
exit
policer 2 create
exit
fc af create
policer 1
exit
fc be create
queue 1
exit
fc ef create
policer 2
exit
fc l2 create
queue 2
exit
exit
To redirect the subscriber egress policed traffic to the access egress queue group qg3 instance 1 on port 5/1/5, which is configured with the host-match, an inter-dest-id is configured for the created subscriber static host, as follows:
configure
service
vprn 3 customer 1 create
route-distinguisher 65536:200
subscriber-interface "sub-int-1" create
address 10.3.2.1/24
group-interface "group-int-1" create
arp-populate
sap 5/1/5:3 create
sub-sla-mgmt
def-sub-profile "basic-sub"
def-sla-profile "basic-sla"
multi-sub-sap 200
single-sub-parameters
profiled-traffic-only
exit
no shutdown
exit
static-host ip 10.3.2.2 mac 00:00:10:03:02:02 create
inter-dest-id "dslam-1"
sla-profile "basic-sla"
sub-profile "basic-sub"
subscriber "sub1"
no shutdown
exit
exit
The host match configured under the egress queue group instance is shown as follows:
A:PE-1# show port 5/1/5 queue-group "qg3" instance 1 access | match post-lines 3 Host-Matches
Host-Matches
-------------------------------------------------------------------------------
Dest: dslam-1
-------------------------------------------------------------------------------
When the subscriber host is created, the inter-dest-id for the subscriber host is shown as follows:
A:PE-1# show service active-subscribers subscriber "sub1" detail | match expression "Subscriber sub1 |Sub. Int Dest Id"
Subscriber sub1 (basic-sub)
Sub. Int Dest Id : "dslam-1"
The inter-dest-id dslam-1 is matched against the host-match destination configured on the access egress group instances on the port on which the host is being created. If a match is found, the subscriber egress policed traffic will use that egress queue group instance, with the actual queue used being selected by the FC-to-queue mapping in the related queue group template. Otherwise, the default policer-output-queues queue group instance will be used.
The egress queue group instance subscriber host associations are shown as follows:
A:PE-1# show port 5/1/5 queue-group egress "qg3" associations | match post-lines 6 Subscriber-Host
Subscriber-Host Queue-Group Associations
-------------------------------------------------------------------------------
svc-id : 3 (VPRN)
sap : 5/1/5:3
subscr: sub1
ip : 10.3.2.2
mac : 00:00:10:03:02:02 pppoe-sid: N/A
The following output shows that FC ef is using policer 2 and its traffic exits using queue 2 in queue group qg3, while FC af is using policer 1 and its traffic exits using queue 1 in queue group qg3.
A:PE-1# show qos policer subscriber "sub1" egress detail | match post-lines 4 "Policer Info"
Policer Info (Sub=1:1 3->5/1/5:3->2), Slot 5
===============================================================================
Policer Name : Sub=1:1 3->5/1/5:3->2
Direction : Egress Fwding Plane : 1
FC->[QGrp:Inst->]Q : ef->qg3->2
Policer Info (Sub=1:1 3->5/1/5:3->1), Slot 5
===============================================================================
Policer Name : Sub=1:1 3->5/1/5:3->1
Direction : Egress Fwding Plane : 1
FC->[QGrp:Inst->]Q : af->qg3->1
After traffic is sent through the subscriber, the egress policed traffic can be shown in the port egress access queue group instance, as follows:
A:PE-1# show port 5/1/5 queue-group "qg3" instance 1 access egress statistics
-------------------------------------------------------------------------------
Ethernet port 5/1/5 Access Egress queue-group
-------------------------------------------------------------------------------
Packets Octets
Egress Queue: 1 Group: qg3 Instance: 1
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
Egress Queue: 2 Group: qg3 Instance: 1
In Profile forwarded : 0 0
In Profile dropped : 0 0
Out Profile forwarded : 1000 128000
Out Profile dropped : 0 0
-------------------------------------------------------------------------------
A:PE-1#
The traffic statistics are either counted in the subscriber queues or policers, or in the queue group instance queues, but not in both. However, summary statistics per SAP are available when using FP ingress queue groups.
The number of valid ingress packets received on a SAP, or subscribers on that SAP, can be shown in the sap-stats output, as follows. The received valid counter includes both the local SAP counters and the counters from the related FP ingress queue group instance. This is useful to display SAP-level traffic statistics when forwarding classes in a SAP ingress policy have been redirected to an ingress queue group.
*A:PE-1# show service id 3 sap 5/1/5:3 sap-stats | match post-lines 6 "Forwarding Engine Stats"
Forwarding Engine Stats
Dropped : 0 0
Received Valid : 4000 512000
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Off. Uncolor : 0 0
Off. Managed : 0 0
Traffic forwarded through port egress access queue groups can be monitored, as follows:
monitor port queue-group <queue-group-name> egress <access> [instance <instance-id>] [egress-queue <egress-queue-id>] [interval <seconds>] [repeat <repeat>] [absolute|rate]
The summary of the queue groups applied to a port is shown as follows:
A:PE-1# show port 5/1/5 queue-group summary
===============================================================================
Port queue-group summary
===============================================================================
Access-egress queue groups:
----------------------------
qg3
policer-output-queues
Total number of access-egress queue groups : 2
Network-egress queue groups:
----------------------------
Total number of network-egress queue groups : 0
Access-ingress queue groups:
----------------------------
Total number of access-ingress queue groups : 0
===============================================================================
A:PE-1#
The total usage of queue groups is shown as follows:
A:PE-1# show qos queue-group summary
===============================================================================
Queue-group instances per card
===============================================================================
card port-acc-ing port-acc-egr port-nw-egr fp-acc-ing fp-nw-ing
-------------------------------------------------------------------------------
1 0 0 0 0 0
2 0 0 0 0 0
3 0 0 0 0 0
4 0 0 0 0 0
5 0 3 0 0 0
-------------------------------------------------------------------------------
Total ingress QG templates per system : 3
Total egress QG templates per system : 5
===============================================================================
A:PE-1#
The preceding output includes the three system-created ingress templates, and the created egress template plus the four system-created egress templates (making five in total). There are three port access egress queue group instances (the applied queue group instance and two instances of the policer-output-queues queue group), one on each access port used for VPRN service interfaces.
Conclusion
This chapter described the use of queue groups as a mechanism to provide an aggregate QoS control for multiple SAPs and per-network interface QoS control. The configuration steps and commands are described, followed by example configurations on a SAP, network interface, and for egress policed traffic subscriber traffic.