User's Manual

Fortress ES-Series CLI Guide: Networking and Radio Configuration
95
 low - packets in the low queue are delivered after packets
in all other QoS queues; the
low priority queue is intended
for network background traffic.
The Mesh Point’s implementation of DiffServ and the earlier IP
precedence traffic prioritization standards are mutually
compatible. QoS prioritization information will be derived from
Incoming packet headers in any of the supported standard
formats. All such information is overridden, however, by the
QoS setting of the Ethernet port through which the packet is
received, if the port is enabled for QoS.
Mesh Point QoS processing follows these steps:
1 If the packet is received on an Ethernet port on which the
QoS is enabled, it is sorted into the
TrafficClass queue
specified by the port setting.
2 If the packet header includes a VLAN tag, the packet is
sorted into the queue that maps to the 802.1p user-priority
tag contained in the VLAN tag.
3 If the IPv4 or IPv6 packet header includes a DiffServ field,
the packet is sorted into the queue that maps to the DSCP
(DiffServ Code Point) contained in the DS field.
4 If the packet is a wireless frame, it is sorted according to
the WMM information in the 802.11 header.
5 If the packet contains no QoS information, it is sorted into
the
medium queue.
The mapping that determines an incoming packet’s traffic class
in Step 2 is configured in the Mesh Point’s
TrafficClass-to-
Tags map. In Step 3, this mapping is configured in the Mesh
Point’s
TrafficClass-to-DSCP map. Reconfiguring these maps
is described below.
View the Mesh Point’s current QoS mapping schemes with
show qos:
# show qos
TrafficClass Tags
------------ ------------
low 1 2
medium 0 3
high 4 5
critical 6 7
TrafficClass DSCP
------------ ------------------------
low 10 12 14
medium 0 1 2 3 4 5 6 7
8 9 11 13 15 16 17 18
19 20 21 22 23 24 25 27
29 31 32 33 35 37 39 40
41 42 43 44 45 47 48 49