q Commands

Context

[Tree] (config>port>ethernet qinq-etype)

Full Context

configure port ethernet qinq-etype

Description

This command configures the Ethertype used for Q-in-Q encapsulation.

The no form of this command reverts the qinq-etype value to the default.

Default

no qinq-etype

Parameters

qinq-etype-value

Specifies the qinq-etype to expect in the form of 0x600 to 0xfff.

Values

1536 to 65535 in decimal or hex formats

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>sap>egress qinq-mark-top-only)

Full Context

configure service vprn interface sap egress qinq-mark-top-only

Description

When the encapsulation type is qinq for the access port for the specified SAP, enabling this command specifies which P-bits or DEI bit to mark during packet egress. Only the P-bits or DEI bit in the top Q tag are marked. When this command is disabled, both sets of P-bits and the DEI bit are marked.

Default

no qinq-mark-top-only

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap>egress qinq-mark-top-only)

Full Context

configure service epipe sap egress qinq-mark-top-only

Description

When enabled (the encapsulation type of the access port where this SAP is defined as qinq), the qinq-mark-top-only command specifies which P-bits/DEI bit to mark during packet egress. When disabled, both set of P-bits/DEI bit are marked. When the enabled, only the P-bits/DEI bit in the top Q-tag are marked.

Default

no qinq-mark-top-only

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>egress qinq-mark-top-only)

Full Context

configure service vpls sap egress qinq-mark-top-only

Description

When enabled (the encapsulation type of the access port where this SAP is defined as qinq), the qinq-mark-top-only command specifies which P-bits/DEI bit to mark during packet egress. When disabled, both set of P-bits/DEI bit are marked. When enabled, only the P-bits/DEI bit in the top Q-tag are marked.

The no form of this command disables the command.

Default

no qinq-mark-top-only

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>sap>egress qinq-mark-top-only)

Full Context

configure service ies interface sap egress qinq-mark-top-only

Description

When enabled (the encapsulation type of the access port where this SAP is defined as qinq), the qinq-mark-top-only command specifies which P-bits/DEI bit to mark during packet egress. When disabled, both set of P-bits/DEI bit are marked. When the enabled, only the P-bits/DEI bit in the top Q-tag are marked.

Default

no qinq-mark-top-only

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>sap>egress qos)

[Tree] (config>service>ies>if>sap>egress qos)

[Tree] (config>service>vpls>sap>egress qos)

Full Context

configure service vprn interface sap egress qos

configure service ies interface sap egress qos

configure service vpls sap egress qos

Description

This command associates a Quality of Service (QoS) policy with an egress Service Access Point (SAP) or IP interface.

QoS egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP or IP interface. If the policy ID does not exist, an error is returned.

The qos command associates both ingress and egress QoS policies. The qos command only allows ingress policies to be associated on SAP or IP interface ingress and egress policies on SAP or IP interface egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP or IP interface at one time. Attempts to associate a second QoS policy of a given type returns an error.

By default, no specific QoS policy is associated with the SAP or IP interface for ingress or egress, so the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP or IP interface, and the QoS policy reverts to the default.

Parameters

policy-id

The ingress/egress policy ID to associate with SAP or IP interface on ingress/egress. The policy ID must already exist.

Values

1 to 65535

port-redirect-group

This keyword associates a SAP egress with an instance of a named queue group template on the egress port of a given IOM/IMM/XMA. The queue-group-name and instance instance-id are mandatory parameters when executing the command.

queue-group-name

Specifies the name of the egress port queue group of the IOM/IMM/XMA, up to 32 characters in length. The queue-group-name must correspond to a valid egress queue group, created under config>port>ethernet>access>egress.

instance instance-id

Specifies the instance of the named egress port queue group on the IOM/IMM/XMA.

Values

1 to 40960

Default

1

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>egress qos)

Full Context

configure service vpls sap egress qos

Description

This command associates a Quality of Service (QoS) policy with an egress Service Access Point (SAP).

QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP. If the policy-id does not exist, an error will be returned.

The qos command is used to associate both ingress and egress QoS policies. The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP at one time. Attempts to associate a second QoS policy of a specified type will return an error.

When an egress QoS policy is associated with an IES IP interface that has been bound to a VPLS, the policy becomes associated with every SAP on the VPLS and augments the egress QoS policy that is defined on each SAP. Packets that are bridged will be processed using the policy defined on the VPLS SAP; packets that are routed will be processed using the policy defined in the IES IP interface- binding context.

By default, if no specific QoS policy is associated with the SAP for ingress or egress, so the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Parameters

port-redirect-group

Associates a SAP egress with an instance of a named queue group template on the egress port of a specified IOM/IMM/XMA. The queue-group-name and instance instance-id are mandatory parameters when executing the command.

queue-group-name

Specifies the name of the egress port queue group of the IOM/IMM/XMA, up to 32 characters in length. The queue-group-name must correspond to a valid egress queue group, created under config>port>ethernet>access>egress.

instance instance-id

Specifies the instance of the named egress port queue group on the IOM/IMM/XMA

Values

1 to 40960

Default

1

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>sap>ingress qos)

[Tree] (config>service>vprn>if>sap>ingress qos)

Full Context

configure service ies interface sap ingress qos

configure service vprn interface sap ingress qos

Description

This command associates a Quality of Service (QoS) policy with an ingress Service Access Point (SAP).

QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP. If the policy ID does not exist, an error is returned.

The qos command is used to associate both ingress and egress QoS policies. The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP or IP interface at one time. Attempts to associate a second QoS policy of a given type returns an error.

By default, no specific QoS policy is associated with the SAP for ingress or egress, so the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

The no form of this command removes the QoS policy association from the SAP or IP interface, and the QoS policy reverts to the default.

Parameters

policy-id

The ingress/egress policy ID to associate with SAP or IP interface on ingress/egress. The policy ID must already exist.

1 to 65535

shared-queuing

Specifies the ingress shared queue policy used by this SAP. When the value of this object is null it means that the SAP uses individual ingress QoS queues instead of the shared ones.

multipoint-shared

Specifies that this queue-id is for multipoint forwarded traffic only. This queue-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. Attempting to map forwarding class unicast traffic to a multipoint queue generates an error; no changes are made to the current unicast traffic queue mapping.

A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command is not executed.

The multipoint keyword can be entered in the command line on a preexisting multipoint queue to edit queue ID parameters.

Default

Present (the queue is created as non-multipoint).

Values

Multipoint or not present.

fp-redirect-group

Creates an instance of a named queue group template on the ingress forwarding plane of a given IOM/IMM/XMA. The queue-group-name and instance instance-id are mandatory parameters when executing the command. The named queue group template can contain only policers. If it contains queues, then the command fails.

queue-group-name

Specifies the name of the queue group template to be instantiated on the forwarding plane of the IOM/IMM/XMA, up to 32 characters. The queue-group-name must correspond to a valid ingress queue group template name, configured in the config>qos>queue-group-templates context.

instance-id

Specifies the instance of the named queue group to be created on the IOM/IMM/XMA ingress forwarding plane.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap>egress qos)

Full Context

configure service epipe sap egress qos

Description

This command associates a Quality of Service (QoS) policy with an egress Service Access Point (SAP).

QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP. If the policy-id does not exist, an error will be returned.

The qos command, when used under the egress context, is used to associate egress QoS policies.

The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP at one time. Attempts to associate a second QoS policy of a specified type will return an error.

By default, if no specific QoS policy is associated with the SAP for ingress or egress, so the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Parameters

policy-id

The egress policy ID to associate with SAP on egress. The policy ID must already exist.

Values

1 to 65535

queue-group-name

Specifies the name of the egress port queue group of the IOM/IMM/XMA, up to 32 characters in length. The queue-group-name must correspond to a valid egress queue group, created under config>port>ethernet>access>egress.

instance-id

Specifies the instance of the named egress port queue group on the IOM/IMM/XMA.

Values

1 to 40960

Default

1

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap>ingress qos)

Full Context

configure service epipe sap ingress qos

Description

This command associates a Quality of Service (QoS) policy with an ingress Service Access Point (SAP).

QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP. If the policy-id does not exist, an error will be returned.

The qos command, when used under the ingress context, is used to associate ingress QoS policies. The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP at one time. Attempts to associate a second QoS policy of a specified type will return an error.

By default, if no specific QoS policy is associated with the SAP for ingress or egress, so the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Parameters

policy-id

The ingress policy ID to associate with SAP or IP interface on ingress. The policy ID must already exist.

Values

1 to 65535

shared-queuing

This keyword can only be specified on SAP ingress. The shared-queuing keyword specifies the shared queue policy will be used by this SAP. When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

fp-redirect-group

This keyword can only be used on SAP ingress and associates a SAP ingress with an instance of a named queue group template on the ingress forwarding plane of a specified IOM/IMM/XMA. The queue-group-name and instance instance-id are mandatory parameters when executing the command.

queue-group-name

Specifies the name of the queue group to be instance on the forwarding plane of the IOM/IMM/XMA, up to 32 characters in length. The queue-group-name must correspond to a valid ingress forwarding plane queue group, created under config>card>fp>ingress> access.

instance-id

Specifies the instance of the named queue group on the IOM/IMM/XMA ingress forwarding plane.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>spoke-sdp>egress qos)

[Tree] (config>service>vpls>mesh-sdp>egress qos)

[Tree] (config>service>epipe>spoke-sdp>egress qos)

Full Context

configure service vpls spoke-sdp egress qos

configure service vpls mesh-sdp egress qos

configure service epipe spoke-sdp egress qos

Description

This command is used to redirect pseudowire (PW) packets to an egress port queue-group for the purpose of shaping.

The egress PW shaping provisioning model allows the mapping of one or more PWs to the same instance of queues, or policers and queues, that are defined in the queue-group template.

Operationally, the provisioning model consists of the following steps:

1. Create an egress queue-group template and configure queues only, or policers and queues for each FC that needs to be redirected.

2. Apply the queue-group template to the network egress context of all ports where there exists a network IP interface that the PW packets can be forwarded on. This creates one instance of the template on the egress of the port. One or more instances of the same template can be created.

3. Configure FC-to-policer or FC-to-queue mappings together with the redirect to a queue-group in the egress context of a network QoS policy. No queue-group name is specified in this step, which means the same network QoS policy can redirect different PWs to different queue-group templates.

4. Apply this network QoS policy to the egress context of a spoke-sdp inside a service, or to the egress context of a PW template and specify the redirect queue-group name.

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. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group and the queue-group name does not exist, the association is failed at the time the user associates the egress context of a spoke-sdp to the named queue-group. In such a case, the PW packet will be fed directly to the corresponding egress queue for that FC used by the IP network interface the PW packet is forwarded on. This queue can be a queue-group queue or the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port. This is the existing implementation and default behavior for a PW packet.

2. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group and the queue-group name exists but the policer-id and/or the queue-id is not defined in the queue-group template, the association is failed at the time the user associates the egress context of a spoke-sdp to the named queue-group. In such a case, the PW packet will be fed directly to the corresponding egress queue for that FC used by the IP network interface the PW packet is forwarded on.

3. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group and the queue-group name exists and the policer-id or policer-id plus queue-id exist, it is not required to check that an instance of that queue-group exists in all egress network ports that have network IP interfaces. The handling of this is dealt with in the data path as follows:

   • When a PW packet for that FC is forwarded and an instance of the referenced queue-group name exists on that egress port, the packet is processed by the queue-group policer and will then be fed to the queue-group queue.

   • 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 will be fed directly to the corresponding egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.

4. If a network QoS policy is applied to the egress context of a PW, any PW FC that is not explicitly redirected in the network QoS policy will have the corresponding packets feed directly the corresponding the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.

When the queue-group name the PW is redirected to exists and the redirection succeeds, the marking of the packet’s DEI/dot1p/DSCP and the tunnel’s DEI/dot1p/DSCP/EXP is performed according to the relevant mappings of the {FC, profile} in the egress context of the network QoS policy applied to the PW. This is true regardless of whether an instance of the queue-group exists or not on the egress port the PW packet is forwarded to. If the packet’s profile value changed due to egress child policer CIR profiling, the new profile value is used to mark the packet’s DEI/dot1p and the tunnel’s DEI/dot1p/EXP, and the DSCP/prec will be remarked if enable-dscp-prec-marking is enabled under the policer.

When the queue-group name the PW is redirected does not exist, the redirection command is failed. In this case, the marking of the packet’s DEI/dot1p/DSCP and the tunnel’s DEI/dot1p/DSCP/EXP fields is performed according to the relevant commands in the egress context of the network QoS policy applied to the network IP interface to which the PW packet is forwarded.

The no version of this command removes the redirection of the PW to the queue-group.

Parameters

network-policy-id

Specifies the network policy identification. The value uniquely identifies the policy on the system.

Values

1 to 65535

queue-group-name

Specifies the name of the queue group template up to 32 characters in length.

instance-id

Specifies the optional identification of a specific instance of the queue-group.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>spoke-sdp>egress qos)

[Tree] (config>service>vprn>if>spoke-sdp>egress qos)

Full Context

configure service ies interface spoke-sdp egress qos

configure service vprn interface spoke-sdp egress qos

Description

This command is used to redirect pseudowire packets to an egress port queue-group for the purpose of shaping.

The egress pseudowire shaping provisioning model allows the mapping of one or more pseudowires to the same instance of queues, or policers and queues, which are defined in the queue-group template.

Operationally, the provisioning model consists of the following steps:

1. Create an egress queue-group template and configure queues only or policers and queues for each FC that needs to be redirected.

2. Apply the queue-group template to the network egress context of all ports where there exists a network IP interface on which the pseudowire packets can be forwarded. This creates one instance of the template on the egress of the port. One or more instances of the same template can be created.

3. Configure FC-to-policer or FC-to-queue mappings together with the redirect to a queue-group in the egress context of a network QoS policy. No queue-group name is specified in this step, which means the same network QoS policy can redirect different pseudowires to different queue-group templates.

4. Apply this network QoS policy to the egress context of a spoke-SDP inside a service or to the egress context of a pseudowire template and specify the redirect queue-group name.

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. When a pseudowire FC is redirected to use a queue or a policer and a queue in a queue-group and the queue-group name does not exist, the association is failed at the time the user associates the egress context of a spoke-SDP to the named queue-group. In such a case, the pseudowire packet will be fed directly to the corresponding egress queue for that FC used by the IP network interface on which the pseudowire packet is forwarded. This queue can be a queue-group queue, or the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port. This is the existing implementation and default behavior for a pseudowire packet.

2. When a pseudowire FC is redirected to use a queue or a policer, and a queue in a queue-group and the queue-group name exists, but the policer-id and/or the queue-id is not defined in the queue-group template, the association is failed at the time the user associates the egress context of a spoke-SDP to the named queue-group. In such a case, the pseudowire packet will be fed directly to the corresponding egress queue for that FC used by the IP network interface the pseudowire packet is forwarded on.

3. When a pseudowire FC is redirected to use a queue, or a policer and a queue in a queue-group, and the queue-group name exists and the policer-id or policer-id plus queue-id exist, it is not required to check that an instance of that queue-group exists in all egress network ports which have network IP interfaces. The handling of this is dealt with in the data path as follows:

   1. When a pseudowire packet for that FC is forwarded and an instance of the referenced queue-group name exists on that egress port, the packet is processed by the queue-group policer and will then be fed to the queue-group queue.

   2. When a pseudowire packet for that FC is forwarded and an instance of the referenced queue-group name does not exist on that egress port, the pseudowire packet will be fed directly to the corresponding egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.

4. If a network QoS policy is applied to the egress context of a pseudowire, any pseudowire FC, which is not explicitly redirected in the network QoS policy, will have the corresponding packets feed directly the corresponding the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.

When the queue-group name the pseudowire is redirected to exists and the redirection succeeds, the marking of the packet DEI/dot1p/DSCP and the tunnel DEI/dot1p/DSCP/EXP is performed; according to the relevant mappings of the (FC, profile) in the egress context of the network QoS policy applied to the pseudowire. This is true regardless, whether an instance of the queue-group exists or not on the egress port to which the pseudowire packet is forwarded. If the packet profile value changed due to egress child policer CIR profiling, the new profile value is used to mark the packet DEI/dot1p and the tunnel DEI/dot1p/EXP, and the DSCP/prec will be remarked if enable-dscp-prec-marking is enabled under the policer.

When the queue-group name the pseudowire is redirected does not exist, the redirection command is failed. In this case, the marking of the packet DEI/dot1p/DSCP and the tunnel DEI/dot1p/DSCP/EXP fields is performed according to the relevant commands in the egress context of the network QoS policy applied to the network IP interface to which the pseudowire packet is forwarded.

The no version of this command removes the redirection of the pseudowire to the queue-group.

Parameters

network-policy-id

Specifies the network policy identification. The value uniquely identifies the policy on the system.

Values

1 to 65535

port-redirect-group queue-group-name

This optional parameter specifies that the queue-group-name will be used for all egress forwarding class redirections within the network QoS policy ID. The specified queue-group-name must exist as a port egress queue group on the port associated with the IP interface.

egress-instance instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 16384

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>spoke-sdp>ingress qos)

[Tree] (config>service>ies>if>spoke-sdp>ingress qos)

Full Context

configure service vprn interface spoke-sdp ingress qos

configure service ies interface spoke-sdp ingress qos

Description

This command is used to redirect pseudowire packets to an ingress forwarding plane queue-group for the purpose of rate-limiting.

The ingress pseudowire rate-limiting feature uses a policer in queue-group provisioning model. This model allows the mapping of one or more pseudowires to the same instance of policers, which are defined in a queue-group template.

Operationally, the provisioning model in the case of the ingress pseudowire shaping feature consists of the following steps:

1. Create an ingress queue-group template and configure policers for each FC that needs to be redirected and optionally, for each traffic type (unicast, broadcast, unknown, or multicast).

2. Apply the queue-group template to the network ingress forwarding plane where there exists a network IP interface to which the pseudowire packets can be received. This creates one instance of the template on the ingress of the FP. One or more instances of the same template can be created.

3. Configure FC-to-policer mappings together with the policer redirect to a queue-group in the ingress context of a network QoS policy. No queue-group name is specified in this step, which means the same network QoS policy can redirect different pseudowires to different queue-group templates.

4. Apply this network QoS policy to the ingress context of a spoke-SDP inside a service, or to the ingress context of a pseudowire template, and specify the redirect queue-group name.

5. One or more spoke-SDPs can have their FCs redirected to use policers in the same policer queue-group instance.

The following are the constraints and rules of this provisioning model when used in the ingress pseudowire rate-limiting feature:

1. When a pseudowire 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 pseudowire packet will feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

2. When a pseudowire FC is redirected to use a policer in a named policer queue-group and the queue-group name exists but the policer-id is not defined in the queue-group template, 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 pseudowire packet will feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

3. When a pseudowire FC is redirected to use a policer in a named policer queue-group and the queue-group name exists and the policer-id is defined in the queue-group template, it is not required to check that an instance of that queue-group exists in all ingress FPs which have network IP interfaces. The handling of this is dealt with in the data path as follows:

When a pseudowire packet for that FC is received and an instance of the referenced queue-group name exists on that FP, the packet is processed by the policer and will then feed the per-FP ingress shared queues referred to as policer-output-queues.

When a pseudowire packet for that FC is received and an instance of the referenced queue-group name does not exist on that FP, the pseudowire packets will be fed directly into the corresponding ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

• If a network QoS policy is applied to the ingress context of a pseudowire, any pseudowire FC which is not explicitly redirected in the network QoS policy will have the corresponding packets feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

• If no network QoS policy is applied to the ingress context of the pseudowire, then all packets of the pseudowire will feed:

the ingress network shared queue for the packet FC defined in the network-queue policy applied to the ingress of the FP. This is the default behavior.

a queue-group policer followed by the per-FP ingress shared queues referred to as policer-output-queues if the ingress context of the network IP interface from which the packet is received is redirected to a queue-group (csc-policing). The only exceptions to this behavior are for packets received from a IES/VPRN spoke interface and from an R-VPLS spoke-SDP, which is forwarded to the R-VPLS IP interface. In these two cases, the ingress network shared queue for the packet FC defined in the network-queue policy applied to the ingress of the FP is used.

When a pseudowire 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 pseudowire. This is true regardless of whether an instance of the named policer queue-group exists on the ingress FP on which the pseudowire packet is received. The user can apply a QoS filter matching the dot1.p in the VLAN tag corresponding to the Ethernet port encapsulation, the EXP in the outer label when the tunnel is an LSP, the DSCP in the IP header if the tunnel encapsulation is GRE, and the DSCP in the payload IP header if the user enabled the ler-use-dscp option and the pseudowire terminates in IES or VPRN service (spoke-interface).

When the policer queue-group name the pseudowire is redirected does not exist, the redirection command is failed. In this case, the packet classification is performed according to default classification rule or the QoS filters defined in the ingress context of the network QoS policy applied to the network IP interface on which the pseudowire packet is received.

The no version of this command removes the redirection of the pseudowire to the queue-group.

Parameters

