Cisco 350 Series Administration Manual page 662

23
NOTE
STEP 1
STEP 2
STEP 3
STEP 4
STEP 5
STEP 6
442
Policy Binding
The Policy Binding page shows which policy profile is bound and to which port. A policy can
be bound to an interface as an ingress (input) policy or as an egress (output) policy. When a
policy profile is bound to a specific port, it is active on that port. Only one policy profile can
be configured per port, per direction, but a single policy can be bound to more than one port.
When a policy is bound to a port, it filters and applies QoS to traffic that belongs to the flows
defined in the policy.
To edit a policy, it must first be removed (unbound) from all those ports to which it is bound.
It is possible to either bind a port to a policy or to an ACL but both cannot be bound.
To define policy binding:
Click Quality of Service > QoS Advanced Mode > Policy Binding.
Select an Interface Type if required.
Click Go. The policies for that interface are displayed.
Click Edit.
Select the following for the input policy/interface:
• Input Policy Binding—Select to bind the input policy to the interface.
• Policy Name—Select the input policy being bound.
• Default Action—Select action if packet matches policy:
- Deny Any—Select to forward packets on the interface if they match any policy.
- Permit Any—Select to forward packets on the interface if they do not match any
policy.
Permit Any can be defined only if IP Source Guard is not activated on the
NOTE
interface.
Select the following for the output policy/interface:
• Output Policy Binding—Select to bind the output policy to the interface.
• Policy Name—Select the output policy being bound.
• Default Action—Select action if packet matches policy:
- Deny Any—Select to forward packets on the interface if they match any policy.
Cisco 350, 350X and 550X Series Managed Switches, Firmware Release 2.4, ver 0.4
Quality of Service
QoS Advanced Mode