Service Management Tasks
Page 274 7210 SAS D, E, K OS Quality of Service Guide
Service Management Tasks
This section discusses the following service management tasks:
• Deleting QoS Policies on page 330
• Copying and Overwriting QoS Policies on page 332
• Remove a Policy from the QoS Configuration on page 333
• Editing QoS Policies on page 333
Deleting QoS Policies
Every service SAP is associated, by default, with the appropriate ingress policy (policy-id 1). You
can replace the default policy with a customer-configured policy, but you cannot entirely remove
the policy from the SAP configuration. When you remove a non-default service ingress policy, the
association reverts to the default policy-id 1.
A QoS policy cannot be deleted until it is removed from all SAPs where they are applied.
A:ALA-7>config>qos# no sap-ingress 100
MINOR: CLI SAP ingress policy "100" cannot be removed because it is in use.
A:ALA-7>config>qos#
Remove a QoS Policy from Service SAP(s)
The following Epipe service output examples show that the SAP service ingress reverted to
policy-id “1” when the non-default policies were removed from the configuration.
A:ALA-104>config>service>epipe# info detail
----------------------------------------------
description "Distributed Epipe service to west coast"
no tod-suite
dot1ag
exit
ingress
qos 1
no filter
exit
egress
no filter
exit
no collect-stats
no accounting-policy
no shutdown
----------------------------------------------
A:ALA-7>config>service>epipe#
To Next Page
Loading...
Need help?
General
