Table of Contents
Advertisement
member with the lowest evaluation order. Non-conforming (i.e., out-of-profile traffic) traffic is processed
based on the out-of-profile action criteria associated with the overall filter set.
Filter Set Statistics Tracking: by default, a counter is associated with each filter set classifier element
and unique classifier block. For a classifier element, the counter tracks matches of the specified
classification criteria. For classifier blocks, the counter tracks the total filter data hits across all the
classifiers in the block. Different statistics tracking modes are available. The default mode is referred to as
'aggregate' mode because of the way counts are totaled, or aggregated, across all the filters referenced
by a policy. Should the user wish to track statistics for each classifier block member, the 'individual' mode
should be specified. Note that counter resource availability determines whether either 'aggregate' or
'individual' statistics tracking modes can be used. If statistics tracking is not necessary or a filter set can
only be installed with statistics tracking disabled (i.e., counter resources are exhausted), the statistics
tracking mode 'disabled' can be specified.
4. Traffic-Profile Filter Set Usage
With the filter set essentials covered, it is time to specifically examine traffic-profile filter set usage.
Configuration and display command syntax will be presented first. Next a series of usage examples will
be presented, followed by a discussion of the areas in which configuration issues more commonly arise.
4.1 Traffic-Profiles Filter Set Configuration
Traffic-profile filter set configuration begins with specifying the classifier criteria used to identify the traffic
being targeted and with specifying the actions to be taken when matching traffic is identified. The 'qos
traffic-profile classifier' CLI command is used for this purpose:
Command: qos traffic-profile classifier name [filterSetName] {classifierData} {actionData}
{elemData}
name [filterSetName] – mandatory command variable that associates the element with a
o
label. Name labels are used to identify 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.
classifierData – optional command variables used for traffic identification purposes.
o
actionData – optional command variables used to specify actions to be performed when
o
traffic matching the classifier data is identified.
elemData – optional command variables that facilitate filter set element ordering and
o
efficient resource utilization.
A large number of classifier options are available to facilitate traffic identification. Zero (i.e., a fully
defaulted element), one or more classifier options can be specified in a single filter set classifier element.
Certain combinations of classifier options may be prohibited based on the ERS stackable platform and
the underlying QoS hardware.
September 2015
Avaya Inc. – External Distribution
avaya.com
16
Hide quick links:
Advertisement
Table of Contents
