egress
config>service>epipe>sap
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure egress SAP parameters.
[no] force-vlan-vc-forwarding
config>service>epipe>spoke-sdp
config>service>vpls>spoke-sdp
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command forces VC VLAN-type forwarding in the datapath for spokes that have either VC-type. This command is not allowed on VC VLAN-type SDPs.
The no version of this command reverts to the default value.
ingress
config>service>epipe>sap
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure ingress SAP QoS policies.
If no SAP-ingress QoS policy is defined, the system default SAP-ingress QoS policy is used for ingress processing.
agg-shaper-rate agg-rate
no agg-shaper-rate
config>service>epipe>sap>ingress
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command configures the aggregate rate for the access SAP shaper. The aggregate SAP shaper is available to limit only the unicast traffic and the BUM traffic across all the FCs of the SAP configured to use ingress queues.
The no form of this command disables the use of the SAP aggregate rate shaper. That is, the SAP can use up the maximum bandwidth available.
no agg-shaper-rate
Specifies the rate in kilobits per second.
agg-shaper-rate agg-rate
no agg-shaper-rate
config>service>epipe>sap>egress
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command configures the aggregate rate for the access SAP shaper. The aggregate SAP shaper is available to limit only the unicast traffic and the BUM traffic across all the FCs of the SAP configured to use egress queues.
The no form of this command disables the use of the SAP aggregate rate shaper. That is, the SAP can use up the maximum bandwidth available.
no agg-shaper-rate
Specifies the rate in kilobits per second.
aggregate-meter-rate rate-in-kbps [burst burst-in-kbits] [enable-stats]
no aggregate-meter-rate
config>service>epipe>sap>egress
config>service>ies>if>sap>egress
config>service>vpls>sap>egress
7210 SAS-D, 7210 SAS-Dxp
This command configures the access SAP egress aggregate policer. The rate (PIR) of the SAP egress aggregate policer must be specified. The user can optionally specify the burst size for the SAP aggregate policer. The aggregate policer monitors the traffic sent out of the SAP and determines the final disposition of the packet, which is either forwarded or dropped.
The user can optionally associate a set of two counters to count total forwarded packets and octets and total dropped packets and octets. When use of this counter is enabled, the amount of resources required increases by twice the amount of resources taken up when the 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, use the no aggregate-meter-rate command, 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 accounting 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 config system resource-profile egress-internal-tcam egress-sap-aggregate-meter command. Refer to the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C 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 in which 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 to count forwarded and dropped packets and octets is allocated. If this keyword is used while configuring the meter, the counter is allocated.
aggregate-meter-rate rate-in-kbps [burst burst-in-kbits]
no aggregate-meter-rate
config>service>epipe>sap>ingress
config>service>ies>if>sap>ingress
config>service>vpls>sap>ingress
config>service>vprn>if>sap>ingress
7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
IES contexts apply only to the 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
VPRN contexts apply only to the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command allows the user to configure the access SAP ingress aggregate policer. The rate of the SAP ingress 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 ingress traffic on different FCs using policers to rate-limit the flow and determines the final disposition of the packet. The packet is either forwarded to an identified profile or dropped.
The sum of the CIR of the individual FCs configured under the SAP cannot exceed the PIR rate configured for the SAP. Although the 7210 SAS software does not block this configuration, Nokia does not recommend this configuration.
The queued traffic flows are not limited by the aggregate meter. That is, only metered flows can use the aggregate meter. Queue flows can use only the aggregate shaper.
The following table lists 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 |
Final packet color |
|---|---|---|---|
Within CIR |
Green |
Within PIR |
Green or In-profile |
Within CIR |
Green |
Above PIR |
Red and Dropped |
Above CIR, Within PIR |
Yellow |
Within PIR |
Yellow or Out-of-Profile |
Above CIR, Within PIR |
Yellow |
Above PIR |
Red or Dropped |
Above PIR |
Red |
Within PIR |
Red or Dropped |
Above PIR |
Red |
Above PIR |
Red or Dropped |
The SAP ingress meter counters increment the packet or octet counts based on the final disposition of the packet.
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]
filter [ipv6 ipv6-filter-id]
filter [mac mac-filter-id]
no filter [ip ip-filter-id]
no filter [ipv6 ipv6-filter-id]
no filter [mac mac-filter-id]
config>service>epipe>sap>egress
config>service>epipe>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. Only one filter can be applied to a SAP at a time.
The filter command is used to associate a filter policy with a specified filter-id with an ingress or egress SAP. The filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
IP filters apply only to RFC 2427-routed IP packets. Frames that do not contain IP packets are not subject to the filter and are always passed, even if the filter default action is to drop.
For filter support available on different 7210 SAS platforms, refer to the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.
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.
Both MAC and IP filters are supported on an Epipe service SAP.
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.
dot1p-inner [use-rcvd-outer-dot1p | use-rcvd-inner-dot1p]
no dot1p-inner
config>service>epipe>sap>egress
config>service>vpls>sap>egress
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command defines the dot1p marking values used per SAP on egress for the inner tag when the SAP encapsulation is QinQ (that is, Q1.Q2 SAP).
This command takes effect only if remarking is enabled in the remark policy associated with this SAP (under the egress context). It overrides the marking values defined in the remark policy associated with this SAP, if any.
The following table describes the dot1p values extracted from the packet on SAP (ingress) when dot1p-inner and dot1p-outer CLI commands are configured.
Ingress SAP type |
Dot1p value extracted from the packet |
|
|---|---|---|
rcvd-inner-dot1p is configured |
use-rcvd-outer-dot1p is configured |
|
Null SAP |
None |
None |
Dot1q SAP |
Dot1p from the outermost VLAN tag |
Dot1p from the outermost VLAN tag |
Dot1q Default SAP (that is, * SAP) |
None |
None |
Dot1q Explicit null SAP (that is,:0 SAP) |
Dot1p from the outermost VLAN tag (if priority-tagged packet), else none. |
Dot1p from the outermost VLAN tag (if priority-tagged packet), else none. |
Dot1q range SAP |
Dot1p from the outermost VLAN tag |
Dot1p from the outermost VLAN tag |
Q1.Q2 SAP |
Dot1p of the inner tag |
Dot1p from the outermost VLAN tag |
Q1.* SAP |
Dot1p from the outermost VLAN tag |
Dot1p from the outermost VLAN tag |
0.* SAP |
Dot1p from the outermost VLAN tag |
Dot1p from the outermost VLAN tag |
Q1.0 SAP |
Dot1p of the inner priority tag, if available, else from outermost VLAN tag |
Dot1p from the outermost VLAN tag |
QinQ Default SAP (that is,. *.* SAP) |
None |
None |
The following table describes the dot1p values marked in the packet on SAP egress when dot1p inner and dot1p-outer CLI commands are configured.
Egress SAP Type |
Dot1p-inner dot1p value marked in the packet sent out from this SAP |
Dot1p-outer dot1p value marked in the packet sent out from this SAP |
||
|---|---|---|---|---|
use-rcvd-inner-dot1p is configured |
use-rcvd-outer-dot1p is configured |
use-rcvd-inner-dot1p is configured |
use-rcvd-outer-dot1p is configured |
|
Null SAP |
NA |
NA |
NA |
NA |
Dot1q SAP |
NA |
NA |
Dot1p bits in the outermost tag |
Dot1p bits in the outermost tag |
Dot1q Default SAP (that is, * SAP) |
NA |
NA |
NA |
NA |
Dot1q Explicit null SAP (that is, :0 SAP) |
NA |
NA |
NA |
NA |
Dot1q range SAP |
NA |
NA |
NA |
NA |
Q1.Q2 SAP |
Dot1p bits from the inner tag |
Dot1p bits from the outermost tag |
Dot1p bits from the inner tag |
Dot1p bits from the outermost tag |
Q1.* SAP |
NA |
NA |
Dot1p bits from the inner tag |
Dot1p bits from the outermost tag |
0.* SAP |
NA |
NA |
NA |
NA |
Q1.0 SAP |
NA |
NA |
Dot1p bits from the inner tag |
Dot1p bits from the outermost tag |
QinQ Default SAP (that is, *.* SAP) |
NA |
NA |
NA |
NA |
The NA entry in the preceding table means egress encapsulation is not done, and neither the remark policy nor the use-rcvd command will be applicable at that level.
When the no form of this command is executed, the values defined in the remark policy associated with this SAP are used, if any. If no remark policy is associated with SAP egress, the default values are used.
no dot1p-inner
For information about this option, see Table: Dot1p values extracted from the packet on SAP (ingress) when dot1p-inner and dot1p-outer commands are configured and Table: Dot1p values marked in the packet on SAP egress when dot1p-inner and dot1p-outer commands configured.
For information about this option, see Table: Dot1p values extracted from the packet on SAP (ingress) when dot1p-inner and dot1p-outer commands are configured and Table: Dot1p values marked in the packet on SAP egress when dot1p-inner and dot1p-outer commands configured.
dot1p-outer [use-rcvd-outer-dot1p | use-rcvd-inner-dot1p]
no dot1p-outer
config>service>epipe>sap>egress
config>service>vpls>sap>egress
config>service>ies>if>sap>egress
config>service>vprn>if>sap>egress
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C; IES and VPRN contexts apply only to the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command defines the dot1p marking values to be used per SAP on egress for the outer tag when the SAP encapsulation is QinQ or dot1q. The command takes effect only if remarking is enabled in the remark policy associated with this SAP (under the egress context). It overrides the marking values defined in the remark policy associated with this SAP, if any. For more information, see Table: Dot1p values extracted from the packet on SAP (ingress) when dot1p-inner and dot1p-outer commands are configured and Table: Dot1p values marked in the packet on SAP egress when dot1p-inner and dot1p-outer commands configured.
When the no form of this command is executed, the values defined in the remark policy associated with this SAP are used, if any. If no remark policy is associated with SAP egress, the default values are used.
no dot1p-outer
For information about this option, see Table: Dot1p values extracted from the packet on SAP (ingress) when dot1p-inner and dot1p-outer commands are configured and Table: Dot1p values marked in the packet on SAP egress when dot1p-inner and dot1p-outer commands configured.
For information about this option, see Table: Dot1p values extracted from the packet on SAP (ingress) when dot1p-inner and dot1p-outer commands are configured and Table: Dot1p values marked in the packet on SAP egress when dot1p-inner and dot1p-outer commands configured.
[no] meter-override
config>service>epipe>sap>ingress
config>service>vpls>sap>ingress
config>service>vprn>if>sap>ingress
Supported on all 7210 SAS platforms as described in this document.
The config>service>vprn>if>sap>ingress context is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
This command, within the SAP ingress contexts, creates a CLI node 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 any existing meter overrides.
no meter-overrides
meter meter-id [create]
no meter meter-id
config>service>epipe>sap>ingress>meter-override
config>service>vpls>sap>ingress>meter-override
config>service>vprn>if>sap>ingress>meter-override
Supported on all 7210 SAS platforms as described in this document.
The config>service>vprn>if>sap>ingress>meter-override context is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
This command, within the SAP ingress contexts, creates a CLI node for specific overrides to a specific meter created on the SAP through a SAP-ingress QoS policies.
The no form of this command removes any existing overrides for the specified meter ID.
Required when executing the meter command within the meter-overrides context. 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 will not actually exist on the SAP. This does not preclude creating an override context for the meter-id.
Keyword that is required when a meter 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>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document.
The config>service>vprn>if>sap>ingress>meter-override>meter context is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
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 specifies the constraints enforced when adapting the PIR rate defined within the meter-override meter 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.
When the meter mode in use is ‟trtcm2”, this parameter is interpreted as the EIR value. Refer to the 7210 SAS-D, Dxp Quality of Service Guide and 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide for a description and relevant notes about meter modes.
Keyword that specifies 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>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document.
The config>service>vprn>if>sap>ingress>meter-override>meter context is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
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 the CBS size to the default value.
32 kbits
Specifies the value in kbits, bytes, or kilobytes.
mbs size [kbits | bytes | kbytes]
no mbs
config>service>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document.
The config>service>vprn>if>sap>ingress>meter-override>meter context is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
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 PIR. 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 with meter-configured parameters.
The no form of this command reverts the MBS size to the default value.
32Kbits
Specifies the value in kbits, bytes, or kilobytes.
mode mode
no mode
config>service>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document.
The config>service>vprn>if>sap>ingress>meter-override>meter context is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
This command overrides 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>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>vprn>if>sap>ingress>meter-override>meter
Supported on all 7210 SAS platforms as described in this document.
The config>service>vprn>if>sap>ingress>meter-override>meter context is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
This command within the SAP ingress meter-overrides contexts overrides the SAP-ingress QoS policy configured rate parameters for the specified meter ID.
The no form of this command reverts 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 specified as a positive integer.
When the meter mode is set to ‟trtcm2”, the PIR value is interpreted as the EIR value. Refer to the 7210 SAS-D, Dxp Quality of Service Guide and 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide for more information.
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 specified as a positive integer.
qos policy-id
no qos
config>service>epipe>sap>ingress
Supported on all 7210 SAS platforms as described in this document
This command associates a QoS policy with an ingress SAP.
QoS ingress 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 ingress policies. The qos command only allows ingress policies to be associated on SAP ingress. Attempts to associate a QoS policy of the wrong type returns an error.
Only one ingress QoS policy can be associated with a SAP or IP interface at one time. Attempts to associate a second QoS policy of a specific type returns an error.
By default, if no specific QoS policy is associated with the SAP for ingress, 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.
Specifies the ingress policy ID to associate with SAP on ingress. The policy ID must already exist.
statistics
config>service>epipe>sap
7210 SAS-D
Commands in this context configure the counters associated with SAP ingress and egress.
egress
config>service>epipe>sap>statistics
7210 SAS-D
Commands in this context configure the egress SAP statistics counter and set the mode of the counter.
This counter counts the number of packets forwarded through the SAP.
ingress
config>service>epipe>sap>statistics
7210 SAS-D and 7210 SAS-Dxp
Commands in this context configure the ingress SAP statistics counter.
The ingress counters are not enabled by default for access-uplink SAPs. For access SAPs, if the ingress counter is enabled by default, it can be disabled.
The types of ingress SAP counters are the following:
a counter that counts the total packets or octets received on the SAP. This counter is supported only on the 7210 SAS-D.
a counter associated with meters defined in the QoS policy of the SAP. This counter counts the in-profile and out-of-profile packets or octets received on the SAP.
[no] forwarded-count
config>service>epipe>sap>statistics>egress
7210 SAS-D
This command associates a counter with the SAP. The counter counts the number of packets forwarded through the SAP.
A limited number of such counters are available for use with access SAPs and access-uplink SAPs.
Use this command before enabling applicable accounting record collection on the SAP to associate a counter with the SAP.
The no form of this command disables the packet count.
counter-mode {in-out-profile-count | forward-drop-count}
config>service>epipe>sap>statistics>ingress
7210 SAS-D and 7210 SAS-Dxp
This command sets the counter mode for counters associated with SAP ingress meters. A pair of counters is available for each meter. These counters count different events based on the configured counter-mode value.
If an accounting policy is associated with a SAP, the counter mode can be changed. In this case, 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 that the correct statistics are collected when the counter mode is changed.
Configure the config>service>epipe>sap no collect-stats command to disable writing of accounting records for the SAP.
Change the counter mode option by configuring the config>service>epipe>sap counter-mode {in-out-profile-count | forward-drop-count} command.
Configure the config>service>epipe>sap collect-stats command to enable writing of accounting records for the SAP.
The no form of this command reverts the counter mode to the default value.
counter-mode in-out-profile-count
Specifies that one counter counts the forwarded packets and octets received on ingress of a SAP and the other counts the dropped packets. The forwarded count is the sum of in-profile and out-of-profile packets or octets received on SAP ingress. The dropped count is the count of packets or octets dropped by the policer. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters. A packet is dropped by the policer if it exceeds the configured PIR. The in-profile count and out-of-profile count is not individually available when operating in this mode.
Specifies that one counter counts the total in-profile packets and octets received on ingress of a SAP and the other 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. 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. The dropped counts are obtained by subtracting the sum of in-profile count and out-of-profile count from the total SAP ingress received count and displayed.
[no] received-count
config>service>epipe>sap>statistics>ingress
7210 SAS-D
This command associates a counter with the SAP. It counts the number of packets and octets received on the SAP (ingress).
A limited number of such counters are available for use with access-uplink SAPs.
Use this command before enabling applicable accounting record collection on the SAP.
The no form of this command disables counter.