Service ingress QoS policies

This chapter provides information to configure SAP ingress QoS policies using the CLI.

Overview of service ingress policy

There is one default service ingress policy. The default policy has two classification resources and one meter (the num-qos-classifiers set to value ‟2”). Service ingress queuing is not supported on the 7210 SAS-D and 7210 SAS-Dxp. Instead the user has the option of using policing per FC (and for VPLS services, per FC and per traffic type). The default policies can be copied and modified but cannot be deleted. The default policies are identified as policy ID 1.

The default policies are applied to the appropriate interface, by default. For example, the default SAP ingress policy is applied to access ingress SAPs. Other QoS policies must be explicitly associated. See ‟CLI Usage” in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about the tasks and commands necessary to access the CLI, and to configure and maintain devices.

Default SAP ingress policy

The default policy 1 maps all traffic to default FC ‟be” and maps FC ‟be” to meter 1. Meter 1 is configured with cir 0 and pir max.

The following is a sample configuration output.

*A:7210-SAS>config>qos>sap-ingress# info detail
----------------------------------------------
            description "Default SAP ingress QoS policy."
            num-qos-classifiers 2
            scope template
            meter 1 create
                mode trtcm1
                adaptation-rule cir closest pir closest
                rate cir 0 pir max
                mbs default
                cbs default
            exit
            default-fc "be"
----------------------------------------------
*A:7210-SAS>config>qos>sap-ingress#

SAP ingress policy defaults

The following table lists the SAP ingress policy defaults.

Table 1. SAP ingress policy defaults
Field	Default
description	‟Default SAP ingress QoS policy.”
scope	template
num-qos-classifiers	2
meter	1
mode	trtcm1
adaptation-rule	cir closest pir closest
rate	pir = max, cir= 0
cbs	32kbits
mbs	128kbits
default-fc	be

Use of index file by SAP QoS ingress policy

The 7210 SAS uses an index file to store the map that indicates the QoS resource allocation to the SAPs. This file is used to ensure that all the SAPs that were created successfully before the reboot can be recreated during reboot. Without an index file, it is possible that all the SAPs that were configured successfully may fail on a reboot after saving the configuration file. The index file is stored in the flash. During a reboot, if the file is found, the system allocates resources as per the stored map. If the file is not found, the system implements a best-fit algorithm and attempts to allocate resources for all the SAPs on a first-come-first-served basis. There is no guarantee that resources will be allocated to all SAPs. When the index file is not present, it is possible that saved the configuration does not execute successfully after the reboot.

Note:

The index file used for QoS maps is different from the one used for storing interface indexes.

Use of the keyword multipoint for default meter ‟11”

The system allows the sharing of a single meter for both unicast and multipoint traffic. The user can configure any of the available meters for multipoint traffic. The use of the multipoint keyword during meter creation is deprecated, except for use with meter 11 as described in the following paragraphs.

When the multipoint keyword is specified with meter 11 the software interprets it to be the default multipoint meter. The default multipoint meter is used for all FCs that do not have explicit multipoint meters configured.The software performs resource checks to ensure that resources needed to use the multipoint meter with all the FCs are available before allowing this change.

Note:

When the num-qos-resources command is set to a value of 2, the default multipoint meter 11 cannot be used because only a single meter is available for use.
When associating a meter with an FC for BUM traffic, the software does not validate whether the meter is a multipoint meter, which allows the user to use a single meter for unicast and BUM traffic. This implies efficient use of SAP ingress qos resources. From Release 4.0R4 onwards when the multipoint keyword is used, the software issues a warning indicating that it is an obsolete CLI command, and it is not saved in the configuration file, deprecating the use of multipoint keyword with any meter other than the default.

Example uses of the multipoint meter

1

*7210-SAS>config>qos# sap-ingress 12 create 
*7210-SAS>config>qos>sap-ingress$ info 
----------------------------------------------
            num-qos-classifiers 4
            meter 1 create
            exit
----------------------------------------------
*7210-SAS>config>qos>sap-ingress$

In example 1, all FCs in the SAP ingress policy use the default meter 1 (for all traffic types). If the configure qos sap-ingress id meter 11 multipoint create command is executed, it attaches the default meter ‟11” with all the FCs defined in the SAP ingress policy.

After this configuration, all the FCs in this policy use two meters: default meter "1" to meter unicast traffic for all the FCs, and meter ‟11” to meter BUM traffic for all the FCs. In this example, because only the default FC ‟be” is in use, the multipoint meter is used to meter BUM traffic associated with default FC ‟be”.

The following example shows the policy after the configuration is changed.

*7210-SAS>config>qos# sap-ingress 12
*7210-SAS>config>qos>sap-ingress$ info 
----------------------------------------------
             num-qos-classifiers 4
             meter 1 create
             exit
meter 11 multipoint create
----------------------------------------------
*7210-SAS>config>qos>sap-ingress$

Delete the multipoint meter ‟11” to remove all the FCs associated with the multicast-meter (assuming all the FCs are using the default multicast meter and do not have any other multicast meter explicitly configured). Execute the configure qos sap-ingress id no meter 11 command to dissociate meter ‟11” from the FCs, and the FCs use only meter ‟1” (if no other meter configured explicitly).

2

*7210-SAS>config>qos# sap-ingress 12
*7210-SAS>config>qos>sap-ingress$ info 
----------------------------------------------
configure> qos> sap-ingress 10 create
meter 1 create
exit
meter 3 create
exit
default-fc be
fc be 
meter 3
multicast-meter 3
exit
fc af
meter 3
exit
exit
----------------------------------------------

Starting with the policy in example 2, if the user executes the configure qos sap-ingress <id> meter 11 multipoint create command, the FC ‟be” continues to use meter ‟3” and the FC "af" uses meter "11" for BUM traffic. In this example, if the user executes the configure qos sap-ingress id fc be no multicast-meter command, the default meter ‟11” is used for FC "be".

3

----------------------------------------------
configure> qos> sap-ingress 10 create
meter 1 create
exit
meter 3 create
exit

default-fc be

fc be 
meter 3
unknown-meter 3
exit
exit
----------------------------------------------

On execution of the configure qos sap-ingress id meter 11 multipoint create command, the FC "be" unknown-unicast traffic type continues to use meter 3 and broadcast and multicast traffic types use meter ‟11”.

In example 3, if a broadcast-meter was initially configured in the SAP-ingress policy and then followed by execution of the configure qos sap-ingress id meter 11 multipoint create command, the FC ‟be” changes to use meter ‟11” for multicast traffi, and broadcast traffic continues to use meter ‟3” for unknown-unicast traffic and meter ‟3” for unicast traffic.

In example 3, if the user executes configure qos sap-ingress id fc be no unknown-meter command, meter "3" is used for all traffic types classified to FC ‟be”. But, if the default meter "11" is defined in the policy, FC ‟be” uses meter ‟11” for BUM traffic.

Service ingress meter selection rules

This section describes the rules for meter selection by different traffic types under various configurations for VPLS services:

In the default policy, only meter ‟1” is defined. All FC and all traffic types use meter ‟1” by default. Meter ‟11” is not created by default and is not available for use.

The following is a sample default policy configuration output.

*7210-SAS>config>qos# sap-ingress 1 create // Default policy
*7210-SAS>config>qos>sap-ingress$ info
----------------------------------------------
num-qos-classifiers 2
meter 1 create
exit
----------------------------------------------
*7210-SAS>config>qos>sap-ingress$

The following describes the use of meters in a VPLS service, when meter ‟11” is not configured in the policy:

If an FC is created without explicit meters, the default meter ‟1” is used for unicast traffic and for multipoint traffic types (such as broadcast, multicast, and unknown-unicast traffic).
If an FC is created with an explicit unicast meter, that meter is used for unicast traffic and for multipoint traffic types (such as broadcast, multicast, and unknown-unicast traffic).
If an FC is created with an explicit unicast meter and explicit broadcast meter, use these meters for unicast and broadcast traffic respectively, and use the unicast meter for all other traffic types.
If an FC is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for all other traffic types.
If an FC is created with an explicit unicast meter, an explicit broadcast meter, and an explicit multicast meter, use these meters for unicast, broadcast, and multicast traffic types respectively. The unknown unicast traffic types use the explicitly defined multicast meter.
If an FC is created with an explicit unicast meter, explicit broadcast meter, explicit unknown-unicast meter, and explicit multicast meter, use these meters for unicast, broadcast, unknown-unicast, and multicast traffic types respectively.

The following describes the use of meters in a VPLS service, when meter ‟11” is defined in the policy:

If an FC is created without explicit meters, use the default meter ‟1” for unicast traffic and default meter ‟11” for all other traffic types (such as broadcast, multicast, and unknown-unicast).
If an FC is created with an explicit unicast meter, use that meter for unicast traffic, and use default meter ‟11” for all other traffic types.
If an FC is created with an explicit unicast meter and explicit broadcast meter, use these meters for unicast and broadcast traffic respectively, and use meter ‟11” for all other traffic types.
If an FC is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for all other kinds of traffic.
If an FC is created with an explicit unicast meter, explicit broadcast meter, and explicit multicast meter, use these meters for unicast, broadcast, and multicast traffic types respectively. Unknown unicast traffic types use the explicitly defined multicast meter.
If an FC is created with an explicit unicast meter, explicit broadcast meter, explicit unknown-unicast meter, and explicit multicast meter, use these meters for unicast, broadcast, unknown-unicast, and multicast traffic types respectively.

The following are rules for meter selection for Epipe and IES services:

Note:

These rules apply to IES services when PIM, multicast is not enabled in the service.

IPv4 multicast with PIM is not supported on all 7210 SAS platforms. Check the 7210 SAS release notes to know the availability of this feature on all platforms.
A multipoint meter cannot be used. A multipoint meter configured in a policy is not used when the policy is applied to a SAP in an Epipe service.
All FCs associated with a meter always use the unicast meter.

Service ingress QoS policy configuration considerations

The num-qos-classifiers command cannot be modified when the policy is in use (for example, when it is associated with a SAP). Other parameters in the SAP ingress policy can be changed.

When changing other parameters (for example, FC meter map or FC classification match criteria entries) for a policy that is in use, the system recomputes the resources required to accommodate the change. If the resources required exceed the configured value for num-qos-classifiers, the change is not allowed.

If more resources are needed than are configured in num-qos-classifiers for an existing policy, the following options are available:

Copy the existing policy to a new policy, modify the num-qos-classifiers command, modify the match criteria entries, and finally modify the SAP configuration to associate it with the new policy.
Ensure the existing policy is not in use by any SAP (if required, change the SAP configuration to disable the use of the QoS policy using the no qos form of the command), change all the required parameters, and finally modify the SAP configuration to use the policy again.

Note:

Both these options have side-effects; for example, they can reset the statistics associated with the meters and potentially cause existing traffic classification not to take effect; however, the system ensures that the default policy is in use during the intermittent time when the policy changes are being made after the two options are performed.

In releases before Release 3.0R1, the software always computes the number of resources (like classifiers and meters) required by a policy assuming it will be used in a VPLS service. This allows the policy to be applied to either an Epipe or VPLS service.
From Release 3.0R1 onwards, when creating a SAP ingress policy, the software does not compute the number of resources required by a policy and validate it against resources available in the system. The software validates the resources needed only when the SAP ingress policy is attached to a SAP. If enough resources are available, the association succeeds, otherwise the command fails. Based on the service (VLL, VPLS, and so on) in which the SAP is configured, for the same SAP ingress policy the amount of resources required is different. The software validates that the number of QoS resources specified with the num-qos-classifiers command is sufficient for the match criteria, FC, and service specified, and the resources are available in hardware. If the validation fails, the software disallows the association of the SAP ingress policy with the SAP.
The match criteria type (that is, mac-criteria, ipv4-criteria, and ipv6-criteria) cannot be changed when the SAP ingress QoS policy is in use. For example, if the match criteria type is set to ipv4-criteria and the policy is associated with a SAP, the ipv6-criteria or mac-criteria cannot be enabled in the same policy. If there is a need to change the criteria, the user must remove the association and then change the SAP ingress policy to use the new match criteria.

See Resource allocation for service ingress QoS policy classification rules for more information.

Resource allocation for service ingress QoS policy classification rules

The available global pool of ingress internal CAM hardware resources can be allocated as per user needs for use with different features such as SAP ingress QoS policy, ingress ACLs, and so on. SAP ingress QoS can be allocated classification and meter resources for use from this pool. Further on, resources can be allocated for different SAP ingress QoS policy classification match criteria, based on the operator needs. Users can modify resources allocated to scale the number of entries available per match criteria or scale the number of SAPs. The resources from the global ingress internal CAM pool are allocated in slices with fixed number of entries.

The number of slices allotted for a SAP ingress QoS policy is specified using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource command.

User can specify a limit for the amount of resources required for SAP ingress QoS policies and also an option to limit the amount of resources used per match criteria supported for SAP ingress QoS policies. A specific slice can be used for MAC criteria, IP criteria, or IPv6 criteria. Allocation of classification entries also allocates meter/policer resources, used to implement per FC per traffic type policing.

