EasyManua.ls Logo

Alcatel-Lucent OmniSwitch 6860 Series

Alcatel-Lucent OmniSwitch 6860 Series
1078 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Configuring QoS Creating Policies
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 26-51
A QoS policy list that is assigned to an Application Fingerprinting port must contain policy rules with
the appfp-group condition.
QoS policy lists that contain rules with a link aggregate source port condition are not supported on the
OmniSwitch 9900 or the OmniSwitch 6560.
On the OmniSwitch 9900, only policy rules with the following conditions can be assigned to a UNP
policy list:
Destination MAC
EtherType / IPv6 Hop limit
Source VLAN
–SIP
–DIP / DIPv6
Layer 4 Protocol /NextHeader
Layer 4 source port
Layer 4 destination port
Source port bitmap
Only one policy list per UNP is allowed, but a single policy list can be associated with multiple
profiles. See Chapter 28, “Configuring Access Guardian,” for more information.
Up to 32 policy lists (including the default list) are supported per switch.
If a rule is a member of multiple policy lists but one or more of these lists are disabled, the rule is still
active for those lists that are enabled.
If the QoS status of an individual rule is disabled, then the rule is disabled for all policy lists, even if a
list to which the policy belongs is enabled.
Policy lists are not active on the switch until the qos apply command is issued.
Using the Default Policy List
A default policy list always exists in the switch configuration. By default, a policy rule is added to this list
at the time the rule is created. A rule remains a member a of the default list even when it is subsequently
assigned to additional lists.
Each time a rule is assigned to a list, an instance of that rule is created and allocated system resources. As
a result, rules that belong to multiple lists create multiple instances of the same rule. One way to conserve
resources is to remove a rule from the default policy list.
To exclude a rule from the default policy list, use the no default-list option of the policy rule command
when the rule is created. For example:
-> policy rule r1 condition c1 action a1 no default-list
The no default-list option can also remove an existing rule from the default list. For example, the r2 rule
already exists in the switch configuration but was not excluded from the default list at the time the rule
was created. The following command removes the rule from the default list:
-> policy rule r2 condition c1 action a1 no default-list
To add an existing rule to the default list, use the default-list parameter option of the policy rule
command. For example:

Table of Contents

Related product manuals