Table of Contents
Advertisement
This command ignores any pending policies (any additions, modifications, or deletions to the policy
configuration since the last qos apply) and writes the last applied policies to the pending configuration. At
this point, the pending policies are the same as the last applied policies.
In this example, there are two new pending policies and three applied policies:
Pending Policies
rule5
rule6
If you enter qos revert, the configuration then looks like:
Pending Policies
rule1
rule2
rule3
Flushing the Configuration
In some cases, when you need to remove all of your rules and start over again, erase the pending policies
completely from the configuration, use the
-> qos flush
If you then enter qos apply, all policy information is deleted.
In this example, there are two new pending policies and three applied policies:
Pending Policies
rule5
rule6
If you enter qos flush, the configuration then looks like:
Pending Policies
In this scenario, you can do one of two things. To write the applied policies back to the pending configura-
tion, use qos revert. Or, to delete all policy rule configuration, enter qos apply. If qos apply is entered,
the empty set of pending policies are written to the applied policies and all policy rule configuration is
deleted.
Interaction With LDAP Policies
The qos apply, qos revert, and qos flush commands do not affect policies created through the Policy-
View application. Separate commands are used for loading and flushing LDAP policies on the switch. See
Chapter 23, "Managing Authentication Servers,"
OmniSwitch AOS Release 7 Network Configuration Guide
Applied Policies
rule1
rule2
rule3
Applied Policies
rule1
rule2
rule3
qos flush
Applied Policies
rule1
rule2
rule3
Applied Policies
rule1
rule2
rule3
for information about managing LDAP policies.
command. For example:
March 2011
page 21-67
Advertisement
Table of Contents
