Table of Contents
Advertisement
has the effect of negating this match condition for the class (i.e., match all source layer 4 ports except for
those within the range specified here).
The optional [not] parameter has the effect of negating this match condition for the class (i.e., match all
source layer 4 port numbers except for the one specified here).
▫
Default
None
▫
Format
match [not] srcl4port {<portkey> | <0-65535> [<0-65535>]}
▫
Mode
Class-Map Config
9.4.15 match vlan
This command adds to the specified class definition a match condition based on the value of the layer 2
VLAN Identifier field of a packet. The VLAN ID is an integer from 1 to 4094. The optional [not] parameter
has the effect of negating this match condition for the class (i.e., match all VLAN Identifier values except
for what is specified here).
▫
Default
None
▫
Format
match [not] vlan <1-4094>
▫
Mode
Class-Map Config
9.5 Policy Commands
The 'policy' command set is used in DiffServ to define:
▫
Traffic Conditioning Specify traffic conditioning actions (policing, marking, shaping) to apply to
traffic classes
▫
Service Provisioning Specify bandwidth and queue depth management requirements of service
levels (EF, AF, etc.)
The policy commands are used to associate a traffic class, which was defined by the class command set,
with one or more QoS policy attributes. This association is then assigned to an interface in a particular
direction to form a service. The user specifies the policy name when the policy is created.
The DiffServ CLI does not necessarily require that users associate only one traffic class to one policy. In
fact, multiple traffic classes can be associated with a single policy, each defining a particular treatment for
packets that match the class definition. When a packet satisfies the conditions of more than one class,
preference is based on the order in which the classes were added to the policy, with the foremost class
taking highest precedence.
This set of commands consists of policy creation/deletion, class addition/removal, and individual policy
attributes. Note that the only way to remove an individual policy attribute from a class instance within a
policy is to remove the class instance and re-add it to the policy. The values associated with an existing
policy attribute can be changed without removing the class instance.
The CLI command root is policy-map.
Advertisement
Table of Contents
