Release Notes for Cisco Service Control Operating System Release 3.1.

6S and Cisco Service Control Application for Broadband Release 3.1.6 with Cisco SCE8000
February, 2009 OL-17014-04

The following release notes describe functional enhancements, fixes, and known caveats for Cisco Service Control software deployed with the Cisco SCE8000 Service Control Engine. These release notes apply to Cisco Service Control Operation System (SCOS) Release 3.1.6S and Cisco Service Control Application for Broadband (SCA-BB) Release 3.1.6. Supports: SCOS Release 3.1.6S and SCA BB Release 3.1.6

Introduction, page 1 SCOS Release 3.1.6S, page 3 Open Caveats in Cisco SCE Release 3.16, page 7 Obtaining Documentation and Submitting a Service Request, page 9

Introduction
This document describes the Service Control Engine SCE8000 platform together with Release 3.1.6S of the Service Control Operating System (SCOS). The primary enhancement of Release 3.1.6S is support for the Cisco SCE8000 platform. The Cisco service control engine 8000 (SCE8000) is a high-capacity, carrier-grade network element designed to perform stateful application and session-based classification and to manage application-level IP traffic per subscriber. The SCE8000 has the highest performance and capacity of the SCE product family, capable of supporting multiple, 10-gigabit interfaces. The Cisco SCE8000 is deployed in a number of capacities within service provider networks. It can be integrated into the core, at aggregation peering-points, as well as at the edge and aggregation layers to provide advanced application-level bandwidth optimization, management, and service control functions.

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Introduction

The Cisco SCE8000 is access agnostic and can be deployed in any Cable, Wireline, or Mobile IP network environment. The Cisco SCE8000 is deployed using high-speed 10-gigabit ethernet interfaces connected to these core and aggregation elements of today's Service Provider networks. Residing at these critical junctions of the network, the Cisco SCE8000 is not only a high performance solution, but also a highly available and robust solution. It employs a number of High Availability (HA) and reliability features to meet expectations of the most demanding multimedia applications and Service Level Agreements (SLAs). The Cisco SCE8000 employs both inter- and intrachassis redundancy features to guarantee high availability. Multiple CiscoSCE8000s can be deployed to achieve high availability and failover without imposing any single point of failure. An N+1 high-availability topology is supported by clustering multiple Cisco SCE8000s allowing the solution to scale linearly. To achieve higher performance and maximum capacity, the Cisco SCE8000 takes advantage of patented system logic and stateful Deep Packet Inspection (DPI) technology. This document outlines issues related to the operation of SCOS Release 3.1.6S and SCA BB Release 3.1.6 with the Cisco SCE8000 platform. It assumes the reader already has a good working knowledge of the Cisco Service Control solution. For additional information, refer to the Cisco Service Control Engine documentation.

Note

To access the new Cisco Service Control online documentation site, do the following:
1. 2. 3. 4.

Go to the following page on Cisco.com: http://www.cisco.com/web/psa/products/index.html From the Select a category list, select Service Exchange. From the Select a subcategory list, select the desired Cisco Service Control category. From the Select a product list, select the desired Cisco Service Control product.

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

SCOS Release 3.1.6S

SCOS Release 3.1.6S

Compatibility Information, page 3 Capacity Information, page 3 SCOS Release 3.1.6S Functional Enhancements, page 3 SCA BB Release 3.1.6 Functional Enhancements to Support the SCE8000, page 4 CLI and File System Compatibility, page 5 API Support, page 6 Protocol Support, page 6 Resolved Issues, page 6

Compatibility Information
SCOS Release 3.1.6S may be installed on the following Service Control Engine platform:

Cisco SCE8000 SCE 2020 4 x GBE SCE 2020 4/8 x FE SCE 1010 2 x GBE (2-U only)

The following SCE platforms cannot be used with SCOS Release 3.1.6S.

These platforms should use SCOS Release 3.1.6. For information regarding compatibility between Service Control components, refer to the Cisco Service Control Application for Broadband Download Guide.

Capacity Information
SCA BB Release 3.1.6 supports the following flow and subscriber capacity numbers. Device (Capacity Option) SCE8000 (SCE8000) Number of Subscribers 250,000 Number of Flow 16 M (8 M bidirectional)

