91
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Creating a Class Map and Rules
Policy maps are lists of QoS-related actions to perform on packets that match certain criteria.
The matching criteria are specified by an associated classification map that lists rules to
identify packets, such as VoIP traffic.
This topic describes how to create a class map and class rules that specify certain selection
criteria, such as P-bit or VLAN values, to classify traffic from the network that is arriving at
the E-Series. If packets match the criteria listed in the class map, an associated policy map
states the Quality of Service (QoS) actions to perform on those identified packets. The class
map can specify whether packets must match any or all rules in order to be selected.
Class map rule for untagged traffic destined for the Native VLAN
The E-Series Ethernet port Trunk and Edge interfaces are always associated with at least one
VLAN, through the native VLAN attribute (VLAN 1 by default). The native VLAN ID is
specified on the interface and is used for untagged user traffic on that interface.
Note:
Interfaces with the Access role do not support a native VLAN. To forward untagged
traffic on E-Series Ethernet ports with an Access interface, an add-tag action must be applied
to untagged frames, assigning the traffic to a designated VLAN.
To create a class rule for matching untagged traffic, do the following:
1.
Specify the native VLAN ID when defining the Ethernet Interface attributes.
2.
Set the following parameters when creating a class rule:
Match pbit = pbit-any
Match Outer = native VLAN ID
Match Inner = Any
For example, if you specify the native VLAN ID as 4 for the Ethernet interface, the class
rule for matching untagged traffic would appear as follows:
3.
Apply the class rule to a class map, and then in turn, associate the class map to a policy
map that is associated to the Ethernet interface where you specified the Native VLAN
ID.