By default, the system allocates resources for SAP ingress QoS policies to maintain backward compatibility with Release 4.0 and allocates resources for MAC criteria and IP criteria (by setting it to 'max'). Setting the value to ‛max’ allows each match criterion to use the available SAP ingress QoS resources on a first-come-first-served model. By default, the software does not allocate resources for use by ingress IPv6 filters. Before associating an IPv6 SAP ingress policy to a SAP, resources must be allocated. Until resources are allocated for use by IPv6 filters, software fails all attempts to associate an IPv6 filter policy with a SAP.

When the user allocates resources for use by SAP ingress QoS policies using the configure system resource-profile qos-sap-ingress-resource command, the system allocates resources in slices of 256 entries. The following table describes the use of these entires by different types of match criteria.

Note:

See the 7210 SAS Release Notes for information about services supported on different 7210 SAS platforms. The references to services in the following table appear for completeness and do not imply support is available.

Table 2. SAP ingress resource allocation and match criteria types
Type of match criteria	Description
mac-criteria (any)	User needs to allocate resources for mac-criteria from the SAP ingress QoS resource pool by using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource mac-match-enable command before using SAP ingress policies with mac-criteria. Every entry configured in the SAP ingress QoS policy using the mac-criteria uses one entry from the slices in the hardware. For example, assume a SAP-ingress QoS policy is configured to use mac-criteria with 25 entries and uses configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource mac-match-enable 1, to configure one slice for use by mac-criteria (allowing a total of 256 entries for use by policies using mac-criteria). In this case, the user can have 10 SAPs using mac-criteria SAP ingress policy and consumes 250 entries.
ipv4-criteria (any)	The usage is same as the mac-criteria. Resources need to be allocated using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv4-match-enable command. Additionally, IPv4 criteria can share the entries allocated for IPv6 criteria. The software automatically allocates entries from an IPv6 criteria slice to IPv4 criteria policies, if there are no entries available in the allocated IPv4 criteria slices and there are no slices available for allocation to IPv4 criteria from the SAP ingress QoS resource pool. The number of hardware entries taken up by an IPv4 criteria entry when using the IPv6 criteria slices is the same as required by an entry using IPv6 criteria (see below for details).
ipv6-criteria (any)	User needs to allocate resources from the SAP ingress QoS resource pool for ipv6-criteria by using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv6-ipv4-match-enable command before using IPv6 criteria and num-qos-classifiers must specify the ipv6 keyword. Every ipv4 criteria match entry or ipv6 criteria match entry configured in the QoS policy using ipv6-criteria uses two entries from the slices allocated for use by ipv6-criteria (128-bit) in the hardware. Software allocates entries from the ipv6-criteria pool if the SAP ingress QoS policy uses both ipv6-criteria entries and ipv4-criteria (any or IPv4 DSCP) entries or if the SAP ingress QoS policy uses only IPv6 criteria any or if the SAP ingress QoS policy uses ipv4 criteria any and there are no resources available in the IPv4 criteria (as described above). For example, assume a QoS policy is configured to use ipv6-criteria with 25 entries and using configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv4-ipv6-128-match-enable 1, user configures one slice for use by ipv6-criteria. This allows for a total of 128 entries for use by SAPs using SAP ingress QoS policies with ipv6-critiera (as each IPv6 entry uses two entries in hardware). In this example, user can have five SAPs using this policy and consuming 125 entries in total. These resources can be shared with policies that use IPv4 criteria, though it consumes two entries in hardware consumed per IPv4 criteria entry. It allows user to make use of spare IPv6 resources for IPv4 criteria policies, though if user plans to have a larger number of IPv4 criteria policies they are better off allocating more resources for use with IPv4 criteria. Note when a slice is allocated to IPv6 criteria, software automatically adjusts the number of available entries in that slice to 128, instead of 256, because 2 entries are needed to match IPv6 fields. The number of meters available does not reduce though and 128 meters are available for use.
dot1p-only, IPv4 dscp-only, IPv6 dscp-only, and default SAP ingress QoS policies	User can use the option 'dot1p-only' or dscp-only', if they plan to use only dot1p bits or only DSCP bits for SAP ingress classification. This typically allows for efficient use of available hardware resources and better scaling. SAP ingress policies that use only dot1p bits or only IPv4/IPv6 DSCP and Default SAP ingress QoS policies can use the resources from slices currently allocated for use by either IP-criteria or MAC-criteria or IPv6 criteria. The following are some special cases noted below for allocation of resources for default, dot1p-only and dscp-only SAP ingress policies: If no slices are available to accommodate a SAP that is associated with default or dot1p-only, or a dscp-only SAP ingress policy, the software allocates resources against mac-criteria when the SAP is configured in a VLL or VPLS service. The software uses the required number of entries for this policy. The remaining entries is available for SAPs that use mac-criteria or that use only dot1p or only ipv4/ipv6 DSCP or that use default policy. If no slices are available to accommodate a SAP that is associated with default, dot1p-only, or a dscp-only SAP ingress policy, the software allocates resources against ipv4-criteria when the SAP is configured in an IES or a VPRN service. The software uses the required number of entries for this policy. The remaining entries are available for SAPs that use ipv4-criteria or that use only ipv4/ipv6 DSCP or only dot1p criteria or that use the default policy.

The SAP ingress resource slices described in this section are different from the resources that are configured using the num-qos-classifiers command. The num-qos-classifiers command sets the limit on the resources needed per SAP ingress QoS policy. The resources set the maximum limit on the resources available for use by all the SAP ingress policies that are in use simultaneously on the system. The SR OS manages the resource slices allocated to the SAP ingress QoS policy pool and allocates the entries in the slices when a SAP ingress QoS policy is associated with a SAP. This means that a SAP specifies the amount of QoS resources it needs, using the num-qos-resources command (in the SAP ingress policy) and the system allocates the resources required by a SAP from the slices, depending on whether the SAP ingress policy uses ip-criteria, mac-criteria, or ipv6-criteria.

Note:

On the 7210 SAS-D and 7210 SAS-Dxp, mac-criteria SAP ingress QoS policies can use an additional 128 classification entries with 64 meters. These entries are allocated to the mac-criteria SAP ingress QoS resource pool by default and cannot be reassigned to any another feature or any other match criteria.

Use the tools dump system-resources command to display information about the current usage and availability. One or more entries per slice are reserved for system use.

Computation of SAP ingress classification and meter resources used per SAP ingress policy

Note:

This section provides information about the resource consumption per SAP ingress policy. Resources required by the SAP ingress policy are allocated from the ingress-internal-tcam resource pool, based on the amount of resources allocated for SAP ingress classification.

The user can configure the number of classification entries the SAP requires (for example, TQ).

Number of meters allocated automatically by system = TQ / 2

(up to a maximum of 32 meters)

To calculate the number of SAPs allowed, assume all configured to use ‛TQ’ QoS resources per SAP.

Number of SAPs allowed = maximum classification entries / TQ

Note:

The number of SAPs arrived at using the preceding equation is subject to system limits. The preceding equation is used to derive the limit on the number of SAPs due to QoS resources only.

The user is allowed to mix and match SAPs with different QoS resources (that is, using different values of TQ). The allowed values in 7210 SAS-D devices for the num-qos-classifiers command are: 4, 8, 16, 32, 64, 128, and 256. The allowed num-qos-classifiers values for 7210 SAS-Dxp devices are any multiple of 2, between 2 and 256.

The following items determine the number of QoS resources to be allocated for a SAP:

number of match-criteria entries used to identify the FC
number of FCs to use and number of traffic-types to be policed per FC
the amount of hardware classification resources needed per entry configured by the user (see Resource allocation for service ingress QoS policy classification rules for information about resources needed per match entry; it varies based on different match criteria in use)

Only those FCs that are in use by the match-criteria classification entries are considered for the number of FCs. These FCs are referred to as ‟FCs in use”.

Determining the number of classification entries

This section describes the rules and methods of determining the number of classification entries.

Rules for a SAP in a VPLS

Given the number of traffic types to use per ‟FC in use”, the following rules apply for a SAP in a VPLS service to determine the number of classification entries per FC in use:

If an FC is in use and is created without explicit meters, use default meter 1 for unicast traffic and for all other traffic types (that is, broadcast, multicast, and unknown-unicast). This requires one classification entry in hardware. This assumes default mulitpoint meter 11 is not created by the user.
If an FC is in use and is created without explicit meters, use default meter 1 for unicast traffic and default meter 11 (assuming meter ‟11” is created by the user), for all other traffic types (that is, broadcast, multicast, and unknown-unicast). This requires two classification entries in hardware.
If an FC is in use and is created with an explicit unicast meter, use that meter for unicast traffic and for all other traffic types (that is, broadcast, multicast, and unknown-unicast). This requires one classification entry in hardware. This assumes default multipoint meter ‟11” is not created by the user.
If an FC is in use and is created with an explicit unicast meter, use that meter for unicast traffic and use default meter 11 (assuming meter ‟11” is created by the user) for all other traffic types. This requires two classification entries in hardware.
If an FC is in use and is created with an explicit unicast meter and explicit broadcast meter, use these meters for unicast and broadcast traffic respectively and use the unicast meter for all other traffic types (that is, multicast and unknown-unicast). This requires two classification entries in hardware. This assumes that the default multipoint meter 11 is not created by the user.
If an FC is in use and is created with an explicit unicast meter and explicit broadcast meter, use these meters for unicast and broadcast traffic respectively and use meter 11 (assuming meter 11 is created by the user) for all other traffic types. This requires three classification entries in hardware.
If an FC is in use and is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for all other kinds of traffic. This requires two classification entries in hardware.
If an FC is in use and is created with an explicit unicast meter, an explicit broadcast meter, and an explicit multicast meter, use these meters for unicast, broadcast, and multicast traffic types respectively. The unknown unicast traffic type uses the explicitly defined multicast meter. This requires three classification entries in hardware.

Rules for a SAP in a VLL, IES, or VPRN service with PIM/IP multicast disabled

For calculating the number of classification entries per FC for a SAP in a VLL, IES or VPRN service with PIM/ IP multicast disabled, the following rules apply:

Multipoint meters cannot be used. Multipoint meters configured in a policy are not used when the policy is applied to a SAP in an Epipe service.
All FCs in use and associated with a meter always use the unicast meter. Therefore, all FCs in use only use one classification entry in the hardware.

Rules for a SAP in an IES or VPRN service with PIM/IP multicast enabled

Given the number of traffic types to use per ‟FC in use”, the following rules apply for a SAP in an IES and VPRN service enabled with PIM/IP multicast enabled to arrive at a number of classification entries per FC in use:

If an FC is in use and is created without explicit meters, use default meter 1 for unicast traffic and multicast traffic. This requires one classification entry in hardware. This assumes the default multipoint meter 11 is not created by the user.
If an FC is in use and is created without explicit meters, use default meter 1 for unicast traffic and default meter 11 (assuming meter ‟11” is created by the user) for multicast traffic. This requires two classification entries in hardware.
If an FC is in use and is created with an explicit unicast meter, use that meter for unicast traffic and for multicast traffic. This requires one classification entry in hardware. This assumes default multipoint meter ‟11” is not created by the user.
If an FC is in use and is created with an explicit unicast meter, use that meter for unicast traffic and use default meter 11 (assuming meter ‟11” is created by the user) for multicast traffic. This requires two classification entries in hardware.
If an FC is in use and is created with an explicit unicast meter and explicit multicast meter, use the unicast meter for unicast traffic and multicast meter for multicast traffic. This requires two classification entries in hardware.

Calculating the number of classification entries per FC

Apply the rules to determine the number of classification entries per FC (only for the FCs in use) using the following equation:

C(i) = SFC_{i (unicast)}+ FC_{i
(multicast)} + FC_{i( broadcast)} + FC_{i
(unknown_unicast)}

i = nc, h1, ef, h2, l1, af, l2, be

where:

FC_i (unicast), FC_i (multicast), FC_i (broadcast), and FC_i (unknown-unicast) are set to a value of 1 if this FC uses classifier to identify traffic-type unicast, multicast, broadcast, and unknown-unicast respectively
FC_i (unicast), FC_i (multicast), FC_i(broadcast), and FC_i (unknown-unicast) are set to a value of 0 if this FC does not use a classifier to identify this traffic-type

If the user does not configure meters explicitly for the FC and meter ‟11” is not created, the default unicast meter is used for all traffic types; therefore only one classification entry in hardware is required by the FC. If the user does not configure meters explicitly for the FC and meter ‟11” is created, the default unicast meter and multicast meter are used. By default, two classification entries in hardware are required by an FC.

Determining the number of classification entries per policy (TC)

Taking into account the number of match criteria and the number of FCs used, use the following equation to determine the total number of classification entries per policy.

TC = S E(i) * C(i)

i = nc, h1, ef, h2, l1, af, l2, be

where:

E(i) is the number of match-criteria entries that classify packets to FCi. For 7210 SAS platforms, the maximum number of classification entries per policy can be 64 (including default).
C(i) is the number of classification entries that are required by FCi to identify different traffic types.

Determining the number of policers/meters per policy (TP)

Determine the number of policers or meters to use (for example TP). A maximum of 32 meters per policy are available.

Only those meters associated with FCs are considered for number of meters. Note that only ‟FCs in use” is considered.

