Белая книга для Cisco Cisco Prime Infrastructure 3.0

 

 

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 30 of 68 

The key converged access business use cases where AVC would be imperative are bring your own device 

(BYOD)/mobility and video. 

The following is a representation of the converged access network and where can AVC pictures be deployed: 

 

The differences as compared to the Cisco Unified Wireless Network architecture for AVC would be that NBAR2 

and NetFlow export need not happen only at the controller/WLC now. Here is a quick summary of how the features 

are enforced in this deployment model: 

● 

For wireless traffic, NBAR2 would run on the access point and learn the applications. 

● 

The learned information is sent to the switch using CAPWAP tunnels. 

● 

For wired traffic, NBAR2 runs on the switch (limited Doppler capability and software). 

● 

The switch does the collective NetFlow export for both wired and wireless traffic. 

● 

QoS for downstream traffic (switch to access point) is done on the switch (3850). 

● 

QoS for upstream traffic (access point to switch) is done on the access point - the access point is 

provisioned from the switch and like the Cisco Unified Wireless Network model has no direct access to the 

console. 

Note that NBAR2 running on the switch would coexist with other Medianet solutions like Media Services and flow 
metadata that would also be a part of the switch’s capabilities. 

The following is a summary of what AVC capabilities can be deployed on what devices: 

NBAR2 (Version 7.4, PP 2.1) 

Protocol Pack support future 
(7.5) 

NetFlow (fixed record) 

QoS 

NBAR2 - Future: Cisco IOS-XE 
3.3 (Darya, Q4CY13) 

NetFlow (fixed record) for wireless traffic - 
Future: Cisco IOS-XE 3.3 (Darya, Q4CY13) 

App-aware QoS policies for wireless - 
Future: Cisco IOS XE 3.4 (Amur, 1H 
CY14)