We need an
Authoritative · Light–Weight · Unambiguous
way to identify applications.
Network As a Sensor for Application Assurance
Needs Support across various PINS – Wireless, UA, WAN/Internet edge, Core, DC, Security
Visibility, Capacity Planning, Reporting on LAN & WAN
Zoom in on “Where The Problem Is” for business applications – could be ANYWHERE!
E2E QoS & ACL (any Policy) enforcement – Drop “selectively”, Access Marking & Core/WAN Queuing
“Readiness Assessments” – Determine readiness for Application Deployment at planned scale
Use Application Information to Drive Network Data Analytics – e.g. CMX/ wireless scenarios
To support cloud apps breakouts to the Internet based on app-aware Routing policies
|Wireless (WLC, AP), Converged Access||2/3+ clients connect via wireless (per latest VNI stats); Need to classify/mark at the edge;|
90%+ still deploying centralized WLCs; Prevent scavenger apps from getting too deep!
Block/Mitigate heavy hitters over shared (half duplex), second most congested medium!
|Distribution, Core||Troubleshooting – analyze traffic utilization (packet captures)|
Domain based routing starting at L3 Distribution for cloud apps (ITeS use case)
|WAN Edge||Premium Links & Limited Bandwidth – Need Capacity Planning & Optimal allocation for apps|
|Internet Edge||Cloud migration – Need for DIA and first packet classification for cloud apps|
|Wired Access||1/3 traffic still wired; 60-70% is voice/video with low latency requirements. Waiting till WAN is too late! Classification of this traffic known to be cumbersome today (port/subnet based)|
|Data Center/Server Farm||Apps reside in DC – need to identify app level performance issues in multi-tiered client-server design|
|Firewall, Perimeter Security||Entry Point (check what apps to allow) – Filter Applications/Users – URL filtering|
|MSP Edge||Provide Application Level SLA – Managed Services|