Configuring Application Monitoring and Enforcement Application Monitoring and Enforcement Overview
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 29-5
Application monitoring functionality includes:
• Identify traffic flows from attached networks at Layer 3.
• Application recognition of these traffic flows.
• Signature toolkit upgrade from OmniVista.
• Report the identified application flow information.
• Report application specific flow details including 5-tuple flow credentials, total number of flows,
number of flows per application, and so on.
Application Enforcement
The following diagram provides a high-level example of Application Enforcement process:
Application enforcement functionality includes:
• Identify traffic flows from attached networks at Layer 3.
• Application recognition of these traffic flows.
• Signature toolkit upgrade from OmniVista.
• Report the identified application flow information to CPU for UNP/VNP association.
• Policy enforcement that provides user configured application specific QoS treatment for application
traffic flows including higher DSCP/802.1p or internal priority marking that translates to higher egress
queue for traffic scheduling. QoS treatment can also include security policies that can perform policy
action such as dropping or rate limiting the flows.
Application
Enforcement
Process
Update
flow database;
policy rule,
Application
Signatures
Signature
Matching
Packet Sampling
AppMon
Apply
Matched
Flows
Signatures
flow counters,
Port
flow aging
QoS
Policy
UNP
Policy List