7705 SAR Interfaces
352
Interface Configuration Guide
3HE 11011 AAAC TQZZA Edition: 01
For access egress per-customer aggregate shaping, the shaper policy is assigned to a port
and SAPs on that port must be bound to a shaper group within the shaper policy bound to
that port.
The shaper policy defines shaper parameters such as shaper group, and PIR and CIR rates.
The shaper policy is defined in the config>qos>shaper-policy context. Refer to the
7705 SAR Quality of Service Guide, “QoS for Hybrid Ports” and “Per-Customer Aggregate
shapers (Multiservice Site)”, for more information.
The no form of this command reverts to the default.
Default “default”
Parameters name — specifies an existing shaper policy name
unshaped-sap-cir
Syntax unshaped-sap-cir cir-rate
no unshaped-sap-cir
Context config>port>ethernet>access>egress
Description This command sets the CIR rate for the aggregate of all the unshaped 4-priority SAPs on the
port. The default cir-rate is 0 kb/s. When the cir-rate is set to max, the CIR rate adopts the
maximum rate of the port, which is set using the egress-rate sub-rate command.
If the cir-rate is higher than the sub-rate, the cir-rate is stored in the configuration database
but the sub-rate limit is used.
On a Gen-3-based port, this command can be set for mix-and-match LAG SAP purposes, but
is not applied to the Gen-3-based port. See LAG Support on Mixed-Generation Hardware for
more information.
The no form of the command sets the unshaped-sap-cir CIR rate to 0 kb/s.
Note:
• The port shaper rate applies to the bulk of access and network traffic. Thus, once the
configured egress shaper rate is reached, both the access and network traffic
scheduling pauses.
• For hybrid ports, there can be a single shaper policy on access egress and a single
shaper policy on network egress. Therefore, all the SAP traffic and all the network
traffic is each bound to its own shaper group in the shaper policy (access and network
shaper policy, respectively). In other words, shaped SAPs and the bulk/aggregate of
unshaped SAPs are shaped together as per the shaper policy assigned to the access
egress. A similar behavior applies to network traffic, where the shaped interfaces and
the bulk/aggregate of unshaped interfaces are shaped together as per the shaper
policy assigned to the network egress.
To Next Page
Loading...
