Alcatel-Lucent 7210 SAS E OS Quality Of Service Manual page 99

Parameters fc-name — The case-sensitive, system-defined forwarding class name for which policy entries will
create — The keyword used to create the forwarding class. The create keyword requirement can be
meter
Syntax meter meter-id
no meter meter-id [multipoint] [create]
Context config>qos>network>ingress
Description
This command enables the context to configure an ingress Network QoS policy meter. The meter
command allows the creation of multipoint meters. Only multipoint meters can receive ingress pack-
ets that need to be sent to multiple destinations.
Multipoint meters are for traffic bound to multiple destinations. 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.
The no form of this command removes the meter-id from the Network ingress QoS policy and from
any existing Ports using the policy. If any forwarding class forwarding types are mapped to the meter,
they revert to their default meters. When a meter is removed, any pending accounting information for
each port meter created due to the definition of the meter in the policy is discarded.
Default meter 1 (for unicast traffic)
meter 9 multipoint (for all other traffic, other than unicast traffic)
Parameters meter-id — Specifies the meter-id that uniquely identifies the meter within the policy. This is a
multipoint — This keyword specifies that this meter-id is for multipoint forwarded traffic only. This
7210 SAS-E OS Quality of Service Guide
be created.
Values be, l2, af, l1, h2, ef, h1, nc
enabled/disabled in the environment>create context.
required parameter each time the meter command is executed.
Values 1 — 12
meter-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown
unicast ingress traffic. If you attempt to map forwarding class unicast traffic to a multipoint
queue, an error is generated and no changes are made to the current unicast traffic queue
mapping.
The meter must be created as multipoint. The multipoint designator cannot be defined after the
meter is created. If an attempt is made to modify the command to include the multipoint
keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint meter
to edit meter-id parameters.
Values
multipoint or not present
Default Not present (the queue is created as non-multipoint)
QoS Commands
Page 99