network-policy-id

Specifies the network policy identification. The value uniquely identifies the policy on the system.

Values

1 to 65535

fp- redirect-group queue-group-name

Specifies the name of the queue group template up to 32 characters in length.

ingress-instance instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 16384

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template>egress qos)

Full Context

configure service pw-template egress qos

Description

This command is used to redirect PW packets to an egress port queue-group for the purpose of shaping.

The egress PW shaping provisioning model allows the mapping of one or more PWs to the same instance of queues, or policers and queues, that are defined in the queue-group template.

Operationally, the provisioning model consists of the following steps:

1. Create an egress queue-group template and configure queues only, or policers and queues for each FC that needs to be redirected.

2. Apply the queue-group template to the network egress context of all ports where there exists a network IP interface that the PW packets can be forwarded on. This creates one instance of the template on the egress of the port. One or more instances of the same template can be created.

3. Configure FC-to-policer or FC-to-queue mappings together with the redirect to a queue- group in the egress context of a network QoS policy. No queue-group name is specified in this step, which means the same network QoS policy can redirect different PWs to different queue-group templates.

4. Apply this network QoS policy to the egress context of a spoke-SDP inside a service, or to the egress context of a PW template and specify the redirect queue-group name.

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. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group and the queue-group name does not exist, the association is failed at the time the user associates the egress context of a spoke-SDP to the named queue-group. In such a case, the PW packet will be fed directly to the corresponding egress queue for that FC used by the IP network interface the PW packet is forwarded on. This queue can be a queue-group queue or the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port. This is the existing implementation and default behavior for a PW packet.

2. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group and the queue-group name exists but the policer-id and/or the queue-id is not defined in the queue-group template, the association is failed at the time the user associates the egress context of a spoke-SDP to the named queue-group. In such a case, the PW packet will be fed directly to the corresponding egress queue for that FC used by the IP network interface the PW packet is forwarded on.

3. When a PW FC is redirected to use a queue or a policer and a queue in a queue-group and the queue-group name exists and the policer-id or policer-id plus queue-id exist, it is not required to check that an instance of that queue-group exists in all egress network ports that have network IP interfaces. The handling of this is dealt with in the data path as follows:

   • When a PW packet for that FC is forwarded and an instance of the referenced queue-group name exists on that egress port, the packet is processed by the queue-group policer and will then be fed to the queue-group queue.

   • 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 will be fed directly to the corresponding egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.

4. If a network QoS policy is applied to the egress context of a PW, any PW FC that is not explicitly redirected in the network QoS policy will have the corresponding packets feed directly the corresponding the egress shared queue for that FC defined in the network-queue policy applied to the egress of this port.

When the queue-group name the PW is redirected to exists and the redirection succeeds, the marking of the packet’s DEI/dot1p/DSCP and the tunnel’s DEI/dot1p/DSCP/EXP is performed according to the relevant mappings of the {FC, profile} in the egress context of the network QoS policy applied to the PW. This is true regardless of whether an instance of the queue-group exists or not on the egress port the PW packet is forwarded to. If the packet’s profile value changed due to egress child policer CIR profiling, the new profile value is used to mark the packet’s DEI/dot1p and the tunnel’s DEI/dot1p/EXP, and the DSCP/prec will be remarked if enable-dscp-prec-marking is enabled under the policer.

When the queue-group name the PW is redirected does not exist, the redirection command is failed. In this case, the marking of the packet’s DEI/dot1p/DSCP and the tunnel’s DEI/ dot1p/DSCP/EXP fields is performed according to the relevant commands in the egress context of the network QoS policy applied to the network IP interface the PW packet is forwarded to.

The no version of this command removes the redirection of the PW to the queue-group.

Parameters

network-policy-id

Specifies the network policy identification. The value uniquely identifies the policy on the system.

This variant of the command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The qos name network-policy-name variant can be used in all configuration modes.

Values

1 to 65535

queue-group-name

Specifies the name of the queue group template up to 32 characters in length.

instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 65535

name network-policy-name

Specifies the network policy name. The value uniquely identifies the policy on the system, up to 64 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>spoke-sdp>ingress qos)

[Tree] (config>service>vpls>spoke-sdp>ingress qos)

[Tree] (config>service>vpls>mesh-sdp>ingress qos)

Full Context

configure service epipe spoke-sdp ingress qos

configure service vpls spoke-sdp ingress qos

configure service vpls mesh-sdp ingress qos

Description

This command is used to redirect pseudowire packets to an ingress forwarding plane queue-group for the purpose of rate-limiting.

The ingress pseudowire rate-limiting feature uses a policer in queue-group provisioning model. This model allows the mapping of one or more pseudowires to the same instance of policers, which are defined in a queue-group template.

Operationally, the provisioning model in the case of the ingress pseudowire shaping feature consists of the following steps:

1. Create an ingress queue-group template and configure policers for each FC that needs to be redirected and optionally, for each traffic type (unicast or multicast).

2. Apply the queue-group template to the network ingress forwarding plane where there exists a network IP interface to which the pseudowire packets can be received. This creates one instance of the template on the ingress of the FP. One or more instances of the same template can be created.

3. Configure FC-to-policer mappings together with the policer redirect to a queue-group in the ingress context of a network QoS policy. No queue-group name is specified in this step, which means the same network QoS policy can redirect different pseudowires to different queue-group templates.

4. Apply this network QoS policy to the ingress context of a spoke-SDP inside a service, or to the ingress context of a pseudowire template, and specify the redirect queue-group name.

5. One or more spoke-SDPs can have their FCs redirected to use policers in the same policer queue-group instance.

The following are the constraints and rules of this provisioning model when used in the ingress pseudowire rate-limiting feature:

1. When a pseudowire 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 pseudowire packet will feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

2. When a pseudowire FC is redirected to use a policer in a named policer queue-group and the queue-group name exists but the policer-id is not defined in the queue-group template, 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 pseudowire packet will feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

3. When a pseudowire FC is redirected to use a policer in a named policer queue-group and the queue-group name exists and the policer-id is defined in the queue-group template, it is not required to check that an instance of that queue-group exists in all ingress FPs which have network IP interfaces. The handling of this is dealt with in the data path as follows:

When a pseudowire packet for that FC is received and an instance of the referenced queue-group name exists on that FP, the packet is processed by the policer and will then feed the per-FP ingress shared queues referred to as policer-output-queues.

When a pseudowire packet for that FC is received and an instance of the referenced queue-group name does not exist on that FP, the pseudowire packets will be fed directly into the corresponding ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

• If a network QoS policy is applied to the ingress context of a pseudowire, any pseudowire FC which is not explicitly redirected in the network QoS policy will have the corresponding packets feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

• If no network QoS policy is applied to the ingress context of the pseudowire, then all packets of the pseudowire will feed:

  • the ingress network shared queue for the packet FC defined in the network-queue policy applied to the ingress of the FP. This is the default behavior.

  • a queue-group policer followed by the per-FP ingress shared queues referred to as policer-output-queues if the ingress context of the network IP interface from which the packet is received is redirected to a queue-group. The only exceptions to this behavior are for packets received from a IES/VPRN spoke interface and from an R-VPLS spoke-SDP, which is forwarded to the R-VPLS IP interface. In these two cases, the ingress network shared queue for the packet FC defined in the network-queue policy applied to the ingress of the FP is used.

When a pseudowire 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 pseudowire. This is true regardless of whether an instance of the named policer queue-group exists on the ingress FP on which the pseudowire packet is received. The user can apply a QoS filter matching the dot1-p in the VLAN tag corresponding to the Ethernet port encapsulation, the EXP in the outer label when the tunnel is an LSP, the DSCP in the IP header if the tunnel encapsulation is GRE, and the DSCP in the payload IP header if the user enabled the ler-use-dscp option and the pseudowire terminates in IES or VPRN service (spoke-interface).

When the policer queue-group name the pseudowire is redirected does not exist, the redirection command is failed. In this case, the packet classification is performed according to default classification rule or the QoS filters defined in the ingress context of the network QoS policy applied to the network IP interface on which the pseudowire packet is received.

The no version of this command removes the redirection of the pseudowire to the queue-group.

Parameters

network-policy-id

Specifies the network policy identification. The value uniquely identifies the policy on the system.

Values

1 to 65535

queue-group-name

Specifies the name of the queue group template up to 32 characters in length

instance-id

Specifies the identification of a specific instance of the queue-group

Values

1 to 16384

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template>ingress qos)

Full Context

configure service pw-template ingress qos

Description

This command is used to redirect pseudowire packets to an ingress forwarding plane queue-group for the purpose of rate-limiting.

The ingress pseudowire rate-limiting feature uses a policer in queue-group provisioning model. This model allows the mapping of one or more pseudowires to the same instance of policers which are defined in a queue-group template.

Operationally, the provisioning model in the case of the ingress pseudowire shaping feature consists of the following steps:

1. Create an ingress queue-group template and configure policers for each FC which needs to be redirected and optionally for each traffic type (unicast or multicast).

2. Apply the queue-group template to the network ingress forwarding plane where there exists a network IP interface which the pseudowire 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.

3. Configure FC-to-policer mappings together with the policer redirect to a queue-group in the ingress context of a network QoS policy. No queue-group name is specified in this step which means the same network QoS policy can redirect different pseudowires to different queue-group templates.

4. Apply this network QoS policy to the ingress context of a spoke-sdp inside a service or to the ingress context of a pseudowire template and specify the redirect queue-group name.

One or more spoke-sdps can have their FCs redirected to use policers in the same policer queue-group instance.

The following are the constraints and rules of this provisioning model when used in the ingress pseudowire rate-limiting feature:

1. When a pseudowire 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 pseudowire packet will feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

2. When a pseudowire FC is redirected to use a policer in a named policer queue-group and the queue-group name exists but the policer-id is not defined in the queue-group template, 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 pseudowire packet will feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

3. When a pseudowire FC is redirected to use a policer in a named policer queue-group and the queue-group name exists and the policer-id is defined in the queue-group template, it is not required to check that an instance of that queue-group exists in all ingress FPs which have network IP interfaces. The handling of this is dealt with in the data path as follows:

   • When a pseudowire packet for that FC is received and an instance of the referenced queue-group name exists on that FP, the packet is processed by the policer and will then feed the per-FP ingress shared queues referred to as "policer-output-queues”.

   • When a pseudowire packet for that FC is received and an instance of the referenced queue-group name does not exist on that FP, the pseudowire packets will be fed directly into the corresponding ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

4. If a network QoS policy is applied to the ingress context of a pseudowire, any pseudowire FC which is not explicitly redirected in the network QoS policy will have the corresponding packets feed directly the ingress network shared queue for that FC defined in the network-queue policy applied to the ingress of the FP.