Total QoS resources required (TQ) = max ((TC), (2 * TP))

The number obtained is rounded off to next multiple of ‟2” greater than the TQ obtained using this equation.

The user configures the value of TQ using the num-qos-classifiers command.

For more examples and information about resource allocation, see Service ingress QoS policy configuration considerations.

Service ingress QoS policies resource usage examples

This section provides resource usage examples for service ingress QoS policies.

Example 1

sap-ingress 10 create
description‟example-policy-1”
           num-qos-classifiers 8
            meter 1 create
            exit
            meter 3 create
                rate cir 100 pir 100
            exit
            meter 11 multipoint create
            exit
            fc "af" create
                meter 1
            exit
            fc "be" create
                meter 3
            exit
            fc "h2" create
                meter 3
            exit
            fc "l1" create
                meter 3
            exit
            mac-criteria
                entry 1 create        
                    match 
                        dot1p 7 7
                    exit
                    action fc "af"
                exit
                entry 2 create
                    match 
                        dot1p 5 7
                    exit
                    action fc "l1"
                exit
                entry 3 create
                    match 
                        dot1p 6 7
                    exit
                    action fc "h2"
                exit
                default-fc "be"

In example 1, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 1 + 0 = 2

Because this FC uses a unicast meter, an entry is needed to identify this traffic type explicitly. Another entry is needed to classify broadcast, multicast, and unknown-unicast traffic type to the same FC and use the default meter 11.

FCl1 = 1 + 0 + 1 + 0 = 2

FCaf = 1 + 0 + 1 + 0 = 2

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 1 + 0 = 2

Use the following equation to calculate the total classification entries used by this policy.

TC = (0 * 0)nc + (0 * 0)h1 + (0 * 0)ef + (1 * 2)h2 + (1 * 2) l1 + (1 * 2)af + (0 * 0) l2 + (1 * 2) be = 8

(three explicit match criteria entries are used to map traffic to each of FC H2, FC L1, and FC AF along with a default classification entry for FC BE).

The number of meters used = 3 (because both FCs use meter 1, meter 3, and meter 11).

In this example, num-qos-classifiers 16 is used (that is, maximum of (8, (2 * 3))).

If the same policy were used for a SAP in an Epipe service, and all traffic is classified to a unicast traffic type and only unicast meters are used, the following computation is used.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using the preceding equation, calculate the total classification entries used = 4 and meters used = 2.

Example 1a (default multipoint meter 11 is not used)

sap-ingress 10 create
description  ‟example-policy”
num-qos-classifiers 4
meter 1  create
rate cir 0 pir max
exit
meter 3 create
rate cir 100 pir 100
exit

scope template

default-fc  be

fc be  create
meter 3
exit
fc af  create
meter 1
exit
fc l1  create
meter 3
exit
fc h2  create
meter 3
exit
mac-criteria dot1p-only
entry 1 create
match dot1p 7
action fc af
exit
entry 2  create
match dot1p 5
action fc l1
exit
entry 3  create
match dot1p  6
action fc h2
exit
exit
exit

In example 1a, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 0 + 0 = 1

Because this FC uses unicast meter for all traffic types, an entry to classify all traffic types to this FC explicitly is required.

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Calculate the total classification entries used by this policy, using the following equation.

TC = (0 * 0)nc + (0 * 0)h1 + (0 * 0)ef + (1 * 1)h2 + (1 * 1)l1 + (1 * 1)af + (0 * 0)l2 + (1 * 1)be = 4

(three explicit match criteria entries are used to map traffic to each of FC H2, FC L1, and FC AF along with a default classification entry for FC BE).

The total number of meters used = 2 (because FCs use meter 1 and meter 3).

In this example, num-qos-classifiers 4 is used (maximum of (4, (2 * 2))). The use of a unicast meter for all traffic-types allows QoS resources to be used efficiently.

If the same policy were used for a SAP in an Epipe service, and all traffic is classified to a unicast traffic type and only unicast meters are used, the following computations are used.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using this equation, total classification entries used = 4 and meters used = 2.

Using the same policy for Epipe SAPs can lead to inefficient use of resources. Nokia recommends creating a different policy with the required number of resources (that is, with num-qos-classifiers 4).

Example 2

sap-ingress 10 create
description‟example-policy-1”
num-qos-classifiers16
             meter 1 create
              exit
            meter 2 create
                rate cir 1 pir 20
            exit
            meter 3 create
                rate cir 100 pir 100
            exit
            meter 11 multipoint create
            exit
            fc "af" create
                meter 3
                broadcast-meter 2
            exit
            fc "be" create
                meter 3
                broadcast-meter 2
            exit
            fc "h2" create
                meter 3
                broadcast-meter 2
            exit                      
            fc "l1" create
                meter 3
                broadcast-meter 2
            exit
            mac-criteria
                entry 1 create
                    match 
                        dot1p 7 7
                    exit
                    action fc "af"
                exit
                entry 2 create
                    match 
                        dot1p 5 7
                    exit
                    action fc "l1"
                exit
                entry 3 create
                    match 
                        dot1p 6 7
                    exit
                    action fc "h2"
                exit                  
            exit
            default-fc "be"

In example 2, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 1 + 1 + 0 = 3

FC uses unicast meter and broadcast meter, so two entries are required to identify these traffic types explicitly. Another entry is required to classify multicast and unknown-unicast traffic type to the same FC and use the default meter 11.

FCl1 = 1 + 1 + 1 + 0 = 3

FCaf = 1 + 1 + 1 + 0 = 3

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 1 + 1 + 0 = 2

Using this equation, the total classification entries used = 11 (three explicit match criteria entries map to each of FC H2, L1, and AF along with a default classification rule for BE).

Meters used = 3 (FCs use only meter 2, meter 3, and meter 11).

Therefore, in this example, num-qos-classifiers 16 is used (that is, a maximum of (12, (2*3))). Note that the system internally uses 18, instead of 16.

If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type, and only unicast meters are used, use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using this equation, the total classification entries used = 4 and the total meters used = 1.

Example 2a (default multipoint meter 11 is not used)

sap-ingress 10 create
description  ‟example-policy-1”
num-qos-classifiers  8

meter 1 create
rate cir 0 pir max
exit
meter 3 create
rate cir  100 pir 100
exit
meter 2 create
rate cir 1 pir 20
exit
scope template
default-fc be
fc be  create
meter  3
broadcast-meter 2
exit
fc af  create
meter  3
broadcast-meter 2
exit
fc l1  create
meter  3
broadcast-meter 2
exit
fc h2  create
meter  3
broadcast-meter 2
exit
mac-criteria dot1p-only
entry  1  create
match dot1p  7
action fc af
exit
entry 2  create
match dot1p 5
action fc l1
exit
entry 3 create
match dot1p  6
action fc h2
exit
exit

In example 2a, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 1 + 0 = 2

Because this FC uses a unicast meter for unicast, multicast, unknown-unicast traffic, and broadcast meter for broadcast traffic, so two entries are needed.

FCl1 = 1 + 0 + 1 + 0 = 2

FCaf = 1 + 0 + 1 + 0 = 2

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 1 + 0 = 2

Using this equation to get the total classification, entries used = 8 (three explicit match criteria entries map to each of FC H2, L1, and AF along with a default classification rule for BE).

The number of meters used = 2 (FCs use only meter 2 and meter 3).

Hence, in this example num-qos-classifiers 8 is used (that is, maximum of (8, (2*2))).

If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type and only unicast meters are used, use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using the preceding equation, to get total classification entries used = 4 and meters used = 1. As can be seen here, using the same policy for Epipe SAP can lead to inefficient use of resources. Nokia recommends creating a different policy with the required number of resources (that is, with num-qos-classifiers 4).

Example 3

sap-ingress 10 create
description‟example-policy-2”
num-qos-classifiers 16
             meter 1 create
                rate cir 100 pir 100
            exit
            meter 2 create
                rate cir 1 pir 20
            exit
            meter 3 create
                rate cir 100 pir 100
            exit
            meter 4 create
                rate cir 10 pir 100
            exit
            meter 5 create
                rate cir 10 pir 10
            exit
            meter 11 multipoint create
                rate cir 1 pir 20
            exit
            fc "af" create
                meter 3
                broadcast-meter 2     
                multicast-meter 4
            exit
            fc "h1" create
                meter 5
                broadcast-meter 4
                multicast-meter 4
                unknown-meter 4
            exit
            fc "h2" create
                meter 3
                broadcast-meter 2
            exit
            fc "l1" create
                meter 3
                broadcast-meter 2
            exit
            mac-criteria
                entry 1 create
                    match 
                        dot1p 7 7
                    exit
                    action fc "af"
                exit                  
                entry 2 create
                    match 
                        dot1p 5 7
                    exit
                    action fc "l1"
                exit
                entry 3 create
                    match 
                        dot1p 6 7
                    exit
                    action fc "h2"
                exit
                entry 4 create
                    match 
                        dot1p 3 7
                    exit
                    action fc "h1"
                exit
            exit
            default-fc "be"

In example 3, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 1 + 1 + 1 + 1 = 4

Because this FC uses unicast, broadcast, multicast, and unknown-unicast meter, four entries are required to identify these traffic types explicitly.

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 1 + 1 + 0 = 3

Because this FC uses unicast meter and broadcast meter, two entries are required to identify these traffic types explicitly. Another entry is required to classify multicast and unknown-unicast traffic type to the same FC and use the default meter 11.

FCl1 = 1 + 1 + 1 + 0 = 3

Because this FC uses only unicast meter, an entry is required to identify this traffic type explicitly. Another entry is required to classify broadcast, multicast, and unknown-unicast traffic type to the same FC and use the default meter 11.

FCaf = 1 + 1 + 1 + 0 = 3

Because this FC uses unicast, broadcast, and multicast meter, three entries are required to identify these traffic types explicitly. Unknown-unicast traffic type is classified using the same entry as multicast traffic type and uses the same meter.

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 1 + 0 = 2

Using the preceding equation, the total classification entries used = 15 and the total meters used = 6.

If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type and only unicast meters are used, use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 1 + 0 + 0 + 0 = 1

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using the preceding equation, the total classification entries used = 5 and the total meters used = 3 (because all FCs used only meter 1, meter 3, and meter 5).

Example 3a (default multipoint meter 11 is not used)

sap-ingress 10 create
description  ‟example-policy-2”
num-qos-classifiers  12

meter 1 create
rate cir 100 pir 100
exit
meter 3 create
rate cir 100 pir 100
exit
meter  2 create
rate cir 1 pir 20
exit
meter 4 create
rate cir 10 pir 100
exit
meter 5 create
rate cir 10 pir 10
exit
scope template
default-fc   be
fc af  create
meter  3
broadcast-meter 2
multicast-meter 4
exit
fc l1  create
meter  3
broadcast-meter 2
exit
fc h2  create
meter  3
broadcast-meter 2
exit
fc h1  create
meter 5
broadcast-meter 4
multicast-meter 4
unknown-meter 4
exit 
mac-criteria dot1p-only
entry  1  create
match dot1p  7
action fc af
exit
entry 2  create
match dot1p 5
action fc l1
exit
entry 3  create
match dot1p  6
action fc h2
exit
entry 4  create
match dot1p 3
action fc h1
exit
exit

In example 3a, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 1 + 1 + 1 + 1 = 4

Because this FC uses unicast, broadcast, multicast, and unknown-unicast meter, four entries are needed to identify these traffic types explicitly.

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 1 + 0 = 2

Because this FC uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly, multicast and unknown-unicast traffic use the same resource as the unicast traffic.

FCl1 = 1 + 0 + 1 + 0 = 2

Because this FC uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly. Multicast and unknown-unicast traffic use the same resource as unicast traffic.

FCaf = 1 + 1 + 1 + 0 = 3

Because this FC uses unicast, broadcast, and multicast meter, three entries are needed to identify these traffic types explicitly. Unknown-unicast traffic type is classified using the same entry as multicast traffic type and uses the same meter.

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Because no explicit meters are configured for FC ‟be”, it uses meter 1 for all traffic types and needs one entry to identify these traffic types.

Using the preceding equation, the total classification entries used = 12 and meters used = 5. The num-qos-classifiers CLI command can be set to 12 (the minimum value).

Using the same policy for a SAP in an Epipe service, all traffic is classified to a unicast traffic type and only unicast meters are used, the following computations are used.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 1 + 0 + 0 + 0 = 1

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using the preceding equation, the total classification entries used = 5 and meters used = 3 (because all FCs used only meter 1, meter 3, and meter 5). For Epipe service, a policy with num-qos-resources 6 can be used.

Example 4

