The Cisco SCA BB installation package is a ZIP file located in the CCO.

The installation package consists of the following files:

• The installer for the Console: scas-bb-console-<version>-<build>.exe.
• A Cisco installation application package file (PQI file) for each type of Cisco SCE platform. Each PQI file is located in a subfolder whose name is the platform name.
• The file scas_bb_util.tgz, which contains the files for the Cisco SCA BB Service Configuration Utility ( servconf) , the Cisco SCA BB Signature Configuration Utility ( sigconf) , the Cisco SCA BB Real-Time Monitoring Configuration Utility ( rtmcmd) (together with real-time monitoring report templates), and the BGP Autonomous System Dynamic Detection scripts and files ( routerInfo.properties , asFetch.bat , asFetch.sh ).
• The file PCubeEngageMib.mib, which defines the SCAS BB MIB, located in the SNMP subfolder.
• The Cisco SCA BB Service Configuration Java API distribution file: serviceconfig-java-api-dist.tgz.
• The file surfcontrol.xml, which lists the content categories for content filtering using SurfControl Content Port Authority, located in the URL Filtering subfolder.

Cisco SCA BB has two software components that reside on the Cisco SCE platform:

• The Cisco SCA BB SLI, which performs traffic processing
• The Cisco SCA BB SCE applicative management plug-in, which performs some service configuration operations

Cisco SCA BB also has one software component that resides on the Subscriber Manager device:

• The Cisco SCA BB Subscriber Manager applicative management plug-in, which performs some application-specific subscriber management operations

To install these components from the Console, see the How to Install PQI Files on Cisco SCE Devices and Managing Collection Manager Devices sections.

To install these components from a command line, see the Installing PQI Files from the Command Line section.

Before installing Cisco SCA BB, verify that the SCE platform and, if used, the Cisco Service Control Subscriber Manager are operational and are running appropriate versions of their software.

You should install the following Cisco SCA BB front ends:

• The Console
• The Cisco SCA BB Service Configuration Utility ( servconf) , the Cisco SCA BB Signature Configuration Utility ( sigconf) , and the Cisco SCA BB Real-Time Monitoring Configuration tool ( rtmcmd) (together with associated real-time monitoring report templates).
  • servconf requires access to the Java Runtime Environment (JRE) (see “Installing the Java Runtime Environment” section).

Periodically, Cisco publishes protocol packs containing new and improved protocol signatures for Cisco SCA BB. A typical protocol pack is a file containing signatures for detecting network worms, popular peer-to-peer applications, and other relevant protocols. When loaded into SCE platforms, these signatures improve Cisco SCA BB classification abilities.

Note	You can install a protocol pack on an SCE platform only if a PQI is already installed on the platform.

A protocol pack for Cisco SCA BB may be either a DSS file or an SPQI file:

• Loading a DSS file to the SCE platform requires no downtime of Cisco SCA BB or the platform.
• Loading an SPQI file to the SCE platform entails updating the SCE application:
  • If hitless upgrade (see Hitless Upgrade of the SLI section ) is enabled, there is no downtime of the SCE platform when loading the SPQI file.
  • If hitless upgrade is not enabled, loading an SPQI file requires a short downtime (up to one minute) of the SCE platform. During that time, network traffic bypasses the platform and is neither controlled nor reported.

Note	If hitless upgrade is disabled, SPQI installation can cause the loss of the following subscriber data from all subscribers: package ID, real-time monitoring flag, and quota settings. Subscribers are assigned default values for these properties.

Opening a PQB using the Client (GUI) exposes its service hierarchy tree (signatures, flavors, protocols, and so on). The client defines the Service Configuration Hierarchy.

When loading a PQB file from the SCE, the PQB Hierarchy Tree must be of the same version as the one in the client. In other words, the PQB must be the same version as the Client, otherwise the PQB doe not open.

Because the client can be connected with different SCE with different versions, and each PQB can have different Service Hierarchy Tree definition, you must install the relevant Service Hierarchy Tree in the Client (GUI) before opening a PQB.

The client can install the service hierarchy tree according to the SCE version. The GUI installation comes with a fixed set of service hierarchy elements which are placed in a specific version-related jar file. You can select between different jar files related to different versions.

The SCE service hierarchy tree is different than the client version. When installing a service hierarchy tree for a SCE:

• Always back up user PQB before upgrade to PPXY and keep a copy since the PQB is changed.
• Remove/Reinstall Service Tree Protocol.

Note

Common SCABB console is going to be used for SCE 8000, SCE10000 and vSCE platform releases. The SCABB console reaction for PQB files are listed below: SCE 8000 platform level service tree will be maintained if we open 4.1.x or any earlier release PQB file in 5.1.0 SCABB console. SCE10000 platform level service tree will be maintained if we open 5.0.0 release PQB file in 5.1.0 SCABB console. SCE10000 platform level service tree will be maintained if we create new policy in 5.1.0 SCABB console.

To view, install, and remove the service hierarchy tree use the following procedures:

