egress
config>service>vprn>if>sap
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
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.
ingress
config>service>vprn>if>sap
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Commands in this context configure ingress SAP Quality of Service (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, excluding platforms configured in the access-uplink operating mode; not supported on 7210 SAS-Sx 10/100GE
This command allows the user to configure 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 sum of CIR of the individual FCs configured under the SAP cannot exceed the PIR rate configured for the SAP. Though the 7210 SAS software does not block this configuration, it is not recommended for use.
The following table provides 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, per FC policer can be only configured in ‟trtcm2” mode (RFC 4115).
The meter modes ‟srtcm” and ‟trtcm1” are used in the absence of an aggregate meter.
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.
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, except those operating in access-uplink mode
This command associates an IP filter policy with an ingress or egress Service Access Point (SAP) or IP interface. Filter policies control the forwarding and dropping of packets based on IP matching criteria.
SAP egress QoS policies are only supported on the 7210 SAS-Mxp.
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 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] (for 7210 SAS-Mxp only)
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, except those operating in access-uplink mode
This command associates a Quality of Service (QoS) policy with an ingress or egress Service Access Point (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 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 same or different type replaces the earlier one with the new policy.
SAP egress QoS policies are only supported on the 7210 SAS-Mxp.
On the 7210 SAS-Mxp (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.
On the 7210 SAS-Mxp, when the interface is associated with RVPLS, the behavior of the qos command is affected. Refer to the config>service>vprn>if>vpls> ingress>enable-table-classification and routed-override-qos-policy commands for more information about classification behavior for RVPLS.
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.
No specific QoS policy is associated with the SAP or IP interface for ingress or egress, so the default QoS policy is used.
Specifies the ingress/egress policy ID to associate with SAP or IP interface on ingress/egress. The policy ID must already exist.
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.