Alcatel-Lucent OmniAccess 5740 - Page 1035

QoS Configuration
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
1009
Alcatel-Lucent
Beta Beta
OmniAccess 5740 Unified Services Gateway CLI Configuration Guide
Example 2
Consider another case with policy p1 with class c1 without random detect. And,
policy p2 with class c2 and random detect enabled included in p1:
ALU(config)# policy-map p1
ALU(config-qos-p1)# class c1
ALU(config-qos-p1-c1)#
ALU(config)# policy-map p2
ALU(config-qos-p2)# class c2
ALU(config-qos-p2-c2)# random detect
ALU(config-qos-p1-c1)# service-policy p2
In the above example, class c2 is random-detect enable but c1 is not.
S
ET (MARKING)
Marking can be configured in every level. But, marking will be applicable in the
leaf level only.
Q
UEUE LIMIT
Queue-limit can be configured in every level. But, queue-limit will be applicable in
the leaf level only.
Example 1
Consider a policy p1 with class c1 and queue limit 150 enabled. And, policy p2
(without queue limit) included in p1:
ALU(config)# policy-map p1
ALU(config-qos-p1)# class c1
ALU(config-qos-p1-c1)# queue-limit 150
ALU(config)# policy-map p2
ALU(config-qos-p2)# class c2
ALU(config-qos-p2-c2)#
ALU(config-qos-p1-c1)# service-policy p2
In the above example, class c2 will also have queue limit 150, which is inherited from
its parent class.