Remove A Policy From The Qos Configuration; Editing Qos Policies; Queue Depth Monitoring - Alcatel-Lucent 7950 Quality Of Service Manual

Remove a Policy from the QoS Configuration

CLI Syntax: config>qos# no sap-ingress policy-id
Example

Editing QoS Policies

You can change QoS existing policies and entries. The changes are applied immediately to all
services where this policy is applied. To prevent configuration errors copy the policy to a work
area, make the edits, and then write over the original policy.

Queue Depth Monitoring

Queue depth monitoring gives more visibility to the operator of the queue depths being
experienced on a set of queues when the traffic is bursty. The instantaneous depth of a queue can
be seen using the show pools command, whereas queue depth monitoring shows the variation in
queue depth over a period of time. It is applicable to SAP ingress unicast and multipoint queues
and SAP egress queues, and for ingress and egress access and network queue group queues used
by any service or network interfaces. The monitoring uses a polling mechanism by the line card
CPU. Consequently, the results provided are statistical in nature. This is supported on FP2- and
higher-based line cards.
An override (monitor-depth) is used to enable queue depth monitoring, which is configured under
the SAP or queue group queue-overrides. There are show and clear commands, using the queue-
depth parameter, for both service SAPs and port queue groups with associated MIB variables.
The configuration below gives an example of enabling the monitoring of the depth of queue 1 on
an Epipe SAP.
epipe 1 customer 1 create
7950 XRS Quality of Service Guide
:
config>qos# no sap-ingress 100
config>qos# no sap-egress 1010
sap 1/2/1 create
egress
qos 10
queue-override
queue 1 create
monitor-depth
exit
exit
exit
exit
Service Egress and Ingress QoS Policies
Page 161