SCOS Release 3.1.6S Functional Enhancements

The following section lists the functional enhancements in SCOS Release 3.1.6S. See the Cisco SCE8000 Software Configuration Guide for more information regarding these features.

Cisco SCE8000 Platform Support

The primary enhancement of Release 3.1.6S is to support the Cisco SCE8000 platform.

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

SCOS Release 3.1.6S

SCA BB Release 3.1.6 Functional Enhancements to Support the SCE8000

This section lists the functional enhancements in SCA BB Release 3.1.6S. For more information regarding these features, see the Cisco Service Control Application for Broadband User Guide.

SCA-BB Console Changes

In the Service Configuration Editor, the Global Controllers user interface is adjusted for 10 GBE interfaces. An SCA BB tool tip indicates that an option of 10 Gigabit Ethernet exists (Figure 1).
Figure 1 Global Bandwidth Controllers User Interface

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

SCOS Release 3.1.6S

The Network Navigator graphical user interface Online Status window provides a correct indication of the SCE platform and interface type. The following values are presented when applicable (Figure 2):

SCE8000 - 4 x 10 GBE SCE8000 - 2 x 10 GBE

SCE Platform Type

Figure 2

Note

SCA BB Release 3.1.6 supports both legacy SCE platforms as well as Cisco SCE8000. SCA BB Release 3.1.6 comprises two main packages: the management software that is installed on a workstation, and the agent package with the PQI files that are loaded on the SCE on top of the SCOS. For purposes of identification, the PQI file of SCA BB Release 3.1.6 for Cisco SCE8000 carries a version string of 3.1.6S and the build number is different from the PQI of other SCE platforms. However, it is functionally identical to SCA BB Release 3.1.6.

CLI and File System Compatibility

In general, Cisco SCE8000 functionality and interfaces are identical to the Cisco SCE 1010 and SCE 2020 platforms. This section describes functional differences between Cisco SCE8000 and Cisco SCE 2020.

Cisco SCE8000 CLI Adaptation

Most of the CLI in Cisco SCE8000 are identical to Cisco SCE 2020. There are some changes implied by the Cisco SCE8000 architecture. Interface names are changed to comply with Cisco standard, based on the different rates of the SCE8000 data links and management links. Detailed CLI reference for the Cisco SCE8000 appears in the Cisco SCE8000 CLI Command Reference.

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

SCOS Release 3.1.6S

File System Structure

The SCOS home directory changed. When a user logs into the Cisco SCE8000, the current working directory is /apps/data/scos (in the SCE2020 this location is /tffs0). All files that are or may be used by the user are located under this directory tree. For example, the configuration file config.txt is located in /apps/data/scos/system. In the Cisco SCE 2020, system files and executables are also located under this same tree. For the SCE8000 platform, all system and executables are located under a different tree, which is a read-only file system, for greater protection of the system and image files.

Filename Structure
SCE8000 file system, which is based on Linux file system, has the following differences from SCE 2020:

SCE8000 filenames are case sensitive. SCE8000 filenames are not restricted to the 8.3 file name format (file name up to 8 characters in length with an extension of up to 3 characters in length). Some file names may still comply to the 8.3 file name restriction, as they are used in both SCE 2020 and SCE8000. User-created and copied files can have any name.

API Support
Both the SCE Subscriber API and the Service Configuration API of Release 3.1.6 and later support the SCE8000 as well as SCE 2020. User code that worked with earlier versions of these APIs does not require change to function with SCE8000.

Protocol Support
For information about protocol support for Protocol Pack #13, refer to the Protocol Pack Notes (included in SCA BB Release l3.1.6).

Note

When you upgrade old PQB files, new signature-based protocols are not assigned to any service. Signature-based protocols that are not assigned to a service are classified as Default Service. To fix this, manually assign these protocols to a service.

Resolved Issues
No existing caveats were resolved in this SCOS release.

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

Open Caveats in Cisco SCE Release 3.16

Open Caveats in Cisco SCE Release 3.16

CSCsv49142

The SCE8000 management interface does not support speed and duplex configuration SCOS release 3.1.6S for the SCE8000 platform does not support management interface speed and duplex configuration. The commands are available in the CLI under interface GigabitEthernet 1/1, but have no actual implication on the system. The user should not use these commands in SCOS Release 3.1.6S. Workaround: Not needed, since the system is always in auto. If the peer device works at a speed slower than 1000 Mbps, the interface will adjust, as it is in autonegotiation mode.
CSCsq96310

