NBAR2 Protocol Pack 7.1.0 contains the Enhanced Web Classification feature that supports multi-transactions export of URLs. For more information on this feature, see Classifying Network Traffic Using NBAR.
Network Based Application Recognition (NBAR) Protocol Pack 7.1.0 is supported on Cisco ASR 1000 Series Aggregation Services Routers.
Updated Protocols in NBAR2 Protocol Pack 7.1.0
The following protocols are updated in NBAR2 Protocol Pack 7.1.0:
Updated signatures to support Microsoft Lync 2013.
Updated signatures to support mac client.
Caveats in NBAR2 Protocol Pack 7.1.0
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 7.1.0
The following table lists the resolved caveats in NBAR2 Protocol Pack 7.1.0:
Some qqlive traffic may be misclassified as qq-accounts when qqlive is configured under a class-map
SSL sub classification will not be matched if a built-in protocol was matched in the SSL client-hello message
SIP related protocols classification and RTP sub-classification may fail when compact headers are used
SIP related protocols classification and RTP sub-classification may fail when field extraction is activated and the 'contact' or 'from' fields do not contain '@'.
The drop policy may not work for ms-office-web-apps protocol
The drop policy may not work for sky-drive protocol
Cisco-jabber-video and cisco-phone might be misclassified when configured under a class-map
Cisco-jabber-video for windows may not be classified correctly
Microsoft Lync might be misclassified in certain scenarios
Known Caveats in NBAR2 Protocol Pack 7.1.0
The following table lists the known caveats in NBAR2 Protocol Pack 7.1.0:
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
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
When using Microsoft Lync in Office-365, the traffic might be misclassified as rtp or SSL
Matching under ms-office-web-apps attributes might be misclassified
Field-Extraction of SSL unique-name might not work in particular cases
Restrictions and Limitations in NBAR2 Protocol Pack 7.1.0
The following table lists the limitations and restrictions in NBAR2 Protocol Pack 7.1.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
Encrypted cisco jabber might be classified as unknown.
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
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
Traffic generated by the mobile or mac app is not supported. ms-lync 2013 traffic if any, might be misclassified.
Traffic generated by pcanywhere for mac might be classified as unknown.
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