- Release Notes for NBAR2 Protocol Pack 6.1.0
- 3COM-AMP3 through AYIYA-IPV6-TUNNELED
- BABELGUM through BR-SAT-MON
- CABLEPORT through CYCLESERV2
- DASP through DWR
- ECHO through EXEC
- FACEBOOK through FUJITSU-DEV
- GAME-SPY through GURUGURU
- H323 through HYPERWAVE-ISP
- IAFDBASE through JARGON
- KALI through LWAPP
- MAC-SRVR-ADMIN through MYSQL
- NAME through NXEDIT
- OBEX through OSU-NMS
- P10 through PWDGEN
- QBIKGDP through RXE
- SAFT through SYSTAT
- TACACS through TWITTER
- UAAC through VSLMP
- WAP-PUSH through ZSERV
Release Notes for NBAR2 Protocol Pack 6.1.0
Supported Platforms
Network Based Application Recognition (NBAR) Protocol Pack 6.1.0 is supported on Cisco ASR 1000 Series Aggregation Services Routers.
Caveats in NBAR2 Protocol Pack 6.1.0
Known Caveats in NBAR2 Protocol Pack 6.1.0
The following table lists the known caveats in NBAR2 Protocol Pack 6.1.0:
Known Caveat |
Description |
---|---|
CSCtx65481 |
Traffic generated by pcAnywhere for mac and pcAnywhere mobile app might be misclassified as unknown |
CSCub62860 |
gtalk-video might be misclassified as rtp |
CSCub89835 |
gbridge pc client might not be blocked |
CSCuc43505 |
Traffic generated by AIM Pro might be misclassified as unknown and webex-meeting |
CSCue08462 |
Some Xunlei-KanKan traffic may be misclassified as Xunlei |
CSCug12174 |
Under heavy SSL traffic, the following error message my appear: ": %STILE_CLIENT-4-MAX_LINK_TOUCH_WARN: F0: cpp_cp: NBAR number of flow-slinks threshold is reached, can't allocate more memory for flow-slinks" |
CSCuh49380 |
PCoIP session-priority configuration limitation |
CSCuh53623 |
Segmented packets are not classified when using NBAR sub classification |
CSCuh63870 |
Video traffic generated by some ESPN websites might be misclassified as unknown |
CSCuh63889 |
Web traffic generated by some ESPN websites might be misclassified as unknown |
CSCuh95182 |
Some qqlive traffic may be misclassified as qq-accounts when qqlive is configured under a class-map |
Restrictions and Limitations in NBAR2 Protocol Pack 6.1.0
Protocol |
Limitation/Restriction |
---|---|
bittorrent |
http traffic generated by the bitcomet bittorrent client might be classified as http |
capwap-data |
For capwap-data to be classified correctly, capwap-control must also be enabled. |
ftp |
During configuring QoS class-map with ftp-data, the ftp protocol must be selected. As an alternative, the ftp application group can be selected. |
hulu |
Encrypted video streaming generated by hulu might be classified as its underlying protocol rtmpe |
livemeeting |
Application is discontinued and replaced with ms-lync, traffic generated by livemeeting may be classified as ms-lync |
logmein |
Traffic generated by the logmein android app might be misclassified as ssl |
ms-lync |
Login and chat traffic generated by the ms-lync client might be misclassified as ssl |
qq-accounts |
Login to QQ applications which is not via web may not be classified as qq-accounts |
secondlife |
Voice traffic generated by secondlife might be misclassified as ssl |
Downloading NBAR2 Protocol Packs
NBAR2 Protocol Packs are available for download as Software Type 'NBAR2 Protocol Pack' on cisco.com software download page (http://www.cisco.com/cisco/software/navigator.html).
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
Application Visibility and Control |
|
Classifying Network Traffic Using NBAR |
|
NBAR Protocol Pack |
NBAR Protocol Pack module |
QoS: NBAR Configuration Guide |
|
QoS Command Reference |
Quality of Service Solutions Command Reference |