Table 6: Traffic-Profile Set Command Metering Options; Table 7: Traffic-Profile Set Command Action Options - Avaya ERS 45 Series Technical Configuration Manual

port [port] – mandatory command variable the identifies the port to which the filter set will
o
be applied. A valid, QoS-enabled port must be provided.
name [filterSetName] – mandatory command variable that associates the filter set with a
o
label. Name labels are used to identify classifier elements belonging to the same traffic-
profile filter set (i.e., members of a given filter set share the same name label). A 16
character (maximum) name string is supported.
meterData – optional command variables used to specify metering criteria.
o
actionData – optional command variables used to specify additional actions to be
o
performed.
As previously discussed, the ability to meter traffic processed by a traffic-profile filter set is currently
limited. Metering data may be defined for the filter set overall using the options presented in Table 6.
When metering data is specified, a meter is associated with each classifier and unique classifier block.
Each meter has the same characteristics (determined by the command options) and is independently
evaluated (i.e., there is no relationship between meters associated with different filter set
classifiers/blocks). Conforming (i.e., in-profile) traffic is processed based on the action criteria associated
with the individual classifier or block member with the lowest evaluation order. Non-conforming (i.e., out-
of-profile traffic) traffic is processed according to the out-of-profile action options.
Meter Option
committed-rate <64-10230000> Kbps
committed-burst-size <burst-size-options>
max-burst-rate <64-4294967295> Kbps
max-burst-duration <1-4294967295> ms
drop-out-action <enable | disable>
update-dscp-out-action <0-63>

Table 6: Traffic-Profile Set Command Metering Options

Optional command variables can be used to initiate actions that are applied to the overall filter set. The
ability to specify the statistics tracking mode is one such action. Statistics tracking is enabled by default
for all traffic-profile filter sets using the 'aggregate' mode. Statistics may be tracked at a finer level of
granularity (i.e., per classifier) using the 'individual' statistics tracking mode. Statistics tracking can be
bypassed and no counter resources consumed using the 'disable' mode.
Action Option
track-statistics <disable | aggregate | individual>

Table 7: Traffic-Profile Set Command Action Options

Active traffic-profile filter sets can be deleted based on name and/or the associated port. The 'no qos
traffic-profile set' CLI command is used for this purpose:

Command: no qos traffic-profile set [name [filterSetName] | port [port] name
[filterSetName]]
September 2015
Description
Committed rate metering criteria
Committed burst size metering criteria
Maximum burst rate metering criteria
Maximum burst duration metering criteria
Drop (enable) or pass (disable) out-of-profile packets
Update DSCP value in out-of-profile IP packets
Description
Statistics tracking mode (default mode: aggregate)
Avaya Inc. – External Distribution
avaya.com
19