5. If no network QoS policy is applied to the ingress context of the pseudowire, then all packets of the pseudowire will feed:

   • the ingress network shared queue for the packet’s FC defined in the network-queue policy applied to the ingress of the FP. This is the default behavior.

   • a queue-group policer followed by the per-FP ingress shared queues referred to as "policer-output-queues” Good received is redirected to a queue-group. The only exceptions to this behavior are for packets received from a IES/VPRN spoke interface and from a R-VPLS spoke-sdp which is forwarded to the R-VPLS IP interface. In these two cases, the ingress network shared queue for the packet’s FC defined in the network-queue policy applied to the ingress of the FP is used. When a pseudowire 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 pseudowire. This is true regardless if an instance of the named policer queue-group exists on the ingress FP the pseudowire packet is received on. The user can apply a QoS filter matching the dot1p in the VLAN tag corresponding to the Ethernet port encapsulation, the EXP in the outer label when the tunnel is an LSP, the DSCP in the IP header if the tunnel encapsulation is GRE, and the DSCP in the payload’s IP header if the user enabled the ler-use-dscp option and the pseudowire terminates in IES or VPRN service (spoke-interface).

When the policer queue-group name the pseudowire is redirected does not exist, the redirection command is failed. In this case, the packet classification is performed according to default classification rule or the QoS filters defined in the ingress context of the network QoS policy applied to the network IP interface the pseudowire packet is received on.

The no version of this command removes the redirection of the pseudowire to the queue-group.

Parameters

network-policy-id

Specifies the network policy identification. The value uniquely identifies the policy on the system.

This variant of the command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The qos name network-policy-name variant can be used in all configuration modes.

Values

1 to 65535

queue-group-name

Specifies the name of the queue group template up to 32 characters in length.

instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 65535

name network-policy-name

Specifies the network policy name. The value uniquely identifies the policy on the system, up to 64 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>template>vpls-sap-template>ingress qos)

Full Context

configure service template vpls-sap-template ingress qos

Description

This command associates a Quality of Service (QoS) policy with an ingress Service Access Point (SAP) for the Epipe SAP template.

Parameters

policy-id

The ingress policy ID to associate with SAP or IP interface on ingress. The policy ID must already exist.

This variant of the command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The qos name sap-ingress-policy-name variant can be used in all configuration modes.

Values

1 to 65535

shared-queuing

This keyword can only be specified on SAP ingress. Specify the ingress shared queue policy used by this SAP. When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

multipoint-shared

This keyword can only be specified on SAP ingress. Multipoint shared queuing is a superset of shared queuing. When multipoint shared queuing keyword is set, as well as the unicast packets, multipoint packets also used shared queues.

Ingress unicast service queues are mapped one-for-one with hardware queues and unicast packets traverse the ingress forwarding plane twice, similar to the shared-queuing option. In addition, the multipoint queues defined in the ingress SAP QoS policy are not created. Instead, multipoint packets (broadcast, multicast and unknown unicast destined) are treated to the same dual pass ingress forwarding plane processing as unicast packets.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

Values

Multipoint or not present

Default

Present (the queue is created as non-multipoint)

sap-ingress-policy-name

The SAP ingress QoS policy name to associate with the SAP on ingress, up to 64 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>template>vpls-sap-template>egress qos)

Full Context

configure service template vpls-sap-template egress qos

Description

This command associates an existing QoS policy with the template.

Parameters

sap-egress-policy-id

The egress policy ID to associate with SAP or IP interface on egress. The policy ID must already exist.

This variant of the command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The qos name sap-egress-policy-name variant can be used in all configuration modes.

Values

1 to 65535

sap-egress-policy-name

The SAP egress QoS policy name to associate with the SAP on egress, up to 64 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>ingress qos)

Full Context

configure service vpls sap ingress qos

Description

This command associates a Quality of Service (QoS) policy with an ingress Service Access Point (SAP).

QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined prior to associating the policy with a SAP or IP interface. If the policy-id does not exist, an error will be returned.

The qos command is used to associate both ingress and egress QoS policies. The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP at one time. Attempts to associate a second QoS policy of a specified type will return an error.

When an ingress QoS policy is defined on IES ingress IP interface that is bound to a VPLS, the policy becomes associated with every SAP on the VPLS and augments the QoS policy that is defined on each SAP. Packets that are bridged will be processed using the policy defined on the VPLS SAP; packets that are routed will be processed using the policy defined in the IES IP interface-binding context.

By default, if no specific QoS policy is associated with the SAP for ingress or egress, the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Parameters

policy-id

The ingress policy ID to associate with SAP or IP interface on ingress. The policy ID must already exist.

Values

1 to 65535

shared-queuing

This keyword can only be specified on SAP ingress. Specify the ingress shared queue policy used by this SAP. When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

multipoint-shared

This keyword can only be specified on SAP ingress. Multipoint shared queuing is a superset of shared queuing. When multipoint shared queuing keyword is set, as well as the unicast packets, multipoint packets also used shared queues.

Ingress unicast service queues are mapped one-for-one with hardware queues and unicast packets traverse the ingress forwarding plane twice, similar to the shared-queuing option. In addition, the multipoint queues defined in the ingress SAP QoS policy are not created. Instead, multipoint packets (broadcast, multicast and unknown unicast destined) are treated to the same dual pass ingress forwarding plane processing as unicast packets.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.

Values

Multipoint or not present

Default

Present (the queue is created as non-multipoint)

fp-redirect-group

Creates an instance of a named queue group template on the ingress forwarding plane of a specified IOM/IMM/XMA. The queue-group-name and instance instance-id are mandatory parameters when executing the command. The named queue group template can contain only policers. If it contains queues, then the command will fail.

queue-group-name

Specifies the name of the queue group template to be instantiated on the forwarding plane of the IOM/IMM/XMA, up to 32 characters in length. The queue-group-name must correspond to a valid ingress queue group template name, configured under the configure qos queue-group-templates context.

instance-id

Specifies the instance of the named queue group to be created on the IOM/IMM/XMA ingress forwarding plane.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>nw-if qos)

Full Context

configure service vprn network-interface qos

Description

This command associates a network Quality of Service (QoS) policy with a network IP interface. Only one network QoS policy can be associated with an IP interface at one time. Attempts to associate a second QoS policy return an error.

Associating a network QoS policy with a network interface is useful for the following purposes:

• To apply classification rules for determining the forwarding-class and profile of ingress packets on the interface.

• To associate ingress packets on the interface with a queue-group instance applied to the ingress context of the interface’s forwarding plane (FP). (This is only applicable to interfaces on IOM4 and later cards.) The referenced ingress queue-group instance may have policers defined in order to rate limit ingress traffic on a per-forwarding class (and forwarding type: unicast vs. multicast) basis.

• To perform 802.1p, DSCP, IP precedence and/or MPLS EXP re-marking of egress packets on the interface.

• To associate egress packets on the interface with a queue-group instance applied to the egress context of the interface’s port. The referenced egress queue-group instance may have policers and/or queues defined in order to rate limit egress traffic on a per-forwarding class basis.

The no form of this command removes the network QoS policy association from the network IP interface, and the QoS policy reverts to the default.

Default

no qos

Parameters

network-policy-id

An existing network policy ID to associate with the IP interface.

Values

1 to 65535

port-redirect-group queue-group-name

This optional parameter specifies the egress queue-group used for all egress forwarding-class redirections specified within the network QoS policy ID. The specified queue-group-name must exist as an egress queue group applied to the egress context of the port associated with the IP interface.

egress-instance instance-id

Since multiple instances of the same egress queue-group can be applied to the same port this optional parameter is used to specify which particular instance to associate with this particular network IP interface.

Values

1 to 16384

fp- redirect-group queue-group-name

This optional parameter specifies the ingress queue-group used for all ingress forwarding-class redirections specified within the network QoS policy ID. The specified queue-group-name must exist as an ingress queue group applied to the ingress context of the forwarding plane associated with the IP interface.

ingress-instance instance-id

Since multiple instances of the same ingress queue-group can be applied to the same forwarding plane this parameter is required to specify which particular instance to associate with this particular network IP interface.

Values

1 to 16384

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>network>ingress qos)

Full Context

configure service vprn network ingress qos

Description

This command is used to redirect unicast packets arriving on an automatically (using the auto-bind-tunnel command) or manually configured (using a spoke-sdp command, but not the spoke-sdp command under the VPRN IP interface) binding in a VPRN to a policer in an ingress forwarding plane queue-group for the purpose of rate-limiting.

For the policer to be used, the following must be true:

1. The configured queue group template name must be applied to the forwarding plane on which the ingress traffic arrives using the instance id specified.

2. The policer referenced in the FC-to-policer mappings in the ingress context of a network QoS policy must be present in the specified queue group template.

The command fails if the queue group template name does not exist or if the policer specified in the network QoS policy does not exist in the queue group template. If the queue group template name with the specified instance is not applied to the forwarding plane on which the VPRN binding unicast traffic arrives then this traffic uses the ingress network queues related to the network interface, however, the ingress classification is still based on the applied network QoS policy.

The unicast traffic can be redirected to a policer under the forwarding class fp-redirect-group command in the ingress section of a network QoS policy; any fp-redirect-group multicast-policer, broadcast-policer or unknown-policer commands are ignored for this traffic. Multicast traffic would use the ingress network queues or queue group related to the network interface.

Ingress classification is based on the configuration of the ingress section of the specified network QoS policy, noting that the dot1p and exp classification is based on the outer Ethernet header and MPLS label whereas the DSCP applies to the outer IP header if the tunnel encapsulation is GRE, or the DSCP in the first IP header in the payload if ler-use-dscp is enabled in the ingress section of the referenced network QoS policy.

When this command is applied, it overrides the QoS applied to the related network interfaces for unicast traffic arriving on bindings in that VPRN.

The no version of this command removes the redirection of VPRN binding traffic to the queue-group policers.

Parameters

network-policy-id

Specifies the network policy identification. The value uniquely identifies the policy on the system.

Values

1 to 65535

fp-redirect-group queue-group-name

Specifies the name of the queue group template up to 32 characters in length.

instance instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>mirror>mirror-dest>sap>egress qos)

Full Context

configure mirror mirror-dest sap egress qos

Description

This command associates a QoS policy with an egress SAP for a mirrored service.

By default, no specific QoS policy is associated with the SAP for egress, so the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Default

qos 1

Parameters

policy-id

Specifies the QoS policy ID to associate with SAP for the mirrored service. The policy ID must already exist.

Values

1 to 65535

queue-group-name

