 Feedback
|
Table Of Contents
Cisco Service Control Application for Broadband Protocol Pack Notes, Older Protocol Packs (1-18)
New Flavors - (Supported by Release 3.5.0 and later)
SCA BB 2.5.10 Protocol Pack #10
What's new in the SCA BB 2.5.10 Protocol Pack #10
SCA BB 3.0.6 Protocol Pack #10
What's new in the SCA BB 3.0.6 Protocol Pack #10
SCA-BB 3.0.6 Protocol Pack #10 limitations and caveats
SCA BB 3.1.0 Protocol Pack #10
What's new in the SCA BB 3.1.0 Protocol Pack #10
SCA-BB 3.1.0 Protocol Pack #10 limitations and caveats
SCA BB 2.5.10 Protocol Pack #09
What's new in the SCA BB 2.5.10 Protocol Pack #09
SCA-BB 2.5.10 Protocol Pack #09 limitations and caveats
SCA BB 3.0.6 Protocol Pack #09
What's new in the SCA BB 3.0.6 Protocol Pack #09
SCA-BB 3.0.6 Protocol Pack #09 limitations and caveats
SCA BB 3.1.0 Protocol Pack #09
What's new in the SCA BB 3.1.0 Protocol Pack #09
SCA-BB 3.1.0 Protocol Pack #09 limitations and caveats
SCA BB 2.5.10 Protocol Pack #08
What's new in the SCA BB 2.5.10 Protocol Pack #08
SCA BB 3.0.6 Protocol Pack #08
What's new in the SCA BB 3.0.6 Protocol Pack #08
SCA-BB 3.0.6 Protocol Pack #08 limitations and caveats
SCA BB 2.5.10 Protocol Pack #07
What's new in the SCA BB 2.5.10 Protocol Pack #07
SCA-BB 2.5.10 Protocol Pack #07 limitations and caveats
SCA BB 3.0.5A Protocol Pack #07
What's new in the SCA BB 3.0.5A Protocol Pack #07
SCA-BB 3.0.5A Protocol Pack #07 limitations and caveats
SCA BB 2.5.10 Protocol Pack #06
What's new in the SCA BB 2.5.10 Protocol Pack #06
SCA-BB 2.5.10 Protocol Pack #06 limitations and caveats
SCA BB 3.0.4 Protocol Pack #06
What's new in the SCA BB 3.0.4 Protocol Pack #06
SCA-BB 3.0.4 Protocol Pack #06 limitations and caveats
SCA BB 2.5.10 Protocol Pack #05
What's new in the SCA BB 2.5.10 Protocol Pack #05
SCA-BB 2.5.10 Protocol Pack #05 limitations and caveats
SCA BB 3.0.3 Protocol Pack #05
What's new in the SCA BB 3.0.3 Protocol Pack #05
SCA-BB 3.0.3 Protocol Pack #05 limitations and caveats
SCA BB 2.5.9 Protocol Pack #04
What's new in the SCA BB 2.5.9 Protocol Pack #04
SCA BB 3.0.1 Protocol Pack #04
What's new in the SCA BB 3.0.1 Protocol Pack #04
January 2006 Protocol Pack (Protocol Pack #03)
January 2006 2.5.8 Protocol Pack
What's new in the January 2006 2.5.8 Protocol Pack
January 2006 3.0.0 Protocol Pack
What's new in the January 2006 3.0.0 Protocol Pack
November 2005 Protocol Pack (Protocol Pack #02)
What's new in the November 2005 Protocol Pack
September 2005 Protocol Pack (Protocol Pack #01)
What's new in the September 2005 Protocol Pack
Obtaining Documentation and Submitting a Service Request
Cisco Service Control Application for Broadband Protocol Pack Notes, Older Protocol Packs (1-18)
Revised: November 12, 2010, OL-8483-26Introduction
These protocol pack notes for the Cisco Service Control Application for Broadband (SCA BB) describe the content of the various protocol packs that are available at the Software Download page of the Cisco website.
Contents
Overview
Cisco protocol packs include new and improved protocol signatures for SCA BB. A typical signature update is a file containing new and updated signatures for better detection of new or updated popular peer-to-peer applications, gaming applications, and other interesting protocols. When loaded into the SCE platform, these signatures improve classification abilities of SCA BB with minimal or zero SCE platform service downtime.
The protocol pack files are available for Cisco partners and customers for download from the Software Download page of the Cisco website.
Installation
Installation of the SCA BB Protocol Pack #22 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information, see the Cisco Service Control Application for Broadband User Guide for your SCA BB release:
SCA BB Protocol Pack #18
Compatibility Information
The SCA BB Protocol Pack #18 can be installed on an SCE 1000, SCE 2000, or SCE8000 platform on which one of the following versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
SCA BB Release 3.1.7
•
•
Protocol Library Updates
New Protocols
•
•
•
•
•
•
•
•
•
•
•
Updated Protocols
•
•
•
•
•
•
•
•
New Flavors - (Supported by Release 3.5.0 and later)
•
•
•
•
•
•
•
•
•
•
•
•
Resolved Caveats
CSCta25715
uTorrent 1.9 with uTP enabled might be misclassified as Generic UDP.
CSCta92977
uTorrent might be misclassified as Generic TCP when multiple flows are sent together.
CSCsy81524
PPLive 2.0.21 might be misclassified as Behavioral P2P.
Known Limitations
CSCsv44394
The installation of Protocol Pack #18 upon SCOS release 3.1.7 requires the following manual configuration in order to support all the Protocol Pack #18 features.
Step 1
Step 2
Step 3
script run script.txt.CSCsx78811
Upgrading from 3.1.7 with Protocol Pack #18 to 3.5.0 with Protocol Pack #18 requires manual configuration in order to support all the Protocol Pack #18 features.
Step 1
Configuration > Signature Settings > Signature Script
and choose Remove.
Step 2
Step 3
Note
CSCta17754
Hitless upgrade is not supported on the SCE 2000 platform for release 3.5.5 .
DSS Content
Note
The SUS script contains no DSS-based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #18. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide).
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
SCA BB Protocol Pack #17
Compatibility Information
The SCA BB Protocol Pack #1t can be installed on an SCE 1000, SCE 2000, or SCE8000 platform on which one of the following versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
•
•
•
Protocol Library Updates
New Protocols
•
•
•
•
Updated Protocols
•
•
•
•
•
Resolved Caveats
CSCsx69375
In certain scenarios, several online games might be misclassified as Bittorrent Encrypted.
CSCsy28207
In certain scenarios, Skype might be misclassified as Bittorrent Encrypted traffic.
CSCsy33909
WinnyP detection dropped compared to previous protocol packs.
CSCsy44809
Yahoo Mail login over HTTPS might be misclassified as Yahoo Messenger traffic.
Known Limitations
CSCsv03281
Hitless upgrade in 3.1.6S is not supported.
CSCsv44394
The installation of Protocol Pack #17 upon SCOS release 3.1.6, 3.1.6S, or 3.1.7 requires the following manual configuration in order to support all the Protocol Pack #17 features.
Step 1
Step 2
Step 3
script run script.txt.CSCsx78811
Upgrading from 3.1.x with Protocol Pack #16 or later to 3.5.0 with Protocol Pack #16 or later requires the following manual configuration in order to support all the latest Protocol Pack features.
Step 1
Configuration > Signature Settings > Signature Script
and choose Remove.
Step 2
Step 3
CSCsz30295
Hitless upgrade in 3.1.7/3.5.0 SCE8000 is not supported.
DSS Content
Note
The SUS script contains no DSS-based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #17. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide).
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
SCA BB Protocol Pack #16
Compatibility Information
The SCA BB Protocol Pack #16 can be installed on an SCE 1000, SCE 2000, or SCE8000 platform on which one of the following versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
•
•
•
•
•
Protocol Library Updates
New Protocols
•
•
•
•
•
•
•
Updated Protocols
•
•
•
Resolved Caveats
CSCsw78280
In certain scenarios, Manolito protocol is misclassified as Behavioral Upload/Download.
CSCsq04726
In certain scenarios Bittorrent might be misclassified as Generic traffic.
CSCsq96038
In certain scenarios, Oracle traffic might be misclassified as Encrypted eMule.
CSCsr17352
Some online games might be misclassified as Winny 2.
CSCsr22638
In certain scenarios, SSH traffic might be misclassified as Behavioral P2P.
CSCsu06798
In certain scenarios, uTorrent 1.8 might be misclassified as Generic TCP.
CSCsv54098
In certain scenarios, RTMP based protocols such as iView and Hulu might be misclassified as RTMP.
CSCsw33095
UDP traffic might be misclassified as Generic UDP when open-flow-mode is set to minimum packets 5.
Known Limitations
CSCsv44394
The installation of Protocol Pack #16 upon SCOS release 3.1.5, 3.1.6, 3.1.6S, or 3.1.7 requires the following manual configuration in order to support all the Protocol Pack #16 features.
Step 1
Step 2
Step 3
script run script.txt.CSCsx78811
Upgrading from 3.1.1, 3.1.5, 3.1.6, 3.1.6S, or 3.1.7 with Protocol Pack #16 to 3.5.0 with Protocol Pack #16 requires the following manual configuration in order to support all the Protocol Pack #16 features.
Step 1
Configuration > Signature Settings > Signature Script
and choose Remove.
Step 2
Step 3
CSCsv03281
Hitless upgrade in 3.1.6S is not supported.
CSCsv03281
Hitless upgrade on top of 3.1.1 with protocol pack #15 is not supported.
DSS Content
Note
The SUS script contains no DSS-based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #16. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide).
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
WinnyP manual configuration instructions
To enable WinnyP classification, the following root level CLI commands should be executed
SCE#>configureSCE (config)#>interface LineCard 0SCE (config if)#>tunable GT_PL_WINNYP_CLASSIFICATION_ENABLE value trueSCE(config if)#>tunable GT_PL_WINNYP_AGGRESSIVE_CLASSIFICATION_ENABLE value trueThe following command should be executed in 3.5.0 only:
SCE2000(config if)#>tunable GT_PL_BEHAVIORAL_DOWNLOAD_CHECK_SPECIFIC_SIGNATURES value trueSCA BB Protocol Pack #15
Compatibility Information
The SCA BB Protocol Pack #15 can be installed on an SCE 1000, SCE 2000, or SCE8000 platform on which one of the following versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
•
•
•
•
Protocol Library Updates
New Protocols
•
•
•
•
•
•
•
Updated Protocols
•
•
Resolved Caveats
CSCsr04812
In certain scenarios, third party gaming is misclassified as Skype.
CSCsr72588.
In certain scenarios, Mario cart is misclassified as Bittorrent.
CSCsu49225
In certain scenarios, LDAP is misclassified as Skype.
CSCsr81179.
In certain scenarios, RTMP is misclassified as Generic TCP.
CSCsr81134.
RTMP misclassified as Generic Non-Established due to premature aging.
CSCsr30750
MS Remote Desktop misclassified as MSN Messenger.
CSCsr93345
VNC misclassified as PPLive.
Known Limitations
CSCsv44394
The installation of Protocol Pack #15 upon SCOS release 3.1.5 or 3.1.6 requires the following manual configuration in order to support all the Protocol Pack #15 features.
Step 1
Step 2
Step 3
script run script.txt.CSCsv03281
Hitless upgrade in 3.1.6S is not supported.
CSCsu91574
In extreme network topologies where UDP is throttled by a NAT or a Firewall device, Skype might be misclassified as Generic TCP.
PPFilm might be misclassified as Generic TCP
PPFilm video service consists of hundreds of channels updated on a daily basis. The SCE platform may not support all channels.
DSS Content
Note
The SUS script contains no DSS-based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #15. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide).
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
Google Mobile Maps special configuration instructions:
Step 1
a.
The Flavors Editing dialog opens.
b.
•
Add a parameter to this flavor with a Host Suffix value of "*.google.com" (case sensitive). Leave all other fields as "*".
•
Add a parameter to this flavor with a User Agent value of "WINM-TEST-USER-AGENT" (case sensitive).
c.
•
–
–
Step 2
Open the Services tab and create a new service called "Google Mobile Maps" under 'HTTP' (or other desired group).
Step 3
Create new service elements by filling the following values in the Create Service element dialog (fields that are not listed below should not be changed):
•
–
–
–
Youtube mobile special configuration instructions:
Step 1
a.
The Flavors Editing Dialog opens.
b.
•
Add a parameter to this flavor with a Host Suffix value of "*rtsp-youtube.l.google.com" (case sensitive).
Step 2
Open the Services tab and create a new service called "Youtube Mobile" under Streaming (or other desired group).
Step 3
Create new service elements by filling the following values in the Create Service element dialog (fields that are not listed below should not be changed):
•
–
–
–
SCA BB Protocol Pack #14
Compatibility Information
The SCA BB Protocol Pack #14 can be installed on an SCE 1000, SCE 2000, or SCE8000 platform on which one of the following versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
•
•
•
•
•
Protocol Library Updates
New Protocols
•
•
•
•
Updated Protocols
•
•
•
•
•
•
•
•
•
•
Resolved Caveats
CSCsq83081
When browsing MySpace, it is sometimes classified as 'Flash' rather than 'Flash MySpace'.
CSCsq26609
Lineage gaming is misclassified as Bittorrent Encrypted.
CSCsq83045
Multicast DNS is classified as Second Life.
CSCsq66448
HTTPS traffic is misclassified to MS Push Mail in addition to SSL-VPN traffic.
CSCsq09521
PPLive is misclassified to other protocols due to lack of support for client version 1.9.35.
CSCsm95034
EVE online gaming and VGaurd Video surveillance are misclassified to PPLive.
CSCso89456
In certain scenarios when HBC is disabled and eMule is set to an obfuscated mode, most of the traffic is misclassified to Behavioral Upload / Download and only 15 - 20% is classified to eMule.
CSCso75547
BBC iPLayer is misclassified to Behavioral Upload / Download.
CSCso30107
TFTP - Write request is misclassified to Generic UDP.
CSCso17765
Yahoo messenger is misclassified to SSL.
Known Limitations
CSCsm06607
The installation of Protocol Pack #14 upon 3.1.5 requires the following manual configuration in order to support all the Protocol Pack #14 features.
Step 1
Step 2
Step 3
script run script.txt.CSCsr20314
Protocol Packs #12 and above installed on top of SCA-BB Release 3.1.0 or SCA-BB Release 3.1.1 may cause to some P2P traffic to be misclassified.
Following are the protocols that can be misclassified: Manolito, Neonet, Direct_Connect, PPStream, Winny, and Share.
Workaround: Configure the SCE platform by executing the following command sequence:
enable 15configureInterface linecard 0lookup GT_LUT_HBC_SOCKET_BASED_PROTOCOLS remove-key 118030336lookup GT_LUT_HBC_SOCKET_BASED_PROTOCOLS remove-key 118620160lookup GT_LUT_HBC_SOCKET_BASED_PROTOCOLS remove-key 117899264lookup GT_LUT_HBC_SOCKET_BASED_PROTOCOLS remove-key 118816768lookup GT_LUT_HBC_SOCKET_BASED_PROTOCOLS remove-key 117702656lookup GT_LUT_HBC_SOCKET_BASED_PROTOCOLS remove-key 118292480exitexitcopy running-config-application startup-config-applicationCSCsq04726
Azureus might not be completely blocked and might be misclassified to Generic TCP / UDP in certain scenarios enforcing BLOCK mode.
CSCso84926
BT Azureus might be misclassified to Generic TCP when the client is working in encrypted mode.
CSCso55461
Upon upgrading from Protocol Pack #11 to Protocol Pack #12 , #13 or #14, WebThunder protocol signature might change, and thus be misclassified to Generic traffic.
Workaround:
Step 1
Step 2
Step 3
DSS Content
Note
The SUS script contains no DSS-based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #14. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide).
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
SCA BB Protocol Pack #13
Compatibility Information
The SCA BB Protocol Pack #13 can be installed on an SCE 1000 or SCE 2000 platform on which one of these versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
•
•
•
Protocol Library Updates
New Protocols
•
•
•
•
Updated Protocols
•
•
•
•
•
Resolved Caveats
CSCsl96818
Specific YouTube videos are classified as Flash rather than Flash YouTube.
CSCsl98416
SMTP may be misclassified to FTP.
CSCsl98389
SCE platform sends RADIUS RDR with no Acct-Status-Type attribute.
CSCsm15090
Some video over HTTP traffic may be misclassified due to wrong file extension usage.
CSCsl93375
PPTP traffic must be classified by a Signature.
CSCsl85317
MSN messenger misclassified to Generic TCP in video and voice conference.
CSCsl99223
MSN Messenger - Voice via Relay server can not be blocked
Known Limitations
CSCsm06607
The installation of Protocol Pack #13 upon 3.1.5 requires the following manual configuration in order to support all the Protocol Pack #13 features.
Step 1
Step 2
Step 3
script run script.txt.
DSS Content
Note
The SUS script contains no DSS-based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #13. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide).
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
Nico Nico Douga special configuration instructions:
Step 1
a.
The Flavors Editing Dialog window opens.
b.
c.
Step 2
Open the Services tab and create a new service called "Nico Nico Douga" under Streaming (or other desired group).
Step 3
Edit the newly created service element by filling the following values in the Create Service element dialog window (fields that are not listed below should stay unchanged):
•
•
•
SCA BB Protocol Pack #12
Compatibility Information
The SCA BB Protocol Pack #12 can be installed on an SCE 1000 or SCE 2000 platform on which one of the versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
•
•
•
•
Protocol Library Updates
New Protocols
•
•
•
•
Updated Protocols
•
•
•
•
•
•
Resolved Caveats
CSCsi21093
Error in output log file when illegal bind info appears in IRC traffic.
CSCsl20455
POP3 may be classified as Generic TCP.
CSCsl78566
Behavioral P2P mechanism causes misclassifications.
This issue is not relevant for 3.0.6 platform.
CSCsl11500
WebThunder misclassification (New signature should be developed).
CSCsl45174
Online gaming traffic is misclassified as Winny.
CSCsl27582
Nintendo DS WiFi might be misclassified as Manolito.
CSCsl83338
Some SSL TLS 1.0 flows are misclassified as Nodezilla.
Known Limitations
CSCsm06607
The installation of Protocol Pack #12 upon 3.1.5 requires the following manual configuration in order to support all the Protocol Pack #12 features.
Step 1
Step 2
Step 3
script run script.txt.CSCsl85317, CSCsl99223
In certain network topologies, such as multiple NATs/PATs, MSN voice sessions generate traffic that is not classified correctly.
DSS Content
Note
The SUS script contains no DSS-based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #12. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
SCA BB Protocol Pack #11
Compatibility Information
The SCA BB Protocol Pack #11 can be installed on an SCE 1000 or SCE 2000 platform on which one of the versions of SCA BB has already been installed.
This Protocol Pack can be installed on top of the following platforms,
•
•
•
Protocol Library Updates
New Protocols
•
•
•
•
Updated Protocols
•
•
•
•
Resolved Caveats
CSCsk51763
If some traffic generated by a P2P client is classified as B.P2P, it causes all the traffic of that client to be mapped to B.P2P.
This issue is relevant for 3.1.0 and 3.1.1 platforms only
CSCsj14472
Encrypted traffic of Winny2 is misclassified.
Resolved for 3.1.1 platform only.
CSCsj58100
Blackberry traffic is classified as Skype.
CSCsj99194
Some SIP flows have preemptive packet that is not recognized as SIP.
CSCsk61759
"PRACK" SIP method is not recognized and thus some SIP flows are mapped to Generic UDP.
CSCsk69072
PL tries to re-bind flows that it already requested a bind for.
CSCsk17816
Some YouTube videos are classified as Flash instead of Flash YouTube.
CSCsk88129
HTTP & HTTPS half-closed flows leftovers are misclassified as Winny2.
CSCsk86079
Misclassifications of Google Earth to "HTTP port" and to "HTTP Browsing" were observed.
Known Limitations
CSCsk92699
Several clients (BBC-iPlayer/4oD/Sky) use the same underlying protocol - Kontiki. '4oD' and 'Sky' clients are not distinguished and will be mapped to Kontiki.
DSS Content
Note
The SUS script contains no DSS based signatures and is only provided to expose the new signature IDs to the application.
Protocol Signature Details
Note
The following table contains protocol IDs for the protocols that were added or enhanced in Protocol Pack #11. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide).
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
Gyao special configuration instructions:
Step 1
a.
The 'Flavors Editing Dialog' window opens.
b.
•
Add a parameter to this flavor with a 'Host Suffix' value of "*gyao.jp" (case sensitive)
Hit 'Accept' when finished.
•
Add a parameter to this flavor with a 'Host Suffix' value of "*gyao.jp" (case sensitive). Leave all other fields as "*".
Step 2
Open the 'Services' tab and create a new service called "Gyao" under 'Streaming' (or other desired group).
Step 3
Create two new service elements by filling the following values in the 'Create Service element' dialog window (fields that are not listed below should stay unchanged):
•
–
–
–
•
–
–
–
SCA BB Protocol Pack #10
The SCA BB Protocol Pack #10 contains the following three protocol packs:
•
•
•
Refer to the relevant section for your SCA BB version.
Upgrading release 2.5.10, 3.0.6, or 3.1.0 with Protocol Pack #10 in a network where the newly supported protocols are relatively common has little performance impact. In a network where the majority of the newly supported protocols are not common, performance might drop, depending on the traffic mix and control policy.
Note
Installation- SCA BB 2.5.10 Protocol Pack #10
Installation- SCA BB 3.0.6 Protocol Pack #10
Installation- SCA BB 3.1.0 Protocol Pack #10
SCA BB 2.5.10 Protocol Pack #10
Prerequisites
The SCA BB 2.5.10 Protocol Pack #10 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.10 has already been installed.
What's new in the SCA BB 2.5.10 Protocol Pack #10
Note
This Protocol Pack includes support for the following new protocols over SCA BB 2.5.10:
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.10:
•
•
•
•
•
•
•
•
The SCA BB 2.5.10 Protocol Pack #10 for SCA BB 2.5.10 includes the following two spqi files:
•
•
SCA-BB 2.5.10 Protocol Pack #10 limitations and caveats
•
Note
The SCA BB 2.5.10 Protocol Pack 10 includes the following legacy DSS-based signatures:
•
•
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 2.5.10 Protocol Pack #10 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 2.5.10 Protocol Pack #10 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
Manual configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide)
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
GoogleEarth special configuration instructions:
Using the SCA BB console, manually assign the protocol 'GoogleEarth' to the 'HTTP' Service.
ICQ VoIP special configuration instructions:
Although 2.5.10-Protocol Pack #10 correctly classifies 'ICQ VoIP' traffic as SIP, the following additional manual configuration change is required:
Using the Protocols dialog of the SCA BB console, add UDP port 5190 to the SIP protocol.
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
Video/Audio/Binary over HTTP special configuration instructions:
Using the SCA BB console, manually assign the protocols 'Video over HTTP', 'Audio over HTTP' and 'Binary over HTTP' to the 'HTTP' Service.
SCA BB 3.0.6 Protocol Pack #10
Prerequisites
The SCA BB 3.0.6 Protocol Pack #10 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.6 has already been installed.
What's new in the SCA BB 3.0.6 Protocol Pack #10
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.6:
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.6:
•
•
•
•
•
•
•
•
The SCA BB 3.0.6 Protocol Pack #10 for SCA BB 3.0.6 includes the following spqi file:
•
SCA-BB 3.0.6 Protocol Pack #10 limitations and caveats
•
DSS Content
Note
The SCA BB 3.0.6 Protocol Pack #10 includes the following legacy DSS based signatures:
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.0.6 Protocol Pack #10 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.0.6 Protocol Pack #10 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information see Release Notes for Cisco Service Control Application for Broadband (SCA BB)
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB 3.1.0 Protocol Pack #10
Prerequisites
The SCA BB 3.1.0 Protocol Pack #10 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.1.0 has already been installed.
What's new in the SCA BB 3.1.0 Protocol Pack #10
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.1.0:
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.1.0:
•
•
•
•
•
•
•
•
The SCA BB 3.1.0 Protocol Pack #10 for SCA BB 3.1.0 includes the following spqi file:
•
SCA-BB 3.1.0 Protocol Pack #10 limitations and caveats
•
DSS Content
Note
The SCA BB 3.1.0 Protocol Pack #10 includes the following legacy DSS based signatures:
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.1.0 Protocol Pack #10 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.1.0 Protocol Pack #10 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information see Release Notes for Cisco Service Control Application for Broadband (SCA BB)
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB Protocol Pack #09
The SCA BB Protocol Pack #09 contains the following three protocol packs:
•
•
•
Refer to the relevant section for your SCA BB version.
Upgrading release 2.5.10, 3.0.6, or 3.1.0 with Protocol Pack #09 in a network where the newly supported protocols are relatively common has little performance impact. In a network where the majority of the newly supported protocols are not common, performance might drop, depending on the traffic mix and control policy.
Note
Installation- SCA BB 2.5.10 Protocol Pack #09
Installation- SCA BB 3.0.6 Protocol Pack #09
Installation- SCA BB 3.1.0 Protocol Pack #09
SCA BB 2.5.10 Protocol Pack #09
Prerequisites
The SCA BB 2.5.10 Protocol Pack #09 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.10 has already been installed.
What's new in the SCA BB 2.5.10 Protocol Pack #09
Note
This Protocol Pack includes support for the following new protocols over SCA BB 2.5.10:
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.10:
•
•
•
The SCA BB 2.5.10 Protocol Pack #09 for SCA BB 2.5.10 includes the following two spqi files:
•
•
SCA-BB 2.5.10 Protocol Pack #09 limitations and caveats
•
•
DSS Content
Note
The SCA BB 2.5.10 Protocol Pack 09 includes the following legacy DSS-based signatures:
•
•
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 2.5.10 Protocol Pack #09 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 2.5.10 Protocol Pack #09 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
Manual configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide)
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
GoogleEarth special configuration instructions:
Using the SCA BB console, manually assign the protocol 'GoogleEarth' to the 'HTTP' Service.
ICQ VoIP special configuration instructions:
Although 2.5.10-Protocol Pack #09 correctly classifies 'ICQ VoIP' traffic as SIP, the following additional manual configuration change is required:
Using the Protocols dialog of the SCA BB console, add UDP port 5190 to the SIP protocol.
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
Video/Audio/Binary over HTTP special configuration instructions:
Using the SCA BB console, manually assign the protocols 'Video over HTTP', 'Audio over HTTP' and 'Binary over HTTP' to the 'HTTP' Service.
SCA BB 3.0.6 Protocol Pack #09
Prerequisites
The SCA BB 3.0.6 Protocol Pack #09 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.6 has already been installed.
What's new in the SCA BB 3.0.6 Protocol Pack #09
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.6:
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.6:
•
•
•
•
•
The SCA BB 3.0.6 Protocol Pack #09 for SCA BB 3.0.6 includes the following spqi file:
•
SCA-BB 3.0.6 Protocol Pack #09 limitations and caveats
•
DSS Content
Note
The SCA BB 3.0.6 Protocol Pack #09 includes the following legacy DSS based signatures:
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.0.6 Protocol Pack #09 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.0.6 Protocol Pack #09 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information see Release Notes for Cisco Service Control Application for Broadband (SCA BB)
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB 3.1.0 Protocol Pack #09
Prerequisites
The SCA BB 3.1.0 Protocol Pack #09 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.1.0 has already been installed.
What's new in the SCA BB 3.1.0 Protocol Pack #09
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.1.0:
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.1.0:
•
•
•
The SCA BB 3.1.0 Protocol Pack #09 for SCA BB 3.1.0 includes the following spqi file:
•
SCA-BB 3.1.0 Protocol Pack #09 limitations and caveats
•
DSS Content
Note
The SCA BB 3.1.0 Protocol Pack #09 includes the following legacy DSS based signatures:
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.1.0 Protocol Pack #09 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.1.0 Protocol Pack #09 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information see Release Notes for Cisco Service Control Application for Broadband (SCA BB)
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB Protocol Pack #08
The SCA BB Protocol Pack #08 contains the following two protocol packs:
•
•
Refer to the relevant section for your SCA BB version.
Upgrading release 2.5.10 or 3.0.6 with Protocol Pack #08 in a network where the newly supported protocols are relatively common has little performance impact. In a network where the majority of the newly supported protocols are not common, performance might drop, depending on the traffic mix and control policy.
Note
Installation- SCA BB 2.5.10 Protocol Pack #08
Installation - SCA BB 3.0.6 Protocol Pack #08
SCA BB 2.5.10 Protocol Pack #08
Prerequisites
The SCA BB 2.5.10 Protocol Pack #08 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.10 has already been installed.
What's new in the SCA BB 2.5.10 Protocol Pack #08
Note
•
•
•
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.10:
•
•
•
The SCA BB 2.5.10 Protocol Pack #08 for SCA BB 2.5.10 includes the following two spqi files:
•
•
•
•
•
DSS Content
Note
The SCA BB 2.5.10 Protocol Pack 08 includes the following legacy DSS-based signatures:
•
•
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 2.5.10 Protocol Pack #08 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 2.5.10 Protocol Pack #08 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
Manual Configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide)
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
GoogleEarth special configuration instructions:
Using the SCA BB console, manually assign the protocol 'GoogleEarth' to the 'HTTP' Service.
ICQ VoIP special configuration instructions:
Although 2.5.10-Protocol Pack #08 correctly classifies 'ICQ VoIP' traffic as SIP, the following additional manual configuration change is required:
Using the Protocols dialog of the SCA BB console, add UDP port 5190 to the SIP protocol.
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
Video/Audio/Binary over HTTP special configuration instructions:
Using the SCA BB console, manually assign the protocols 'Video over HTTP', 'Audio over HTTP' and 'Binary over HTTP' to the 'HTTP' Service.
SCA BB 3.0.6 Protocol Pack #08
Prerequisites
The SCA BB 3.0.6 Protocol Pack #08 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.6 has already been installed.
What's new in the SCA BB 3.0.6 Protocol Pack #08
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.6:
•
•
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.6:
•
•
•
•
The SCA BB 3.0.6 Protocol Pack #08 for SCA BB 3.0.6 includes the following spqi file:
•
SCA-BB 3.0.6 Protocol Pack #08 limitations and caveats
•
•
DSS Content
Note
The SCA BB 3.0.6 Protocol Pack #08 includes the following legacy DSS based signatures:
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.0.6 Protocol Pack #08 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.0.6 Protocol Pack #08 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information see Release Notes for Cisco Service Control Application for Broadband (SCA BB).
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB Protocol Pack #07
The SCA BB Protocol Pack #07 contains the following two protocol packs:
•
•
Refer to the relevant section for your SCA BB version.
Upgrading release 2.5.10 or 3.0.5A with Protocol Pack #07 in a network where the newly supported protocols are relatively common has little performance impact. In a network where the majority of the newly supported protocols are not common, performance might drop, depending on the traffic mix and control policy.
Note
Installation- SCA BB 2.5.10 Protocol Pack #07
Installation- SCA BB 3.0.5A Protocol Pack #07
SCA BB 2.5.10 Protocol Pack #07
Prerequisites
The SCA BB 2.5.10 Protocol Pack #07 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.10 has already been installed.
What's new in the SCA BB 2.5.10 Protocol Pack #07
Note
This Protocol Pack includes support for the following new protocols over SCA BB 2.5.10:
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.10:
•
•
•
•
•
•
•
The SCA BB 2.5.10 Protocol Pack #07 for SCA BB 2.5.10 includes the following two spqi files:
•
•
SCA-BB 2.5.10 Protocol Pack #07 limitations and caveats
•
•
DSS Content
Note
The SCA BB 2.5.10 Protocol Pack 07 includes the following legacy DSS-based signatures:
•
•
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 2.5.10 Protocol Pack #07 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 2.5.10 Protocol Pack #07 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
Manual configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco Service Control Application for Broadband User Guide)
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
GoogleEarth special configuration instructions:
Using the SCA BB console, manually assign the protocol 'GoogleEarth' to the 'HTTP' Service.
ICQ VoIP special configuration instructions:
Although 2.5.10-Protocol Pack #07 correctly classifies 'ICQ VoIP' traffic as SIP, the following additional manual configuration change is required:
Using the Protocols dialog of the SCA BB console, add UDP port 5190 to the SIP protocol.
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB 3.0.5A Protocol Pack #07
Prerequisites
The SCA BB 3.0.5A Protocol Pack #07 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.5A has already been installed.
What's new in the SCA BB 3.0.5A Protocol Pack #07
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.5A:
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.5A:
•
•
•
•
•
•
•
The SCA BB 3.0.5A Protocol Pack #07 for SCA BB 3.0.5A includes the following spqi file:
•
SCA-BB 3.0.5A Protocol Pack #07 limitations and caveats
•
•
•
DSS Content
Note
The SCA BB 3.0.5A Protocol Pack #07 includes the following legacy DSS based signatures:
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.0.5A Protocol Pack #07 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.0.5A Protocol Pack #07 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information see Release Notes for Cisco Service Control Application for Broadband (SCA BB)
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB Protocol Pack #06
The SCA BB Protocol Pack #06 contains the following two protocol packs:
•
•
Refer to the relevant section for your SCA BB version.
Upgrading release 2.5.10 or 3.0.4 with Protocol Pack #06 in a network where the newly supported protocols are relatively common has little performance impact. In a network where the majority of the newly supported protocols are not common, performance might drop, depending on the traffic mix and control policy.
Note
Installation- SCA BB 2.5.10 Protocol Pack #06
Installation- SCA BB 3.0.4 Protocol Pack #06
SCA BB 2.5.10 Protocol Pack #06
Prerequisites
The SCA BB 2.5.10 Protocol Pack #06 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.10 has already been installed.
What's new in the SCA BB 2.5.10 Protocol Pack #06
Note
This Protocol Pack includes support for the following new protocols over SCA BB 2.5.10:
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.10:
•
•
•
•
•
•
•
•
•
•
•
The SCA BB 2.5.10 Protocol Pack #06 for SCA BB 2.5.10 includes the following two spqi files:
•
•
SCA-BB 2.5.10 Protocol Pack #06 limitations and caveats
•
•
DSS Content
Note
The SCA BB 2.5.10 Protocol Pack 06 includes the following legacy DSS based signatures:
•
•
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 2.5.10 Protocol Pack #06 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 2.5.10 Protocol Pack #06 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
Manual configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco SCA BB User Guide)
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
GoogleEarth special configuration instructions:
Using the SCA BB console, manually assign the protocol 'GoogleEarth' to the 'HTTP' Service.
ICQ VoIP special configuration instructions:
Although 2.5.10-Protocol Pack #06 correctly classifies 'ICQ VoIP' traffic as SIP, the following additional manual configuration change is required:
Using the Protocols dialog of the SCA BB console, add UDP port 5190 to the SIP protocol.
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB 3.0.4 Protocol Pack #06
Prerequisites
The SCA BB 3.0.4 Protocol Pack #06 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.4 has already been installed.
What's new in the SCA BB 3.0.4 Protocol Pack #06
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.4:
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.4:
•
•
•
•
•
•
•
•
•
•
•
The SCA BB 3.0.4 Protocol Pack #06 for SCA BB 3.0.4 includes the following spqi file:
•
Note
SCA-BB 3.0.4 Protocol Pack #06 limitations and caveats
•
•
DSS Content
Note
The SCA BB 3.0.4 Protocol Pack #06 includes the following legacy DSS based signatures:
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.0.4 Protocol Pack #06 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.0.4 Protocol Pack #06 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation using hitless upgrade mechanism. For more detailed information see SCA BB 3.0.4 Release Notes
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document
SCA BB Protocol Pack #05
The SCA BB Protocol Pack #05 contains the following two protocol packs:
•
•
Refer to the relevant section for your SCA BB version.
Upgrading release 2.5.10 or 3.0.3 with Protocol Pack #05 in a network where the newly supported protocols are relatively common has little performance impact (±1%). In a network where the majority of the newly supported protocols are not common, performance might drop by up to 2%, depending on the traffic mix and control policy.
Note
Installation- SCA BB 2.5.10 Protocol Pack #05
Installation- SCA BB 3.0.3 Protocol Pack #05
SCA BB 2.5.10 Protocol Pack #05
Prerequisites
The SCA BB 2.5.10 Protocol Pack #05 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.10 has already been installed.
What's new in the SCA BB 2.5.10 Protocol Pack #05
Note
This Protocol Pack includes support for the following new protocols over SCA BB 2.5.10:
•
•
•
•
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.10:
•
–
–
•
–
–
•
•
•
•
•
The SCA BB 2.5.10 Protocol Pack #05 for SCA BB 2.5.10 includes the following two spqi files:
•
•
SCA-BB 2.5.10 Protocol Pack #05 limitations and caveats
•
•
DSS Content
Note
The SCA BB 2.5.10 Protocol Pack 05 includes the following legacy DSS based signatures:
•
•
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 2.5.10 Protocol Pack #05 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 2.5.10 Protocol Pack #05 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
Manual configuration
The manual configuration should be performed after the PP installation has been completed (according to the procedure described in the Cisco SCA BB User Guide)
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
GoogleEarth special configuration instructions:
Using the SCA BB console, manually assign the protocol 'GoogleEarth' to the 'HTTP' Service.
ICQ VoIP special configuration instructions:
Although 2.5.10-Protocol Pack #05 correctly classifies 'ICQ VoIP' traffic as SIP, the following additional manual configuration change is required:
Using the Protocols dialog of the SCA BB console, add UDP port 5190 to the SIP protocol.
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB 3.0.3 Protocol Pack #05
Prerequisites
The SCA BB 3.0.3 Protocol Pack #05 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.3 has already been installed.
What's new in the SCA BB 3.0.3 Protocol Pack #05
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.3:
•
•
•
•
•
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.3:
•
–
–
•
–
–
•
•
•
•
•
•
•
The SCA BB 3.0.3 Protocol Pack #05 for SCA BB 3.0.3 includes the following spqi files:
•
•
SCA-BB 3.0.3 Protocol Pack #05 limitations and caveats
•
•
DSS Content
Note
The SCA BB 3.0.3 Protocol Pack #05 includes the following legacy DSS based signatures:
•
•
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.0.3 Protocol Pack #05 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.0.3 Protocol Pack #05 involves a replacement of the SCE platform application. This is done automatically as part of the SPQI installation. It should be noted that a short service downtime is expected.
Manual configuration
The manual configuration should be performed after the Protocol Pack #05 installation has been completed (according to the procedure described in the Cisco SCA BB User Guide)
To perform any required manual configuration, complete the following steps:
Step 1
Step 2
Step 3
ICQ VoIP special configuration instructions:
Although SCA BB 3.0.3-Protocol Pack #05 correctly classifies 'ICQ VoIP' traffic as SIP, the following additional manual configuration change is required:
Using the Advanced Options dialog of the SCA BB console, add port 5190 to the list "UDP ports for which flows should be opened on first packet".
For further information regarding the installation or distribution process, please use the Cisco SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB Protocol Pack #04
Starting with this protocol pack, SCA BB Protocol Pack #04, protocol packs will be named by serial number, rather than by month/year.
Thus, the previous protocol packs are:
•
•
•
The SCA BB Protocol Pack #04 contains the following two protocol packs:
•
•
Refer to the relevant section for your SCA BB version.
SCA BB 2.5.9 Protocol Pack #04
Prerequisites
The SCA BB 2.5.9 Protocol Pack #04 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.9 has already been installed.
What's new in the SCA BB 2.5.9 Protocol Pack #04
Note
This Protocol Pack includes support for the following new protocols over SCA BB 2.5.9:
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.9:
•
•
•
The SCA BB 2.5.9 Protocol Pack #04 includes the following two spqi files:
•
•
DSS Content
Note
The SCA BB 2.5.9 Protocol Pack #04 includes the following legacy DSS based signatures:
•
•
–
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 2.5.9 Protocol Pack #04 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 2.5.9 Protocol Pack #04 involves a replacement of the SCE application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
For further information regarding the installation or distribution process, please use the SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
SCA BB 3.0.1 Protocol Pack #04
Prerequisites
The January SCA BB 3.0.1 Protocol Pack #04 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.1 has already been installed.
What's new in the SCA BB 3.0.1 Protocol Pack #04
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.1:
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.0:
•
•
•
The SCA BB 3.0.1 Protocol Pack #04 includes the following spqi files:
•
•
DSS Content
Note
The SCA BB 3.0.1 Protocol Pack #04 includes the following legacy DSS based signatures:
•
•
–
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The SCA BB 3.0.1 Protocol Pack #04 includes the following new/enhanced interfaces:
Installation
Installation of the SCA BB 3.0.1 Protocol Pack #04 involves a replacement of the SCE application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
For further information regarding the installation or distribution process, please use the SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
January 2006 Protocol Pack (Protocol Pack #03)
The January 2006 Protocol Pack contains the following two protocol packs:
•
•
Refer to the relevant section for your SCA BB version.
January 2006 2.5.8 Protocol Pack
Prerequisites
The January 2006 2.5.8 Protocol Pack for SCA BB 2.5.8 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 2.5.8 has already been installed.
What's new in the January 2006 2.5.8 Protocol Pack
Note
This Protocol Pack includes support for the following new protocols over SCA BB 2.5.8:
•
This Protocol Pack includes updates for the following protocols over SCA BB 2.5.8:
•
•
The January 2006 2.5.8 Protocol Pack for SCA BB 2.5.8 includes the following two spqi files:
•
•
DSS Content
Note
The January 2006 2.5.8 Protocol Pack includes the following legacy DSS based signatures:
•
–
–
•
–
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The January 2006 2.5.8 Protocol Pack includes the following new/enhanced interfaces:
Table 25 New/Enhanced Protocols in SCA BB 2.5.8 Protocol Pack
HTTP Tunnel
80
Skype
25
Version 1.4.0.84
PPLive
44
Version 1.1.0.0
Installation
Installation of the January 2006 2.5.8 Protocol Pack involves a replacement of the SCE application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
For further information regarding the installation or distribution process, please use the SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
January 2006 3.0.0 Protocol Pack
Prerequisites
The January 2006 3.0.0 Protocol Pack for SCA BB 3.0.0 can be installed on an SCE 1000 or SCE 2000 platform on which SCA BB 3.0.0 has already been installed.
What's new in the January 2006 3.0.0 Protocol Pack
Note
This Protocol Pack includes support for the following new protocols over SCA BB 3.0.0:
•
•
•
•
•
•
•
•
•
•
This Protocol Pack includes updates for the following protocols over SCA BB 3.0.0:
•
•
This Protocol Pack includes the following bug fixes over SCA BB 3.0.0:
•
•
The January 2006 3.0.0 Protocol Pack for SCA BB 3.0.0 includes the following spqi file:
•
DSS Content
Note
The January 2006 3.0.0 Protocol Pack includes the following legacy DSS based signatures:
•
Please note that the January 2006 3.0.0 Protocol Pack does not support the following protocols:
•
•
•
•
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
Installation
Installation of the January 2006 3.0.0 Protocol Pack involves a replacement of the SCE application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
For further information regarding the installation or distribution process, please use the SCA BB Protocol Signatures Distribution User Guide Supplement, which is available on CCO at the same directory as the current document.
November 2005 Protocol Pack (Protocol Pack #02)
Prerequisites
The November 2005 Protocol Pack for 2.5.7 can be installed on an SCE 1000 or SCE 2000 on which either one of the following software versions has already installed:
•
•
What's new in the November 2005 Protocol Pack
Note
This Protocol Pack includes support for the following new protocols:
•
•
•
•
•
•
•
This Protocol Pack includes updates for the following protocols:
•
•
•
This Protocol Pack includes the following bug fixes:
•
•
•
The November Protocol Pack includes the following two zip files:
•
•
DSS Content
Note
The November Protocol Pack includes the following legacy DSS based signatures:
•
–
–
•
–
–
–
–
–
Protocol Signature Details
The following table contains protocol IDs for the protocols that were added or enhanced in this protocol pack. These IDs appear in the PROTOCOL_ID field of RDRs that are generated for these protocols.
The November Protocol Pack includes the following new/enhanced interfaces:
Table 28 Enhanced Protocols from Previous Protocol Pack Release
BaiBao
80
Version 1.3.1
PPLive
81
Version 1.0.7.4
DNS
82
FC 1035
Installation
Installation of the November 2005 Protocol Pack involves a replacement of the SCE application. This is done automatically as part of the SPQI installation. It should be noted that some service downtime is expected, similar to that of an SCE platform application upgrade. This is due to the closing of all active flow contexts and reclassification of all traffic with the new version.
For further information regarding the installation or distribution process, please use the SCA BB Protocol Signatures Distribution - User Guide Supplement, which is available on CCO at the same directory as the current document.
September 2005 Protocol Pack (Protocol Pack #01)
What's new in the September 2005 Protocol Pack
The September 2005 Protocol pack is relevant for the SCA BB 2.5.7 release.
•
•
•
•
•
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.