sap-ingress 10 create
description‟example-policy-3”
num-qos-classifiers 36
            meter 1 create
                rate cir 100 pir 100
            exit
            meter 2 create
                rate cir 1 pir 20
            exit
            meter 3 create
                rate cir 100 pir 100
            exit
            meter 4 create
                rate cir 10 pir 100
            exit
            meter 5 create
                rate cir 10 pir 10
            exit
            meter 6 create
                rate cir 11 pir 100
            exit
            meter 8 create
                rate cir 20 pir 100
            exit                      
            meter 11 multipoint create
                rate cir 1 pir 20
            exit
            fc "af" create
                meter 3
                broadcast-meter 2
                multicast-meter 4
            exit
            fc "ef" create
                meter 6
                broadcast-meter 2
                multicast-meter 8
            exit
            fc "h1" create
                meter 5
                broadcast-meter 4
                multicast-meter 4
                unknown-meter 4
            exit
            fc "h2" create
                meter 3
                broadcast-meter 2
            exit                      
            fc "l1" create
                meter 3
                broadcast-meter 2
            exit
            fc "nc" create
                meter 6
                broadcast-meter 2
                multicast-meter 8
            exit
            mac-criteria
                entry 1 create
                    match 
                        dot1p 4 7
                    exit
                    action fc "af"
                exit
                entry 2 create
                    match 
                        dot1p 5 7
                    exit
                    action fc "l1"
                exit
                entry 3 create        
                    match 
                        dot1p 6 7
                    exit
                    action fc "h2"
                exit
                entry 4 create
                    match 
                        dot1p 3 7
                    exit
                    action fc "h1"
                exit
                entry 5 create
                    match 
                        dot1p 2 7
                    exit
                    action fc "ef"
                exit
                entry 6 create
                    match 
                        dot1p 7 7
                    exit
                    action fc "nc"
                exit                  
            exit
            default-fc "be"

In example 4, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 1 + 1 + 1 + 0 = 3

FCh1 = 1 + 1 + 1 + 1 = 4

Because this FC uses unicast, broadcast, multicast and unknown-unicast meter, four entries are required to identify these traffic types explicitly.

FCef = 1 + 1 + 1 + 0 = 3

FCh2 = 1 + 1 + 1 + 0 = 3

FCl1 = 1 + 1 + 1 + 0 = 3

FCaf = 1 + 1 + 1 + 0 = 3

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 1 + 0 = 2

Using the preceding equation, the total classification entries used = 21 and the total meters used = 8.

If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type and only unicast meters are used, use the following computation.

FCnc = 1 + 0 + 0 + 0 = 1

FCh1 = 1 + 0 + 0 + 0 = 1

FCef = 1 + 0 + 0 + 0 = 1

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using the preceding equation, the total classification entries used = 7 and the total meters used = 4.

Using the same policy for Epipe SAP can lead to inefficient use of resources. Nokia recommends creating a different policy with the required number of resources (that is, num-qos-classifiers 16)

Example 4a (default multipoint meter 11 is not used)

sap-ingress 10 create
description  ‟example-policy-3”
num-qos-classifiers  20
meter 1 create
rate cir 100 pir 100
exit
meter 3 create
rate cir  100 pir 100
exit
meter 2 create
rate cir 1 pir 20
exit
meter 4 create
rate cir 10 pir 100
exit
meter 5 create
rate cir 10 pir 10
exit
meter 6 create
rate cir 11 pir 100
exit
meter 8 create
rate cir 20 pir 100
exit
scope template
default-fc  be
fc af  create
meter  3
broadcast-meter 2
multicast-meter 4
exit
fc l1  create
meter 3
broadcast-meter 2
exit
fc h2 create
meter 3
broadcast-meter 2
exit
fc h1 create
meter 5
broadcast-meter 4
multicast-meter 4
unknown-meter 4
exit
fc ef  create
meter 6
broadcast-meter 2
multicast-meter 8
exit
fc nc  create
meter 6
broadcast-meter 2
multicast-meter 8
exit
mac-criteria dot1p-only
entry  1  create
match dot1p  4
action fc af
exit
entry  2  create
match dot1p 5
action fc l1
exit
entry  3   create
match dot1p  6
action fc h2
exit
entry  4  create
match dot1p 3
action fc h1
exit
entry   5  create
match dot1p 2
action fc ef
exit
entry   6  create
match dot1p 7
action fc nc
exit
exit
exit

In example 4a, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 1 + 1 + 1 + 0 = 3

FCh1 = 1 + 1 + 1 + 1 = 4

Because this FC uses unicast, broadcast, multicast, and unknown-unicast meter, four entries are needed to identify these traffic types explicitly.

FCef = 1 + 1 + 1 + 0 = 3

FCh2 = 1 + 1 + 1 + 0 = 3

Because this FC uses unicast meter and broadcast meter, two entries are needed to identify these traffic types explicitly. Multicast and unknown-unicast traffic of the same FC use the unicast resources (both meter and classification entry).

FCl1 = 1 + 1 + 1 + 0 = 3

FCaf = 1 + 1 + 1 + 0 = 3

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Because this FC uses a single meter for all traffic-types only, a single meter and single entry is needed.

Using the preceding equation, the total classification entries used = 20 and meters used = 7. Therefore, in this example num-qos-classifiers 20 is used (the minimum value).

If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type, and only unicast meters are used, use the following computation.

FCnc = 1 + 0 + 0 + 0 = 1

FCh1 = 1 + 0 + 0 + 0 = 1

FCef = 1 + 0 + 0 + 0 = 1

FCh2 = 1 + 0 + 0 + 0 = 1

FCl1 = 1 + 0 + 0 + 0 = 1

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Using the preceding equation, the total classification entries used = 7 and meters used = 4.

Using the same policy for Epipe SAP can lead to inefficient use of resources. Nokia recommends creating a different policy with the required number of resources (that is, with num-qos-classifiers 8).

Example 5

sap-ingress 10 create

          num-qos-classifiers 72
            meter 1 create
            exit
            meter 3 create
            exit
            meter 4 create
            exit
            meter 11 multipoint create
            exit
            fc "af" create
                meter 3
                broadcast-meter 11
                multicast-meter 4
            exit
            fc "be" create
                meter 1
                broadcast-meter 11
            exit
            ip-criteria
                entry 1 create
                    match 
                        dscp be       
                    exit
                    action fc "af"
                exit
                entry 2 create
                    match 
                        dscp cp1
                    exit
                    action fc "af"
                exit
                entry 3 create
                    match 
                        dscp cp3
                    exit
                    action fc "af"
                exit
                entry 4 create
                    match 
                        dscp cp4
                    exit
                    action fc "af"
                exit
                entry 5 create
                    match             
                        dscp cp5
                    exit
                    action fc "af"
                exit
                entry 6 create
                    match 
                        dscp cp6
                    exit
                    action fc "af"
                exit
                entry 7 create
                    match 
                        dscp cp7
                    exit
                    action fc "af"
                exit
                entry 8 create
                    match 
                        dscp cs1
                    exit
                    action fc "af"
                exit
                entry 9 create        
                    match 
                        dscp cp9
                    exit
                    action fc "af"
                exit
                entry 10 create
                    match 
                        dscp af11
                    exit
                    action fc "af"
                exit
                entry 11 create
                    match 
                        dscp cp11
                    exit
                    action fc "af"
                exit
                entry 12 create
                    match 
                        dscp af12
                    exit
                    action fc "af"
                exit                  
                entry 13 create
                    match 
                        dscp cp13
                    exit
                    action fc "af"
                exit
                entry 14 create
                    match 
                        dscp cp15
                    exit
                    action fc "af"
                exit
                entry 15 create
                    match 
                        dscp cp15
                    exit
                    action fc "af"
                exit
            exit
            default-fc "be"

In example 5, assuming the policy is attached to a SAP in a VPLS service, classification entries used per FC use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 0 + 0 + 0 + 0 = 0

FCl1 = 0 + 0 + 0 + 0 = 0

FCaf = 1 + 0 + 1 + 0 = 3

Because this FC uses unicast meter, an entry is required to identify these traffic types explicitly. Another entry is required to classify broadcast, multicast, and unknown-unicast traffic type to the same FC and use the default meter 11.

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 1 + 1 + 0 = 3

Calculate the total classification entries used by this policy using the following equation.

TC = (0 * 0)nc + (0 * 0)h1 + (0 * 0)ef + (0 * 0)h2 + (0 * 0)l1 + (15 * 3)af + (0 * 0)l2 + (1 * 3)be = 48

The total meters used in this policy = 4.