Specifies the queue group redirect list policy name.

instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>if qos)

Full Context

configure router interface qos

Description

This command associates a network Quality of Service (QoS) policy with a network IP interface. Only one network QoS policy can be associated with an IP interface at one time. Attempts to associate a second QoS policy return an error.

Associating a network QoS policy with a network interface is useful for the following purposes:

• To apply classification rules for determining the forwarding-class and profile of ingress packets on the interface.

• To associate ingress packets on the interface with a queue-group instance applied to the ingress context of the interface’s forwarding plane (FP). The referenced ingress queue-group instance may have policers defined in order to rate limit ingress traffic on a per-forwarding class (and forwarding type: unicast vs. multicast) basis.

• To perform 802.1p, DSCP, IP precedence and/or MPLS EXP re-marking of egress packets on the interface.

• To associate egress packets on the interface with a queue-group instance applied to the egress context of the interface’s port. The referenced egress queue-group instance may have policers and/or queues defined in order to rate limit egress traffic on a per-forwarding class basis.

The no form of this command removes the network QoS policy association from the network IP interface, and the QoS policy reverts to the default.

Default

no qos

Parameters

network-policy-id

Specifies an existing network policy ID to associate with the IP interface.

Values

1 to 65535

egress-port-redirect-group queue-group-name

This optional parameter specifies the egress queue-group used for all egress forwarding-class redirections specified within the network QoS policy ID. The specified queue-group-name must exist as an egress queue group applied to the egress context of the port associated with the IP interface.

egress-instance instance-id

Since multiple instances of the same egress queue-group can be applied to the same port this optional parameter is used to specify which instance to associate with this specific network IP interface.

Values

1 to 16384

ingress-fp- redirect-group queue-group-name

This optional parameter specifies the ingress queue-group used for all ingress forwarding-class redirections specified within the network QoS policy ID. The specified queue-group-name must exist as an ingress queue group applied to the ingress context of the forwarding plane associated with the IP interface.

ingress-instance instance-id

Since multiple instances of the same ingress queue-group can be applied to the same forwarding plane this parameter is required to specify which instance to associate with this specific network IP interface.

Values

1 to 16384

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>md-auto-id qos-policy-id-range)

Full Context

configure qos md-auto-id qos-policy-id-range

Description

This command specifies the range of IDs used by SR OS to automatically assign an ID to QoS policies that are created in model-driven interfaces without an ID explicitly specified by the user or client.

A QoS policy created with an explicitly-specified ID cannot use an ID in this range. In classic CLI and SNMP, the ID range cannot be changed while objects exist inside the previous or new range. In MD interfaces, the range can be changed which will cause any previously existing objects in the previous ID range to be deleted and re-created using a new ID in the new range.

The no form of this command removes the range values.

See the config>eth-cfm md-auto-id command for further details.

Default

no qos-policy-id-range

Parameters

start policy-id

Specifies the lower value of the ID range. The value must be less than or equal to the end value.

Values

1 to 65535

end policy-id

Specifies the upper value of the ID range. The value must be greater than or equal to the start value.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>spoke-sdp>mld-snooping query-interval)

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping query-interval)

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping query-interval)

[Tree] (config>service>vpls>sap>mld-snooping query-interval)

[Tree] (config>service>vpls>sap>igmp-snooping query-interval)

[Tree] (config>service>vpls>igmp-snooping query-interval)

[Tree] (config>service>vpls>mesh-sdp>mld-snooping query-interval)

[Tree] (config>service>vpls>mld-snooping query-interval)

Full Context

configure service vpls spoke-sdp mld-snooping query-interval

configure service vpls mesh-sdp igmp-snooping query-interval

configure service vpls spoke-sdp igmp-snooping query-interval

configure service vpls sap mld-snooping query-interval

configure service vpls sap igmp-snooping query-interval

configure service vpls igmp-snooping query-interval

configure service vpls mesh-sdp mld-snooping query-interval

configure service vpls mld-snooping query-interval

Description

This command configures the IGMP query interval. If the send-queries command is enabled, this parameter specifies the interval between two consecutive general queries sent by the system on this SAP or SDP.

The configured query-interval must be greater than the configured query-response-interval.

If send-queries is not enabled on this SAP or SDP, the configured query-interval value is ignored.

Default

query-interval 125

Parameters

seconds

Specifies the time interval, in seconds, that the router transmits general host-query messages

Values

2 to 1024

Values

config>service>vpls>igmp-snooping: 1 - 65535

config>service>vpls>sap>igmp-snooping: 2 - 1024

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mld query-interval)

[Tree] (config>router>mld>if query-interval)

Full Context

configure router mld query-interval

configure router mld interface query-interval

Description

This command specifies the frequency that the querier router transmits general host-query messages. The host-query messages solicit group membership information and are sent to the all-systems multicast group address, 224.0.0.1.

The no form of this command reverts to the default value.

Default

query-interval 125

Parameters

seconds

The time frequency, in seconds, that the router transmits general host-query messages.

Values

2 to 1024

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>igmp query-interval)

Full Context

configure service vprn igmp query-interval

Description

This command specifies the frequency that the querier router transmits general host-query messages. The host-query messages solicit group membership information and are sent to the all-systems multicast group address, 224.0.0.1.

Default

query-interval 125

Parameters

seconds

The time frequency, in seconds, that the router transmits general host-query messages.

Values

2 to 1024

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>mld>if query-interval)

[Tree] (config>service>vprn>mld query-interval)

Full Context

configure service vprn mld interface query-interval

configure service vprn mld query-interval

Description

This command specifies the frequency that the querier router transmits general host-query messages. The host-query messages solicit group membership information and are sent to the all-systems multicast group address, 224.0.0.1.

Default

query-interval 125

Parameters

seconds

The time frequency, in seconds, that the router transmits general host-query messages.

Values

2 to 1024

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>igmp>if query-interval)

Full Context

configure router igmp interface query-interval

Description

This command specifies the frequency that the querier router transmits general host-query messages. The host-query messages solicit group membership information and are sent to the all-systems multicast group address, 224.0.0.1.

Default

query-interval 125

Parameters

seconds

Specifies the frequency, in seconds, that the router transmits general host-query messages.

Values

2 to 1024

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template>igmp-snooping query-interval)

Full Context

configure service pw-template igmp-snooping query-interval

Description

This command configures the IGMP query interval. If the send-queries command is enabled, this parameter specifies the interval between two consecutive general queries sent by the system on this SAP or SDP.

The configured query-interval must be greater than the configured query-response-interval.

If send-queries is not enabled on this SAP or SDP, the configured query-interval value is ignored.

Default

query-interval 125

Parameters

seconds

Specifies the time interval, in seconds, that the router transmits general host-query messages.

Values

2 to 1024

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mld>if query-last-listener-interval)

Full Context

configure router mld interface query-last-listener-interval

Description

This command configures the frequency at which the querier router sends a group-specific query messages, including the messages sent in response to leave-group messages and is only applicable when the group interface is configured with the no sub-hosts-only command. The shorter the interval, the faster the loss of the last listener of a group can be detected. If nothing is configured, by default, the query-last-listener-interval takes the value defined in the config>router>mld context or in the config>service>vprn>mld context.

The no form of this command reverts to the default value.

Default

query-last-listener-interval 1

Parameters

seconds

Specifies the frequency, in seconds, at which query messages are sent.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>mld query-last-listener-interval)

[Tree] (config>service>vprn>mld>if query-last-listener-interval)

Full Context

configure service vprn mld query-last-listener-interval

configure service vprn mld interface query-last-listener-interval

Description

This command specifies the Max Response Time inserted into Group-Specific Queries sent in response to Leave Group messages, and is also the amount of time between Group-Specific Query messages. This value may be tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last member of a group.

The no form of this command reverts to the default value.

Default

query-last-listener-interval 1

Parameters

seconds

Specifies the frequency, in seconds, at which Group-Specific-Query packets are transmitted.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>igmp query-last-member-interval)

[Tree] (config>router>igmp>if query-last-member-interval)

Full Context

configure router igmp query-last-member-interval

configure router igmp interface query-last-member-interval

Description

This command configures the frequency at which the querier sends group-specific query messages including messages sent in response to leave-group messages. The lower the interval, the faster the detection of the loss of the last member of a group.

Default

query-last-member-interval 1

Parameters

seconds

Specifies the frequency, in seconds, at which query messages are sent.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>igmp query-last-member-interval)

Full Context

configure service vprn igmp query-last-member-interval

Description

This command configures the frequency at which the querier sends group-specific query messages including messages sent in response to leave-group messages. The lower the interval, the faster the detection of the loss of the last member of a group.

Default

query-last-member-interval 1

Parameters

seconds

Specifies the frequency, in seconds, at which query messages are sent.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping query-response-interval)

[Tree] (config>service>vpls>sap>mld-snooping query-response-interval)

[Tree] (config>service>vpls>sap>igmp-snooping query-response-interval)

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping query-response-interval)

[Tree] (config>service>vpls>spoke-sdp>mld-snooping query-response-interval)

[Tree] (config>service>vpls>mesh-sdp>mld-snooping query-response-interval)

Full Context

configure service vpls spoke-sdp igmp-snooping query-response-interval

configure service vpls sap mld-snooping query-response-interval

configure service vpls sap igmp-snooping query-response-interval

configure service vpls mesh-sdp igmp-snooping query-response-interval

configure service vpls spoke-sdp mld-snooping query-response-interval

configure service vpls mesh-sdp mld-snooping query-response-interval

Description

This command configures the IGMP query response interval. If the send-queries command is enabled, this parameter specifies the maximum response time advertised in IGMPv2 or IGMPv3 queries.

The configured query response interval must be smaller than the configured query interval.

If send-queries is not enabled on this SAP or SDP, the configured query response interval value is ignored.

The no form of this command reverts to the default value.

Default

query-response-interval 10

Parameters

seconds

Specifies the length of time to wait to receive a response to the host-query message from the host.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>igmp query-response-interval)

Full Context

configure service vprn igmp query-response-interval

Description

This command configures the query response interval on when the group interface is configured with the no sub-hosts-only command. If nothing is configured, by default, the query-response-interval takes the value defined in the config>router>igmp (or mld) context or in the config>service>vprn>igmp (or mld) context.

The no form of this command reverts to the default value.

Default

query-response-interval 10

Parameters

seconds

Specifies the length of time to wait to receive a host-query message response from the host.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mld query-response-interval)

[Tree] (config>router>mld>if query-response-interval)

Full Context

configure router mld query-response-interval

configure router mld interface query-response-interval

Description

This command specifies how long the querier router waits to receive a response to a host-query message from a host.

The no form of this command reverts to the default value.

