2.5.2 - Force10 Networks

The following example shows the use of the policy-map command:
policy-map pm-1 in
class cl-map-1
assign-queue 3
exit
class cl-map-2
mark ip-precedence 1
exit
Figure 138 policy-map Command Example
In the above example, we have created a policy-map with the name of “pm-1”. This policy-map is meant to
affect inbound traffic. Traffic that is part of the class cl-map-1 (created in the previous example) is affected.
Traffic that falls into this class will be assigned to queue 3. Traffic that is a match for class cl-map-2 will
have ip-precedence marked as 1.
Applying Policies
Policy maps may be applied globally, to all interfaces, or on a per-interface basis. This is accomplished
with the service-policy in policyname command. The in keyword indicates that the policy is specific to
inbound traffic, because SFTOS supports only the inbound (ingress) direction. The policyname parameter
is the name of an existing DiffServ policy (shown defined, above). Note that this command causes a
service to create a reference to the policy.
Note: This command effectively enables DiffServ on an interface (in a particular direction).
The command can be used in the Interface Config mode to attach a policy to a specific interface.
Alternatively, the command can be used in the Global Config mode to attach this policy to all system
interfaces.
There is no separate interface administrative mode command for DiffServ.
Note: This command shall fail if any attributes within the policy definition exceed the
capabilities of the interface. Once a policy is successfully attached to an interface, any attempt
to change the policy definition such that it would result in a violation of said interface
capabilities shall cause the policy change attempt to fail.
Example (global):
Force10 #config
Force10 (Config)#service-policy in pm-1
Force10 (Config)#
Figure 139 service-policy Global Command Example
SFTOS Configuration Guide, Version 2.5.2.0 191