8.9. Service Ingress QoS Policy Command Reference

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.

This command enables the context to create or edit the ingress policy. The ingress policy defines the Service Level Agreement (SLA) enforcement service packets receive as they ingress a SAP. SLA enforcement is accomplished through the definition of meters and 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 or meter that all ingress traffic flows through. Complex policies have multiple meters/queues combined with classification entries that indicate which meter or queue a packet will flow though.

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

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. That work-in-progress 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 associating a SAP ingress policy with a SAP, resources must be allocated using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command. For more information about this CLI command and resource allocation, see Service Ingress QoS Policies and refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System Configuration Guide. Only meters with the SAP ingress policy are supported on the 7210 SAS-M (access-uplink and network mode), 7210 SAS-T (access-uplink and network mode), 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE; queues are not supported.

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 reverts the factory defaults to policy ID 1.

Note: Default SAP ingress policy ID 1 is used in low-sap-scale mode. Refer to the 7210 SAS-M, T, Mxp, Sx, S Services Guide for more information about low-sap-scale mode and high-sap-scale mode.

This command configures the Service Ingress QoS policy scope as exclusive or template.

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

This command allows the user to choose the dot1p or DSCP classification policies to classify the traffic to an FC. The option to select either dot1p, DSCP, or both, applies only to SAPs configured in Layer 2 services (Epipe and VPLS). It is not applicable to SAPs configured in Layer 3 services (IES, VPRN and RVPLS). See Table-based IP DSCP and Dot1p Classification Policy Commands for SAP Ingress (7210 SAS-Mxp) for more information.

The following options can be used to configure the classification policy.

This command configures the default forwarding class for the policy. In the event that an ingress packet does not match a higher priority (more explicit) classification command, the default forwarding class will be associated with the packet. Unless overridden by an explicit forwarding class classification rule, all packets received on an ingress SAP using this ingress QoS policy will be classified to the default forwarding class.

The default forwarding class is best effort (be). The default-fc settings are displayed in the show configuration and save output regardless of inclusion of the detail keyword.

This command associates a DSCP classification policy with a SAP ingress QoS policy.

The no form of this command removes the DSCP classification policy from its association with the SAP ingress QoS policy.

This command creates a class instance of the forwarding class fc-name. Once the fc-name is created, classification actions can be applied and can be used in match classification criteria.

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

This command must be executed if user intends to match on both IP and MAC criteria in a SAP ingress policy. If this command is not executed software does not allow for configuration of both IP and MAC criteria in a SAP ingress policy. That is, 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 vice-versa. That is, if ip-first is configured all the IP criteria entries are matched and only if there are no matches in the MAC criteria entries are matched. If a match is found no further matches are done and the actions associated with the matched entry are taken.

This command enables the context to create or edit policy entries that specify IP criteria DiffServ code point. IP criteria-based SAP ingress policies are used to select the appropriate ingress meter and corresponding forwarding class 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 SAP Ingress Resource Allocation and Match Criteria Types for more information.

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.

Note: When the use-svc-meter-pool parameter is set or when table-based-classification is used, the ip-criteria entries in the policy are ignored.

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

This command selects the appropriate ingress meters and corresponding forwarding class 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 DiffServ code point.

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.

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. Refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S 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. Once ipv6-criteria entries are removed from a SAP ingress policy, the ipv6-criteria is removed from all services where that policy is applied.

Note: When the use-svc-meter-pool parameter is set or when table-based-classification is used, the ip-criteria entries in the policy are ignored.

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

The 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 SAP Ingress Resource Allocation and Match Criteria Types for more information.

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.

Note: When the use-svc-meter-pool parameter is set or when table-based-classification is used, the ip-criteria entries in the policy are ignored.

The no form of this command deletes all the entries specified under this node. Once mac-criteria entries are removed from a SAP ingress policy, the mac-criteria is removed from all services where that policy is applied.

This command configures the number of classifiers the SAP ingress Qos policy can use. A user cannot modify this parameter when it is in use (that is, applied to a SAP).

The num-resources parameter determines the maximum number of meters that are available to this policy. The maximum number of meters available for use by the forwarding classes (FC) defined under this policy is equal to half the value specified in the parameter num-resources. Any of these meters is 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 keyword ipv6 lets users indicate that they plan to use the ipv6-criteria and the resources needed for this SAP ingress QoS policy must be allocated for the chunk allocated to IPv6 criteria.

On the 7210 SAS-Mxp, this parameter is ignored if the use-svc-meter-pool parameter is set.

This mandatory command associates the forwarding class with specific IP or MAC criteria entry ID. The action command supports setting the forwarding class parameter. Packets that meet all match criteria within the entry have their forwarding class 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 previous entered values for fc is 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 is lost.

This command enables the context to create or edit 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 entries reclassification actions. 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. Since 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 will not be 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.