In example 5, num-qos-classifiers 72 is used (that is, a maximum of (48, (2 * 4)) = 48, rounded off to the next available numQosClassifier range.

If the same policy were used for a SAP in an Epipe service, all traffic is classified to a unicast traffic type and only unicast meters are used, use the following computation.

FCnc = 0 + 0 + 0 + 0 = 0

FCh1 = 0 + 0 + 0 + 0 = 0

FCef = 0 + 0 + 0 + 0 = 0

FCh2 = 0 + 0 + 0 + 0 = 0

FCl1 = 0 + 0 + 0 + 0 = 0

FCaf = 1 + 0 + 0 + 0 = 1

FCl2 = 0 + 0 + 0 + 0 = 0

FCbe = 1 + 0 + 0 + 0 = 1

Calculate the total classification entries used by this policy using the following equation.

TC = (0 * 0)nc + (0 * 0)h1 + (0 * 0)ef + (0 * 0)h2 + (0 * 0)l1 + (15 * 1)af + (0 * 0)l2 + (1 * 1)be = 16

The total meters used in this policy = 2.

For Epipe SAP, Nokia recommends defining another sap-ingress policy using num-qos-classifiers 16 (maximum of (16, (2 * 2)) = 16.

Basic configurations

A basic service ingress QoS policy must conform to the following:

have a unique service ingress QoS policy ID
allocate the number of classifier and meter resources needed for use
have a QoS policy scope of template or exclusive
have at least one default unicast FC meter/queue
(optional) use multipoint FC meter/queue

Create service ingress QoS policies

Configuring and applying QoS policies is optional. If no QoS policy is explicitly applied to a SAP, a default QoS policy is applied.

Service ingress QoS policy

Note:

A meter is available to limit the bandwidth per FC on service ingress.

To create a service ingress policy, perform the following.

Define a policy ID value. The system does not dynamically assign a value.
Define a description that provides a brief overview of policy features.
Specify the num-qos-classifiers command. The default value is 2. The number of meters/queue allocated is equal to half the number of classifiers specified.
Specify a default FC for the policy. All packets received on an ingress SAP using this ingress QoS policy will be classified to the default FC.
Define FC parameters by performing the following:
- Modify the unicast-meter/queue default value to override the default unicast forwarding type meter mapping for fc fc-name.
- Modify the multicast-meter/queue default value to override the default multicast forwarding type meters/queue mapping for fc fc-name.
- Modify the multicast-meter/queue default value to override the default unknown unicast forwarding type meter mapping for fc fc-name.
- Modify the broadcast-meter default value to override the default broadcast forwarding type meter mapping for fc fc-name.
On platforms where applicable, specify the following classification criteria - IPv4/IPv6 or MAC criteria, or both IP and MAC criteria. You can define IPv4/IPv6, MAC-based and MAC and IP based SAP ingress policies to select the ingress meter and corresponding FC for matched traffic.

A SAP ingress policy is created with a template scope. The scope can be modified to exclusive for a special one-time use policy. Otherwise, the template scope enables the policy to be applied to multiple SAPs.

The following is a sample service ingress policy configuration output.

A:ALA-7>config>qos>sap-ingress# info
----------------------------------------------
...
        sap-ingress 100 create
            description "Used on VPN sap"
...
----------------------------------------------
A:ALA-7>config>qos>sap-ingress#

Service ingress QoS meter

To create service ingress meter parameters, perform the following.

Define a new meter ID value; the system does not dynamically assign a value.

Configure meter parameters. Ingress meters support the definition of either srTCM (Single Rate Tri-Color Meter) or trTCM (Two Rate Tri-Color Meter), CIR/PIR, CBS/MBS parameters.

The following is a sample ingress meter configuration output.

A:ALA-7>config>qos# info
#------------------------------------------
echo "QoS Policy Configuration"
#------------------------------------------
...
sap-ingress 100 create
description "Used on VPN sap"
meter 1 create
exit
meter 11 multipoint create
exit
meter 2 create
rate cir 11000
exit
meter 3 create
cbs 32
rate cir 11000
exit
meter 4 create
rate cir 100 pir 500
exit
meter 5 create
cbs 64
mbs 128
rate cir 1500 pir 1500
exit
meter 6 create
mode srtcm
rate cir 2500 pir 2500
exit
meter 7 create
cbs 256
mbs 512
rate cir 100 pir 36
exit
meter 8 create
cbs 256
mbs 512
rate cir 11000
exit
meter 9 create
rate cir 11000
exit
meter 10 create
rate cir 1
exit
meter 12 create
rate cir 1500 pir 1500
exit
meter 13 create
rate cir 2500 pir 2500
exit
meter 14 create
rate cir 36 pir 100
exit
meter 15 create
rate cir 36 pir 100
exit
meter 16 create
cbs 128
mbs 256
rate cir 36 pir 100
exit
...
#------------------------------------------
A:ALA-7>config>qos#

SAP ingress FC

The following is a sample FC configuration output.

A:ALA-7>config>qos# info
#------------------------------------------
...
fc af create
meter 1
broadcast-meter 7
unknown-meter 8
exit
fc be create
meter 2
unknown-meter 9
exit
fc ef create
meter 3
broadcast-meter 10
exit
fc h1 create
meter 4
multicast-meter 12
exit
fc h2 create
meter 5
broadcast-meter 13
multicast-meter 14
unknown-meter 15
exit
fc nc create
meter 6
broadcast-meter 16
multicast-meter 17
unknown-meter 18
exit


...
#------------------------------------------

Service ingress IP match criteria

When specifying SAP ingress match criteria, only one match criteria type can be configured in the SAP ingress QoS policy.

The following is a sample ingress IP criteria configuration output.

A:ALA-7>config>qos# info
...
#------------------------------------------
echo "QoS Policy Configuration"
#------------------------------------------
...
sap-ingress 100 create
...
ip-criteria
entry 10 create
description "Entry 10-FC-AF"
match dscp af12
exit
action fc af
exit
entry 20 create
description "Entry 20-FC-BE"
match dscp be
exit
no action
exit
exit
exit
..
#------------------------------------------
A:ALA-7>config>qos#

Service ingress MAC match criteria

To configure service ingress policy MAC criteria, perform the following.

Define a new entry ID value. Entries must be explicitly created; the system does not dynamically assign entries or a value.
Associate the FC with a specific MAC criteria entry ID.

Define a description. The description provides a brief overview of policy features.

The following is a sample ingress MAC criteria configuration output.

A:ALA-7>config>qos# info
...
#------------------------------------------
echo "QoS Policy Configuration"
#------------------------------------------
...
        sap-ingress 101 create
...
            mac-criteria
                entry 10 create
                    description "Entry10"
                    match
                        dst-mac 04-67-ff-00-00-01 ff-ff-ff-ff-ff-ff
                        dot1p 7 7
                    exit
                    action fc be
                exit
            exit
        exit
#------------------------------------------
A:ALA-7>config>qos#

Applying service ingress policies

This section describes applying SAP ingress policies to service SAPs.

Epipe service

The following sample configuration output shows an Epipe service configuration with SAP ingress policy 100 applied to the SAP.

A:ALA-7>config>service# info
----------------------------------------------
        epipe 6 customer 6 vpn 6 create
            description "Epipe service to west coast"
            sap 1/1/10:10 create
                exit
                ingress
                    qos 100
                exit
            exit
        exit
----------------------------------------------
A:ALA-7>config>service#

VPLS

The following sample configuration output shows a VPLS service configuration with SAP ingress policy 100.

A:ALA-7>config>service# info
----------------------------------------------
        vpls 700 customer 7 vpn 700 create
            description "test"
            stp
                shutdown
            exit
            sap 1/1/9:10 create
                ingress
                    qos 100
                exit
            exit
        exit
----------------------------------------------
A:ALA-7>config>service#

IES

Note:

SAP ingress QoS policies for access SAPs and IES on access SAPs are only supported on 7210 SAS-D and 7210 SAS-Dxp.

The following is a sample IES service configuration output.

A:ALA-7>config>service# info
----------------------------------------------
...
ies 1 customer 1 create
 interface "to-c1" create
  address 10.1.0.1/24
   sap 1/1/10:100 create
    ingress
     qos 100
    exit
   exit
  exit
  no shutdown
 exit
...
----------------------------------------------
A:ALA-7>config>service#

Service management tasks

This section describes the service management tasks.

Deleting QoS policies

Every service SAP is associated, by default, with the appropriate ingress policy (policy-id 1). You can replace the default policy with a customer-configured policy, but you cannot entirely remove the policy from the SAP configuration. When you remove a non-default service ingress policy, the association reverts to the default policy-id 1.

A QoS policy cannot be deleted until it is removed from all SAPs where it is applied.

A:ALA-7>config>qos# no sap-ingress 100
MINOR: CLI SAP ingress policy "100" cannot be removed because it is in use#
A:ALA-7>config>qos#

Removing a QoS policy from service SAPs

The following Epipe service output examples show that the SAP service ingress reverts to policy-id 1 when the non-default policies are removed from the configuration.

A:ALA-104>config>service>epipe# info detail
----------------------------------------------
description "Distributed Epipe service to west coast"
                no tod-suite
                dot1ag
                exit
                ingress
                    qos 1 
                    no filter
                exit
                egress
                    no filter
                exit
                no collect-stats
                no accounting-policy
                no shutdown           
----------------------------------------------
A:ALA-7>config>service>epipe#

Copying and overwriting QoS policies

You can copy an existing service ingress policy, rename it with a new policy ID value, or overwrite an existing policy ID. The overwrite option must be specified or an error occurs if the destination policy ID exists.

 config>qos# copy {sap-ingress} source-policy-id dest-policy-id [overwrite]

Remove a policy from the QoS configuration

Use the following syntax to remove a configuration policy from the QoS configuration.

 config>qos# no sap-ingress policy-id

 config>qos# no sap-ingress 100

Editing QoS policies

You can change existing QoS policies and entries. The changes are applied immediately to all services where this policy is applied. To prevent configuration errors, copy the policy to a work area, make the edits, and then overwrite the original policy.

Service SAP QoS policy command reference

Service ingress QoS policy commands

    - config 
        - qos
            - [no] sap-ingress policy-id [create]
                - default-fc fc 
                - no default-fc
                - description description-string
                - no description 
                - [no] fc fc-name [create]
                    - broadcast-meter meter-id
                    - no broadcast-meter
                    - meter meter-id
                    - no meter
                    - multicast-meter meter-id
                    - no multicast-meter
                    - unknown-meter meter-id
                    - no unknown-meter
                - [no] ip-mac-match {ip-first | mac-first}
                - [no] ip-criteria [any | dscp-only]
                    - [no] entry entry-id [create]
                        - action [fc fc-name]
                        - no action
                        - description description-string
                        - no description
                        - match [protocol protocol-id]
                        - no match
                            - dscp dscp-value | dscp-name [dscp-mask]
                            - no dscp
                            - dst-ip {ip-address/mask | ip-address netmask} 
                            - no dst-ip
                            - dst-port {eq} dst-port-number
                            - no dst-port
                            - ip-prec ip-prec-value [ip-prec-mask]
                            - no ip-prec
                            - src-ip ip-address/mask
                            - no src-ip
                            - src-port {eq} src-port-number
                            - no src-port
                    - renum [old-entry-id new-entry-id]
                - [no] ipv6-criteria [any | dscp-only] [IPv6 Match Criteria]
                    - [no] entry entry-id [create]
                        - action [fc fc-name]
                        - no action
                        - description description-string
                        - no description
                        - match [next-header next-header]
                        - no match
                            - dscp dscp-value | dscp-name [dscp-mask]
                            - no dscp
                            - dst-ip {ipv6-address/prefix-length} 
                            - no dst-ip
                            - dst-port {eq} dst-port-number}
                            - no dst-port
                            - ip-prec ip-prec-value [ip-prec-mask]
                            - no ip-prec
                            - src-ip {ipv6-address/prefix-length} 
                            - no src-ip
                            - src-port {eq} src-port-number
                            - no src-port
                        - renum [old-entry-id new-entry-id]
                - [no] mac-criteria [any |dot1p-only]
                    - [no] entry entry-id [create]
                        - action [fc fc-name]
                        - no action
                        - description description-string
                        - no description
                        - [no] match
                            - dot1p dot1p-value [dot1p-mask]
                            - no dot1p
                            - dst-mac ieee-address [ieee-address-mask]
                            - no dst-mac
                            - etype 0x0600..0xffff
                            - no etype
                            - src-mac ieee-address [ieee-address-mask]
                            - no src-mac
                        - renum old-entry-id new-entry-id
                - meter meter-id [multipoint] [create]
                - no meter meter-id
                    - adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
                    - no adaptation-rule
                    - cbs size [kbits | bytes | kbytes]
                    - no cbs
                    - color-mode color-mode
                    - no color-mode
                    - mbs size [kbits | bytes | kbytes]
                    - no mbs
                    - mode mode
                    - no mode
                    - rate cir-rate-in-kbps [pir pir-rate-in-kbps]
                    - no rate
                - num-qos-classifiers [num-resources] [ipv6 | no-ipv6]
                - scope {exclusive | template}
                - no scope

Operational commands

    - config
        - qos
            - copy sap-ingress src-pol dst-pol [overwrite]

Show commands

    - show
        - qos
            - sap-ingress policy-id [detail | association | match-criteria]

Command descriptions

Configuration commands

Generic commands

description

Syntax

description description-string

no description

Context

config>qos>sap-ingress

config>qos>sap-ingress>ip-criteria>entry

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a text description stored in the configuration file for a configuration context.

The no form of this command removes any description string from the context.

Parameters

description-string: Specifies a text string describing the entity. Allowed values are any string up to 80 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Operational commands

Note:

QoS capabilities vary across 7210 SAS platforms. The terms meter/queue or queue/meter are used in the command descriptions; meters, queues, or both may apply depending on the capabilities of the 7210 SAS platform. The descriptions of specific commands also mention the capabilities of the platform/node, where applicable.

copy

Syntax

copy sap-ingress src-pol dst-pol [overwrite]

Context

config>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command copies existing QoS policy entries for a QoS policy-id to another QoS policy-id.

The copy command is a configuration level maintenance tool used to create new policies based on existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters

sap-ingress src-pol dst-pol

Specifies that the source policy ID and the destination policy ID are SAP ingress policy IDs. Specify the source policy ID that the copy command will attempt to copy from, and specify the destination policy ID to which the command will copy a duplicate of the policy.

Values: 1 to 65535

overwrite: Specifies to replace the existing destination policy. Everything in the existing destination policy is overwritten by the contents of the source policy. If overwrite is not specified, an error occurs if the destination policy ID exists.

renum

Syntax

renum old-entry-id new-entry-id

Context

config>qos>sap-ingress>ip-criteria

config>qos>sap-ingress>ipv6-criteria

config>qos>sap-ingress>mac-criteria

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command renumbers existing QoS policy criteria entries to properly sequence policy entries.

This can be required in some cases because the 7210 SAS exits when the first match is found and executes the actions in accordance with the accompanying action command. This requires that entries be sequenced correctly from most to least explicit.

Parameters

old-entry-id

Specifies the entry number of an existing entry.

Values: 1 to 64

new-entry-id

Specifies the new entry number to be assigned to the old entry.

Values: 1 to 64

Service ingress QoS policy commands

sap-ingress

Syntax

[no] sap-ingress policy-id [create]

Context

config>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command is used to create or edit the ingress policy. The ingress policy defines the Service Level Agreement (SLA) enforcement service packets receive when they ingress a SAP. SLA enforcement requires the definition of meters/queues (depends on the support available on a platform) that have Forwarding Class (FC), Committed Information Rate (CIR), Peak Information Rate (PIR), Committed Burst Size (CBS), and Maximum Burst Size (MBS) characteristics. The simplest policy defines a single queue/meter that all ingress traffic flows through. Complex policies have multiple meters/queues combined with classification entries that indicate which meter/queue a packet flows though.

Policies in effect are templates that can be applied to multiple services as long as the scope of the policy is template. Meters/ queues defined in the policy are not instantiated until a policy is applied to a service SAP.

Depending on the support available on different 7210 SAS platforms, SAP ingress policies can be defined with either dot1p, IP DSCP, IP headers, MAC headers, or all as the match criteria.

Only one service ingress policy can be provisioned. The SAP ingress policy with policy-id 1 is a system-defined policy applied to services when no other policy is explicitly specified. The system SAP ingress policy can be modified but not deleted. The no sap-ingress command restores the factory default settings when used on policy-id 1. See Default SAP ingress policy for more information.

Any changes made to the existing policy, using any of the sub-commands, are applied immediately to all services where this policy is applied. For this reason, when many changes are required on a policy, it is recommended that the policy be copied to a work area policy ID. The work area policy can be modified until complete and then written over the original policy ID. Use the config qos copy command to maintain policies in this manner.

Note:

Before a SAP ingress policy can be associated with a SAP, resources must be allocated using the config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource command. See Resource allocation for service ingress QoS policy classification rules for information about resource allocation. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about system resource allocation and examples for this CLI command.
On the 7210 SAS-D and 7210 SAS-Dxp, only meters are supported on service ingress for rate enforcement. These platforms do not support service ingress queues.
On the 7210 SAS-D and 7210 SAS-Dxp, the user has the option to use dot1p, IP DSCP, IPv4 and IPv6 criteria, and MAC criteria.

The no form of this command deletes the SAP ingress policy. A policy cannot be deleted until it is removed from all services where it is applied. The system default SAP ingress policy is a special case; the no command restores the factory defaults to policy ID1.

Default

policy-id 1

Parameters

policy-id

Specifies a policy ID that uniquely identifies the policy.

Values: 1 to 65535

create: Specifies to create a SAP ingress policy.

scope

Syntax

scope {exclusive | template}

no scope

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the service ingress QoS policy scope.

The no form of this command reverts the scope of the policy to the default.

Default

template

Parameters

exclusive: Specifies that the policy can only be applied to one SAP. If a policy with an exclusive scope is assigned to a second SAP, an error message is generated. If the policy is removed from the exclusive SAP, it will become available for assignment to another exclusive SAP.

template: Specifies that the policy can be applied to multiple SAPs on the router. An error is generated when scope template is changed to scope exclusive for default policies.

default-fc

Syntax

default-fc fc

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the default FC for the policy. If an ingress packet does not match a higher priority (more explicit) classification command, the default FC is associated with the packet. Unless overridden by an explicit FC classification rule, all packets received on an ingress SAP using this ingress QoS policy is classified to the default FC.

The default FC is best effort (be). The default-fc settings are displayed in the show configuration and save output, regardless of whether the detail keyword is included in the show command.

The in and out parameters are mutually exclusive following the profile classification keyword. Either in or out must be specified when the profile keyword is present.

Default

Parameters

fc: Specifies the FC name for the queue/meter. The value specified for fc must be one of the predefined FCs in the system.

fc

Syntax

[no] fc fc-name [create]

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

The fc command creates a class instance of the FC fc-name. After the fc-name is created, classification actions can be applied and then used in match classification criteria.

The no form of this command removes all explicit queue mappings for fc-name forwarding types. The queue mappings revert to the default meters for fc-name.

Parameters

fc-name

Specifies the FC name for the queue. The value specified for the fc-name must be one of the predefined FCs for the system.

Values: be, l2, af, l1, h2, ef, h1, nc

create: Keyword to create a class instance of the FC.

ip-mac-match

Syntax

[no] ip-mac-match {ip-first | mac-first}

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the user to match on both IP and MAC criteria in a SAP ingress policy. If this command is not executed, the software does not allow for configuration of both IP and MAC criteria in a SAP ingress policy. In other words, without this command in a SAP ingress policy, IP and MAC criteria are mutually exclusive.

The user also has the option to specify if all the IP criteria entries configured in the policy need to be matched first followed by all the MAC criteria entries or the other way around. For example, if ip-first is configured, all the IP criteria entries are compared for matches first; if there are no matches, then MAC criteria entries are compared for matches.If a match is found, no further matches are performed and the actions associated with the matched entry are taken.

The no form of the command reverts to the default value.

Default

no ip-mac-match

Parameters

ip-first: Specifies to match all the IP criteria entries first before matching any of the MAC entries.

mac-first: Specifies to match all the MAC criteria entries first before matching any of the IP entries.

ip-criteria

Syntax

[no] ip-criteria [any | dscp-only] policy id

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command selects the ingress meter and corresponding FC for matched traffic.

The user can specify either any or dscp-only as the sub-criteria. The sub-criteria determines what fields can be used to match traffic. The resource allocation for classification is affected by the sub-criteria in use. See Resource allocation for service ingress QoS policy classification rules for more information.

This command is used to enter the context to create or edit policy entries that specify IP criteria DiffServ code point.

The 7210 SAS implementation exits on the first match found and executes the actions in accordance with the accompanying action command. For this reason, entries must be sequenced correctly from most to least explicit.

The no form of this command deletes all the entries specified under this node. After an IP criteria entry is removed from a SAP ingress policy, the IP criteria is removed from all services where that policy is applied.

Default

dscp-only

Parameters

any: Specifies that entries can use any of the fields available under ip-criteria (Example - IP source, IP destination, IP protocol fields can be used) for matching

dscp-only: Specifies that entries can use the IP DSCP field or IP precedence field.

policy-id

Specifies the policy ID.

Values: 1 to 65535

ipv6-criteria

Syntax

[no] ipv6-criteria [any | dscp-only] policy-id

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command selects the appropriate ingress meters and corresponding FC for matched traffic.

This command is used to enter the node to create or edit policy entries that specify IPv6 criteria, such as IP quintuple lookup or DSCP.

Note:

Before associating a SAP ingress policy configured to use IPv6 criteria with a SAP, resources must be allocated using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv6-ipv4-match-enable command. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information about this CLI command and resource allocation.

The no form of this command deletes all the entries specified under this node. After an IPv6 criteria entry is removed from a SAP ingress policy, the IPv6 criteria is removed from all services where that policy is applied.

Parameters

any: Specifies that entries can use any of the fields available under ipv6-criteria (Example - IPv6 source, IPv6 destination, IPv6 protocol fields can be used) for matching

dscp-only: Specifies that entries can use the IP DSCP field or IPv6 precedence field.

policy-id

Specifies the policy ID.

Values: 1 to 65535

mac-criteria

Syntax

[no] mac-criteria [any | dot1p-only] policy id

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command selects the appropriate ingress meters and corresponding FC for matched traffic.

User can specify either any or dot1p-only as the sub-criteria. The sub-criteria determines what fields can be used to match traffic. The resource allocation for classification is affected by the sub-criteria in use. See Resource allocation for service ingress QoS policy classification rules for more information about SAP ingress resource allocation.

This command is used to enter the node to create or edit policy entries that specify MAC criteria.

The 7210 SAS OS implementation exits on the first match found and executes the actions in accordance with the accompanying action command. For this reason, entries must be sequenced correctly from most to least explicit.

The no form of this command deletes all the entries specified under this node. After a MAC criteria entry is removed from a SAP ingress policy, the MAC criteria is removed from all services where that policy is applied.

Default

dot1p-only

Parameters

any: Specifies that entries can use the other MAC header fields for matching.

dot1p-only: Specifies that entries can use only the dot1p field.

policy-id

Specifies the policy ID.

Values: 1 to 65535

num-qos-classifiers

Syntax

num-qos-classifiers [num-resources] [ipv6 | no-ipv6]

Context

config>qos>sap-ingress>num-qos-classifiers

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the number of classifiers the SAP ingress Qos policy can use. This parameter cannot be modified when it is associated with a SAP.

The num-resources parameter also determines the maximum number of meters that are available to this policy. The maximum number of meters available for use by the FCs (FC) defined under this policy is equal to half the value specified in num-resources parameter (maximum of 32). Any of these meters are available for use to police unicast or multipoint traffic. Any of these meters is available for use by more than one FC (or a single meter is available for use by all the FCs).

The ipv6 keyword indicates a plan to use ipv6-criteria, and the resources needed for this SAP ingress QoS policy must be allocated to the slice assigned to IPv6 criteria.

Default

num-qos-classifiers 2 no-ipv6

Parameters

num-resources

Specifies the number of resources planned for use by this policy. The value must be a multiple of two.

Values: 2 to 256

ipv6: Specifies to use ipv6-criteria. The software must allocate resources from the chunks alloted to IPv6 criteria.

no-ipv6: Specifies to not use ipv6-criteria. Resources are then allocated from the chunk alloted to either IPv4 criteria or MAC criteria, depending on what criteria the user uses.

Service ingress QoS policy forwarding class commands

broadcast-meter

Syntax

broadcast-meter meter-id

no broadcast-meter

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default broadcast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a multipoint meter before the mapping can be made. After the FC mapping is executed, all broadcast traffic on a SAP using this policy is forwarded using the meter-id.

The broadcast forwarding type usually tracks the multicast forwarding type definition. This command overrides that default behavior.

The no form of this command reverts the broadcast forwarding type meter-id to the default of tracking the multicast forwarding type meter mapping.

Parameters

meter-id

Specifies an existing multipoint queue defined in the config>qos>sap-ingress context.

Values: 1 to 32

Default: 1

meter

Syntax

meter meter-id

no meter

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default unicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a non-multipoint meter before the mapping can be made. After the FC mapping is executed, all unicast traffic (this includes all traffic, even broadcast and multicast for services) on a SAP using this policy is forwarded using the meter-id.

The no form of this command reverts the unicast (point-to-point) meter-id to the default meter for the FC.

Parameters

meter-id

Specifies an existing non-multipoint meter defined in the config>qos>sap-ingress context.

Values: 1 to 32

Default: 1

multicast-meter

Syntax

multicast-meter meter-id

no multicast-meter

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default multicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a multipoint meter before the mapping can be made. After the FC mapping is executed, all multicast traffic on a SAP using this policy is forwarded using the meter-id.

The multicast forwarding type includes the unknown unicast forwarding type and the broadcast forwarding type, unless each is explicitly defined to a different multipoint meter. When the unknown and broadcast forwarding types are left as default, they will track the defined meter for the multicast forwarding type.

The no form of this command reverts the multicast forwarding type meter-id to the default meter for the FC. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint meter, they are also reverted to the default multipoint meter.

Parameters

meter-id

Specifies an existing multipoint meter defined in the config>qos>sap-ingress context.

Values: 1 to 32

Default: 1

unknown-meter

Syntax

unknown-meter meter-id

no unknown-meter

Context

config>qos>sap-ingress>fc

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default unknown unicast forwarding type meter mapping for fc fc-name. The specified meter-id must exist within the policy as a multipoint meter before the mapping can be made. After the FC mapping is executed, all unknown traffic on a SAP using this policy is forwarded using the meter-id.

The unknown forwarding type usually tracks the multicast forwarding type definition. This command overrides that default behavior.

The no form of this command reverts the unknown forwarding type meter-id to the default of tracking the multicast forwarding type meter mapping.

Parameters

meter-id

Specifies an existing multipoint meter defined in the config>qos>sap-ingress context.

Values: 1 to 32

Default: 1

Service ingress QoS policy entry commands

action

Syntax

action [fc fc-name]

no action

Context

config>qos>sap-ingress>ip-criteria>entry

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This mandatory command associates the FC with specific IP or MAC criteria entry ID. The action command supports setting the FC parameter. Packets that meet all match criteria within the entry have their FC overridden based on the parameters included in the action parameters.

The action command must be executed for the match criteria to be added to the active list of entries.

Each time action is executed on a specific entry ID, the previously entered values for fc fc-name are overridden with the newly defined parameters.

The no form of this command removes the entry from the active entry list. Removing an entry on a policy immediately removes the entry from all SAPs using the policy. All previous parameters for the action are lost.

Default

action specified by the default-fc command

Parameters

fc fc-name

Specifies the FC name for the queue. When a packet matches the rule, the FC is only overridden when the fc fc-name parameter is defined on the rule. If the packet matches and the FC is not explicitly defined in the rule, the FC is inherited based on previous rule matches.The value specified for fc fc-name must be one of the predefined FCs in the system.

Values: be, l2, af, l1, h2, ef, h1, nc

entry

Syntax

[no] entry entry-id [create]

Context

config>qos>sap-ingress>ip-criteria

config>qos>sap-ingress>mac-criteria

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates or edits an IP or MAC criteria entry for the policy. Multiple entries can be created using unique entry-id numbers.

The list of flow criteria is evaluated in a top-down fashion with the lowest entry ID at the top and the highest entry ID at the bottom. If the defined match criteria for an entry within the list matches the information in the egress packet, the system stops matching the packet against the list and performs the matching reclassification actions specified by the entries. If none of the entries match the packet, the IP flow reclassification list has no effect on the packet.

An entry is not populated in the list unless the action command is executed for the entry. An entry that is not populated in the list has no effect on egress packets. If the action command is executed without any explicit reclassification actions specified, the entry is populated in the list allowing packets matching the entry to exit the list, preventing them from matching entries lower in the list. Because this is the only flow reclassification entry that the packet matched and this entry explicitly states that no reclassification action is to be performed, the matching packet is not reclassified.

The no form of this command removes the specified entry from the policy. Entries removed from the policy are immediately removed from all services where that policy is applied.

Parameters

entry-id

Specifies a match criterion and the corresponding action. It is recommended that multiple entries be assigned entry IDs in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.

An entry may not have any match criteria defined (in which case, everything matches) but it must have at least the command action fc for it to be considered complete. Entries without the action command are considered incomplete and are rendered inactive.

Values: 1 to 64

create: This keyword is required when creating a flow entry if the system is configured to require the explicit use of the keyword to prevent accidental object creation. Objects may be accidentally created when this protection is disabled and an object name is mistyped when attempting to edit the object. This keyword is not required when the protection is disabled. The keyword is ignored when the flow entry already exists.

match

Syntax

[no] match [protocol protocol-id]

Context

config>qos>sap-ingress>ip-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures match criteria for SAP QoS policy matches. When the match criteria are satisfied, the action associated with the match criteria is executed.

If more than one match criteria (within one match statement) are configured, then all criteria must be satisfied (and function) before the action associated with the match will be executed.

A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.

The no form of this command removes the match criteria for the entry.

Parameters

protocol protocol-id

Specifies an IP protocol to be used as an ingress or egress network QoS policy match criterion.

The protocol type is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), and UDP(17).

