Guest

Cisco Service Control Application for Mobile Networks

Field Notice: FN - 62930 - SCE1010/2020 - Protocol Pack 10 for SCAS BB 3.0.6/3.1.0 - HTTP Traffic is Misclassified to IM


September 5, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

Comments

SCE SCAS BB - 3.0.6

Protocol Pack#10 affected for this release

SCE SCAS BB - 3.1

Protocol Pack#10 affected for this release

Problem Description

When SCA-BB 3.0.6/3.1.0 Protocol-Pack#10 is installed over Protocol-Pack#09, some HTTP traffic will be misclassified to Instant Messaging service. This applies to HTTP traffic with a user-agent header field value starting with 'Mozilla'. The problem doesn't occur when PP#10 is installed over previous PP versions or over the SCA-BB 3.0.6/3.1.0 base releases.

Background

One of the techniques to classify HTTP based protocol is to look at the user-agent field value. As part of Protocol-Pack#09, one of the signatures added to support MSN Live Messenger, was based on HTTP user-agent field value to start with 'Mozilla'.

In Protocol-Pack#10, this signature was update not to be based on HTTP user-agent. The entry for 'Mozilla' was not removed from the lookup table while a new entry was introduced to support a new protocol - 'Fring'.

Having both entries in the lookup table simultaneously causes the misclassification.

Problem Symptoms

While upgrading from SCA-BB 3.0.6/3.1.0 Protocol-Pack#09 to 3.0.6/3.1.0 Protocol-Pack#10 accordingly, all HTTP traffic that includes a user-agent field value which starts with portion 'Mozilla' will be misclassified to Instant Messaging service.

This is true only while doing the upgrade from Protocol-Pack#09.

Workaround/Solution

Solution

A fix is planned for the next Protocol-Pack#11.

Workaround

The workaround is to remove the redundant entry and by this to resolve the problem. The workaround should not have any impact on SCE service or performance.

To implement the workaround, run the following CLI commands after the upgrade procedure:

SCE#>configure 
SCE(config)#>interface LineCard 0 
SCE(config if)#>lookup GT_LUT_HTTP_BASED_PROTOCOLS_UserAgents remove-key 'Mozilla' 
SCE(config if)#>exit 
SCE(config)#>exit 

SCE#>copy running-config-all startup-config-all 

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsk31825 (registered customers only)

An upgrade from PP#9 to PP#10 will cause misclassification of 'Fring' (IM).

Revision History

Revision

Date

Comment

1.0

05-SEP-2007

Initial Public Release

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.