41-19
Catalyst 6000 Family Software Configuration Guide—Releases 6.3 and 6.4
78-13315-02
Chapter 41 Configuring QoS
Understanding How QoS Works
Note
ICMP ACEs with only a Layer 4 ICMP
type
parameter match all
code
values for that
type
value.
ICMP ACEs that do not include any Layer 4 ICMP type and code parameters match all ICMP traffic.
IP ACE Layer 4 IGMP Classification Criteria
You can create IGMP ACEs that match traffic containing specific IGMP messages by including an
IGMP type parameter (for more information, see the
“IP ACEs for IGMP Traffic” section on
page 41-40
). You can specify the IGMP type numerically (0–255) or with these keywords:
host-query
(1),
host-report
(2),
dvmrp
(3),
pim
(4), or
trace
(5).
Note
QoS does not support Internet Group Management Protocol (IGMP) traffic when IGMP snooping is
enabled. QoS supports IGMP classification using version 1 four-bit Type fields.
Note
IGMP ACEs that do not include a Layer 4 IGMP type parameter match all IGMP traffic.
IPX ACE Classification Criteria
You can create IPX ACEs that match specific IPX traffic by including these parameters (for more
information, see the
“Creating or Modifying Named IPX ACLs” section on page 41-42
):
•
IPX source network (-1 matches any network number)
•
Protocol, which can be specified numerically (0–255) or with these keywords:
any
,
ncp
(17),
netbios
(20),
rip
(1),
sap
(4),
spx
(5)
•
IPX ACEs support the following optional parameters:
–
IPX destination network (-1 matches any network number)
–
If you specify an IPX destination network, IPX ACEs support the following optional
parameters: an IPX destination network mask (-1 matches any network number), an IPX
destination node, and an IPX destination node mask
information-request
15
0
time-exceeded
1
11
—
mask-reply
18
0
timestamp-reply
14
0
mask-request
17
0
timestamp-request
13
0
mobile-redirect
32
0
traceroute
30
0
net-redirect
5
0
ttl-exceeded
11
0
net-tos-redirect
5
2
unreachable
1
3
—
1.
Matches all code values
Keyword
Type
Code
Keyword
Type
Code