The system allows sharing of a single meter for both unicast and multipoint traffic. Users can configure any of the available meters for multipoint traffic. The use of the multipoint keyword during meter creation has been deprecated, except for use with meter ‟11”, as described in the following paragraphs.
When the multipoint keyword is specified with meter "11" the system 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 system does the appropriate resource checks to ensure that resources needed to use multipoint meter with all the FCs are available before allowing this change.
When num-qos-classifiers is set to a value of ‟2”, default multipoint meter "11" cannot be used because only a single meter is available for use.
When associating a meter with an FC for broadcast, unknown-unicast, or multicast (BUM) traffic, the system does not validate whether the meter is a multipoint meter, thereby allowing users to use a single meter for unicast and BUM traffic. This implies efficient use of SAP ingress QoS resources. When the multipoint keyword is used, the system system displays a warning to indicate that multipoint is an obsolete CLI command and is not saved in the configuration file, deprecating the use of the multipoint keyword with any meter other than the default.