The SCE8000 cannot configure default gateway before IP address is configured. The default gateway cannot be configured until an IP address is first configured. Trying to set the default gateway when IP address is set results in an error. Workaround: Configure the IP address before adding the default gateway.
CSCsq93712

SCE8000 cannot configure nondefault attack detectors. Attack detectors cannot be used with non-default rules using ACL. Trying to configure ACL rules for attack detector fails. Using attack detector without ACL is working. Workaround: None
CSCsq33416

SCE8000 entity MIB is not updated dynamically when components are added. FRU modules may not appear correctly in the entity MIB after being added. When a second PSU or SPA pluggable optic is added online, it does not appear in the entity MIB. The problem occurs only when new components are added. Replacing FRUs that were installed at system reload is properly reflected in the entity MIB. After reload, the entity MIB is properly updated. Workaround: None.
CSCsk78621

SCE8000 in rare cases, application installation or un-install can cause a system failure if done immediately after clock/time zone change.Updating clock or time zone can, in some rare cases, leave the software in a transient state that in turn can cause application installation or un-install to hang and system reboot. In all the observed cases the transient situation passed after 20 minutes. This can happen when installing, un-installing, or upgrading PQI via the CLI or from SCA-BB GUI.
Conditions:

This event is extremely rare and is only relevant for application or pqi installation, or un-install. As SNTP is currently not supported for FCS, there is no risk for automatic clock update.

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

Open Caveats in Cisco SCE Release 3.16

Workaround: We recommend you avoid application or pqi installation or un-install for a full hour after changing clock or time zone from CLI. If it is necessary to actively change the time or time zone, we recommend you do so after the pqi is installed.
CSCsq94141

In rare cases, there may be a condition in which the SNMP agent does not respond to new SNMP requests Workaround: If the SNMP does not respond, use the following CLI commands to disable it and enable again: Under general configuration menu:
#no snmp-server #snmp-server enable

CSCsm12163

SNMP protocol Version v1 does not show 64-bit counters. Workaround: We recommend you use SNMP v2.
CSCsq67666

SNMP traps have an incorrect index on the management IF status trap. The ENTITY-STATE-MIB includes two entity state notifications:

entStateOperDisabled entStateOperEnabled entStateAdmin entStateAlarm entStateAdmin.22 entStateAlarm.22

Each of these traps include the following two varbinds:

These varbinds explicitly define the entity physical index that triggered the traps, for example:

(Physical Index 22 in the entity MIB represents GigabitEthernet 3/0/0). When the management port triggers one of these notifications, the zero physical Index is sent, for example:

entStateAdmin.0 entStateAlarm.0

Note that when the index is 0, this means that the port is the management port. Workaround: None.
CSCsr19962

Two second link down when moving manually to external-bypass. When the external optical bypass is enabled by CLI command, there is link down time of two seconds. This does not happen when optical bypass is enabled due to system failure or reload. Workaround: To avoid link downtime, use a debug command as follows:
#do debug slot 0 ppc 0 func NjcCPLD[0].SetOpticalBypass 1

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

Obtaining Documentation and Submitting a Service Request

#external-bypass

CSCsx40066

The SCE8000 system fails to establish a Telnet connection due to a DNS issue. When you establish a connection to Cisco SCE8000 using Telnet, the client failed to acquire the IP address and the connection is aborted. Workaround: Any of the following workarounds can be implemented:

Modify the DNS server entries to map the client IP address and hostname correctly. Use a client with IP address which does not exist in the DNS table, to avoid the IP address being converted to hostname by the DNS. Remove the DNS configuration from the Cisco SCE8000. Use the console to remove the DNS configuration. Use SSH instead of Telnet.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly Whats 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 Whats 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.

CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or website 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. (0812R) 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. 2009 Cisco Systems, Inc. All rights reserved.

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03

Obtaining Documentation and Submitting a Service Request

10

Release Notes for Cisco Service Control Operating System Release 3.1.6S and Cisco Service Control Application for Broadband Release 3.1.6 OL-17014-03