Allied Telesis x908 - Manual (Page 9)

Page 9 | AlliedWare Plus™ OS How To Note
Making filters by using QoS class-maps
3. Specify what the class-map will match on (see page 9 ). This involves:
z attaching the ACL to the class-map
z using other match commands to further limit what the traffic will match the class-map
(unless the ACL’s settings were enough)
4. Attach the class-maps to a policy-map (see page 12 ).
5. Attach the policy-map to the ingress port or ports (see page 12 ).
The following sections describe how to do each of these steps (except creating ACLs—that’s
described from
page 3 ).
Creating a class-map
To create a class-map, enter global configuration mode and use the command:
awplus(config)#class-map <name>
This puts you into class-map configuration mode.
Specifying what the class-map will match on
To do this, first attach the ACL to the class-map (unless you don’t need an ACL). In class-map
configuration mode, use the command:
awplus(config-cmap)#match access-group <number>
Next, use other match commands to further limit which traffic will match the class-map
(unless the ACL’s settings were enough). This means that you select the matching traffic by
using a combination of the ACL’s settings and the QoS match commands. The ACL and match
commands are ANDed together to make the class-map’s filtering rule. The available match
commands are:
match cos
match ip-dscp
match ip-precedence
match eth-format protocol (or match protocol eth-format)
match tpid
match inner-cos
match inner-tpid
match inner-vlan
match mac-type
match tcp-flags
match vlan
Most of these options are self-evident, but the following sections give more information
about the “inner” options, the TCP flags, and the eth-format and protocol options.
Except for TCP flags, each class-map can only match on one instance of each match type. If
you enter multiple matches of the same type, the class-map uses the last match you specify.
If you need more than one filtering rule on the port, create class-maps for each other filter.