egress
config>service>ies>if>sap
Supported on all 7210 SAS platforms as described in this document
Commands in this context apply egress policies.
agg-rate-limit agg-rate
no agg-rate-limit
config>service>ies>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.
Set the port scheduler 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.
Specify the scheduler mode using the scheduler-mode command. To implement the aggregate-rate-limit, the scheduler mode must be specified as ‟sap-based”. For more information about the scheduler-mode command, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.
The no form of this command removes the aggregate rate limit from the SAP or multi-service site.
Specifies the rate, in kilobits-per-second, that the maximum aggregate rate 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>ies>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 amount of resources required increases by twice the amount of resources taken up when counter is not used. If enable-stats keyword is specified during the creation of the meter, the counter is allocated by 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 Frame-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 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 taken 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/s.
Specifies the burst size for the policer in kilobits. The burst size cannot be configured without configuring the rate.
Specifies whether the counter is to count forwarded and dropped packets must be allocated.
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
no filter [ip ip-filter-id] [ipv6 ipv6-filter-id]
config>service>ies>if>sap>egress
config>service>ies>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command associates a filter policy with an ingress or egress SAP. Filter policies control the forwarding and dropping of packets based on the matching criteria.
The filter command is used to associate a filter policy with a specified ip-filter-id with an ingress or egress SAP. The filter policy must already be defined before the filter command is run. If the filter policy does not exist, the operation fails and an error message 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 the 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. The filter ID is not removed from the system.
Only IP filters are supported on an IES IP interface, and the filters only apply to routed traffic.
Keyword indicating the filter policy is an IP filter.
Specifies the ID for the IP filter policy. Allowed values are an integer in the range of 1 and 65535 that corresponds to a previously created IP filter policy in the configure>filter>ip-filter context.
Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.
qos policy-id
qos policy-id [enable-table-classification]
no qos policy-id
config>service>ies>if>sap>egress
config>service>ies>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command associates a Quality of Service (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 is used to associate 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 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.
Specifies the ingress or egress policy ID to associate with a SAP or IP interface on ingress or egress. The policy ID must already exist.
Keyword to enable the use of table-based classification at SAP ingress 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>ies>if>sap>egress
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>ies>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
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.
[no] meter-override
config>service>ies>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command 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 is used to remove any existing meter overrides.
no meter-override
meter meter-id [create]
no meter meter-id
config>service>ies>if>sap>ingress>meter-override
Supported on all 7210 SAS platforms as described in this document
This command, within the SAP ingress contexts, creates a CLI node for specific overrides to a specific meter created on the SAP through sap-ingress QoS policies.
The no form of this command removes existing overrides for the specified meter-id.
Required when executing the meter command within the meter-overrides context. The 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 not actually exist on the SAP. This does not preclude creating an override context for the meter-id.
Keyword 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 [max | min | closest]] [cir adaptation-rule [max | min | closest]]
no adaptation-rule
config>service>ies>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
Specifies the constraints enforced when adapting the PIR rate defined within the meter-override meter meter-id command. The pir parameter 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.
Defines the constraints enforced when adapting the CIR rate defined within the meter-override meter meter-id 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>ies>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document
This command overrides the default CBS for the meter. The committed burst 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 to the default value.
cbs 32
Specifies the value in kilobits, bytes, or kilobytes.
mbs size [kbits | bytes | kbytes]
no mbs
config>service>ies>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 maximum burst 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 returns the MBS size to the default value.
mbs 512
Specifies the value in kilobits, bytes, or kilobytes.
mode mode
no mode
config>service>ies>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 reverts 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>ies>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 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.
The no form of this command reverts the policy defined metering and profiling rate to a meter.
max
Specifies the administrative PIR rate, in kilobits, for the queue. When the rate command is run, a valid PIR setting must be explicitly defined. When the rate command has not been run, the default PIR of max is assumed.
Fractional values are not allowed and must be specified as a positive integer.
The actual PIR rate is dependent on the queue adaptation-rule parameters and the hardware where the queue is provisioned.
The cir parameter overrides 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 specified as a positive integer.
counter-mode {in-out-profile-count | forward-drop-count}
config>service>ies>sap>statistics>ingress
Supported on all 7210 SAS platforms as described in this document
This command sets the counter mode for the counters associated with sap ingress meters or policers. A pair of counters is available with each meter. These counters count different events based on the counter mode value.
The counter mode can be changed if an accounting policy is associated with a SAP. If the counter mode is changed, the counters associated with the meter are reset and the counts are cleared. If an accounting policy is in use when the counter mode is changed, a new record is written into the current accounting file.
Perform the following sequence of commands on the specified SAP to ensure the correct statistics are collected when the counter-mode is changed.
Run the config service ies interface sap no collect-stats command, to disable writing of accounting records for the SAP.
Change the counter mode to the desired option by running the config service vprn interface sap counter-mode {in-out-profile-count | forward-drop-count} command.
Run the config service ies interface sap collect-stats command to enable writing of accounting records for the SAP.
The no form of this command restores the counter mode to the default value.
in-out-profile-count
Specifies that one counter counts the total in-profile packets and octets received on ingress of a SAP and another counts the total out-of-profile packets and octets received on ingress of a SAP. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. Dropped counts are not maintained in hardware when this mode is used. It is obtained by subtracting the sum of in-profile count and out-of-profile count from the total SAP ingress received count and displayed.
Specifies that one counter counts the forwarded packets and octets received on ingress of a SAP and another counts the dropped packets. The forwarded count is the sum of in-profile and out-of-profile packets/octets received on SAP ingress. The dropped count is count of packets/octets dropped by the policer. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. The in-profile count and out-of-profile count is not individually available when operating in this mode.
tod-suite tod-suite-name
no tod-suite
config>service>ies>if>sap
Supported on all 7210 SAS platforms as described in this document
This command applies a time-based policy (filter or QoS policy) to the service SAP. The suite name must already exist in the config>cron context.
no tod-suite
Specifies collection of policies (ACLs, QoS) including time-ranges that define the full or partial behavior of a SAP. The suite can be applied to more than one SAP.