meter meter-id [multipoint] [create]
no meter meter-id
config>qos>sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command configures an ingress SAP QoS policy meter.
This command allows the creation of multipoint meters. Only multipoint meters can receive ingress packets that need flooding to multiple destinations. By separating the unicast for multipoint traffic at service ingress and handling the traffic on separate multipoint meters, special handling of the multipoint traffic is possible. Each meter acts as an accounting and (optionally) policing device offering precise control over potentially expensive multicast, broadcast, and unknown unicast traffic. Only the back-end support of multipoint traffic (between the FC and the meter based on forwarding type) needs to be defined. The individual classification rules used to place traffic into FCs are not affected. Meters must be defined as multipoint within the policy at the time of creation.
The multipoint meters are for service traffic destined for multiple destinations, such as multicast traffic in a VPLS service. Within non-multipoint services, such as Epipe services, all traffic is considered unicast because of the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service is mapped to a multipoint service meter.
When an ingress SAP QoS policy with multipoint meters is applied to an Epipe SAP, the multipoint meters are not created.
Any billing or statistical queries about a multipoint meter on a non-multipoint service return zero values. Any meter parameter information requested about a multipoint meter on a non-multipoint service returns the meter parameters in the policy. Multipoint meters are not created for non-multipoint services.
The no form of this command removes the meter-id from the SAP ingress QoS policy and from any existing SAPs using the policy. Any FC mapped to the meter reverts to the default meters. When a meter is removed, any pending accounting information for each SAP meter, created as a result of the definition of the meter in the policy, is discarded.
Specifies the meter within the policy. This is a required parameter each time the meter command is executed.
Keyword that creates the meter as a multipoint meter.
Keyword to create a meter.
adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
no adaptation-rule
config>qos>sap-ingress>meter
Supported on all 7210 SAS platforms as described in this document
This command defines 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 pir and cir apply.
adaptation-rule cir closest pir closest
Specifies the adaptation rule used while computing the operational CIR value and defines the constraints enforced when adapting the CIR rate defined using the meter meter-id rate command. The cir parameter requires a qualifier that defines the constraint used to derive the operational CIR for the meter. When the cir parameter is not specified, the default constraint applies.
For 7210 SAS-Dxp, see Adaptation rule for meters for information about calculating the next multiple equal to or less than the specified rate.
Specifies the adaptation rule used while computing the operational PIR value and defines the constraints enforced when adapting the PIR rate defined using the meter meter-id rate command. The pir parameter requires a qualifier that defines the constraint used to derive the operational PIR for the meter. When the rate command is not specified, the default applies.
For 7210 SAS-Dxp, see Adaptation rule for meters for information about calculating the next multiple equal to or less than the specified rate.
cbs size [kbits | bytes | kbytes]
no cbs
config>qos>sap-ingress>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 cbs command 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 adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation rule for meters for information.
The no form of this command returns the CBS size to the default value.
32 kbits
Specifies the number of kilobits, kilobytes, or bytes reserved for the meter, expressed as an integer. For example, if a value of 100 kb is wanted, enter the value 100 and the keyword kbits. The bucket size is rounded off to the next highest 4096-byte boundary.
color-mode color-mode
no color-mode
config>qos>sap-ingress>meter
Supported on all 7210 SAS platforms as described in this document
This command configures the meter to operate in either color-aware or color-blind mode.
In color-blind mode, the profile/color assigned to the packet on ingress is ignored. The CIR and PIR rate configured for the meter are used to determine the final profile/color for the packet. If the packet is within the CIR, the final profile/color assigned to the packet is in-profile/green; if the packet exceeds the CIR and is within the PIR, the final profile/color assigned to the packet is out-of-profile/yellow. Packets that exceed the PIR rate are dropped.
In color-aware mode, the meter uses the profile assigned to the packet on ingress. Profile can be assigned on ingress either by enabling DEI classification as done on access ports or by assigning profile based on either dot1p or DEI as done on network ports and access-uplink ports.
The following behavior is available in color-aware mode:
If the packet is pre-colored as in-profile (or green packets), depending on the burst size of the packet, the meter can either be marked in-profile or out-profile.
If the packet is pre-colored as out-profile (or yellow packets), even if the packet burst is less than the current available CBS, it is not marked as in-profile and remains as out-profile.
If the packet burst is higher than the MBS, it is marked as red and is dropped by the meter at ingress.
color-blind
Specifies the mode the meter operates in.
mbs size [kbits | bytes | kbytes]
no mbs
config>qos>sap-ingress>meter
Supported on all 7210 SAS platforms as described in this document
This command configures a mechanism to override the default MBS for the meter. The MBS 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 with configures meter parameters.
The adaptation rule configured for the rate influences the step-size used for the burst. See Adaptation rule for meters for information.
The no form of this command reverts the MBS size to the default value.
128 kbits
Specifies the size reserved for the meter. For example, if a value of 100 kb is wanted, enter the value 100 and the keyword kbits. The bucket size is rounded off to the next highest 4096-byte boundary.
mode {trtcm1 | trtcm2 | srtcm}
no mode
config>qos>sap-ingress>meter
Supported on all 7210 SAS platforms as described in this document
This command defines the mode of the meter. The mode can be configured as Two Rate Three Color Marker (trTCM1) or Single Rate Three Color Marker (srTCM). The mode command can be executed at anytime.
The meter counters are reset to zero when the meter mode is changed.
For more information about the interpretation of rate parameters when the meter mode is configured as ‟trtcm2”, see the command description of the policer rate command.
The no form of the command sets the default mode trtcm1.
trtcm1
Specifies the policing algorithm defined in RFC2698 and meters the packet stream and marks its packets as green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise, it is marked as yellow or green, depending on whether it exceeds the CIR. The trTCM1 is useful for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate. Two token buckets are used, the CBS bucket and the MBS bucket. Tokens are added to the buckets based on the CIR and PIR rates. The algorithm deducts tokens from both the CBS and the MBS buckets to determine a profile for the packet.
Specifies the policing algorithm defined in RFC4115 and meter the packet stream and marks its packets either green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise, it is marked yellow or green, depending on whether it exceeds the CIR. The trTCM2 is useful for ingress policing of a service, where a peak rate needs to be enforced separately from a committed rate. Two token buckets are used, the CBS bucket and the EBS bucket. Tokens are added to the buckets based on the CIR and EIR rates. The algorithm deducts tokens from either the CBS bucket (that is, when the algorithm identifies the packet as in-profile or green packet) or the EBS bucket (that is, when the algorithm identifies the packet as out-of-profile or yellow packet).
When the meter mode is configured in trtcm2 mode, the system interprets the PIR rate parameter as EIR and the MBS parameter as the EBS value for use by RFC 4115 algorithm.
Specifies that an IP packet IP packet stream will be metered and marks its packets green, yellow, or red. Marking is based on a CIR and two associated burst sizes, a CBS and an MBS. A packet is marked green if it does not exceed the CBS, yellow if it exceeds the CBS but not the MBS, and red otherwise. The srTCM is useful for ingress policing of a service where only the length, not the peak rate, of the burst determines service eligibility.
rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]
no rate
config>qos>sap-ingress>meter
Supported on all 7210 SAS platforms as described in this document
This command defines the administrative PIR and CIR parameters for the meter.
The rate command can be executed at anytime, altering the PIR and CIR rates for all meters created through the association of the SAP Ingress QoS policy with the meter-id.
The no form of this command reverts all meters created with the meter-id by association with the QoS policy to the default PIR(max) and CIR(0) parameters.
rate cir 0 pir 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 that the cir parameter overrides the default administrative CIR used by the meter. 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.
The actual CIR rate is dependent on the meter’s adaptation-rule parameters and the hardware.
Specifies the administrative PIR rate, in kilobits, for the meter. When this 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. When the rate command is executed, a PIR setting is optional. Fractional values are not allowed, and must be specified as a positive integer.
The actual PIR rate is dependent on the meter’s adaptation-rule parameters and the hardware.