Management and Configuration Guide (Includes ACM xl) 2005-12

ProCurve Secure Access 700wl Series Management and Configuration Guide 1-7
Introduction
After a packet has been marked with a priority setting it becomes accessible for QoS handling on the
network.
Ingress packets with VLAN tags can retain their 802.1p settings while their VLAN ID is replaced. This
includes packets with a VLAN ID of zero (0) also called the null VLAN ID. Just like the VLAN support
feature, VLAN tags can be removed, replaced, or retained. The VLAN ID and 802.1p priority settings
will not be overwritten by the VLAN settings in an Access Policy. However, the QoS capability to
manipulate VLAN tags is not intended as a replacement for the Access Policy’s forced VLAN tagging
option.
Note:
Ingress packets are incoming packets on an Access Controller’s downlink port.
The QoS feature also offers the ability to apply a VLAN tag based on packet type. This can be used to
separate application data on the same device. For instance, a mixed-mode device, like a PDA with a
soft-phone application, can have data traffic sent down one VLAN and priority VoIP traffic sent down
a different VLAN.
QoS settings are defined under the Access Policies tab in the Rights Manager. QoS is evaluated after
packets have been rewritten with any traffic filtering (Allows/Redirects).
The 700wl Series system QoS feature offers the ability to handle IP traffic to meet the service needs of
certain applications while maintaining network use for a full range of applications and users. Current
QoS implementations often depend on the client application applying the priority tagging. However, as
more multi-use client devices come into use, it will become less acceptable to assume that the device is
either trusted or correct in how it marks its traffic. In some cases it may be necessary to explicitly
remove priority tags that have been applied by client applications.