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. When a policy profile is bound to a specific port, it’s active on that port. Only one policy profile can be configured per port and per direction. However, 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’s bound.
Note | It’s possible to either bind a port to a policy or to an ACL but both can’t be bound. |
To define policy binding, complete the following steps:
Procedure
Step 1 | Click Quality of Service > QoS Advanced Mode > Policy Binding. |
Step 2 | Select an Interface Type if required. |
Step 3 | Click Go. The policies for that interface are displayed. |
Step 4 | Click Edit. |
Step 5 | Select the following for the input policy/interface:
|
Step 6 | Click Apply. The QoS policy binding is defined, and the Running Configuration file is updated. |