Default

query-response-interval 10

Parameters

seconds

Specifies the length of time to wait to receive a response to the host-query message from the host.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>igmp>if query-response-interval)

[Tree] (config>router>igmp query-response-interval)

Full Context

configure router igmp interface query-response-interval

configure router igmp query-response-interval

Description

This command specifies how long the querier router waits to receive a response to a host-query message from a host.

Default

query-response-interval 10

Parameters

seconds

Specifies the length of time to wait to receive a response to the host-query message from the host.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>mld>if query-response-interval)

[Tree] (config>service>vprn>mld query-response-interval)

Full Context

configure service vprn mld interface query-response-interval

configure service vprn mld query-response-interval

Description

This command specifies how long the querier router waits to receive a response to a host-query message from a host.

Default

query-response-interval 10

Parameters

seconds

Specifies the length of time to wait to receive a response to the host-query message from the host.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template>igmp-snooping query-response-interval)

Full Context

configure service pw-template igmp-snooping query-response-interval

Description

This command configures the IGMP query response interval. If the send-queries command is enabled, this parameter specifies the maximum response time advertised in IGMPv2/v3 queries.

The configured query-response-interval must be smaller than the configured query-interval.

If send-queries is not enabled on this SAP or SDP, the configured query-response-interval value is ignored.

Default

query-response-interval 10

Parameters

seconds

Specifies the length of time to wait to receive a response to the host-query message from the host.

Values

1 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>igmp-snooping query-src-ip)

Full Context

configure service vpls igmp-snooping query-src-ip

Description

This command configures the IP source address used in IGMP or MLD queries.

The no form of this command removes the IP address from this configuration.

Parameters

ip-address

Specifies an IPv4 address in the form of a.b.c.d or an IPv6 address in the following form:

x:x:x:x:x:x:x:x:x:x:x:x:x:x:d.d.d.d

where:

x - [0 to FF]

d - [0 to 255]

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>mld-snooping query-src-ip)

Full Context

configure service vpls mld-snooping query-src-ip

Description

This command configures the IP source address used in MLD queries.

Parameters

ipv6-address

Specifies an IPv6 address in the following form:

x:x:x:x:x:x:x:x (eight 16-bit pieces)

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>sap>ingress>queue-override queue)

[Tree] (config>service>vpls>sap>ingress>queue-override queue)

[Tree] (config>service>vpls>sap>egress>queue-override queue)

[Tree] (config>service>ies>if>sap>egress>queue-override queue)

Full Context

configure service ies interface sap ingress queue-override queue

configure service vpls sap ingress queue-override queue

configure service vpls sap egress queue-override queue

configure service ies interface sap egress queue-override queue

Description

This command specifies the ID of the queue whose parameters are to be overridden.

The no form of this command removes the queue ID from the configuration.

Parameters

queue-id

Specifies the queue ID whose parameters are to be overridden.

Values

1 to 8 for SAP egress

1 to 32 for SAP ingress

create

Keyword used to create the queue ID. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>access>egr>qgrp>qover queue)

[Tree] (config>port>eth>network>egr>qgrp>qover queue)

Full Context

configure port ethernet access egress queue-group queue-overrides queue

configure port ethernet network egress queue-group queue-overrides queue

Description

This command associates a queue for use in a queue group template. 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. Each queue is identified within the template by a queue-id number. The template ensures that all queue groups created with the template’s name will have the same queue-ids providing a uniform structure for the forwarding class redirection commands in the SAP egress QoS policies. The parameters within the template queue will be used as the default settings for each queue in the actual queue group. The queue parameters may be individually changed for each queue in each queue group using per queue overrides.

The no form of this command removes the queue-id from the configuration.

Parameters

queue-id

Specifies the queue ID.

Values

1 to 8

create

Mandatory when creating an entry.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>access>ing>qgrp>qover queue)

Full Context

configure port ethernet access ingress queue-group queue-overrides queue

Description

This command associates a queue for use in a queue group template. 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. Each queue is identified within the template by a queue-id number. The template ensures that all queue groups created with the template’s name will have the same queue-ids providing a uniform structure for the forwarding class redirection commands in the SAP egress QoS policies. The parameters within the template queue will be used as the default settings for each queue in the actual queue group. The queue parameters may be individually changed for each queue in each queue group using per queue overrides.

The no form of this command removes the queue-id from the configuration.

Parameters

queue-id

Specifies the queue ID.

Values

1 to 32

create

Mandatory when creating an entry.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap>ingress>queue-override queue)

[Tree] (config>service>epipe>sap>egress>queue-override queue)

Full Context

configure service epipe sap ingress queue-override queue

configure service epipe sap egress queue-override queue

Description

This command specifies the ID of the queue whose parameters are to be overridden.

Parameters

queue-id

The queue ID whose parameters are to be overridden.

Values

1 to 32

create

This keyword is mandatory when creating a queue.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>sap>egress>queue-override queue)

[Tree] (config>service>vprn>if>sap>ingress>queue-override queue)

Full Context

configure service vprn interface sap egress queue-override queue

configure service vprn interface sap ingress queue-override queue

Description

This command specifies the ID of the queue whose parameters are to be overridden.

Parameters

queue-id

Specifies the queue ID whose parameters are to be overridden.

Values

1 to 32

create

Keyword used to create the group override instance.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>sap-ingress>fc queue)

Full Context

configure qos sap-ingress fc queue

Description

This command overrides the default queue mapping for fc fc-name. The specified queue-id must exist within the policy before the mapping can be made. When the forwarding class mapping is executed, all traffic classified to fc-name on a SAP using this policy.

The no form of this command sets the queue-id back to the default queue for the forwarding class.

Default

queue 1

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

1

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. The queue-group-name are configured in the config>qos>queue-group-templates egress and ingress contexts. This parameter is used when policy-based queue group redirection is desired. That is, the specific queue group to redirect to is named in the QoS policy.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>sap-ingress queue)

Full Context

configure qos sap-ingress queue

Description

This command creates the context to configure an ingress SAP QoS policy queue.

Explicit definition of an ingress queue’s type is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or best effort 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. When any best effort forwarding classes are mapped to the queue (be, af, l1, or l2), the queue is treated as best effort (be) by the hardware schedulers. The queue type must be defined at the time of queue creation within the policy.

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. Each queue acts as an accounting and (optionally) shaping device offering precise control over potentially expensive multicast, broadcast, and unknown unicast traffic. Only the back-end support of multipoint traffic (between the forwarding class and the queue based on forwarding type) needs to be defined. The individual classification rules used to place traffic into forwarding classes are not affected. Queues must be defined as multipoint at the time of creation within the policy.

The multipoint queues are for multipoint-destined service traffic. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service queue.

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.

Any billing or statistical queries about a multipoint queue on a non-multipoint service returns zero values. Any queue parameter information requested about a multipoint queue on a non-multipoint service returns the queue parameters in the policy. Buffers will not be allocated for multipoint queues on non-multipoint services. Buffer pool queries return zero values for actual buffers allocated and current buffer utilization.

The no form of this command removes the queue-id from the SAP ingress QoS policy and from any existing SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their default queues. When a queue is removed, any pending accounting information for each SAP queue created due to the definition of the queue in the policy is discarded.

Parameters

queue-id

The queue-id for the queue, expressed as an integer. The queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.

Values

1 to 32

queue-type

The expedite, best-effort, and auto-expedite queue types are mutually exclusive. Each defines the method that the system uses to service the queue from a hardware perspective. A keyword can be specified at the time the queue is created. If an attempt to change the keyword after the queue is initially defined, an error is generated.

Values

expedite, best-effort, auto-expedite

expedite — This keyword ensures that the queue is treated in an expedited manner independent of the forwarding classes mapped to the queue.

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. 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. When a single non-expedited forwarding class is mapped to the queue (be, af, l1, and l2), the queue automatically falls back to non-expedited status.

Default

auto-expedite

multipoint

This optional keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. If forwarding class unicast traffic is mapped to a multipoint queue, an error is generated and no changes are made to the current unicast traffic queue mapping.

A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute.

The multipoint keyword can be entered in the command line on a preexisting multipoint queue to edit queue-id parameters.

Default

non-multipoint (unicast queue)

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. The profiles are assigned according to the configuration of the forwarding class or the sub-forwarding class.

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. However, the converse is not valid and a queue in-profile mode should be capable of supporting the different priorities of traffic.

Default

priority-mode

create

Keyword creates an ingress SAP QoS policy queue.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>sap-egress>fc queue)

Full Context

configure qos sap-egress fc queue

Description

This command overrides the default queue mapping for fc fc-name. The specified queue ID must exist within the policy before the mapping can be made. When the forwarding class mapping is executed, all traffic is classified to fc-name on a SAP using this policy.

The no form of this command sets the queue-id back to the default queue for the forwarding class (queue 1).

Default

no queue

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 to 8

Default

1

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. The queue-group-name are configured in the config>qos>queue-group-templates egress and ingress contexts. This parameter is used when policy-based queue group redirection is desired. That is, the specific queue group to redirect to is named in the QoS policy.

instance-id

This parameter is used to specify the specific instance of a queue group with template queue-group-name to which this queue should be redirected. This parameter is only valid for queue groups on egress ports where policy-based redirection is required.

Values

1 to 40960

Default

1

port-redirect-group-queue

This keyword is used to mark a given forwarding class queue for redirection to an egress queue group queue. 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.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>sap-egress queue)

Full Context

configure qos sap-egress queue

Description

This command creates the context to configure an egress service access point (SAP) QoS policy queue.

Explicit definition of an egress queue’s type is supported. A single egress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or best effort 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. When any best effort forwarding classes are mapped to the queue (be, af, l1, or l2), the queue is treated as best effort by the hardware schedulers. The queue type must be defined at the time of queue creation within the policy.

The no form of this command removes the queue-id from the SAP egress QoS policy and from any existing SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their default queues. When a queue is removed, any pending accounting information for each SAP queue created due to the definition of the queue in the policy is discarded.

Parameters

queue-id

The ID for the queue, expressed as an integer. The queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.

Values

1 to 32

queue-type

Specifies the method that system uses to service the queue from a hardware perspective. A keyword can be specified at the time the queue is created. If an attempt is made to change the keyword after the queue is initially defined, an error is generated.

Values

expedite - Specifies that the queue is treated in an expedited manner independent of the forwarding classes mapped to the queue.

best-effort - Specifies that the queue is treated in a non-expedited manner independent of the forwarding classes mapped to the queue.

auto-expedite - 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. When a single non-expedited forwarding class is mapped to the queue (be, af, l1, and l2), the queue automatically falls back to non-expedited status.

Default

auto-expedite