Values

protocol-id: 0 to 255 protocol numbers accepted in decimal, hexadecimal, or binary

keywords: none, crtp, crudp, egp, eigrp, encap, ether-ip, gre, icmp, idrp, igmp, igp, ip, ipv6, ipv6-frag, ipv6-icmp, ipv6-no-nxt, isis, ipv6-opts, isoip, l2tp, ospf-igp, pim, pnni, ptp, rdp, rsvp, stp, tcp, udp, vrrp

* — udp/tcp wildcard

match

Syntax

match

no match

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates or edits the match MAC criteria for ingress SAP QoS policy match criteria. When the match criteria are satisfied the action associated with the match criteria is executed.

If more than one match criterion (within one match statement) is configured, all criteria must be satisfied (and function) before the action associated with the match is executed.

A match context can consist of multiple match criteria, but multiple match statements cannot be entered per entry.

The no form of this command removes the match criteria for the entry-id.

match

Syntax

match [next-header next-header]

no match

Context

config>qos>sap-ingress>ipv6-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures match criteria for ingress SAP QoS policy match IPv6 criteria. When the match criteria are satisfied, the action associated with the match criteria is executed.

If more than one match criterion (within one match statement) is configured, all criteria must be satisfied (and function) before the action associated with the match is executed.