The problems that may cause the installation of a protocol pack to fail and their remedies include:

• Missing or incorrect version of the JRE—Install the correct version of the JRE (see “Installing the Java Runtime Environment” section ).
• Incorrect or missing SCE application version on the SCE platform—Verify that the correct version of the SCE application is installed (see “How to Verify Version Compatibility for Protocol Packs” section ).
• No service configuration (PQB) is applied to the SCE platform—Create a new PQB and apply it using the Console.
• servconf failed to import the new signatures into the PQB—Use the --force-signature update signature option when running servconf (see “servconf Syntax” section).

When reporting problems to Cisco, include the servconf log file, located at <user.home>\.p-cube\servconf.log. With Windows, this usually maps to C:\Documents and Settings\<username>\.p-cube\servconf.log or C:\Users\<username>\.p-cube\servconf.log.

Hitless upgrade is the Cisco SCA BB method of upgrading the software components that reside on the SCE platform without incurring any service downtime.

• Hitless upgrade of Protocol Packs is available on SCE 8000.
• Hitless upgrade of Protocol Packs is available on SCE 10000.

If hitless upgrade is enabled, classification, reporting, and control continue uninterrupted when you install an SPQI file (see Working with Protocol Packs section ). You can install SPQI files using either the Console or servconf, the Cisco SCA BB Service Configuration Utility. An SPQI file is a package that includes the required (SLI) files.

Note	When you apply a new policy or during Protocol Pack upgrade, there is a delay of 30 seconds before the rules are applied to the new flows.

After the new application is loaded on the SCE platform:

• The new application services all new flows and bundles.
• The old application continues to service existing flows (and new flows that belong to bundles of existing flows).
• Both applications share available memory.

Until all old flows die or are killed, the hitless upgrade is considered to be in progress. To make the hitless upgrade process bounded, you can set criteria that triggers the explicit killing of all flows still executing on the old application. Two such criteria exist:

• When a specified amount of time has passed since the process started.
• When the number of old flows goes below a specified threshold.

The default value for the first criterion is 60 (minutes); the default value for the second is zero (flows). This means that the replace operation is guaranteed to complete after no more than one hour (sooner, if all old flows die naturally). But the application does not kill any old flow before one hour completes.

These criteria are configurable by CLI commands.

You can initiate the explicit killing of all old flows using a manual command.

The configuration wizards available from the Welcome view are (three of these wizards can also be executed from the Network Navigator tool):

• Usage Analysis wizard—Creates a simple model of devices and connects to them.
• The P2P Traffic Optimization wizards:
  • P2P Traffic Optimization wizard—Creates a simple model of devices, connects to them, and limits P2P traffic to a specified percentage of total available bandwidth.
  • P2P Traffic Optimization at a Peering Point wizard—Creates a simple model of devices, connects to them, limits P2P traffic to a specified percentage of total available bandwidth, and allows you to enable asymmetric routing classification mode.
• Reporter database Configuration wizard—Connects the Cisco SCA BB Reporter tool to a database.

Asymmetric Routing

Traffic processing depends on the routing environment. The Cisco Service Control solution can operate in two typical routing schemes: symmetric and asymmetric. In asymmetric routing, for a significant number of flows, only one direction (inbound or outbound) is routed through the SCE platform.

Anonymous Subscriber Mode

Anonymous subscriber mode is a mode in which entities defined as IP addresses are treated as subscribers.

The Network Navigator is a tool that allows you to create and manage a simple model of all local and remote devices that are part of the Cisco Service Control solution.

For more information about the Network Navigator, see Using the Network Navigator section.

This section contains information about the following procedures:

The Service Configuration Editor is a tool that allows you to create service configurations. A service configuration is a data structure that defines how the SCE platform analyses network traffic, what rules apply to the traffic, and what actions the SCE platform takes to enforce these rules.

Most of this document discusses using the Service Configuration Editor. See Using the Service Configuration Editor section .

The Signature Editor is a tool that allows you to create and modify files that can add and modify protocols and protocol signatures in Cisco SCA BB.

For more information about the Signature Editor, see Using the Signature Editor section.

This section contains information about the following procedures:

The Subscriber Manager GUI is a tool that allows you to connect to a Cisco Service Control Subscriber Manager and then manage subscribers, assign packages to subscribers, edit subscriber parameters, and manually add subscribers.

For more information about connecting to a Cisco Service Control Subscriber Manager and using the Subscriber Manager GUI, see Using the Subscriber Manager GUI Tool section .

For more information about the Cisco Service Control Subscriber Manager, see the Cisco Service Control Management Suite Subscriber Manager User Guide.

This section contains information about the following procedures:

The Anonymous Group Manager GUI allows you to manage anonymous groups within a SCE. You can create, edit, delete anonymous groups, and list all configured groups for a selected SCE. For a selected group, the GUI lists all anonymous subscribers that are part of the group.

For more information, see Using the Anonymous Group Manager Tool section.

You can access relevant parts of this user guide from the Console. The following sections provide you with the necessary details: