Filt
Filters and QOS Configuration for Ethernet Routing Switch 5500
Technical Configuration Guide
46
January 2013
avaya.com
12.2 Configuration Example 1
– Traffic Meter Using Policies
Figure 5: Traffic Meter Example
The following CLI commands show how to configure a QoS Policy using a Classifier-block with three
classifiers and traffic meters. Overall, in this example, we will configure the following:
Setup one Policy with three classifiers metered with the following TCP flows:
o
For UDP dst port 80, meter traffic at 10M
o
For UDP dst port 69, meter traffic at 5M
o
For UDP dst port 137, meter traffic at 1M
Set the meter bucket size (committed burst) for all meters to maximum value
Add the policy to ports 5 and 6
NOTE:
As all three classifiers use the same mask, we will create a classifier block to group all three
classifiers.
At this time, it is only possible to configure traffic meters using policies. It is not possible
to add traffic meters via ACLs.
12.2.1 ERS 5500 Configuration Using Policies
12.2.1.1 Configure the Interface Role Combination
For this example, we will configure a new role combination with port members 5 and 6. You have the
choice of assigning a policy directly at a port level or using an interface role.
By default, all ports are set for untruste d using the allBayStacklfcs Role Combination. In this example, we
will configure a new Role Combination as unt rusted and assign it to port 5 and 6.
ERS5500 Step 1
– Create the Interface Role Combination and name is “q2”
ERS5500-24T(config)#
qos if-group name q2 class untrusted
ERS5500-24T(config)#
qos if-assign port 5-6 name q2
