
Configuring QoS
Classification
OmniSwitch AOS Release 7 Network Configuration Guide
June 2013
page 25-9
The port trust setting can be configured globally or on a per-port basis to override the global setting.
To configure the global setting on the switch, use the
command. For example:
-> qos trust ports
To configure individual ports as trusted, use the
command with the desired slot/port
number. For example:
-> qos port 3/2 trusted
The global setting is active immediately; however, the port setting requires
qos apply
to activate the
change. See
“Applying the Configuration” on page 25-71
for more information.
To display information about QoS ports, such as whether or not the port is trusted, use the
command. For example:
-> show qos port
Slot/ Default Default
Bandwidth
DEI
Port Active Trust P/DSCP Classification Physical Ingress Egress Map/Mark Type
-----+------+-----+------+---------------+--------+-------+-------+---------+-------------
1/1 No No 0/ 0 DSCP 0K - - No / No ethernet
1/2 Yes No 0/ 0 DSCP 1.00G - - No / No ethernet-1G
1/3 No No 0/ 0 DSCP 0K - - No / No ethernet
1/4 No No 0/ 0 DSCP 0K - - No / No ethernet
1/5 No No 0/ 0 DSCP 0K - - No / No ethernet
1/6 No No 0/ 0 DSCP 0K - - No / No ethernet
1/7 No No 0/ 0 DSCP 0K - - No / No ethernet
1/8 No No 0/ 0 DSCP 0K - - No / No ethernet
1/9 No No 0/ 0 DSCP 0K - - No / No ethernet
1/10 No No 0/ 0 DSCP 0K 50K - No / No ethernet
1/11 No *Yes 0/ 0 *802.1P 0K - - No / No ethernet
1/12 No *Yes 0/ 0 *802.1P 0K - - No / No ethernet
Using Trusted Ports With Policies
Whether or not the port is trusted is important if you want to classify traffic with 802.1p bits. If the policy
condition specifies 802.1p, the switch must be able to recognize 802.1p bits. (Note that the trusted port
must also be 802.1Q-tagged). The 802.1p bits can be set or mapped to a single value using the
command.
In the following example, the
qos port
command specifies that port 2 on slot 3 are able to recognize
802.1p bits. A policy condition (
Traffic
) is then created to classify traffic containing 802.1p bits set to 4
and destined for port 2 on slot 3. The policy action (
SetBits
) specifies that the bits are reset to 7 when the
traffic egresses the switch. A policy rule called
Rule2
puts the condition and the action together.
-> qos port 3/2 trusted
-> policy condition Traffic destination port 3/2 802.1p 4
-> policy action SetBits 802.1p 7
-> policy rule Rule2 condition Traffic action SetBits
To activate the configuration, enter the
qos apply
command. See
“Applying the Configuration” on
for more information.
For actions that set 802.1p bits, note that a limited set of policy conditions are supported. See
and Action Combinations” on page 25-33
for more information.
Note.
802.1p mapping can also be set for Layer 3 traffic, which typically has the 802.1p bits set to zero.
Содержание os6900
Страница 28: ...Contents xxviii OmniSwitch AOS Release 7 Network Configuration Guide June 2013...
Страница 374: ...VRF Route Leak Configuring IP page 15 40 OmniSwitch AOS Release 7 Network Configuration Guide June 2013...
Страница 692: ...Policy Applications Configuring QoS page 25 84 OmniSwitch AOS Release 7 Network Configuration Guide June 2013...