Limitations; Qos Monitor Mode Qos Configuration - Avaya 1000 Series Configuration Manual

QOS Configuration
R87> show qos bundle wan1 d1-web
Class: d1-web (Inbound )
Parent Class: d1 (CR = 0 kbps ; BR = 0 kbps)
Interface: Bundle wan1 (bandwidth = 3072 kbps; MON IN: off)
Configuration
--------------
Policing - Rate: 900 Kbps
Application Ports assigned to this Class:
80 8080
Traffic Statistics
------------------
Avg Rate Out: 901.8 Kbps
Avg Rate In: 1000 Kbps
Counters since last boot/clear:
Packets Forwarded: 26222
Bytes Forwarded: 34088600
Packets Dropped: 2913
Bytes Dropped: 3786900
RED: 0
R87>

Limitations

The following limitations apply for this release:
• Policing is not supported for outbound traffic on ethernet interfaces.
• Multi-level policing is not supported. Policing is done only for leaf classes. Any policing
configuration on non-leaf classes is ignored.
• When adding a new outbound class, it is mandatory to specify CR and BR, which are
CBQ parameters, even though the class is intended to be used only for policing.

QoS Monitor Mode QoS Configuration

When the traffic policies are defined on an interface, there are three options which can be
applied to the policies:
• Mon (for traffic monitoring and statistics)
• CBQ (for Class-Based Queuing)
• Policing
This section provides a typical example of using the monitor option to collect policy statistics;
including step-by-step CLI configuration details.
Configuration Steps:
The following are the step-by-step CLI configuration details to achieve this configuration.
Config term
interface bundle wan
224 Avaya Secure Router 1000 Series Configuration Guide
Burst: 1000 msec
-- Packet drop details
Queue overflow: 0
No buffers: 0
Policing: 2913
December 2010