egress
config>service>vprn>if>sap
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure egress SAP Quality of Service (QoS) policies and filter policies.
If no SAP egress QoS policy is defined, the system default SAP egress QoS policy is used for egress processing. If no egress filter is defined, no filtering is performed.
agg-rate-limit agg-rate
no agg-rate-limit
config>service>vprn>if>sap>egress
Supported on all 7210 SAS platforms as described in this document
This command defines a maximum total rate for all egress queues on a service SAP.
The port scheduler mode should be set to ‟sap-based” scheduling mode before using this command. The egress port scheduler enforces the aggregate queue rate for the SAP as it distributes its bandwidth to all the SAPs configured on the port. The port scheduler stops distributing bandwidth to member queues when it has detected that the aggregate rate limit has been reached.
A SAP aggregate scheduler is created for each instance of the SAP queues created on each of the member ports of the LAG. For a LAG, the port scheduler mode configured for the primary port is used for all the member ports of the LAG.
The scheduler mode is specified by the scheduler-mode command. To implement the agg-rate-limit, the scheduler mode must be specified as ‟sap-based”. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about the scheduler-mode command.
The no form of this command removes the aggregate rate limit from the SAP or multi-service site.
Specifies the aggregate rate, in kilobits-per-second, that the queues on the SAP or MSS can operate.
aggregate-meter-rate rate-in-kbps [burst burst-in-kbits] [enable-stats]
no aggregate-meter-rate
config>service>vprn>if>sap>egress
Supported on all 7210 SAS platforms as described in this document
This command associates a set of two counters to count total forwarded packets and octets and total dropped packets and octets. When the counter is enabled, the number of resources required increases by twice the number of resources taken up when counter is not used. If the enable-stats keyword is specified during the creation of the meter, the counter is allocated by the software, if available. To free up the counter and relinquish its use, the user can use the no aggregate-meter-rate command, and then recreate the meter using the aggregate-meter-rate command.
If egress rrame-based accounting is used, the SAP egress aggregate meter rate accounts for the Ethernet frame overhead. The system accounts for 12 bytes of IFG and 8 bytes of start delimiter. Frame-based counting does not affect the count of octets maintained by the counter, if it is in use.
Before enabling this command for a SAP, resources must be allocated to this feature from the egress internal TCAM resource pool using the configure system resource-profile egress-internal-tcam egress-sap-aggregate-meter command. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.
The egress aggregate meter is not FC aware. The forward and drop decisions are made based on the order the packets are sent out of the SAP by the egress port scheduler.
The no form of this command removes the egress aggregate policer from use.
no aggregate-meter-rate
Specifies the rate in kilobits per second.
Specifies the burst size for the policer in kilobits. The burst size cannot be configured without configuring the rate.
Keyword to specify whether the counter that counts forwarded and dropped packets must be allocated.
filter ip ip-filter-id ipv6 ipv6-filter-id
filter [mac mac-filter-id]
no filter [ip ip-filter-id | ipv6 ipv6-filter-id]
no filter [mac mac-filter-id]
no filter
config>service>vprn>if>sap>egress
config>service>vprn>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command associates an IP filter policy with an ingress or egress SAP or IP interface. Filter policies control the forwarding and dropping of packets based on IP matching criteria.
The filter command is used to associate a filter policy that has a specified ip-filter-id with an ingress or egress SAP. The ip-filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message is returned.
In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID is not removed from the system unless the scope of the created filter is set to local.
Specifies the IP filter policy. The filter ID must already exist within the created IP filters.
Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.
Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.
qos policy-id
qos policy-id [enable-table-classification]
no qos
config>service>vprn>if>sap>egress
config>service>vprn>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command associates a QoS policy with an ingress or egress SAP or IP interface.
QoS ingress and egress policies are important for the enforcement of SLA agreements. The policy ID must be defined before 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 only allows 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 policy of the same or different type replaces the earlier one with the new policy.
On the 7210 SAS-R6 and 7210 SAS-R12 (ingress), using the enable-table-classification keyword enables the use of IP DSCP tables to assign FC and profile on a per-SAP ingress basis. The match-criteria configured in the service ingress policy, which require CAM resources, are ignored. Only meters from the service ingress policy are used (and the meters still require CAM resources). The IP DSCP classification policy configured in the SAP ingress policy is used to assign FC and profile. The default FC is assigned from the SAP ingress policy.
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 value.
Specifies the ingress or egress policy ID to associate with SAP or IP interface on ingress or egress. The policy ID must already exist.
Keyword that enables the use of table-based classification instead of CAM-based classification at SAP ingress. The FC and profile are taken from the IP DSCP classification policy configured in the ingress policy, along with the meters from the SAP ingress policy. Match-criteria entries in the SAP ingress policy are ignored.
ingress
config>service>vprn>if>sap
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure ingress SAP QoS policies and filter policies.
If no SAP ingress QoS policy is defined, the system default SAP ingress QoS policy is used for ingress processing. If no ingress filter is defined, no filtering is performed.
aggregate-meter-rate rate-in-kbps [burst burst-in-kbits]
no aggregate-meter-rate
config>service>vprn>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command configures the SAP aggregate policer. The rate of the SAP aggregate policer must be specified by the user. The user can optionally specify the burst size for the SAP aggregate policer. The aggregate policer monitors the traffic on different FCs and determines the destination of the packet. The packet is either forwarded to an identified profile or dropped.
The following table lists information about the final disposition of the packet based on the operating rate of the per-FC policer and the per-SAP aggregate policer.
| Per-FC meter operating rate | Per-FC assigned color | SAP aggregate meter operating rate | SAP aggregate meter color | Final packet color |
|---|---|---|---|---|
Within CIR |
Green |
Within PIR |
Green |
Green or In-profile |
Within CIR1 |
Green |
Above PIR |
Red |
Green or In-profile |
Above CIR, Within PIR |
Yellow |
Within PIR |
Green |
Yellow or Out-of-Profile |
Above CIR, Within PIR |
Yellow |
Above PIR |
Red |
Red or Dropped |
Above PIR |
Red |
Within PIR |
Green |
Red or Dropped |
Above PIR |
Red |
Above PIR |
Red |
Red or Dropped |
When the SAP aggregate policer is configured, the per-FC policer can be configured only in ‟trtcm2” mode (RFC 4115).
The SAP ingress meter counters increment the packet or octet counts based on the final disposition of the packet.
If ingress frame-based accounting is used, the SAP aggregate meter rate accounts for the Ethernet frame overhead. The system accounts for 12 bytes of IFG and 8 bytes of start delimiter.
The no form of this command removes the aggregate policer from use.
no aggregate-meter-rate
Specifies the rate in kilobits per second.
Specifies the burst size for the policer in kilobits. The burst size cannot be configured without configuring the rate.
[no] meter-override
config>service>vprn>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command, within the SAP ingress contexts, enables the context for specific overrides to one or more meters created on the SAP through the SAP ingress QoS policies.
The no form of this command removes existing meter overrides.
no meter-override
meter meter-id [create]
no meter meter-id
config>service>vprn>if>sap>ingress>meter-override
Supported on all 7210 SAS platforms as described in this document
This command, within the SAP ingress contexts, enables the context for specific overrides to a specific meter created on the SAP through a sap-ingress QoS policies.
The no form of this command is used to remove any existing overrides for the specified meter-id.
Specifies the meter ID. The specified meter-id must exist within the SAP ingress QoS policy applied to the SAP. If the meter is not currently used by any forwarding class or forwarding type mappings, the meter does noty exist on the SAP. This does not preclude creating an override context for the meter-id.
Keyword that is required when a meter meter-id override node is being created and the system is configured to expect explicit confirmation that a new object is being created. When the system is not configured to expect explicit confirmation, the create keyword is not required.
adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
no adaptation-rule
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document
This command overrides specific attributes of the specified meter adaptation rule parameters. The adaptation rule controls the method used by the system to derive the operational CIR and PIR settings when the meter is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.
The no form of this command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.
no adaptation-rule
Keyword that defines the constraints enforced when adapting the PIR rate defined within the meter-override meter command. The pir keyword requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the meter-override command is not specified, the default applies.
When the meter mode in use is ‟trtcm2,” this parameter is interpreted as EIR value. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide for a description and relevant notes for meter modes.
Keyword that defines the constraints enforced when adapting the CIR rate defined within the meter-override meter command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies.
Specifies the criteria to use to compute the operational CIR and PIR values for this meter, while maintaining a minimum offset.
cbs size [kbits | bytes | kbytes]
no cbs
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document
This command provides a mechanism to override the default CBS for the meter. The size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the CBS value, the packets are marked as in-profile by the meter to indicate that the traffic is complying with meter configured parameters.
The no form of this command reverts the CBS size to the default value.
32 kbits
Specifies the value in either kbits, bytes, or kilobytes.
mbs size [kbits | bytes | kbytes]
no mbs
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document
This command overrides the default MBS for the meter. The size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the MBS value, the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.
The no form of this command reverts the MBS size to the default value.
512kbits
Specifies the value in either kbits, bytes, or kilobytes.
mode mode
no mode
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document
This command is used to override the SAP ingress QoS policy configured mode parameters for the specified meter-id.
The no form of this command restores the policy defined metering and profiling mode to a meter.
Specifies the rate mode of the meter-override.
rate cir cir-rate [pir pir-rate]
no rate
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document
This command is used to override the SAP ingress QoS policy configured rate parameters for the specified meter-id.
The no form of this command restores the policy defined metering and profiling rate to a meter.
max
The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.
Specifies the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be entered as a positive integer.
When the meter mode is set to ‟trtcm2,” the PIR value is interpreted as the EIR value. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide for more information.
The actual PIR rate is dependent on the queue adaptation-rule parameters and the hardware where the queue is provisioned.
Specifies to override the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be entered as a positive integer.
ipsec-gw name
no ipsec-gw
config>service>vprn>if>sap
Supported on all 7210 SAS platforms as described in this document
This command configures the IPSec gateway.
Specifies the IPSec gateway name, up to 32 characters.
default-secure-service service-id ipsec-interface ip-int-name
no default-secure-service
config>service>vprn>if>sap>ipsec-gw
Supported on all 7210 SAS platforms as described in this document
This command specifies a service ID or service name of the default security service used by this SAP IPSec gateway.
Specifies a default secure service.
default-tunnel-template ipsec template identifier
no default-tunnel-template
config>service>vprn>if>sap>ipsec-gw
Supported on all 7210 SAS platforms as described in this document
This command configures the default tunnel policy template for the gateway.
1 to 2048
ike-policy ike-policy-id
no ike-policy
config>service>vprn>if>sap>ipsec-gw
Supported on all 7210 SAS platforms as described in this document
This command configures the IKE policy for the gateway.
Specifies the IKE policy ID.
local-gateway-address ip-address
no local-gateway-address
config>service>vprn>if>sap>ipsec-gw
Supported on all 7210 SAS platforms as described in this document
This command configures the ipsec-gateway local address.
Specifies the IP unicast address.
pre-shared-key key
no pre-shared-key
config>service>vprn>if>sap>ipsec-gw
Supported on all 7210 SAS platforms as described in this document
This command specifies the shared secret between the two peers forming the tunnel.
Specifies a pre-shared key for dynamic keying.
multi-service-site customer-site-name
no multi-service-site customer-site-name
config>service>vprn>if>sap
config>service>vprn>sub-if>grp-if>sap
Supported on all 7210 SAS platforms as described in this document
This command creates a new customer site or edits an existing customer site using the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple SAPs.
The scheduler policy association with the customer site prevents the scheduler policy from being deleted until after the scheduler policy is removed from the customer site. The multi-service-site object generates a log message indicating that the association was deleted because of scheduler policy removal.
When the multi-service customer site is created, an ingress and egress scheduler policy association does not exist. This does not prevent the site from being assigned to a chassis slot or prevent service SAP assignment. After the site has been created, the ingress and egress scheduler policy associations can be assigned or removed at any time.
If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications to an existing site affect all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing queues that rely on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following.
The maximum number of customer sites defined for the chassis slot has not been met.
The customer-site-name is valid.
The create keyword is included in the command line syntax (if the system requires it).
When the maximum number of customer sites is exceeded, a configuration error occurs; the command does not execute and the CLI context does not change.
If the customer-site-name is invalid, a syntax error occurs; the command does not execute and the CLI context does not change.
Specifies a unique customer site name within the context of the customer.
[no] queue-override
config>service>epipe>sap>ingress
config>service>vpls>sap>ingress
config>service>ies>sap>ingress
config>service>vprn>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command overrides 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.
[no] queue queue-id
config>service>epipe>sap>ingress>queue-override
config>service>vpls>sap>ingress>queue-override
config>service>ies>sap>ingress>queue-override
config>service>vprn>sap>ingress>queue-override
Supported on all 7210 SAS platforms as described in this document
This command specifies the ID of the queue whose parameters are to be overridden.
Specifies the queue ID whose parameters are to be overridden.
adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
no adaptation-rule
config>service>epipe>sap>ingress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
config>service>ies>sap>ingress>queue-override>queue
config>service>vprn>sap>ingress>queue-override>queue
Supported on all 7210 SAS platforms as described in this document
This command overrides specific attributes of the specified queue adaptation rule parameters. The adaptation rule controls the method used by the system to derive the operational CIR and PIR settings when the queue is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.
The no form of this command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.
no adaptation-rule
Keyword that defines the constraints enforced when adapting the PIR rate defined using the queue queue-id rate command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the rate command is not specified, the default applies.
Keyword that defines the constraints enforced when adapting the CIR rate defined using the queue queue-id rate command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies.
Specifies the criteria to use to compute the operational CIR and PIR values for this queue, while maintaining a minimum offset.
port-parent [cir-level cir-level] [pir-level pir-weight]
config>service>epipe>sap>ingress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
config>service>ies>sap>ingress>queue-override>queue
config>service>vprn>sap>ingress>queue-override>queue
Supported on all 7210 SAS platforms as described in this document
This command configures the queue parameters cir-level and pir-weight. The system creates and associates a port-scheduler with every access port on the system. Every queue within a SAP is associated with the port scheduler available on the port on which the SAP is created. The port scheduler uses these parameters to apportion the bandwidth to all the queues competing for the available bandwidth.
Queues with the cir-level value set to 8 are treated differently by the software than other queues configured with different cir-level values. The PIR rate values configured for the cir-level 8 queues are ignored. Only CIR rate value is used and the PIR is set to the CIR value. In addition, when executing the no form of the rate command for a queue configured at cir-level 8, the default CIR (and PIR) value is set to 1.
The no form of this command sets the cir-level and pir-weight to default values.
port-parent cir-level 1 pir-weight 1
Specifies the priority of the queue with respect to other queues. The priority of the queue is used only in the CIR loop. Level "8" is the highest priority and level "1" is the lowest priority.
In the PIR loop, the priority of the queues cannot be configured. The system assigns the priority to the queues based on the cir-level associated with the queue.
Specifies the relative weight of the queue with respect to the other queues. The weight parameter is used only in the PIR loop. If a queue level parameter is set to ‟8,” the weight parameter is ignored by the system.
queue-mgmt name
config>service>epipe>sap>ingress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
config>service>ies>sap>ingress>queue-override>queue
config>service>vprn>sap>ingress>queue-override>queue
Supported on all 7210 SAS platforms as described in this document
This command specifies the WRED and buffer parameters associated with the queue.
All the queues in the system allocate buffers from the system pool.
Specifies the name of the queue-management policy.
rate pir-rate [cir cir-rate]
no rate
config>service>epipe>sap>ingress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
config>service>ies>sap>ingress>queue-override>queue
config>service>vprn>sap>ingress>queue-override>queue
Supported on all 7210 SAS platforms as described in this document
This command overrides specific attributes of the specified queue PIR and CIR parameters. The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.
The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile packets are preferentially queued by the system at egress and at subsequent next-hop nodes where the packet can traverse. To be properly handled as in-profile or out-of-profile throughout the network, the packets must be marked accordingly for profiling at each hop.
The CIR can be used by the queue parent command cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.
The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.
The no form of this command reverts all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).
rate max cir 0
The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.
Specifies the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be entered as a positive integer.
The actual PIR rate is dependent on the queue adaptation-rule parameters and the actual hardware where the queue is provisioned.
Specifies to override the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.
Fractional values are not allowed and must be entered as a positive integer. The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers or queues.
[no] scheduler-override
config>service>vprn>if>sap>egress
config>service>vprn>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command specifies the set of attributes whose values have been overridden via management on this virtual scheduler. Clearing a specified flag reverts the corresponding overridden attribute to the value defined by the ingress scheduler policy on the SAP.
scheduler scheduler-name
no scheduler scheduler-name
config>service>vprn>if>sap>egress>sched-override
config>service>vprn>if>sap>ingress>sched-override
Supported on all 7210 SAS platforms as described in this document
This command overrides attributes of the specified scheduler name.
A scheduler defines a bandwidth control that limits each child (other schedulers and queues) associated with the scheduler. Scheduler objects are created within the hierarchical tiers of the policy. It is assumed that each scheduler created has queues or other schedulers defined as child associations. The scheduler can be a child (take bandwidth from a scheduler in a higher tier, except for schedulers created in tier 1). A total of 32 schedulers can be created within a single scheduler policy with no restriction on the distribution between the tiers.
Each scheduler must have a unique name within the context of the scheduler policy; however the same name can be reused in multiple scheduler policies. If scheduler-name already exists within the policy tier level (regardless of the inclusion of the create keyword), the context changes to that scheduler name for the purpose of editing the scheduler parameters. Modifications made to an existing scheduler are executed on all instantiated schedulers created through association with the policy of the edited scheduler. This can cause queues or schedulers to become orphaned (invalid parent association) and adversely affect the ability of the system to enforce service level agreements (SLAs).
If the scheduler-name exists within the policy on a different tier (regardless of the inclusion of the keyword create), an error occurs and the current CLI context does not change.
If the scheduler-name does not exist in this or another tier within the scheduler policy, it is assumed that an attempt is being made to create a scheduler of that name. The success of the command execution is dependent on the following.
The maximum number of schedulers has not been configured.
The provided scheduler-name is valid.
The create keyword is entered with the command if the system is configured to require it (enabled in the environment create command).
When the maximum number of schedulers has been exceeded on the policy, a configuration error occurs and the command does not execute nor does the CLI context change. If the provided scheduler-name is invalid, a name syntax error occur, the command does not execute, and the CLI context does not change.
Specifies the name of the scheduler.
Optional keyword that explicitly specifies that it is acceptable to create a scheduler with the specified scheduler-name. If the create keyword is omitted, scheduler-name is not created when the system environment variable create is set to true. This safeguard is intended to avoid accidental creation of system objects (such as schedulers) while attempting to edit an object with a mistyped name or ID. The keyword has no effect when the object already exists.
rate pir-rate [cir cir-rate]
no rate
config>service>vprn>if>sap>egress>sched-override>scheduler
Supported on all 7210 SAS platforms as described in this document
This command overrides attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler ‟within CIR” distribution phase.
The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The parent scheduler may not have the available bandwidth to meet the scheduler needs, or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler because of insufficient offered load or limits to their own maximum rates.
When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler assumes that an infinite amount of bandwidth is available and allows all child queues and schedulers to operate at their maximum rates.
The no form of this command reverts all queues created with this queue-id by association with the QoS policy to the default PIR and CIR parameters.
Specifies the multiplier used to determine the PIR rate at which the queue operates. A value of 0 to 100000000 or the keyword max or sum is accepted. Any other value results in an error without modifying the current PIR rate.
To calculate the actual PIR rate, the rate described by the queue rate is multiplied by the pir-rate.
The SAP ingress context for PIR is independent of the defined forwarding class (fc) for the queue. The default pir and definable range is identical for each class. The PIR in effect for a queue defines the maximum rate at which the queue is allowed to forward packets in a specified second, therefore shaping the queue output.
The PIR parameter for SAP ingress queues does not have a negation (no) function. To revert the queue PIR rate to the default value, that value must be specified as the PIR value.
Specifies a step-multiplier value that specifies the multiplier used to determine the CIR rate at which the queue operates. A value of 0 to 250 or the max keyword is accepted. Any other value results in an error without modifying the current CIR rate.
To calculate the actual CIR rate, the rate described by the rate pir pir-rate is multiplied by the cir cir-rate. If the cir is set to max, the CIR rate is set to infinity.
The SAP ingress context for CIR is dependent on the defined forwarding class (fc) for the queue. The default CIR and definable range is different for each class. The CIR in effect for a queue defines both its profile (in or out) marking level as well as the relative importance compared to other queues for scheduling purposes during congestion periods.