A match context can consist of multiple match criteria, but multiple match statements cannot be specified per entry.

The no form of this command removes the match criteria for the entry-id.

Parameters

next-header next-header

Specifies the next header to match.

The protocol type such as TCP / UDP / OSPF is identified by its respective protocol number. Well-known protocol numbers include ICMP(1), TCP(6), UDP(17).

Values

protocol numbers accepted in DHB: 0 to 42, 45 to 49, 52 to 59, 61 to 255

keywords: none, crtp, crudp, egp, eigrp, encap, ether-ip, gre, icmp, idrp, igmp, igp, ip, ipv6, ipv6-icmp, ipv6-no-nxt, isis, isoip, l2tp, ospf-igp, pim, pnni, ptp, rdp, rsvp, stp, tcp, udp, vrrp

* — udp/tcp wildcard

IP QoS policy match commands

dscp

Syntax

dscp dscp-value | dscp-name [dscp-mask]

no dscp

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a DiffServ Code Point (DSCP) used for classification of packets from the specified FC.

The no form of this command removes the DSCP match criterion.

Note:

This feature is applicable for ip-criteria (any and dscp-only) and ipv6-criteria (any and dscp-only).
The user is not be allowed to configure dscp name and dscp mask combinations.
When the user configures dscp value alone, the ‟show” command displays dscp value as configured value and dscp mask as ‟FC”.
Use of dscp-value and dscp-mask allows for efficient use of match resources in hardware, because the specification of mask allows user to combine individual DSCP entries to a single value/mask pair and specify similar action for all of them.

Parameters

dscp-value

Specifies the DSCP value in hexadecimal, decimal, or binary format.

Values: 0 to 64

dscp-name

Specifies a DSCP name that has been previously mapped to a value using the dscp-name command. The DSCP can only be specified by its name.

Values: be, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cs1, cp9, af11, cp11, af12, cp13, af13, cp15, cs2, cp17, af21, cp19, af22, cp21, af23, cp23, cs3, cp25, af31, cp27, af32, cp29, af33, cp31, cs4, cp33, af41, cp35, af42, cp37, af43, cp39, cs5, cp41, cp42, cp43, cp44, cp45, ef, cp47, nc1, cp49, cp50, cp51, cp52, cp53, cp54, cp55, nc2, cp57, cp58, cp59, cp60, cp61, cp62, cp63

dscp-mask

Specifies a 6-bit mask that can be configured using the formats described in the following table.

This parameter is only supported on the 7210 SAS-D and 7210 SAS-Dxp.

Table 3. DSCP mask value format
Format style	Format syntax	Example
Decimal	D	4
Hexadecimal	0xH	0x4
Binary	0bBBB	0b100

To select a range from 4 up to 7 specify 4 and 0b000100 for value and mask.

Values: 0 to 64 (decimal, hexadecimal, or binary)

Default: 64 (exact match)

dst-ip

Syntax

dst-ip {ip-address/mask}

dst-ip {ipv6-address/mask}

no dst-ip

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a destination address range to use as a SAP QoS policy match criterion.

To match on the destination address, specify the address and its associated mask; for example, 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 can also be used.

The no form of this command removes the destination IP address match criterion.

Parameters

ip-address

Specifies the IP address of the destination IP interface. This address must be unique within the subnet and specified in dotted-decimal notation.

Values


ipv4-prefix -	a.b.c.d

ipv6-address

Specifies the IP address of the destination IPv6 interface. This address must be unique within the subnet.

Values


ipv6-prefix -	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

mask

Specifies the length in bits of the subnet mask.

Values

1 to 32 (IPv4)

1 to 128 (IPv6; 7210 SAS-D)

1 to 64 (IPv6; 7210 SAS-Dxp)

dst-port

Syntax

dst-port {eq} dst-port-number

no dst-port

Context

config>qos>sap-ingress

config>qos>sap-ingress>ip-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a destination TCP or UDP port number for a SAP QoS policy match criterion.

The no form of this command removes the destination port match criterion.

Parameters

eq dst-port-number

Specifies the destination TCP or UDP port number, specified as equal to (eq) the destination port value specified as a decimal integer.

Values: 1 to 65535

ip-prec

Syntax

ip-prec ip-prec-value [ip-prec-mask]

no ip-prec

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-ingress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies an IP precedence value that must be matched to perform the associated classification actions. If an ingress packet on the SAP where the SAP ingress QoS policy is applied to matches the specified IP precedence value, the actions associated with this entry are taken.

The ip-prec-value is derived from the most significant three bits in the IP header ToS byte field (precedence bits). The three precedence bits define eight Class-of-Service (CoS) values commonly used to map packets to per-hop Quality-of-Service (QoS) behavior. The precedence bits are also part of the newer DSCP method of mapping packets to QoS behavior. The DSCP uses the most significant six bits in the IP header ToS byte and so overlaps with the precedence bits.

Both IP precedence and DSCP classification rules are supported. A match entry cannot match on both IP DSCP and IP precedence, which means that the user can use either IP DSCP or IP precedence match in a match entry but not both. The software blocks configuration of ip-precedence match if the ip-dscp command is configured already. The converse is also true. A single policy having multiple match entries can have entries such that some of them match IP DSCP and others match IP precedence. The order of the entry determines the priority of the match.

The no form of this command removes the IP precedence match criterion.

Parameters

ip-prec-value

Specifies the unique IP header ToS byte precedence bits value that matches the IP precedence rule.

Values: 0 to 7

ip-prec-mask

Specifies a mask that can be configured using the formats described in the following table.

Table 4. IP precedence mask value format
Format style	Format syntax	Example
Decimal	D	4
Hexadecimal	0xH	0x4
Binary	0bBBB	0b100

To select a range from 4 up to 7, specify an ip-prec-value of 4 and an ip-prec-mask of 0b100 for value and mask.

src-ip

Syntax

src-ip ipv4-address/mask

no src-ip

Context

config>qos>sap-ingress>ip-criteria>entry>match

config>qos>sap-egress>ip-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a source IPv4 address range to use as a SAP QoS policy match criterion.

To match on the source IPv4 address, specify the address and its associated mask; for example, 10.1.0.0/16. The conventional notation of 10.1.0.0 255.255.0.0 can also be used.

The no form of this command removes the source IPv4 address match criterion.

Parameters

ipv4-address

Specifies the IPv4 address of the source IP interface. This address must be unique within the subnet and specified in dotted-decimal notation.

Values: a.b.c.d

mask

Specifies the subnet mask length, expressed as an integer or in dotted-decimal notation.

Values: 1 to 32

src-ip

Syntax

src-ip ipv6-address/mask

no src-ip

Context

config>qos>sap-ingress>ipv6-criteria>entry>match

config>qos>sap-egress>ipv6-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a source IPv6 address range to use as a SAP QoS policy match criterion.

The no form of this command removes the source IPv6 address match criterion.

Parameters

ipv6-address

Specifies the IPv6 address of the source IP interface. This address must be unique within the subnet.

Values


ipv6-address	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

mask

Specifies the subnet mask length, expressed as an integer.

Values

1 to 128 (7210 SAS-D)

1 to 64 (7210 SAS-Dxp)

src-port

Syntax

src-port {eq} src-port-number

no src-port

Context

config>qos>sap-ingress>ip-criteria>entry>match

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a source TCP or UDP port number for a SAP QoS policy match criterion.

The no form of this command removes the source port match criterion.

Parameters

eq src-port-number

Specifies the source TCP or UDP port number, as a decimal integer, against which to match equal (eq) values.

Values: 1 to 65535

Service ingress MAC QoS policy match commands

dot1p

Syntax

dot1p dot1p-value [dot1p-mask]

no dot1p

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the IEEE 802.1p value to use as the match criterion.

The no form of this command removes the dot1p value as the match criterion.

Parameters

dot1p-value

Specifies the IEEE 802.1p value, expressed as a decimal integer.

Values: 0 to 7

dot1p-mask

Specifies a 3-bit mask that can be configured using the following formats.

Table 5. 3-bit mask format
Format style	Format syntax	Example
Decimal	D	4
Hexadecimal	0xH	0x4
Binary	0bBBB	0b100

Values: 1 to 7 (decimal)

Default: 7 (decimal; exact match)

dst-mac

Syntax

dst-mac ieee-address [ieee-address-mask]

no dst-mac

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a destination MAC address or range to use as a service ingress QoS policy match criterion.

The no form of this command removes the destination MAC address as the match criterion.

Parameters

ieee-address

Specifies the MAC address to use as a match criterion.

Values: HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit

ieee-address-mask

Specifies a 48-bit mask to match a range of MAC address values.

This 48-bit mask can be configured using the formats described in the following table.

Table 6. dot1p mask value format
Format style	Format syntax	Example
Decimal	DDDDDDDDDDDDDD	281474959933440
Hexadecimal	0xHHHHHHHHHHHH	0xFFFFFF000000
Binary	0bBBBBBBB...B	0b11110000...B

All packets with a source MAC OUI value of 00-03-FA subject to a match condition should be specified as: 0003FA000000 0x0FFFFF000000

Values: 0x00000000000000 to 0xFFFFFFFFFFFF (hexadecimal)

Default: 0xFFFFFFFFFFFF (hexadecimal; exact match)

etype

Syntax

etype etype-value

no etype

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures an Ethernet type II value for to use as a service ingress QoS policy match criterion.

The Ethernet type field is a two-byte field used to identify the protocol carried by the Ethernet frame. For example, 0800 is used to identify IPv4 packets.

The Ethernet type field is used by the Ethernet version-II frames. IEEE 802.3 Ethernet frames use the dsap, ssap or snap-pid fields as match criteria; the Ethernet type field is not used.

The snap-pid, etype, ssap, and dsap fields are mutually exclusive and cannot be part of the same match criteria.

For the 7210 SAS-D and 7210 SAS-Dxp, the dataplane processes a maximum of two VLAN tags in a received packet. The Ethertype used in the MAC matching criteria for ACLs is the Ethertype that is found in the packet after processing single-tagged frames, double-tagged frames, and no-tag frames

The packet is considered to have no tags if at least one of the following criteria is true:

the packet is a null-tagged frame
the packet is a priority-tagged frame
the outermost Ethertype does not match the default Ethertype (0x8100)
the outermost Ethertype does not match the configured dot1q-etype on dot1q encapsulated ports
the outermost Ethertype does not match the configured qinq-etype on QinQ encapsulated ports

The packet is considered to have a single tag if at least one of the following criteria is true:

the outermost Ethertype matches the default Ethertype (0x8100)
the outermost Ethertype matches the configured dot1q-etype on dot1q encapsulated ports
the outermost Ethertype matches the configured qinq-etype on QinQ encapsulated ports

The packet is considered to have double tags if at least one of the following criteria is true:

the outermost Ethertype matches the default Ethernet type (0x8100)
the configured dot1q-etype on dot1q encapsulated ports and the immediately following Ethertype match the default Ethertype (0x8100)
the configured qinq-etype on QinQ encapsulated ports and the immediately following Ethertype match the default Ethertype (0x8100)

The no form of this command removes the previously entered etype field as the match criteria.

Parameters

etype-value

Specifies the Ethernet type II frame Ethertype value to be used as a match criterion in decimal or hexadecimal.

Values: 0x0600 to 0xFFFF

src-mac

Syntax

src-mac ieee-address [ieee-address-mask]

no src-mac

Context

config>qos>sap-ingress>mac-criteria>entry

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a source MAC address or range to be used as a service ingress QoS policy match criterion.

The no form of this command removes the source MAC address as the match criteria.

Parameters

ieee-address

Specifies the 48-bit IEEE MAC address to be used as a match criterion.

Values: HH:HH:HH:HH:HH:HH or HH-HH-HH-HH-HH-HH where H is a hexadecimal digit

ieee-address-mask

Specifies a 48-bit mask that can be configured using the formats in the following table.

Table 7. MAC mask format
Format style	Format syntax	Example
Decimal	DDDDDDDDDDDDDD	281474959933440
Hexadecimal	0xHHHHHHHHHHHH	0x0FFFFF000000
Binary	0bBBBBBBB...B	0b11110000...B

To configure all packets with a source MAC OUI value of 00-03-FA are subject to a match condition, then the entry should be specified as: 003FA000000 0xFFFFFF000000

Values: 0x00000000000000 to 0xFFFFFFFFFFFF (hexadecimal)

Default: 0xFFFFFFFFFFFF (hexadecimal; exact match)

Service meter QoS policy commands

meter

Syntax

meter meter-id [multipoint] [create]

no meter meter-id

Context

config>qos>sap-ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters

meter-id

Specifies the meter within the policy. This is a required parameter each time the meter command is executed.

Values: 1 to 32

multipoint: Keyword that creates the meter as a multipoint meter.

create: Keyword to create a meter.

adaptation-rule

Syntax

adaptation-rule [cir adaptation-rule] [pir adaptation-rule]

no adaptation-rule

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

adaptation-rule cir closest pir closest

Parameters

cir adaptation-rule

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.

Note:

For 7210 SAS-Dxp, see Adaptation rule for meters for information about calculating the next multiple equal to or less than the specified rate.

