Cisco Cisco 5520 Wireless Controller 기술 참조
3
Application Visibility and Control Feature Deployment Guide rel 7.4-8.2
Application Visibility and Control–Phase 2
The key use cases for NBAR are capacity planning, network usage base lining and better understanding of what
applications are consuming bandwidth. Trending of application usage helps network admin to plan for network
infrastructure upgrade, improve quality of experience by protecting key applications from bandwidth-hungry applications
when there is congestion on the network, capability to prioritize or de-prioritize, and drop certain application traffic.
applications are consuming bandwidth. Trending of application usage helps network admin to plan for network
infrastructure upgrade, improve quality of experience by protecting key applications from bandwidth-hungry applications
when there is congestion on the network, capability to prioritize or de-prioritize, and drop certain application traffic.
NBAR is supported on 2500, 5500, 7500, 8500 and WiSM2 controllers on Local, Mesh, and Flex Mode APs (for WLANs
configured for central switching only).
configured for central switching only).
NBAR Supported Feature
NBAR as a feature can perform the following tasks:
1.
Classification–Identification of Application/Protocol.
2.
AVC–Provides visibility of classified traffic and also gives an option to control the same using Drop or Mark (DSCP)
action.
action.
3.
NetFlow–Updating NBAR stats to NetFlow collector like Cisco Prime Assurance Manager (PAM).
Application Visibility and Control–Phase 2
In phase two of the AVC support for Protocol Packs has been added. Protocol packs are software packages that allow
update of signature support without replacing the image on the Controller. You have an option to load protocol packs
dynamically when new protocol support is being added. There are two kinds of Protocol Packs—Major and Minor:
update of signature support without replacing the image on the Controller. You have an option to load protocol packs
dynamically when new protocol support is being added. There are two kinds of Protocol Packs—Major and Minor:
Major protocol packs include support for new protocols, updates, and bug fixes.
Minor protocol packs typically do not include support for new protocols.
Protocol packs are targeted to specific platform types, software versions and releases separately. Protocol Packs
can be downloaded from CCO using the software type “NBAR2 Protocol Pack”.
can be downloaded from CCO using the software type “NBAR2 Protocol Pack”.
Protocol packs are released with specific NBAR engine versions. For example, WLC 7.5 has NBAR engine 13, so protocol
packs for it are written for engine 13 (pp-unified-wng-152-4.S-13-4.1.1.pack). Loading a protocol pack can be done
if the engine version on the platform is same or higher than the version required by the protocol pack (13 in the example
above). Therefore for example – PP4.1 for 3.7 (version 13) can be loaded on top of 3.7 (version 13) and 3.8, but PP4.1
for 3.8 cannot be loaded on top of 3.7. It is strongly recommended to use the protocol pack that is the exact match for
the engine.
packs for it are written for engine 13 (pp-unified-wng-152-4.S-13-4.1.1.pack). Loading a protocol pack can be done
if the engine version on the platform is same or higher than the version required by the protocol pack (13 in the example
above). Therefore for example – PP4.1 for 3.7 (version 13) can be loaded on top of 3.7 (version 13) and 3.8, but PP4.1
for 3.8 cannot be loaded on top of 3.7. It is strongly recommended to use the protocol pack that is the exact match for
the engine.
For AVC phase 2, protocol packs can be downloaded directly from CCO–Protocol Pack 4.1.1 for engine XE 3.7. The
protocol pack file “pp-AIR-7.5-13-4.1.1.pack” (Format: pp-AIR-{release}-{engine version}-M.m.r.pack) will be located
in the same location with the controller code version 7.5. This is the only tested and supported protocol pack released
with controller software version 7.5.
protocol pack file “pp-AIR-7.5-13-4.1.1.pack” (Format: pp-AIR-{release}-{engine version}-M.m.r.pack) will be located
in the same location with the controller code version 7.5. This is the only tested and supported protocol pack released
with controller software version 7.5.
Note:
If you download the protocol pack from the below link where protocol packs for other Cisco devices is posted for
download, the protocol packs might work but will not be supported. See