Alcatel-Lucent OmniAccess 700, Cli Configuration Manual

Page: 960 / 1193

Quality of Service
Left running head:
Chapter name (automatic)
934
Beta Beta
CLI Configuration Guide
Alcatel-Lucent
A
TTACHING A
P
OLICY
M
AP TO AN
I
NTERFACE
Notes:
1. An interface can have only one policy map attached in a direction.
2. When a policy map is attached in the ingress direction on an interface, then only
police and mark attributes will be used.
3. When a policy map is attached in the egress direction on an interface, then police,
shape, priority, mark, and queue-limit attributes will be used.
T
O
A
TTACH A
P
OLICY
M
AP TO AN
I
NTERFACE
Note: An empty policy can be attached to the interface as a policy-map will have a default
traffic class associated with it, by default.
Note: 1. You cannot attach a QoS policy (in the egress direction) to a serial interface, which
has MLPPP/MLFR encapsulation. The system gives a warning message.
2. You cannot attach a QoS policy having four levels of hierarchy on a FR interface.
3. You cannot attach a policy map on the tunnel interface in the ingress direction .
E
XAMPLE
ALU(config)# interface GigabitEthernet 7/0
ALU(config-if GigabitEthernet7/0)# service-policy in P1
ALU(config)# interface GigabitEthernet 7/0
ALU(config-if GigabitEthernet7/0)# no service-policy in P1
Command (in ICM) Description
service-policy { in | out }
<policy-map name>
This command is entered in the Interface
Configuration mode.
This command is used to attach a policy-
map to an interface either in ingress or
egress direction.
no service-policy { in | out }
<policy-map name>
This command detaches the policy map
from the interface it has been bound.