create

Creates an entry for the queue.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>network-queue>fc queue)

Full Context

configure qos network-queue fc queue

Description

Commands in this context configure a QoS network-queue policy queue.

Explicit definition of an ingress queue’s type status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or best effort 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. When any best effort forwarding classes are mapped to the queue (be, af, l1, or l2), the queue is treated as best effort (be) by the hardware schedulers. The queue type must be defined at the time of queue creation within the policy.

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. Each queue acts as an accounting and (optionally) shaping device offering precise control over potentially expensive multicast, broadcast, and unknown unicast traffic. Only the back-end support of multipoint traffic (between the forwarding class and the queue based on forwarding type) needs to be defined. The individual classification rules used to place traffic into forwarding classes are not affected. Queues must be defined as multipoint at the time of creation within the policy.

The multipoint queues are for multipoint traffic.

The multipoint queues are for multipoint-destined service traffic. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service queue.

When a QoS policy with multipoint queues is applied to an Epipe or IES SAP, the multipoint queues are not created. Any billing or statistical queries about a multipoint queue on a non-multipoint service returns zero values. Any queue parameter information requested about a multipoint queue on a non-multipoint service returns the queue parameters in the policy. Buffers will not be allocated for multipoint queues on non-multipoint services. Buffer pool queries return zero values for actual buffers allocated and current buffer utilization.

The no form of this command removes the queue-id from the network-queue policy and from any existing SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their default queues. When a queue is removed, any pending accounting information for each SAP queue created due to the definition of the queue in the policy is discarded.

Parameters

queue-id

The queue-id for the queue, expressed as an integer. The queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.

Values

1 to 32

multipoint

This optional keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-id can only be used to forward multicast, broadcast, or unknown unicast ingress traffic.

A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated, and the command will not execute.

The multipoint keyword can be entered in the command line on a preexisting multipoint queue to edit queue-id parameters.

Default

Non-multipoint (unicast queue)

queue-type

The expedite, best-effort, and auto-expedite queue types are mutually exclusive. Each defines the method that the system uses to service the queue from a hardware perspective. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy. An internal mechanism that provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also needed. A keyword must be specified at the time the queue is created in the network-queue policy. If an attempt is made to change the keyword after the queue is initially defined, an error is generated.

Values

expedite, best-effort, auto-expedite

expedite — This keyword ensures that the queue is treated in an expedited manner independent of the forwarding classes mapped to the queue.

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. 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. When a single non-expedited forwarding class is mapped to the queue (be, af, l1, and l2), the queue automatically falls back to non-expedited status.

Default

auto-expedite

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>qgrps>ing>queue-group queue)

Full Context

configure qos queue-group-templates ingress queue-group queue

Description

This command creates a queue for use in a queue group template. When created, the defined queue-id acts as a repository for the default parameters for the queue. The template queue is created on each queue-group object that is created with the queue group template name. Each queue is identified within the template by a queue-id number. The template ensures that all queue groups created with the template name will have the same queue-ids providing a uniform structure for the forwarding class redirection commands in the SAP ingress QoS policies. The parameters within the template queue will be used as the default settings for each queue in the actual queue group. The queue parameters may be individually changed for each queue in each queue group using per queue overrides.

When a queue within a template is mapped by a forwarding class on any object, the queue may be edited, but not deleted.

The no form of this 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.

Parameters

queue-id

This required parameter identifies the queue that will either be created or edited within the queue group template.

Values

1 to 32

multipoint

This optional keyword creates an ingress multipoint queue. Multipoint queues in a queue group may be used by ingress VPLS for forwarding types multicast, broadcast or unknown within a forwarding class. For ingress IES and VPRN access SAPs, only multicast is supported. Multipoint queues are only supported on ingress queue group templates.

Default

non-multipoint (unicast queue)

queue-type

The queue types are mutually exclusive.

Values

expedite — This keyword ensures that the queue is treated in an expedited manner independent of the forwarding classes mapped to the queue.

best-effort — This keyword ensures that the queue is treated in a non-expedited manner independent of the forwarding classes mapped to the queue.

Default

best-effort

queue-mode

These keywords are optional and mutually exclusive when creating a new template queue. The keywords specify how the queue manages ingress explicitly profiled packets.

Values

profile-mode — Overrides the default priority mode of the queue and allows the adoption of color aware profiling within the queue. Forwarding classes and subclasses may be explicitly defined as in-profile or out-of-profile. Out-of-profile classified packets bypass the CIR rate associated with the queue, reserving it for the undefined or in-profile classified packets. If the template queue is not defined as profile-mode and the packet redirected to the queue is explicitly out-of-profile based on the classification rules, the queues within-CIR bandwidth may be consumed by the packet.

priority-mode — Defines that the SAP ingress QoS policy priority classification result will be honored by the queue. Priority mode is the default mode of the queue. High-priority packets are allowed into the queue up to the MBS defined for the queue. Low-priority packets are discarded at the low-priority MBS threshold that is derived from applying the low drop-tail percentage to the queue’s MBS.

create

Keyword used to create the queue ID instance.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>qgrps>egr>qgrp>fc queue)

Full Context

configure qos queue-group-templates egress queue-group fc queue

Description

This command is used to map the forwarding class to the specified queue-id. The specified queue-id must exist within the egress queue group template. When a queue is defined in a forwarding class mapping, that queue cannot be deleted unless the forwarding class mapping is moved to another queue within the template. Other criteria may also exist preventing the queue from being deleted from the template such as an applied SAP egress QoS policy mapping to the queue.

Parameters

queue-id

The specified queue-id must exist within the egress queue group template.

Values

1 to 8

Platforms

7705 SAR Gen 2

Context

[Tree] (cfg>qos>qgrps>egr>queue-group queue)

Full Context

configure qos queue-group-templates egress queue-group queue

Description

This command creates a queue for use in a queue group template. When created, the defined queue-id acts as a repository for the default parameters for the queue. The template queue is created on each queue group object that is created with the queue group template name. Each queue is identified within the template by a queue ID. The template ensures that all queue groups created with the template name will have the same queue-ids providing a uniform structure for the forwarding class redirection commands in the SAP egress QoS policies. The parameters within the template queue will be used as the default settings for each queue in the actual queue group. The queue parameters may be individually changed for each queue in each queue group using per queue overrides.

Parameters

queue-id

Specifies the queue ID. The specified queue-id must exist within the egress queue group template.

Values

1 to 8

queue-type

Specifies the method that the system uses to service the queue from a hardware perspective.

Values

expedite, best-effort

expedite — This keyword ensures that the queue is treated in an expedited manner independent of the forwarding classes mapped to the queue.

best-effort — This keyword ensures that the queue is treated in a non-expedited manner independent of the forwarding classes mapped to the queue.

Default

best-effort

Platforms

7705 SAR Gen 2

Context

[Tree] (config>log>acct-policy>cr queue)

Full Context

configure log accounting-policy custom-record queue

Description

This command specifies the queue-id for which counters will be collected in this custom record. The counters that will be collected are defined in egress and ingress counters.

The no form of this command reverts to the default value.

Parameters

queue-id

Specifies the queue-id for which counters will be collected in this custom record.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>network-queue queue)

Full Context

configure qos network-queue queue

Description

This command enters the context to configure a QoS network-queue policy queue.

Explicit definition of an ingress queue’s type status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or best effort 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. When any best effort forwarding classes are mapped to the queue (be, af, l1, or l2), the queue is treated as best effort (be) by the hardware schedulers. The queue type must be defined at the time of queue creation within the policy.

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. Each queue acts as an accounting and (optionally) shaping device offering precise control over potentially expensive multicast, broadcast, and unknown unicast traffic. Only the back-end support of multipoint traffic (between the forwarding class and the queue based on forwarding type) needs to be defined. The individual classification rules used to place traffic into forwarding classes are not affected. Queues must be defined as multipoint at the time of creation within the policy.

The multipoint queues are for multipoint traffic.

The multipoint queues are for multipoint-destined service traffic. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be mapped to a multipoint service queue.

When a QoS policy with multipoint queues is applied to an Epipe or IES SAP, the multipoint queues are not created. Any billing or statistical queries about a multipoint queue on a non-multipoint service returns zero values. Any queue parameter information requested about a multipoint queue on a non-multipoint service returns the queue parameters in the policy. Buffers will not be allocated for multipoint queues on non-multipoint services. Buffer pool queries return zero values for actual buffers allocated and current buffer utilization.

The no form of this command removes the queue-id from the network-queue policy and from any existing SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their default queues. When a queue is removed, any pending accounting information for each SAP queue created due to the definition of the queue in the policy is discarded.

Parameters

queue-id

The queue-id for the queue, expressed as an integer. The queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.

Values

1 to 32

multipoint

This optional keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-id can only be used to forward multicast, broadcast, or unknown unicast ingress traffic.

A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated, and the command will not execute.

The multipoint keyword can be entered in the command line on a preexisting multipoint queue to edit queue-id parameters.

Default

Non-multipoint (unicast queue)

queue-type

The expedite, best-effort, and auto-expedite queue types are mutually exclusive. Each defines the method that the system uses to service the queue from a hardware perspective. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy. An internal mechanism that provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also needed. A keyword must be specified at the time the queue is created in the network-queue policy. If an attempt is made to change the keyword after the queue is initially defined, an error is generated.

Values

expedite, best-effort, auto-expedite

expedite — This keyword ensures that the queue is treated in an expedited manner independent of the forwarding classes mapped to the queue.

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. 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. When a single non-expedited forwarding class is mapped to the queue (be, af, l1, and l2), the queue automatically falls back to non-expedited status.

Default

auto-expedite

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue queue-delay)

Full Context

configure qos queue-group-templates egress queue-group queue queue-delay

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 queue-delay before the mbs is configured.

If queue-delay is configured for an egress queue group queue, it is not possible to override the MBS for that queue.

The no form of this command disables the determination of the queue parameters based on the queue delay.

Default

no queue-delay

Parameters

delay

Specifies the target queue delay in ms.

Values

0 to 5000 (decimal)

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>sap>egress>agg-rate queue-frame-based-accounting)

Full Context

configure service ies interface sap egress agg-rate queue-frame-based-accounting

Description

This command enables frame-based accounting on all queues associated with the agg-rate context. Only supported on Ethernet ports. Packet byte offset settings are not included in the applied rate when queue frame based accounting is configured, however the offsets are applied to the statistics.

The no form of this command disables frame-based accounting.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap>egress>agg-rate queue-frame-based-accounting)

Full Context

configure service epipe sap egress agg-rate queue-frame-based-accounting

Description

This command is used to enable (or disable) frame based accounting on all policers and queues associated with the agg-rate context.

