Configuring Application Monitoring and Enforcement Configuring AppMon
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 29-19
Clearing Application List
To remove all the applications from the enforcement or monitor application list, use the clear app-mon
app-list command. This command does not clear the active application list, until ‘app-mon apply’ is used.
For example:
-> clear app-mon app-list enforcement
-> clear app-mon app-list monitor
Configuring AppMon Enforcement QoS Policy Rules
AppMon enforcement allows the switch to differentiate between different traffic flows and assign the
proper QoS and Security policies. The following set of policy actions are supported: Disposition Drop/
Accept, Rate limiting, DSCP Marking, 802.1p Marking, Internal Priority Marking, Redirection, and
Mirroring.
• QoS policy rules can be configured for a given application as well as an application group where the
same application also exists. The QoS policy applied is based on what is configured in the application
list at the time of app-mon apply.
• QoS policy lookup considers AppMon specific policies for a given application name only when it is
part of enforcement active application list. In case the policy is configured both for application name
and application group where same application is part, policy will be selected based on what is
configured in the enforcement active application list.
• QoS policy lookup is performed for the flow when AppMon signature matched packet is received. If
there is any change to existing QoS policies, modified policies are effective only for the new flows.
However, the following scenarios are supported:
– If there is a change in policy action, existing matched flows are updated for new policy action.
– If AppMon specific policy rules are removed, flows to which the rules were applied are moved to
the default policy.
– On QoS disable, existing flows are moved to the default policy.
– On QoS flush or apply, existing flows are moved to the default policy.
– Default policy refers to disposition accept policy action.
• While configuring an AppMon policy rule, multiple condition parameters (for example, source IP,
destination IP, source VLAN and so on) cannot be defined in a single policy condition along with
AppMon application name or group.
• The application group needs to be created before adding the application group in QoS policies.
• While configuring the QoS policies, the application name or the application group must exist in
AppMon.
• Destination port or port group based policy condition is not supported for AppMon.
Configure AppMon enforcement QoS policy rules using the policy condition command. An application
name or application-group name can be specified in the policy condition as shown below.
-> policy condition c1 app-mon-application-group appgroup1
-> policy condition c2 app-mon-application-name watsapp
For more information about configuring QoS policy rules for AppMon, see the “QoS Policy Commands”
chapter in the OmniSwitch AOS Release 8 CLI Reference Guide and the Chapter 26, “Configuring QoS.”
chapter in this guide.
To Next Page
Loading...