This command enables the context to configure match criteria for SAP QoS policy match criteria. When the match criteria have been satisfied the action associated with the match criteria is executed.

Only a single match criteria (either MAC or IP) is allowed at any point of time.

This command enables the context for entering and editing match MAC criteria for ingress SAP QoS policy match criteria. When the match criteria have been 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-id.

This command enables the context to configure match criteria for ingress SAP QoS policy match IPv6 criteria. When the match criteria have been 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 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.

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. Once the forwarding class mapping is executed, all broadcast traffic on a SAP using this policy will be 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.

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. Once the forwarding class 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 forwarding class (meter 1).

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. Once the forwarding class 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 forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to a multipoint meter, they will also be set back to the default multipoint meter (11).

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. Once the forwarding class 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.

This command configures a DiffServ Code Point (DSCP) code point to be 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). Either DSCP name or DSCP value with a mask can be configured. When the user configures dscp value alone, the show command displays the dscp value as the configured value and the dscp-mask as the FC.

This command configures a destination address range to be used 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.

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

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

This command configures fragmented or non-fragmented IP packets as a SAP QoS policy match criterion.

The no form of this command removes the match criterion.

This command defines a specific 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 8 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 DiffServ Code Point (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 values. That is, 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 ip-dscp 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 some 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.

This command configures a source IP or IPv6 address range to be used as an SAP QoS policy match criterion.

To match on the source IP or IPv6 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 IP or IPv6 address match criterion.

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

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

This command configures the IEEE 802.1p value to be used as the match criterion.

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

This command configures a destination MAC address or range to be used as a Service Ingress QoS policy match criterion.

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

This command configures an Ethernet type II value for 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.

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 considered to have a single tag if at least one of the following criteria is true:

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

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

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 as the match criteria.

This command enables the context to configure an ingress service access point (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 forwarding class and the meter based on forwarding type) needs to be defined. The individual classification rules used to place traffic into forwarding classes are not affected. Meters must be defined as multipoint at the time of creation within the policy.

The multipoint meters are for multipoint-destined service traffic. Within non-multipoint services, such as Epipe services, all traffic is considered unicast due to the nature of the service type. Multicast and broadcast-destined traffic in an Epipe service will not be 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 returns 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 would not be 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 forwarding class mapped to the meter, will revert to their default meters. When a meter is removed, any pending accounting information for each SAP meter created due to the definition of the meter in the policy is discarded.

Note: The config>qos>fc-meter-map>meter context is only supported on the 7210 SAS-Mxp.

This command defines the method used by the system to derive the operational CIR and PIR rates when the meter is provisioned in hardware. For the cir and pir parameters, the system attempts to find the best operational rate depending on the defined constraint.

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 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 cir and pir apply.

Note: The config>qos>fc-meter-map>meter context is only supported on the 7210 SAS-Mxp.

This command provides a mechanism to override the default CBS for the meter. The committed burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the CBS value then the packets are marked as in-profile by the meter to indicate that the traffic is complying 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 reverts the CBS size to the default value.

Note: The config>qos>fc-meter-map>meter context is only supported on the 7210 SAS-Mxp.

This command specifies that the meter operates in either color-aware mode 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 is used to determine the final color/profile for the packet. If the packet is within the CIR, then the final profile/color assigned to the packet is in-profile/green and if the packets exceeds the CIR and is within the PIR, then 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. Assign the profile on ingress by doing one of the following:

In color-aware mode, the following behavior is expected.

Note: The final disposition of the packet when a hierarchical meter is used depends on the parent meter/policer that is associated with the per FC meter. For example, on the 7210 SAS, when a SAP ingress aggregate meter is used, the final color, and therefore the action taken, also depends on the rate that is configured for the SAP ingress aggregate meter. The SAP ingress aggregate meter, which acts as the parent meter, accounts for the color assigned by the per FC meter.

The no form of this command reverts to the default.

Note: The config>qos>fc-meter-map>meter context is only supported on the 7210 SAS-Mxp.

This command provides a mechanism to override the default maximum burst size (MBS) for the meter. The mbs 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 MBS 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 reverts the MBS size to the default value.

Note: The config>qos>fc-meter-map>meter context is only supported on the 7210 SAS-Mxp.

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 any time.

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 this command reverts to the default mode trtcm1.

Note: The config>qos>fc-meter-map>meter context is only supported on the 7210 SAS-Mxp.

This command defines the administrative PIR and CIR parameters for the meter.

It alters the PIR and CIR for all meters created through the association of the SAP ingress QoS policy with the meter-id.

Note: If the trtcm2 keyword is used to configure the meter mode commands, the system interprets the PIR parameter as the EIR for use by the algorithm defined in RFC 4115. Consequetly, the system configures the policer EIR based on the configured PIR value.

The no form of this command reverts all meters created with the specific meter-id by through the association of the QoS policy with the default PIR and CIR parameters (max, 0). The max default specifies the amount of bandwidth in kilobits per second.

Table 54 lists the maximum CIR and PIR values for 7210 SAS platforms.

This command enables the context to define the map from the dot1p value that is in the Ethernet header of the received frame to the FC and ingress profile.

The no form of this command removes the definition of the map. The no form of this command replaces the specified dot1p-classification with dot1p-classification 1 in the SAP ingress policy or access port.

This command assigns the configured FC and profile to all VLAN tagged Ethernet packets that do not match any of the explicitly configured dot1p values.

The no form of this command assigns a default FC value of be and a profile value of out.

This command maps the dot1p value to a forwarding class and also assign the ingress profile to the packet. This command can be repeated for each dot1p value that the user needs to map.The configured value is used to match the value in the outermost VLAN tag of the received tagged Ethernet packet and assign the configured forwarding class and profile on a exact match.

The no form of this command removes the mapping of the dot1p value to forwarding class.

A default forwarding class is not assigned on executing the no form of this command. If the VLAN tagged packet does not match the explicitly configured dot1p values, it is assigned the FC and profile value configured with the default-dot1p-fc command.

This command enables the context to create or edit a DSCP classification policy.

The no form of this command replaces the specified DSCP classification policy with dscp-classification 1 in the respective SAP ingress policy or access port.

This command configures the default FC and profile values used to map all DSCP values that are not explicitly defined using the dscp command.

The no form of this command reverts the configured default-dscp-fc command FC and profile values to their default settings.

This command maps a DSCP value to an FC and profile. The command can be repeated for each DSCP value that the user needs to map. It is used to match the IP DSCP in the received IP packets to assign the configured FC and profile value.

The no form of this command removes the mapping for the specified dscp-name. If the IP packet does not match the explicitly configured IP DSCP values, it is assigned the FC and profile value that is configured with the default-dscp-fc command.

This command specifies that the SAP ingress policy uses the dot1p classification for the specified policy ID.

The no form of this command reverts to the default.

This command specifies that the SAP ingress policy uses the DSCP classification for the specified policy ID.

The no form of this command reverts to the default.

This command enables the context to specify an FC meter map for a SAP ingress policy. The user cannot modify the FC meter map if it is being referenced by a SAP. The user must update the map before attaching SAP ingress policies on the SAPs.

Note: A single user configurable fc-meter-map policy is available to be used by all SAP ingress policies.

The no form of this command reverts to the default FC meter map policy.

This command is used to configure a counter mode for an FC meter map policy. The in-out-profile-count parameter specifies that in-profile and out-profile packets and octets are counted per meter. The forward-drop-count parameter specifies that forwarded and dropped packets and octets are counted per meter. For all counter modes, packets and bytes are counted simultaneously. The counter counts the in-profile and out-profile packets and octets based on the final profile assigned by the meter/policer using the configured rates.

The no form of this command reverts to the default counter mode.

This command configures FC to meter mappings for an FC meter map policy.

The no form of this command removes all the explicit FC to meter mappings and reverts to the default.

This command overrides the default broadcast forwarding type meter mapping for the fc fc-name command.

The meter-id parameter must exist within the policy before the mapping can be made. After the forwarding class mapping is executed, all broadcast traffic on a SAP that is using this policy is forwarded using the meter-id parameter specified.

The broadcast forwarding type usually tracks the multicast forwarding type definition. This command overrides that default behavior. For more information, see Use of the Keyword “multipoint” for Default Meter “11” and Service Ingress Meter Selection Rules.

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

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

If meter 11 is not configured in the policy, all multipoint traffic (that is, multicast, broadcast, and unknown-unicast traffic) is forwarded using the meter-id. For more information, see Use of the Keyword “multipoint” for Default Meter “11” and Service Ingress Meter Selection Rules.

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

This command overrides the default multicast forwarding type meter mapping for the fc fc-name command. The specified meter-id parameter must exist within the policy before the mapping can be made. After the forwarding class 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 meter. When the unknown and broadcast forwarding types are left as default, they track the defined meter for the multicast forwarding type. For more information, see Use of the Keyword “multipoint” for Default Meter “11” and Service Ingress Meter Selection Rules.

The no form of this command reverts the multicast forwarding type meter-id to the default meter for the forwarding class. If the broadcast and unknown forwarding types are not explicitly defined to a multipoint meter, they are also reverted to the default multipoint meter. By default, the multicast forwarding type uses meter 1, unless the default multipoint meter 11 is configured.

This command overrides the default unknown unicast forwarding type meter mapping for the fc fc-name command. The specified meter-id parameter must exist within the policy before the mapping can be made. After the forwarding class 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. For more information, see Use of the Keyword “multipoint” for Default Meter “11” and Service Ingress Meter Selection Rules.

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

This command configures a meter for an FC meter map policy.