The command is supported on Ethernet ports only.

Packet byte offset settings are not included in the applied rate when queue frame based accounting is configured; however the offsets are applied to the statistics.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>egress>agg-rate queue-frame-based-accounting)

Full Context

configure service vpls sap egress agg-rate queue-frame-based-accounting

Description

This command is used to enabled frame-based accounting on all policers and queues associated with the agg-rate context. Only supported on Ethernet ports. Packet byte offset settings are not included in the applied rate when queue frame based accounting is configured; however the offsets are applied to the statistics.

The no form of this command disables the-frame based accounting.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>sap>egress>agg-rate queue-frame-based-accounting)

Full Context

configure service vprn interface sap egress agg-rate queue-frame-based-accounting

Description

This command is used to enabled (or disable) frame based accounting on all policers and queues associated with the agg-rate context. Only supported on Ethernet ports. Packet byte offset settings are not included in the applied rate when queue frame-based accounting is configured; the offsets are applied to the statistics.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>card>fp>ingress>access queue-group)

Full Context

configure card fp ingress access queue-group

Description

This command creates an instance of a named queue group template on the ingress forwarding plane of a given IOM/IMM. The queue-group-name and instance instance-id are mandatory parameters when executing the command.

The named queue group template can contain only policers. If it contains queues, then the command will fail.

The no form of this command deletes a specific instance of a queue group.

Parameters

queue-group-name

Specifies the name of the queue group template to be instantiated on the forwarding plane of the IOM/IMM, up to 32 characters. The queue-group-name must correspond to a valid ingress queue group template name, configured under config>qos>queue-group-templates.

instance-id

Specifies the instance of the named queue group to be created on the IOM/IMM ingress forwarding plane.

Values

1 to 65535

create

Keyword used to associate the queue group. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>card>fp>ingress>network queue-group)

Full Context

configure card fp ingress network queue-group

Description

This command creates a queue-group instance in the network ingress context of a forwarding plane.

Only a queue-group containing policers can be instantiated. If the queue-group template contains policers and queues, the queues are not instantiated. If the queue-group contains queues only, the instantiation in the data path is failed.

One or more instances of the same policer queue-group name and/or a different policer queue-group name can be created on the network ingress context of a forwarding plane.

The queue-group-name must be unique within all network ingress and access ingress queue groups in the system. The queue-group instance-id must be unique within the context of the forwarding plane.

The no form of this command deletes the queue-group instance from the network ingress context of the forwarding plane.

Parameters

queue-group-name

Specifies the name of the queue group template up to 32 characters.

instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 65535

create

Keyword used to create the queue-group instance.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>network>egress queue-group)

Full Context

configure port ethernet network egress queue-group

Description

This command configures a queue-group instance in the network egress context of a port.

Queue-groups containing queues only or policers and queues can be instantiated. When a port is a LAG, one instance of the queue-group is instantiated on each member link.

One or more instances of the same queue-group name and/or a different queue-group name can be created in the network egress context of a port.

The queue-group-name must be unique within all network egress and access egress queue groups in the system. The queue-group instance-id must be unique within the context of the port.

The no version of this command deletes the queue-group instance from the network egress context of the port.

Parameters

queue-group-name

Specifies the name of the queue group template up to 32 characters.

instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>access>egr queue-group)

[Tree] (config>port>ethernet>access>ing queue-group)

Full Context

configure port ethernet access egress queue-group

configure port ethernet access ingress queue-group

Description

This command creates an ingress or egress queue group on an Ethernet port. A queue group is a collection of queues identified by a group name. Queue groups created on access ports are used as an alternative queue destination for SAPs.

Within a SAP, a forwarding class may be redirected from the local SAP queue to a port queue group queue. The forwarding classes from multiple SAPs may be redirected to the same queue group which can be used to minimize the number of per-SAP queues.

Queue groups may be created on both access and network oriented ports. When the port is in access mode, the queue groups must be created within the port access node.

Within the access node, queue groups are also configured as ingress or egress. Access ingress queue groups can only be used by ingress SAP forwarding classes and only a single ingress queue group per port is supported. Multiple access egress queue groups may be created on a single port and are used by egress SAP forwarding classes. The instance-id parameter identifies different instances of the same queue group template. Creating multiple queue groups with a different instance ID but the same queue group name results in separate queue groups being created on the port. The instance-id parameter is only valid for egress queue groups on access ports.

When the queue group is created in an ingress port context, the group-name must be an existing ingress queue group template. Similarly, queue groups created in an egress port context must have a group-name of an existing egress queue group template. Two ingress queue groups with the same name cannot be created on the same port. Two egress queue groups can only be created on the same port with the same queue group template name if they have different instance-id values.

The queues defined in the template are created on the queue group. The queue parameters within the template are used as the default queue parameters for each queue in the queue group. The default queue parameters for each queue may be overridden on the queue group with specific queue parameters.

Each queue group supports the application of a scheduler-policy for the purpose of managing the queues within the group into an aggregate SLA. The queues defined within the template may be configured with parent scheduler defining the mapping of a queue to one of the schedulers within the scheduler policy. Egress queue groups also support the agg-rate parameter and the queues in the egress template support the port-parent command. Each command is used for configuring egress port virtual scheduling behavior.

Each queue group allows the application of an accounting policy and the ability to enable and disable collecting statistics. The statistics are derived from the queue counters on each queue within the queue group. The accounting policy defines which queue counters are collected and to which accounting file they will be written.

A queue group does not have an administrative shutdown or no shutdown command. A queue group is considered to be always on once created.

When creating a queue group, the system will attempt to allocate queue resources based on the queues defined in the queue group template. If the appropriate queue resources do not currently exist, the queue group will not be created. Ingress port queue groups do not support the shared-queuing or multipoint-shared queuing behavior.

When the queue group is created on a LAG (Link Aggregation Group), it must be created on the primary port member. The primary port member is the port with the lowest port ID based on the slot, MDA position and port number on the MDA. A queue group created on the primary LAG port will be automatically created on all other port members. If a new port is being added to a LAG with an existing queue group, the queue group must first be created on the port prior to adding the port to the LAG. If the LAG queue group has queue overrides, the queue overrides must also be defined on the port queue group prior to adding the port to the LAG.

A port queue group cannot be removed from the port when a forwarding class is currently redirected to the group. All forwarding class redirections must first be removed prior to removing the queue group.

Parameters

queue-group-name

The group-name parameter is required when executing the port queue-group command. The specified group-name must exist as an ingress or egress queue group template depending on the ingress or egress context of the port queue group. Only a single queue group may be created on an ingress port. Multiple queue groups may be created on an egress port.

instance-id

Specifies the identification of a specific instance of the queue-group.

Values

1 to 65535

create

Keyword used to associate the queue group. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>qgrps>egress queue-group)

[Tree] (config>qos>qgrps>ingress queue-group)

Full Context

configure qos queue-group-templates egress queue-group

configure qos queue-group-templates ingress queue-group

Description

This command creates a queue group template. The system does not maintain default queue groups or queue group templates. Each queue group template used in the system must be explicitly created.

The no form of this command removes the specified queue group template from the system. If the queue group template is currently in use by an ingress port, the command will fail. If queue-group-name does not exist, the command has no effect and does not return an error.

Parameters

queue-group-name

Specifies the name of the queue group template up to 32 characters. Each ingress queue group template must be uniquely named within the system. Multiple ingress queue group templates may not share the same name. An ingress and egress queue group template may share the same name.

create

Keyword used to create the queue group instance. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos queue-group-templates)

Full Context

configure qos queue-group-templates

Description

Commands in this context define ingress and egress queue group templates.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>sap>egress queue-override)

[Tree] (config>service>ies>if>sap>ingress queue-override)

[Tree] (config>service>vpls>sap>ingress queue-override)

[Tree] (config>service>vpls>sap>egress queue-override)

[Tree] (config>service>vprn>if>sap>ingress queue-override)

[Tree] (config>service>ies>if>sap>egress queue-override)

Full Context

configure service vprn interface sap egress queue-override

configure service ies interface sap ingress queue-override

configure service vpls sap ingress queue-override

configure service vpls sap egress queue-override

configure service vprn interface sap ingress queue-override

configure service ies interface sap egress queue-override

Description

Commands in this context configure override values for the specified SAP egress or ingress QoS queue. These values override the corresponding ones specified in the associated SAP egress QoS policy.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap>egress queue-override)

[Tree] (config>service>epipe>sap>ingress queue-override)

Full Context

configure service epipe sap egress queue-override

configure service epipe sap ingress queue-override

Description

Commands in this context configure override values for the specified SAP egress or ingress QoS queue. These values override the corresponding ones specified in the associated SAP egress or ingress QoS policy. If the policy was created as a template policy, this command overrides the parameter and its description and queue parameters in the policy.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>access>ing>qgrp queue-overrides)

[Tree] (config>port>ethernet>network>egr>qgrp queue-overrides)

[Tree] (config>port>ethernet>access>egr>qgrp queue-overrides)

Full Context

configure port ethernet access ingress queue-group queue-overrides

configure port ethernet network egress queue-group queue-overrides

configure port ethernet access egress queue-group queue-overrides

Description

Commands in this context define optional queue parameter overrides for each queue within the queue group.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>card>fp>ingress>network queue-policy)

Full Context

configure card fp ingress network queue-policy

Description

This command specifies the network-queue policy which defines queue parameters such as CBS, high priority only burst size, MBS, CIR and PIR rates, as well as forwarding-class to queue mappings. The network-queue policy is defined in the config>qos>network-queue context.

Default

queue-policy default

Parameters

name

Specifies an existing network-queue policy name, up to 32 characters long.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>network queue-policy)

Full Context

configure port ethernet network queue-policy

Description

This command specifies the existing network queue policy which defines queue parameters such as CBS, high priority only burst size, MBS, CIR and PIR rates, as well as forwarding-class to queue mappings. The network-queue policy is defined in the config>qos>network-queue context.

Default

queue-policy default

Parameters

name

Specifies an existing network-queue policy name. The name can be up to 32 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>dot1x quiet-period)

Full Context

configure port ethernet dot1x quiet-period

Description

This command configures the period between two authentication sessions during which no EAPOL frames are sent by the router.

The no form of this command returns the value to the default.

Default

quiet-period 60

Parameters

seconds

Specifies the quiet period in seconds.

Values

1 to 3600

Platforms

7705 SAR Gen 2

Context

[Tree] (candidate quit)

Full Context

candidate quit

Description

This command exits the edit-cfg mode. The contents of the current candidate will not be deleted and the operator can continue editing the candidate later.

Platforms

7705 SAR Gen 2