Chapter: Release Notes for NBAR2 Protocol Pack6.0.0
Release Notes for NBAR2 Protocol Pack 6.0.0
Release Notes for NBAR2 Protocol Pack 6.0.0
NBAR2 Protocol Pack 6.0.0 is the first protocol pack that contains the Enhanced Web Classification feature that supports multi-transaction export of URLs. For more information on this feature, see Classifying Network Traffic Using NBAR.
The NBAR2 Protocol Pack 6.0.0 introduces the support for detecting PCoIP (vm ware-view) granularly, to provide per session and per packet QoS. This feature has been developed in collaboration with Teradici, the developer of the PCoIP protocol. Using this feature, different types of traffic can be assigned to different QoS queues with specific priorities. This ensures that the higher priority traffic gets better treatment, there by improving the quality of experience. For more information on this feature, see the Application Visibility and Control for PCoIP white paper.
Network Based Application Recognition (NBAR) Protocol Pack 6.0.0 is supported on Cisco ASR 1000 Series Aggregation Services Routers.
New Protocols in NBAR2 Protocol Pack 6.0.0
The following protocols are added to NBAR2 Protocol Pack 6.0.0:
ESPN is a global television network focused on sports-related programs. espn-browsing is the protocol used for accessing and browsing the websites and mobile applications of the network for iPhone, iPad, Android, and WinRT.
ESPN is a global television network focused on sports-related programs. espn-video is the protocol used for watching video streams using browser or mobile applications for iPhone, iPad, Android, and WinRT. espn-video is used for video streaming services of the network.
WhatsApp Messenger is a proprietary, cross-platform instant messaging application for smartphones. In addition to text messaging, users can send images, location, contacts, and video and audio media messages.
Updated Protocols in NBAR2 Protocol Pack 6.0.0
The following protocols are updated in NBAR2 Protocol Pack 6.0.0:
Caveats in NBAR2 Protocol Pack 6.0.0
Note: If you have an account on Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. (If the defect that you have requested cannot be displayed, this may be due to one or more of the following reasons: the defect number does not exist, the defect does not have a customer-visible description yet, or the defect has been marked Cisco Confidential.)
Resolved Caveats in NBAR2 Protocol Pack 6.0.0
The following table lists the resolved caveats in NBAR2 Protocol Pack 6.0.0:
bittorrent-networking is not applied to any attributes.
Known Caveats in NBAR2 Protocol Pack 6.0.0
The following table lists the known caveats in NBAR2 Protocol Pack 6.0.0:
Traffic generated by pcAnywhere for mac and pcAnywhere mobile app might be misclassified as unknown
gtalk-video might be misclassified as rtp
gbridge pc client might not be blocked
Traffic generated by AIM Pro might be misclassified as unknown and webex-meeting
NBAR classification granularity may not work or some protocols may be classified as unknown. The CSCuc57822 caveat is specific to Cisco IOS XE Release 3.7S on Cisco ASR 1000 Series Aggregation Services Routers.
BitTorrent's traffic is changed when being blocked
Some Xunlei-KanKan traffic may be misclassified as Xunlei
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"
PCoIP session-priority configuration limitation
Segmented packets are not classified when using NBAR sub classification
Video traffic generated by some ESPN websites might be misclassified as unknown
Web traffic generated by some ESPN websites might be misclassified as unknown
Restrictions and Limitations in NBAR2 Protocol Pack 6.0.0
The following table lists the limitations and restrictions in NBAR2 Protocol Pack 6.0.0:
http traffic generated by the bitcomet bittorrent client might be classified as http
For capwap-data to be classified correctly, capwap-control must also be enabled.
During configuring QoS class-map with ftp-data, the ftp protocol must be selected. As an alternative, the ftp application group can be selected.
Encrypted video streaming generated by hulu might be classified as its underlying protocol rtmpe
Application is discontinued and replaced with ms-lync, traffic generated by livemeeting may be classified as ms-lync
Traffic generated by the logmein android app might be misclassified as ssl
Login and chat traffic generated by the ms-lync client might be misclassified as ssl
Login to QQ applications which is not via web may not be classified as qq-accounts
Voice traffic generated by secondlife might be misclassified as ssl