Default: closest

Values

max — Specifies that the operational CIR value is less than or equal to the specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

min — Specifies that the operational CIR value is greater than or equal to the specified rate, taking into account the hardware step size. When min is defined, the operational CIR is the next multiple of 8 kbps that is greater than or equal to the specified rate.

closest — Specifies that the operational CIR value is equal to the closest specified rate, taking into account the hardware step size. When closest is defined, the operational CIR is the next multiple of 8 kbps that is closest to the specified rate.

pir adaptation-rule

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.

Note:

For 7210 SAS-Dxp, see Adaptation rule for meters for information about calculating the next multiple equal to or less than the specified rate.

Default: closest

Values

max — Specifies that the operational PIR value is less than or equal to the specified rate, taking into account the hardware step size. The hardware step size varies based on the rate and the platform.

min — Specifies that the operational PIR value is greater than or equal to the specified rate, taking into account the hardware step size. When min is defined, the operational PIR is the next multiple of 8 kbps that is greater than or equal to the specified rate.

closest — Specifies that the operational PIR value is equal to the closest specified rate, taking into account the hardware step size. When closest is defined, the operational PIR is the next multiple of 8 kbps that is closest to the specified rate.

cbs

Syntax

cbs size [kbits | bytes | kbytes]

no cbs

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Note:

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.

Default

32 kbits

Parameters

size

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.

Values

kbits — 4 to 16384, default (7210 SAS-D)

4 to 2146959, default (7210 SAS-Dxp)

bytes — 512 to 2097152, default (7210 SAS-D)

512 to 274810752, default (7210 SAS-Dxp)

kbytes — 1 to 2048, default (7210 SAS-D)

1 to 268369, default (7210 SAS-Dxp)

color-mode

Syntax

color-mode color-mode

no color-mode

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

color-blind

Parameters

color-mode

Specifies the mode the meter operates in.

Values

color-aware — The meter operates in color-aware mode.

color-blind —The meter operates in color-blind mode.

mbs

Syntax

mbs size [kbits | bytes | kbytes]

no mbs

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Note:

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.

Default

128 kbits

Parameters

size

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.

Values

kbits — 4 to 16384, default (7210 SAS-D)

4 to 2146959, default (7210 SAS-Dxp)

bytes — 512 to 2097152, default (7210 SAS-D)

512 to 274810752, default (7210 SAS-Dxp)

kbytes — 1 to 2048, default (7210 SAS-D)

1 to 268369, default (7210 SAS-Dxp)

mode

Syntax

mode {trtcm1 | trtcm2 | srtcm}

no mode

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Note:

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.

Default

trtcm1

Parameters

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.

trtcm2: 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).

Note:
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.

srtcm: 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

Syntax

rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]

no rate

Context

config>qos>sap-ingress>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

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.

Parameters

cir cir-rate-in-kbps

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.

Values

0 to 20000000, max (7210 SAS-Dxp)

0 to 4000000, max (7210 SAS-D)

pir pir-rate-in-kbps

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.

Values

0 to 20000000, max (7210 SAS-Dxp)

0 to 4000000, max (7210 SAS-D)

Show commands

sap-ingress

Syntax

sap-ingress [policy-id] [detail | association | match-criteria]

Context

show>qos

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays SAP ingress QoS policy information.

Parameters

policy-id

Displays information about the specific policy ID.

Values: 1 to 65535

Default: all SAP ingress policies

detail: Displays detailed policy information including policy associations.

associations: Displays the policy associations of the sap-ingress policy.

match-criterion: Displays the match-criterion of the sap-ingress policy.

Output

The following outputs are examples of QoS SAP ingress policy information, and Output fields: QoS SAP ingress describes the output fields:

Sample output

*A:SAS>show>qos# sap-ingress 1 detail

===============================================================================
QoS Sap Ingress
===============================================================================
-------------------------------------------------------------------------------
Sap Ingress Policy (1)
-------------------------------------------------------------------------------
Policy-id                 : 1                 Scope                : Template
Default FC                : be
Criteria-type             : None
Accounting                : packet-based
Classifiers Allowed       : 4                 Meters Allowed       : 2
Classifiers Reqrd (VPLS)  : 2                 Meters Reqrd (VPLS)  : 2
Classifiers Reqrd (EPIPE) : 1                 Meters Reqrd (EPIPE) : 1
Description    : Default SAP ingress QoS policy.

-------------------------------------------------------------------------------
Meter Mode  CIR Admin    CIR Rule   PIR Admin   PIR Rule   CBS Admin MBS Admin
            CIR Oper                PIR Oper               CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm1      0         closest       max       closest   7 KBits 10 KBits
                  0                       max                 def       def
11    TrTcm1      0         closest       max       closest   8 KBits 11 KBits
                  0                       max                 def       def

-------------------------------------------------------------------------------
FC              UCastM         MCastM         BCastM         UnknownM
-------------------------------------------------------------------------------
No FC-Map Entries Found.

-------------------------------------------------------------------------------
Match Criteria
-------------------------------------------------------------------------------
No Matching Criteria.

-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
No Associations Found.

===============================================================================
*A:SAS>show>qos#

The following output is an example of SAP ingress QoS policy information about the 7210 SAS-D when the DCSP value and mask are configured.

Sample output for 7210 SAS-D with DSCP value and mask

*A:7210 SAS> show qos sap-ingress 2 detail

===============================================================================
QoS Sap Ingress
===============================================================================
-------------------------------------------------------------------------------
Sap Ingress Policy (2)
-------------------------------------------------------------------------------
Policy-id                 : 2                 Scope                : Template
Default FC                : be
Criteria-type             : IP                IP-Mac Rule Priority : None
Mac Sub-Criteria          : None              IP Sub-Criteria      : any
IPv6 Enabled              : False             IPv6 Sub-Criteria    : dscp
Accounting                : packet-based
Classifiers Allowed       : 2                 Meters Allowed       : 1
Classifiers Reqrd (VPLS)  : 2                 Meters Reqrd (VPLS)  : 1
Classifiers Reqrd (L3 Mc) : 2                 Meters Reqrd (L3 Mc) : 1
Classifiers Reqrd (EPIPE) : 2                 Meters Reqrd (EPIPE) : 1
Description               : (Not Specified)

-------------------------------------------------------------------------------
Meter Mode        CIR Admin  CIR Rule  PIR Admin  PIR Rule  CBS Admin MBS Admin
      Color Mode  CIR Oper             PIR Oper             CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm1      0          closest   max        closest   def       def
      color-blind 0                    20000000             32        512


-------------------------------------------------------------------------------
FC        UCastM      MCastM      BCastM      UnknownM
-------------------------------------------------------------------------------
No FC-Map Entries Found.

-------------------------------------------------------------------------------
Match Criteria
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
IP Match Criteria
-------------------------------------------------------------------------------
Entry                     : 1
Description    : (Not Specified)
Source IP                 : Undefined         Source Port          : None
Dest. IP                  : Undefined         Dest. Port           : None
Protocol                  : none              DSCP value/mask      : 4/5
Fragment                  : Off               Ip Precedence        : None
FC                        : be

-------------------------------------------------------------------------------
IPv6 Match Criteria
-------------------------------------------------------------------------------
No Match Criteria Entries found.


SAP Associations
-------------------------------------------------------------------------------
Service-Id                : 1 (Epipe)         Customer-Id          : 1
 - SAP : 1/1/24

Sample output for 7210 SAS-D with DSCP name

The following output is an example of SAP ingress QoS policy information about the 7210 SAS-D when the DSCP name is configured.

*A:>config>service>epipe>sap$ /show qos sap-ingress 2 detail

===============================================================================
QoS Sap Ingress
===============================================================================
-------------------------------------------------------------------------------
Sap Ingress Policy (2)
-------------------------------------------------------------------------------
Policy-id                 : 2                 Scope                : Template
Default FC                : be
Criteria-type             : IP                IP-Mac Rule Priority : None
Mac Sub-Criteria          : None              IP Sub-Criteria      : any
IPv6 Enabled              : False             IPv6 Sub-Criteria    : dscp
Accounting                : packet-based
Classifiers Allowed       : 2                 Meters Allowed       : 1
Classifiers Reqrd (VPLS)  : 2                 Meters Reqrd (VPLS)  : 1
Classifiers Reqrd (L3 Mc) : 2                 Meters Reqrd (L3 Mc) : 1
Classifiers Reqrd (EPIPE) : 2                 Meters Reqrd (EPIPE) : 1
Description               : (Not Specified)

-------------------------------------------------------------------------------
Meter Mode        CIR Admin  CIR Rule  PIR Admin  PIR Rule  CBS Admin MBS Admin
      Color Mode  CIR Oper             PIR Oper             CBS Oper  MBS Oper
-------------------------------------------------------------------------------
1     TrTcm1      0          closest   max        closest   def       def
      color-blind 0                    20000000             32        512


-------------------------------------------------------------------------------
FC        UCastM      MCastM      BCastM      UnknownM
-------------------------------------------------------------------------------
No FC-Map Entries Found.

-------------------------------------------------------------------------------
Match Criteria
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
IP Match Criteria
-------------------------------------------------------------------------------
Entry                     : 1
Description    : (Not Specified)
Source IP                 : Undefined         Source Port          : None
Dest. IP                  : Undefined         Dest. Port           : None
Protocol                  : none              DSCP                 : cp63
Fragment                  : Off               Ip Precedence        : None
FC                        : be

-------------------------------------------------------------------------------
IPv6 Match Criteria
-------------------------------------------------------------------------------
No Match Criteria Entries found.


SAP Associations
-------------------------------------------------------------------------------
Service-Id                : 1 (Epipe)         Customer-Id          : 1
 - SAP : 1/1/24

Table 8. Output fields: QoS SAP ingress
Label	Description
Policy-Id	The ID that uniquely identifies the policy
Scope	Exclusive — Implies that this policy can only be applied to a single SAP
Scope	Template — Implies that this policy can be applied to multiple SAPs on the router
Default FC	Specifies the default FC for the policy
Criteria-type	IP — Specifies that an IP criteria-based SAP ingress policy is used to select the appropriate ingress meter and corresponding FC for matched traffic
Criteria-type	MAC — Specifies that a MAC criteria-based SAP is used to select the appropriate ingress meters and corresponding FC for matched traffic
Accounting	Packet-based — Specifies that the meters associated with this policy do not account for packet framing overheads (such as the Inter Frame Gap (IFG) and the preamble for the Ethernet), while accounting for the bandwidth to be used by this flow Frame-based — Specifies that the meters associated with this policy account for the packet framing overheads (such as, for Ethernet, the IFG and preamble), while accounting the bandwidth to be used by the flow
Classifiers Allowed	Indicates the number of classifiers allowed for a service
Classifiers Required	Indicates the number of classifiers for a VPLS or Epipe service
Description	A text string that helps identify the policy’s context in the configuration file
Meter	Displays the meter ID
Mode	Specifies the configured mode of the meter (trTcm1,trTcm2 or srTcm)
CIR Admin	Specifies the administrative CIR parameters for the meters
CIR Rule	min — The operational CIR for the meters will be equal to or greater than the administrative rate specified using the rate command
	max — The operational CIR for the meter will be equal to or less than the administrative rate specified using the rate command
	closest — The operational PIR for the meters will be the rate closest to the rate specified using the rate command without exceeding the operational PIR
PIR Admin	Specifies the administrative PIR parameters for the meters.
PIR Rule	min — The operational PIR for the meter will be equal to or greater than the administrative rate specified using the rate command
	max — The operational PIR for the meters will be equal to or less than the administrative rate specified using the rate command
	closest — The operational PIR for the meters will be the rate closest to the rate specified using the rate command
CBS	def — Specifies the default CBS value for the meters
CBS	value — Specifies the value to override the default reserved buffers for the meters
MBS	def — Specifies the default MBS value
MBS	value — Specifies the value to override the default MBS for the meter
UCastM	Specifies the default unicast forwarding type meters mapping
MCastM	Specifies the overrides for the default multicast forwarding type meter mapping
BCastM	Specifies the default broadcast forwarding type meters mapping
UnknownM	Specifies the default unknown unicast forwarding type meters mapping
Match Criteria	Specifies an IP or MAC criteria entry for the policy
Entry	The entry ID in a policy or filter table
DSCP	Specifies a DiffServ Code Point (DSCP) name used for an ingress SAP QoS policy match
FC	Specifies the entry’s FC
Src MAC	Specifies a source MAC address or range to be used as a Service Ingress QoS policy match
Dst MAC	Specifies a destination MAC address or range to be used as a Service Ingress QoS policy match
dot1p	Specifies a IEEE 802.1p value to be used as the match
Ethernet-type	Specifies an Ethernet type II Ethertype value to be used as a Service Ingress QoS policy match
FC	Specifies the entry’s FC
Service Association
Service-Id	The unique service ID number which identifies the service in the service domain
Customer-Id	Specifies the customer ID which identifies the customer to the service
SAP	Specifies the a Service Access Point (SAP) within the service where the SAP ingress policy is applied
Classifiers required	Indicates the number of classifiers for a VPLS or Epipe service
Meters required	Indicates the number of meters for a VPLS or Epipe service