IronClad Quality of Service (QoS)
December 2000
11 - 19
•
eq
– The policy applies to the TCP or UDP port name or number you enter after
eq
.
•
gt
– The policy applies to TCP or UDP port numbers greater than the port number or the numeric equivalent
of the port name you enter after
gt
.
•
lt
– The policy applies to TCP or UDP port numbers that are less than the port number or the numeric
equivalent of the port name you enter after
lt
.
•
neq
– The policy applies to all TCP or UDP port numbers except the port number or port name you enter after
neq
.
•
range
– The policy applies to all TCP or UDP port numbers that are between the first TCP or UDP port name
or number and the second one you enter following the range parameter. The range includes the port names
or numbers you enter. For example, to apply the policy to all ports between and including 23 (Telnet) and 53
(DNS), enter the following: range 23 53. The first port number in the range must be lower than the last
number in the range.
•
established
– This operator applies only to TCP packets. If you use this operator, the QoS policy applies to
TCP packets that have the ACK (Acknowledgment) or RST (Reset) bits set on (set to “1”) in the Control Bits
field of the TCP packet header. Thus, the policy applies only to established TCP sessions, not to new
sessions. See Section 3.1, “Header Format”, in RFC 793 for information about this field.
The
in
parameter applies the policy to packets received in the port.
The
out
parameter applies the policy to packets sent on the port.
NOTE:
To apply the policy to traffic in both directions, enter two
ip access-policy-group
commands, one
specifying the
in
parameter, and the other specifying the
out
parameter.
The <policy-list> parameter is a list of policy IDs.
NOTE:
The device applies the policies in the order you list them, so make sure you order them in such a away
that you receive the results you expect. Once a packet matches a policy, the device takes the action specified in
that policy and stops comparing the packet to the policies in the list.
Summary of Contents for Switch and Router
Page 2: ...December 2000 Copyright 2000 by Foundry Networks Inc ...
Page 26: ...Foundry Switch and Router Installation and Configuration Guide xxvi December 2000 ...
Page 64: ...Foundry Switch and Router Installation and Configuration Guide 2 34 December 2000 ...
Page 162: ...Foundry Switch and Router Installation and Configuration Guide 5 38 December 2000 ...
Page 196: ...Foundry Switch and Router Installation and Configuration Guide 6 34 December 2000 ...
Page 208: ...Foundry Switch and Router Installation and Configuration Guide 7 12 December 2000 ...
Page 236: ...Foundry Switch and Router Installation and Configuration Guide 8 28 December 2000 ...
Page 258: ...Foundry Switch and Router Installation and Configuration Guide 9 22 December 2000 ...
Page 420: ...Foundry Switch and Router Installation and Configuration Guide 13 32 December 2000 ...
Page 442: ...Foundry Switch and Router Installation and Configuration Guide 14 22 December 2000 ...
Page 554: ...Foundry Switch and Router Installation and Configuration Guide 15 112 December 2000 ...
Page 574: ...Foundry Switch and Router Installation and Configuration Guide 16 20 December 2000 ...
Page 626: ...Foundry Switch and Router Installation and Configuration Guide 17 52 December 2000 ...
Page 682: ...Foundry Switch and Router Installation and Configuration Guide 18 56 December 2000 ...
Page 826: ...Foundry Switch and Router Installation and Configuration Guide 20 20 December 2000 ...
Page 994: ...Foundry Switch and Router Installation and Configuration Guide 26 10 December 2000 ...
Page 1004: ...Foundry Switch and Router Installation and Configuration Guide B 6 December 2000 ...
Page 1044: ...Foundry Switch and Router Installation and Configuration Guide C 40 December 2000 ...
Page 1048: ...Foundry Switch and Router Installation and Configuration Guide D 4 December 2000 ...
Page 1070: ...Foundry Switch and Router Installation and Configuration Guide Index 18 December 2000 ...