Cisco Service Control Product Installation Guide, Release 5.0.x

Available Languages

Download Options

  • PDF     (1.5 MB)
    View with Adobe Reader on a variety of devices
Updated:June 23, 2014

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Table of Contents

Cisco Service Control Product Installation Guide, Release 5.0.x

Overview of the Cisco Service Control Solution

Cisco Service Control Components

Options and Versions

System Installation Overview

Cisco Service Control Solution Topology

Overall System Topology

Cisco SCE 10000 Platform Topologies

Physical Topologies

Multi-Gigabit Service Control Platform (MGSCP) Topology

System Installation

Installing the Cisco SCE 10000 Platform

Cisco SCE 10000 Connectivity

Installing the Subscriber Manager

Installing the Collection Manager

Ports Used by the Collection Manager Software

Installing Collection Manager Software

Installing the Cisco SCA BB Application

How to Verify that the Cisco SCE Platform is Running a Compatible Version of the OS

How to Verify that the Subscriber Manager is Running a Compatible Version

How to Install the Cisco SCA BB Console

How to Install the Cisco SCA BB Configuration Utilities

Installing the Application and Protocol Pack on the Cisco SCE Platform

Before You Start

How to Install Files on the Cisco SCE Platform

Initial Configuration

Initial Configuration of the Cisco SCE 10000 Platform

Initial Cisco SCA BB Configuration

How to Use the Usage Analysis Wizard to Define the Default Site

Configuring the Subscriber Manager

System Requirements and Prerequisites

Overall System Requirements

SCA BB System Requirements

Subscriber Manager System Requirements

Cisco Service Control Collection Manager System Requirements

Obtaining Documentation and Submitting a Service Request

Quick Start Guide

Overview of the Cisco Service Control Solution

This section introduces the components of the Cisco Service Control solution and gives a high-level explanation of the entire installation process.

Cisco Service Control Components

The Cisco Service Control solution consists of five main components:

  • Cisco Service Control Engine (SCE) platform—A flexible, powerful, and dedicated network-usage monitor that is custom-built to analyze and report on network transactions at the application level.

For complete information about the installation and initial configuration of the Cisco SCE platform, see the Cisco SCE Platform Installation Guides and Configuration Guides .

  • Cisco Service Control Application for Broadband (SCA BB)—An application that creates a service configuration file containing settings for traffic classification, accounting, and reporting, and applies it to a Cisco SCE platform. Cisco SCA BB provides tools to automate the distribution of these configuration files to Cisco SCE platforms. This simple, standards-based approach makes it easy to manage multiple devices in a large network.

For complete information about the installation and operation of Cisco SCA BB, see the Cisco Service Control Application for Broadband (SCA BB) User Guide .

  • Service Control Management Suite (SCMS) Subscriber Manager—A middleware software component used when dynamic binding of subscriber information and policies is required. The Subscriber Manager manages subscriber information and provisions it in real time to multiple Cisco SCE platforms. The Subscriber Manager stores subscriber policy information internally, and acts as a stateful bridge between the authentication, authorization, and accounting (AAA) system (such as RADIUS and DHCP) and the Cisco SCE platforms.

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

Quota Manager is an optional component of the Subscriber Manager. It enables Cisco Control solution providers to manage subscriber quota across subscriber sessions with a high degree of flexibility.

For more information about the installation and operation of the Quota Manager, see the Cisco Service Control Management Suite Quota Manager User Guide.

Virtual Link Manager (VLM) is a component of the Subscriber Manager that enables Cisco Service Control solution providers to monitor and control individual subscriber links separately. For this, VLM creates a single policy with tier-differentiated packages, as also a number of virtual links, and then assigns subscribers to these virtual links. For more information, see the Cisco Service Control for Managing Remote Cable MSO Links Solution Guide .

  • SCMS Collection Manager—Implementation of a collection system that receives Raw Data Records (RDRs) from one or more Cisco SCE platforms. The Collection Manager collects usage information and statistics, and stores them in a database. The Collection Manager also converts subscriber usage information and statistics into simple text-based files for further processing and collection by external systems.

For more information about the installation and operation of the Collection Manager, see the Cisco Service Control Management Suite Collection Manager User Guide .

  • Insight Reporter—Cisco Insight Reporter is a software platform based on web 2.0 user experience standards, designed to collect and present reports, charts, and statistics about the traffic data collected by Cisco SCE devices.

Together, the Cisco SCE platform, the SCMS Collection Manager, the SCMS Subscriber Manager, and Cisco Insight are designed to support detailed classification, analysis, reporting, and control of IP network traffic. The SCMS Collection Manager and the SCMS Subscriber Manager are optional components; not all deployments of the Cisco Service Control solution require them. The following sites may not require all these components:

  • Sites that employ third-party collection and reporting applications
  • Sites that do not require dynamic subscriber-aware processing
  • Sites that use a RADIUS or DHCP sniffing option.

Options and Versions

The Cisco SCE Platform

The Cisco SCE platform is available in the following version:

  • SCE 10000 8x10GBE—With eight 10 GBE interfaces. The eight interfaces support four traffic links.

The platform version is available with either AC or DC power.

NoteIn general, this guide contains instructions for installing the Cisco SCE 10000 platform. In general, this guide contains instructions for installing the Cisco SCE 10000 platform.

The Cisco SCA BB Application

Cisco SCA BB is not available in different versions.

Subscriber Manager

The SCMS Subscriber Manager is available in the following version:

  • Linux

SCMS Subscriber Manager versions are available with these options:

  • Optional Veritas cluster support for redundancy
  • Optional Login Event Generators (LEGs)

Collection Manager

The SCMS Collection Manager is available in the Linux version

The SCMS Collection Manager versions is available with the following option:

  • Uses an external database (Any JDBC-compliant database, such as Oracle or MySQL, used with the JDBC Adapter)

System Installation Overview

Figure 1 shows the order of in which the Cisco Service Control solution must be installed.

Figure 1 Installing the Complete Cisco Service Control Solution

 

To install the complete Cisco Service Control solution, complete these steps:

Step 1 Install the Cisco SCE platform (see the Cisco SCE 10000 Installation and Configuration Guide).

This task includes:

    • Installation in the rack
    • Initial configuration by using a local console
    • Cabling management and line ports

Step 2 Install the Subscriber Manager (see the “Installing the Subscriber Manager” section ).

This task includes:

    • Preliminary configuration (memory settings and configuration file.)
    • Installing the SCMS Subscriber Manager software
    • Adding a user for Proprietary Remote Procedure Call (PRPC) authentication

Step 3 Install the Collection Manager (see the “Installing the Collection Manager” section ).

This task includes:

    • Installing the SCMS Collection Manager software
    • Configuration related to the various adapters
    • Adding a user for PRPC authentication
    • Configuring the SCMS Collection Manager to be able to connect to the database

Step 4 Install the Cisco SCA BB Console and optional Cisco SCA BB configuration utilities (see the “Installing the Cisco SCA BB Application” section ).

Step 5 Install the Cisco SCA BB application component (PQI file) and protocol pack on the Cisco SCE platform (see the “Installing the Application and Protocol Pack on the Cisco SCE Platform” section ).

Step 6 Perform additional initial configuration, if any, of the Cisco SCE 10000 platform from the management workstation (see the “Initial Configuration of the Cisco SCE 10000 Platform” section ).

Step 7 Perform initial configuration of the Cisco SCA BB application by using the Usage Analysis wizard (see the “Initial Cisco SCA BB Configuration” section ).

 

Cisco Service Control Solution Topology

This section describes the possible deployment topologies of the Cisco Service Control solution.

NoteThis section presents the deployment topologies for the Cisco SCE 10000 platform. For information regarding the deployment topologies for the Cisco SCE 10000 platform, see the This section presents the deployment topologies for the Cisco SCE 10000 platform. For information regarding the deployment topologies for the Cisco SCE 10000 platform, see the “System Requirements and Prerequisites” section.

Overall System Topology

Figure 2 illustrates the general topology of the Cisco Service Control solution.

  • Horizontal flow—Represents traffic between subscribers and an IP network.

The SCE platform monitors traffic flow.

  • Vertical flow—Represents transmission of RDRs from the Cisco SCE platform to the SCMS Collection Manager.

The SCMS Subscriber Manager provides subscriber data. This flow allows Cisco SCA BB to conduct subscriber-level analysis and control.

Figure 2 Flow of Information in SCA BB

 

Cisco SCE 10000 Platform Topologies

The Cisco SCE 10000 platform is an ideal solution for dual links with load sharing and asymmetrical routing and support for fail-over between two Cisco SCE platforms.

Cisco SCE 10000 is built to support wire-speed processing of full-duplex 10 GBE streams. The Cisco SCE 10000 can, therefore, be deployed in a multilink environment, in several topologies:

  • Single Cisco SCE 10000 topology—Enables processing of both upstream and downstream paths of a bidirectional flow, even if these paths traverse different links.
  • Multi-Gigabit Service Control Platform (MGSCP) topology—Provides scalability. The Cisco SCE 10000 platform supports the option to connect multiple SCE platforms to a Cisco 7600 Series Router or a Cisco ASR 9000 Series Router to perform load balancing between the platforms.

Physical Topologies

These are the descriptions of the physical topologies that Cisco SCE 10000 supports:

Single Cisco SCE 10000 Topologies

A single Cisco SCE 10000 supports both single 10GBE link and dual 10GBE link topologies.

Single Link: Inline Topology

Typically, Cisco SCE 10000 is connected in a full-duplex 10GBE link between two devices (Router, broadband remote access server, and so on). When Cisco SCE 10000 is installed inline, it physically resides on the data link between the subscribers and the network.

Multi Link: Inline Installation

In this topology, a Cisco SCE 10000 is connected inline in four links and with eight 10 GBE interfaces.

Single Link: Receive-Only Topology

In this topology, an optical splitter resides physically on the 10GBE link between the subscribers and the network. The traffic passes through the optical splitter, which splits the traffic to Cisco SCE 10000. As a result, Cisco SCE 10000 only receives traffic and does not transmit.

In an optical splitter topology, Cisco SCE 10000 enables only the traffic monitoring functionality.

NoteWhen implementing receive-only topologies with a switch, the switch must support the SPAN functionality that includes separation between ingress and egress traffic and multiple SPAN ports destinations. When implementing receive-only topologies with a switch, the switch must support the SPAN functionality that includes separation between ingress and egress traffic and multiple SPAN ports destinations.

MultiLink: Receive-Only Topology

In this topology, a Cisco SCE 10000 is connected in receive-only mode tn four links and with eight 10 GBE interfaces.

As with the dual link, inline topology, this topology completely overcomes the problem of asymmetrical routing.When implementing receive-only topologies with a switch, the switch must support the SPAN functionality that includes separation between ingress and egress traffic and multiple SPAN ports destinations.

Multi-Gigabit Service Control Platform (MGSCP) Topology

In this topology, multiple Cisco SCE 10000 platforms are connected to a Cisco 7600 Series router, which acts as a dispatcher between the platforms (see Figure 3 ). The router contains two EtherChannels (ECs), one for the subscriber side and one for the network side, that perform load balancing for the Cisco SCE platform traffic. Traffic enters the first router, is distributed between the Cisco SCE platforms by the subscriber-side EC, and then returns to the router so that it can be forwarded to its original destination.

Note You can also use Cisco ASR 9000 series router for the same solution.

Figure 3 Basic MGSCP Topology

 

There are a number of variables to be considered in the MGSCP topology, two of which include:

Type of SCE Platform Redundancy

There are two types of SCE platform redundancy:

  • All Active

All the ports in the EtherChannel and all the Cisco SCE platforms are active. If a failure occurs on one of the Cisco SCE platforms, the links on the related ports in the EC go down and the EC automatically excludes them from load distribution. The load is then distributed among the active Cisco SCE platforms.

  • N+1

N Cisco SCE platforms are active and one platform is on standby. The EC ports connected to the standby Cisco SCE platform must be configured as standby ports. If one Cisco SCE platform fails, the EtherChannel ports connected to the failing SCE platform are shut and the standby EtherChannel ports, connected to the standby SCE platform are activated.

Note The standby SCE platform must be connected to the two highest-numbered ports, because EC behavior automatically designates these ports as the standby ports.

Redundant Cisco 7600 Series Router

Two Cisco 7600 Series routers can be used to provide network redundancy (see Figure 4 ).

In this topology, one link on each Cisco SCE 10000 platform is connected to each router. Therefore, one SCE platform is required for each link.

Figure 4 MGSCP with Redundant Router

 

System Installation

This chapter describes the system installation of the Cisco Service Control solution.

Installing the Cisco SCE 10000 Platform

To install the Cisco SCE 10000 platform, complete the following steps. (For more information, see the Cisco SCE 10000 Installation and Configuration Guide .)

Step 1 Install the Cisco SCE platform on the rack.

Step 2 Connect the Cisco SCE 10000 and power it.

Step 3 Login into the Cisco Integrated Management Controller (CIMC) and launch the KVM Console. (See the “Initial Configuration of the Cisco SCE 10000 Platform” section ).

Step 4 From the KVM Console, telnet to SCE and assign the management interface.

Step 5 Cable the line ports. (See the “Cisco SCE 10000 Connectivity” section for a summary of proper cabling for various topologies).

 

Cisco SCE 10000 Connectivity

Table 1 and Table 2 summarize Cisco SCE 10000 connectivity for the basic topologies.

NoteReceive-only topologies use only Receive fibers. these can be implemented by using either an optical splitter or a switch. If a switch is used, it must support SPAN functionality that includes separation between ingress and egress traffic and multiple SPAN ports destinations. Receive-only topologies use only Receive fibers. these can be implemented by using either an optical splitter or a switch. If a switch is used, it must support SPAN functionality that includes separation between ingress and egress traffic and multiple SPAN ports destinations.

 

Table 1 Single-Link Inline Connectivity

Port
Link
Side

0/0

Link 0

Subscribers

0/1

Link 0

Network

 

Table 2 Multi-Link Inline Connectivity

Port
Link
Side

0/0

Link 0

Subscribers

0/1

Link 0

Network

0/2

Link 1

Subscribers

0/3

Link 1

Network

0/4

Link 2

Subscribers

0/5

Link 2

Network

0/6

Link 3

Subscribers

0/7

Link 3

Network

MGSCP Topologies

In an MGSCP deployment, the exact cabling scheme depends on the number and arrangement of ports in the EtherChannel in the Cisco 7600 Series router. It is, therefore, not possible to provide exact cabling schemes.

The following general guidelines are applicable during the process of designing the cabling scheme:

  • Because there are four links per Cisco SCE 10000 platform, the minimum number of platforms required is one fourth the number of links used.
  • Each link corresponds to one port on the EtherChannel on the Cisco 7600 Series router. Each EtherChannel supports a maximum of eight ports. Therefore, if all eight EtherChannel ports are configured, four Cisco SCE 10000 platforms are required.
  • For N+1 redundancy, two ports (connected to the standby platform) must be configured as standby ports on both EtherChannels. Therefore, for N+1 redundancy, one router and five Cisco SCE 10000 platforms will be used to support eight links.
  • If two Cisco 7600 Series routers are used (for network redundancy), one link on each Cisco SCE 10000 platform is connected to each router. This topology requires twice the number of Cisco SCE 10000 platforms, one platform for each link.

– A minimum of eight Cisco SCE 10000 platforms are required to support eight ports.

– For N+1 redundancy, nine Cisco SCE 10000 platforms are used to support eight active links.

When cabling to the EtherChannel, follow these guidelines:

  • The Cisco SCE platform ports must be connected to the EtherChannel ports in the same order on both sides.
  • The EtherChannel ports must be sorted in ascending order by their physical interface numbers.
  • In a topology with two Cisco 7600 Series routers, the order of connection to the EtherChannel ports must be the same on both routers. For both routers to send the traffic of a given subscriber to the same Cisco SCE platform, the Cisco SCE platforms must be connected to both routers in the same order (one Cisco SCE platform connected to the first link on both routers, another Cisco SCE platform connected to the second link on both routers, and so on).

Installing the Subscriber Manager

This section describes how to install Subscriber Manager, Release 5.0.x, on a computer running Red Hat Linux.

For more information, see the Cisco SCMS Subscriber Manager User Guide .

To install Subscriber Manager, Release 5.0.x, complete these steps:

Step 1 Use FTP to load the distribution files to the Subscriber Manager and extract them.

Step 2 Determine the system memory settings.

Set the system memory configuration requirements according to the maximum number of subscribers. See the “Installation Procedure” section in the “Installation and Upgrading” chapter of the Cisco Service Control Management Suite Subscriber Manager User Guide .

Step 3 Configure the shared memory settings.

TimesTen requires that certain changes be made in the OS kernel configuration file:

    • For Linux, modify the /etc/sysctl.conf file.

These changes increase the shared memory and semaphore resources on the machine from their defaults. See the “Installation Procedure” section in the “Installation and Upgrading” chapter of the Cisco Service Control Management Suite Subscriber Manager User Guide .

Step 4 (Optional) Edit the install-def.cfg file.

Note We recommend that you edit the install-def.cfg file if you do not want the default parameter values to be used.

The install-def.cfg file contains several parameters that can be configured before you install the Subscriber Manager. The installation routine copies these parameters to the relevant Subscriber Manager configuration file. By default, all the parameters are commented and the default values are used.

Table 3 lists the parameters of the install-def.cfg file.

 

Table 3 Parameters of the install-def.cfg File
Parameter Name
Resides In
Description
Alternate Configuration Option

max_subscribers_num

SM definitions

Defines the maximum number of subscribers that the Subscriber Manager supports.

Maximum:

  • Linux—2 million

Default is 200,000.

The max_number_of_subscribers parameter in the p3sm.cfg configuration file.

sm_memory_size

SM definitions

Defines the amount of memory, in megabytes, that is allocated for the Subscriber Manager process.

The PCUBE_SM_MEM_SIZE in the sm.sh file that resides in the ~pcube folder.

database_perm_size

Database definitions

Defines the PermSize, in megabytes, allocated for the database.

The PermSize parameter in the /var/TimesTen/sys.odbc.ini file.

database_temp_size

Database definitions

Defines the TempSize, in megabytes, allocated for the database.

The TempSize parameter in the /var/TimesTen/sys.odbc.ini file.

Step 5 Execute the install-sm.sh script.

Note You can customize the install-sm.sh script.

Note If the /etc/motd file exists, it is not possible to run the script. Move or remove the /etc/motd file before you run the install-sm.sh script.

From your workstation shell prompt, move to the directory to which the distribution file was extracted and run the install-sm.sh script. See the “Installation Procedure” section of the “Installation and Upgrading” chapter of Cisco Service Control Management Suite Subscriber Manager User Guide .

Step 6 Set the password for the pcube user.

After the installation script runs successfully, set the password for the pcube user by running the # passwd pcube command.

Note We recommend that you note down this password for future use.

Step 7 Reboot the computer. This step is mandatory to complete the installation.

Step 8 Add a user for PRPC authentication.

It is necessary to add a user for PRPC authentication because Cisco SCA BB requires a username and password when connecting to the Subscriber Manager.

To add a user for PRPC authentication, use the p3rpc command-line utility. For example:

>p3rpc --set-user --username=pcube --password=pcube-password

 

Installing the Collection Manager

This section describes how to install the Collection Manager, on a computer running Red Hat Linux:

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

Ports Used by the Collection Manager Software

Table 4 describes the TCP/UDP ports on which the Collection Manager software and associated components (such as the Sybase database) listen. This table helps the network administrator understand the behavior of the software and its adherence to the security policy.

 

Table 4 Ports that the Collection Manager Listens on Constantly

Port Number
Description

33000

Used by the Cisco SCE devices to send RDRs for data collection.

21

Used by the legacy (releases earlier than 3.0) SCAS Reporter to authenticate against the Collection Manager user on the Collection manager machine.

33001

Internal collection manager.

Note Access is required only from the local machine; external access can be blocked.

9092

HTTP technician interface.

1099—1120

RMI. Used as the management interface between the data collector and the Service Control management server.

22000

FTP server of the Collection Manager.

Note FTP transactions may listen on other ports (22001 to 22100) for data transfer, as negotiated by the protocol.

7787

Internal logging of the management user log.

Note Access is required only from the local machine; external access can be blocked.

14375

Used by the Cisco SCA BB Console to send symbol definitions (values.ini) to the Collection Manager.

14376

Used by PRPC.

The ports that are listed are those ports on which the device listens constantly. Allow access on these port numbers; otherwise, certain operations may fail.

Some operations (such as file transfer) cause a device to open ports, other than those listed, temporarily; however, these ports close automatically after the operation ends.

 

Installing Collection Manager Software

Use the install-cm.sh script to install the Collection Manager server.

install-cm.sh Options

The usage message for the install-cm.sh script is:

Usage: install-cm.sh [-h] (-d CMDIR | -o)
 
Options: -d CMDIR select directory for ~scmscm
(must not exist and must be on 8 GB free partition)
-o upgrade the existing installation
while preserving the current configuration
(can't be used with -d)
-h print this help and exit
 

The description of the options is as follows:

-d CMDIR
Used to designate the directory of the newly created
scmscm user's home. Should be the name of a
non-existing directory, whose parent resides on a
partition where at least 8 GB is free.
As an alternate to this option, you can specify -o :
 
-o
Use this option when you wish to upgrade the existing
installation while preserving the current configuration.
(can't be used with -d)
 

For information about the actions performed by the install-cm.sh script, see the Cisco Service Control Management Suite Collection Manager User Guide .

Install the Collection Manager server by performing the following procedure:

Step 1 Change directory to install-scripts under the distribution kit root.

Step 2 Run the install-cm.sh script:

# install-cm.sh -d <CM home dir>
 

After running the script, a user-driven configuration manager presents the user with options for the basic configuration of the Collection Manager.

Step 3 Choose whether to enable the verbose mode. If enabled, verbose mode displays a detailed installation log on the console. The default value is no.

Do you want to enable verbose mode (for detailed installation) (yes/no)[no]:
 

Step 4 You can choose to set up the Collection Manager database at the time of installation or configure it at a later time.

Would you like to configure the database? (yes/no): yes
 

Step 5 If you choose to configure the database:

a. Select the number corresponding to the relational database management system of the connecting database:

Enter the CM DB type:
1 - Oracle
2 - MySQL
3 - Sybase
4 - Insight
5 - Exit
Enter your choice:

 

For more information, see the “Configuring Databases” section in the “Managing the Collection Manager” chapter of the Cisco Service Control Management Suite Collection Manager User Guide .

b. Enter the following server information or press Enter to leave at the default shown.

Enter DB server host (default localhost):
Enter DB server listening port (default port no) :
Enter DB server instance id (default schema) :
Enter DB schema user name (default user_id) :
Enter DB schema user password (default password) :
 

You will see the following text:

PASS:db is up
DB connection succeeded.
 

Step 6 Restart Collection Manager for the database configuration to take effect.

Step 7 To start Collection Manager, choose yes:

Would you like to start CM now? (yes/no)[yes]:
 

The most basic installation of Collection Manager software is done.

Note A failed connection results in the user being prompted to re-enter the DB information.

Note After the user configures the requested database options, the dbinfo.vm file updates for the RDR database configuration details, the Cisco IOS Flexible NetFlow database configuration details.

Note We recommend that you set up separate databases for each platform.

Step 8 After the script completes running, set a password for the scmscm user:

passwd scmscm
 

We recommend that you maintain a record of the password.

Step 9 (Optional) To configure the Collection Manager to use an external database, use the ~scmscm/scripts/dbconf.sh -- rdr script.

This is a list of supported external databases:

    • Oracle—Releases 11.2
    • MySQL—Releases 5.6.x and later
    • Sybase—Version 15.7 and later

Step 10 Start the database.

If you are using an external database, start it according to the instructions supplied by the database vendor.

Step 11 Configure the adapters to use and the categorizer.

For details, see the “Configuring the Collection Manager” section of the Cisco Service Control Management Suite Collection Manager User Guide .

 

Step 12 Set the Collection Manager time zone by using the jselect-sce-tz.sh script. For example, if the Cisco SCE device is located in GMT+2, run this command as the scmscm user:

$ ~scmscm/cm/bin/jselect-sce-tz.sh --offset=120
 

Step 13 Activate the periodic delete procedures for the database tables by running the create_periodic_del_procs.sh script as the scmscm user:

~scmscm/db_maint/create_periodic_del_procs.sh
 

For details, see the “Managing the Periodic Deletion of Old Records” section of the Cisco Service Control Management Suite Collection Manager User Guide .

Step 14 Activate the automatic invocation of the periodic delete procedures:

$~scmscm/scripts/dbperiodic.sh --load
 

This loads the default data retention settings defined in ~scmscm/db_maint/dbperiodic.conf.

Step 15 Start the Collection Manager by running this command:

~scmscm/cm/bin/cm start

Step 16 Add a user for PRPC authentication. It is necessary to add a user for PRPC authentication because Cisco SCA BB requires a username and password when connecting to the CM.

To add a user for PRPC authentication, use the p3rpc command-line utility:

~scmscm/cm/bin/p3rpc --set-user --username=scmscm --password=scmscm-password

 

Installing the Cisco SCA BB Application

This section describes how to install the Cisco SCA BB application.

For more information, see the Cisco Service Control Application for Broadband User Guide .

SUMMARY STEPS

Step 1 Ensure that both the Cisco SCE platforms and the Subscriber Manager operate and run on versions that are compatible with your Cisco SCA BB version.

Step 2 Install the Cisco SCA BB Console.

Step 3 (Optional) Install the Cisco SCA BB utilities:

    • Service Configuration Utility ( servconf)
    • SCA BB Signature Configuration Utility ( sigconf)

Step 4 Install the Cisco SCA BB application component that resides on the Cisco SCE platform. This installation can be carried out from the Cisco SCA BB Console at a later stage in the overall installation process. See the “How to Install Files on the Cisco SCE Platform” section .

 

How to Verify that the Cisco SCE Platform is Running a Compatible Version of the OS

Step 1 From the Cisco SCE platform CLI prompt (SCE#), type show version .

Step 2 Press Enter.

The response shows the version of the OS running on the Cisco SCE platform.

 

How to Verify that the Subscriber Manager is Running a Compatible Version

Step 1 Open a Telnet session to the Subscriber Manager.

Step 2 Go to the Subscriber Manager bin directory and enter p3sm version .

Step 3 Press Enter.

The response to this command displays the Subscriber Manager version.

 

How to Install the Cisco SCA BB Console

Step 1 Navigate to the Console installation file, sca-bb-console-<xxx>.exe, and double-click it.

A standard installer wizard appears (see Figure 5 ).

Figure 5 SCA BB Console 5.0.x Setup Wizard

 

Step 2 Follow the standard installation steps to install the application at the desired location.

 

How to Install the Cisco SCA BB Configuration Utilities

Installing the Cisco SCA BB configuration utilities is optional.

Step 1 From the Cisco SCA BB installation package, extract the scas_bb_util.tgz file, and copy it to a Windows, Solaris, or Linux workstation.

Step 2 Unpack the file to a new folder.

These files are in the bin directory:

– SCA BB Service Configuration Utility ( servconf)

– SCA BB Real-Time Monitoring Configuration Utility ( rtmcmd) and associated real-time monitoring report templates

– SCA BB Signature Configuration Utility ( sigconf)

 

Installing the Application and Protocol Pack on the Cisco SCE Platform

Use the Cisco SCE Software Upgrade wizard in the console to install the application file (PQI) and the protocol pack (SPQI) on selected Cisco SCE platforms.

Before You Start

Before you begin the Cisco SCE platform upgrade, ensure that you perform the following tasks:

  • If the IP addresses of the Cisco SCE platforms to be upgraded are not defined in the Network Navigator, gather the IP addresses of all SCE platforms to be upgraded.
  • Download the relevant PQI file and protocol pack to a local location or to a location accessible by FTP. If using an FTP site, make sure you have the complete FTP location and path for each file.

How to Install Files on the Cisco SCE Platform

Step 1 In the Network Navigator of the console, select the Cisco SCE platforms to be upgraded. Right-click the corresponding Cisco SCE platform name and choose SCE Software Upgrade Wizard (see Figure 6) .

If the Cisco SCE platforms are not yet defined in the Network Navigator, you can select the site node.

Figure 6 Network Navigator

 

The SCE Software Upgrade Wizard opens. Click Next(see Figure 7) .

Figure 7 SCE Software Upgrade Wizard

 

Step 2 In the SCE IP Addresses pane (see Figure 8 ), verify that the IP addresses of all the Cisco SCE platforms to be upgraded are displayed. If any of the IP addresses are not displayed, enter the details and click Next.

Figure 8 SCE Software Upgrade Wizard—SCE IP Addresses

 

Step 3 In the SCE Usernames and Passwords pane (see Figure 9 ), enter the username and password required to access the Cisco SCE platform. You can use the same username and password for all the platforms or enter a different username and password for each platform and click Next.

Figure 9 SCE Software Upgrade Wizard—SCE Usernames and Passwords Window

 

Step 4 In the SCE Firmware (PKG) Installation pane (see Figure 10 ), specify the location of the firmware file to be installed on all the selected Cisco SCE platforms and click Next.

Figure 10 SCE Software Upgrade Wizard—SCE Firmware (PKG) Installation

 

Step 5 In the SCE Application Software (PQI) Installation pane (see Figure 11 ), specify the location of the PQI file to be installed on all the selected Cisco SCE platforms and click Next.

Figure 11 SCE Software Upgrade Wizard—SCE Application Software (PQI) Installation

 

Step 6 In the Protocol Pack (SPQI) Update pane (see Figure 12 ), check Skip Protocol Pack Update and click Next.

Note If you install the protocol pack during the upgrade, it must be the same version or a later version of the protocol pack you are upgrading from.

Figure 12 SCE Software Upgrade Wizard—Protocol Pack (SPQI) Update

 

Note Cisco SCE does not support direct downgrade of higher PP versions to a lower PP version. While downgrading the protocol pack from a higher version to a lower version, the Cisco SCA BB console displays an error message and prevents you from applying the policy on the Cisco SCE.

Step 7 In the Service Configuration (PQB) Update pane (see Figure 13 ), check Apply the Default Service Configuration and click Next.

Figure 13 SCE Software Upgrade Wizard—Service Configuration (PQB) Update

 

Step 8 The Connectivity Test pane of the SCE Software Upgrade Wizard is displayed (see ) . Click Next .

Note If a connection to one or more devices cannot be made, or if there is a problem with the connection (such as invalid version of the device), an error is displayed next to the device. (You can skip these tests by clicking Skip connectivity test). The connections are validated when you click Finish.

Figure 14 Connectivity Test

 

Step 9 The Summary pane summarizes all the information (see Figure 15 ). Verify that all the IP addresses and file locations are correct. In this pane, you can:

    • Click Back to edit any information.
    • Click Finish to begin the upgrade process as specified.

Figure 15 SCE Software Upgrade Wizard—Summary

 

Initial Configuration

This section describes the initial configuration of the system.

After all the Service Control components have been installed, perform these tasks to complete the initial setup and configuration of the system:

Step 1 Configure basic global parameters in the Cisco SCE platform, including these:

    • Define the necessary IP addresses.
    • Set the clock.
    • Set the authorization-level passwords.
    • Define RDR formatter destinations.

Step 2 Configure your site and a basic service configuration in the Cisco SCA BB Console. From the Network Navigator, run either the Usage Analysis wizard, the P2P Traffic Optimization wizard, or the P2P Traffic Optimization for Asymmetrical Routing wizard.

Step 3 From the Network Navigator, add the Subscriber Manager to the site.

Step 4 From the Network Navigator, configure a master password for the site.

Step 5 Configure the Subscriber Manager.

 

NoteThe initial setup process is flexible, and you may find that you prefer to do things slightly differently. The steps mentioned above can be considered as a suggested approach, rather than a mandatory approach. The initial setup process is flexible, and you may find that you prefer to do things slightly differently. The steps mentioned above can be considered as a suggested approach, rather than a mandatory approach.

Initial Configuration of the Cisco SCE 10000 Platform

There are several basic global parameters that must be correctly configured for the Cisco SCE platform to communicate properly with the outside world. The following is a brief summary of the initial setup parameters and commands. For more information, see the Cisco SCE10000 Software Configuration Guide .

  • Connect to the CIMC and launch the KVM Console to configure the management IP address.
  • IP address of the default gateway.
  • Hostname—The hostname is used to identify the Cisco SCE platform. It appears as part of the CLI prompt and is also returned as the value of the MIB-II object sysName.

– The maximum length is 20 characters.

– The default hostname is SCE10000.

  • Passwords for user, admin, and root-level access. These are authorization-level passwords, not individual passwords. These passwords may be encrypted.

These passwords must meet the following criteria:

– Minimum length—Four characters

– Maximum length—100 characters

– Begin with an alpha character

– Must contain only printable characters

  • The default password for all levels is cisco .
  • System clock—Current date and time. The clock and the calendar must always be synchronized.
  • Time zone—The name or ID of the time zone along with the number of hours offset from Coordinated Universal Time (UTC).
  • Domain name server—The default domain name used to complete unqualified host names, as well as up to three domain name servers, that are used for DNS lookup. You must also enable DNS lookup.
  • RDR formatter destination—The Cisco SCE platform generates RDRs and sends them to the specified destinations (external collection systems) via the RDR formatter. You can configure up to eight RDR formatter destinations. Specify the IP address and port number for each destination.

Table 5 lists the commands both for displaying the currently configured values and for configuring these parameters. It also lists the command mode for each configuration command. All the show commands are executed in the user EXEC command mode.

 

Table 5 Initial Setup Configuration

Parameter
show Command
Configuration Command
Configuration Command Mode

Management IP address and subnet mask

show interface TenGigabitEthernet 1/1 ip address

ip address x.x.x.x subnet-mask

TenGigabitEthernet interface configuration

Default gateway

show ip default-gateway

ip default-gateway x.x.x.x

Global configuration

Hostname

show hostname

hostname host-name

Global configuration

Authorization-level passwords

—

enable password level level [encryption-type] password

Global configuration

Clock

show clock

show calendar

calendar set hh:mm:ss day month year
clock read-calendar

or

clock set hh:mm:ss day month year
clock update-calendar

Privileged EXEC

Time zone

show timezone

clock timezone zone-name offset-hours

Global configuration

Domain name server

show hosts

ip domain-lookup

ip domain-name domain-name

ip name-server server-address1 [server-address2] [server-address3]

Global configuration

RDR formatter destination

show rdr-formatter destination

rdr-formatter destination ip-address port port-number

Global configuration

Initial Cisco SCA BB Configuration

Initial SCA BB configuration includes two main aspects:

  • Defining your site—Defining all your Cisco Service Control components. Use the Usage Analysis wizard to define your site.
  • Defining a basic service configuration.

Usage Analysis Wizard

Use this wizard to perform these tasks:

  • Create the site.
  • Create a service configuration called Usage Analysis with the following characteristics:

– The mode is set to Report Only.

– The maximum Transaction RDR rate is set as the default value (250) divided by the number of Cisco SCE devices.

How to Use the Usage Analysis Wizard to Define the Default Site

The Usage Analysis wizard allows you to create a simple model of devices and connect to them.

NoteIf they do not exist, the devices defined in the wizard are added to the default site in the Site Manager tree. If they do not exist, the devices defined in the wizard are added to the default site in the Site Manager tree.

To use Usage Analysis Wizard to define the default site, complete these steps:

Step 1 From the Console main menu, choose Help > Welcome.

The Welcome window opens (see Figure 16) .

Figure 16 Welcome Window

 

Step 2 Click Usage Analysis Wizard.

The Usage Analysis Wizard window appears (see Figure 17) .

Figure 17 Usage Analysis Wizard—Usage Analysis

 

Step 3 Click Next.

The SCE IP Addresses window opens ( Figure 18 ).

Figure 18 Usage Analysis Wizard—SCE IP Addresses Window

 

Step 4 In the text box, enter the IP addresses of the Cisco SCE devices that should be added to the model.

Note You can work with up to 20 Cisco SCE devices simultaneously by using the wizard.

Step 5 Click Next.

The SCE Usernames and Passwords window opens (see Figure 19 ).

Figure 19 Usage Analysis Wizard—SCE Usernames and Passwords Window

 

Step 6 Enter the user names and passwords for the SCE devices.

Do one of these:

    • To use the same username and password for all the SCE devices that you are adding, enter the user name in the Username field and the password in the Password field.
    • To provide a different user name and password pair for each SCE device, click the Use separate usernames and passwords for each SCE platform radio button, and, for each SCE device, enter the user name and password in the appropriate cell of the table.

Step 7 Click Next.

The CM Setup window opens (see Figure 20 ).

Figure 20 Usage Analysis Wizard—CM Setup Window

 

Step 8 Define the SCMS Collection Manager to use with this configuration.

Do one of these:

    • Enter the IP address, user name, and password of the Collection Manager device in the appropriate fields.

If you started from the Network Navigator, this information is retrieved and displayed. You can modify these parameters.

    • Check the Skip this step check box.

Step 9 Click Next.

The Connectivity Test window opens (see Figure 21 ).

Figure 21 Usage Analysis Wizard—Connectivity Test Window

 

The wizard tests to see that the connections to the defined devices can be made.

Note If a connection to one or more of the devices cannot be made, or if there is some problem with the connection (such as invalid version of the device), an error is displayed next to the device. You can skip these tests by clicking Skip connectivity test. The connections are validated when you click Finish at the end of the wizard.

Step 10 Click Next.

The Anonymous Subscribers window opens (see Figure 22 ).

Figure 22 Usage Analysis Wizard—Anonymous Subscribers Window

 

Step 11 To disable anonymous subscriber mode, uncheck the Enable Anonymous Subscribers mode check box.

Step 12 Click Next.

The Confirmation window opens (see Figure 23 ).

Figure 23 Usage Analysis Wizard—Confirmation Window

 

The actions that the wizard is about to take are listed on the page.

Step 13 Click Finish.

The Configuration Output window opens (see Figure 24 ).

Figure 24 Usage Analysis Wizard—Configuration Output Window

 

New devices are added to the default site of the Site Manager tree in the Network Navigator (see Figure 25) .

Figure 25 Network Navigator

 

The wizard attempts to connect to all the devices that you defined. The operation fails if:

– The wizard cannot connect to any of the SCE devices that you listed in Step 4 .

– You defined a Collection Manager in Step 8 , but the wizard cannot connect to it.

If you defined a Collection Manager in Step 8 , the SCE devices are configured so that the only category 1 RDR destination is the CM.

A new service configuration named Usage Analysis is created, and opens in the Service Configuration Editor (see Figure 26 ).

Figure 26 Service Configuration Editor

 

The service configuration has these characteristics:

    • They are in Report Only mode.
    • The maximum Transaction RDR rate is set as the default value (250) divided by the number of SCE devices. (To configure the Transaction RDR see How to Manage Transaction RDRs in the Cisco Service Control Application for Broadband User Guide . The content and structure of the Transaction RDR is listed in “Transaction RDR” in the “Raw Data Records: Formats and Field Contents” chapter of Cisco Service Control Application for Broadband Reference Guide .)

The service configuration is applied to the SCE devices.

Step 14 Click Close.

The Usage Analysis wizard closes.

 

Configuring the Subscriber Manager

After installing the SCMS Subscriber Manager, you can configure the Subscriber Manager to your specific needs. In particular, address these parameters:

  • topology—Cluster or standalone
  • introduction_mode—Pull or push
  • support_ip_ranges—Whether IP ranges should be used in the installed setup

To configure the Subscriber Manager, edit the p3sm.cfg configuration file by using any standard text editor. The configuration file is described in detail in the Configuration and Management module and in the Configuration File Options module of Cisco Service Control Management Suite Subscriber Manager User Guide .

After you finish editing the p3sm.cfg configuration file, use the p3sm utility to update the Subscriber Manager with the new settings:

At your workstation shell prompt, run the p3sm command.

This p3sm command loads the configuration file and updates the Subscriber Manager configuration accordingly:

>p3sm --load-config

System Requirements and Prerequisites

This chapter summarizes the system requirements and prerequisites of the Cisco SCE 10000 platform.

Overall System Requirements

  • The SCE platform—Cisco SCE 10000 and CIMC connected to LAN.
  • Cisco SCA BB—Workstation running Windows 2000, Windows XP, Windows Vista, or Windows 7.
  • SCMS Subscriber Manager

– Linux—Intel-based machine with a 64-bit.

The actual number of computers required depends on the number of subscribers in the system.

  • SCMS Collection Manager

– Linux—64-bit machine running RHEL 5.x/6.x or CentOS 5.x/6.x.

The actual number of computers required depends on the amount of traffic in the system.

SCA BB System Requirements

These sections describe the SCA BB system requirements:

Hardware Requirements

The hardware requirements are:

  • At least 1024 MB RAM is required to run the Console.
  • Minimal supported screen resolution for the Console is 1024 x 768 pixels.

Operating System Requirements

The Cisco SCA BB Console can run on Windows 2000, Windows XP, Windows Vista, or Windows 7.

Java Runtime Environment

If you are using the optional SCA BB Service Configuration Utility, servconf , it requires access to JRE version 1.6.

You can download a JRE from the Sun™ website at http://java.com/en/download/ .

To verify that the JRE is installed, run java-version at the command prompt. The Java version should start with 1.6.

If a different version of JRE is also installed on the workstation, you may need to tell servconf where to find the appropriate JRE. Do this configuration by setting the JAVA_HOME environment variable to point to the JRE 1.6 installation directory. For example:

JAVA_HOME=C:\Program Files\Java\j2re1.6_08

Subscriber Manager System Requirements

You can install the SCMS Subscriber Manager on the following platforms:

  • Intel machine (64-bit) running 64-bit versions of Red Hat Enterprise Linux 5.0 and later or Red Hat Enterprise Linux 6.0.
  • Intel-based machine (64-bit) running 64-bit versions of CentOS with a 64-bit version of the Java Virtual Machine. See Table 6 and Table 7 .
  • Cisco Unified Computing System (UCS) server model UCSC-C420-M3 with a Intel Xeon E5-4650 @ 2.70 GHz four processors, 32 cores.

The machine should conform to the system requirements listed in Table 6 and Table 7 .

Note The specifications listed in Table 6 are minimal. Verify the specifications to guarantee specific performance and capacity requirements.

 

Table 6 Minimal System Hardware Requirements

Item
Requirement

CPU

The CPU requirements are:

  • Intel processor, 64 bit, minimum 2.70 GHz 4 processors, 32cores (for Linux Red Hat))

RAM

Minimum 2GB

Free Disk Space

Minimum 3 GB total, of which:

  • Minimum 1 GB free on partition where VARDIR (SM database repository) is installed
  • Minimum 0.5 GB free on partition where PCUBEDIR (Subscriber Manager files) is installed
  • Minimum 200 MB free on partition where /tmp is mounted
  • RAID0 or RAID5 is required to achieve maximum performance of Subscriber Manager

Network Interface

Depends on whether the configuration includes a cluster:

  • Without cluster—One (1) 100BASE-T Ethernet
  • With cluster—Six (6) 1G T-Ethernet

CD-ROM drive

Recommended

For the hardware and software system requirements for the Veritas Cluster Server, see the Veritas Cluster Server chapter of the Cisco Service Control Management Suite Subscriber Manager User Guide .

 

Note We recommend to apply the latest patches from Sun. You can download the latest patches from the Sun patches website.

 

Table 7 Red Hat System Software Requirements

Item
Requirement

OS

Red Hat Enterprise Linux AS/ES 4.0/5.0; currently, both 32-bit and 64-bit versions are supported.

Red Hat Core Installation.

System Packages

Mandatory:

  • GNU Bourne-Again shell (bash-2.05b-29.i386.rpm).
  • GNU Data Compression Program (gzip-1.3.3-9.i386.rpm).
  • File compression and packaging utility (zip-2.3-16.i386.rpm).
  • Standard C++ libraries for Red Hat Linux 6.2 backward compatibility (compat-gcc-7.3-2.96.122.i386.rpm).
  • sudo (superuser do) package.

For integrating with the C API:

  • GNU cc and gcc C compilers (gcc-3.2.3-20.i386.rpm).
  • C++ support for the GNU gcc compiler (gcc-3.2.3-20.i386.rpm).

NoteWe recommend that you apply the latest patches from Red Hat. We recommend that you apply the latest patches from Red Hat.

NoteOnly 32-bit versions of Linux are supported, but it is possible to install 32-bit Linux on a 64-bit CPU. Only 32-bit versions of Linux are supported, but it is possible to install 32-bit Linux on a 64-bit CPU.

Cisco Service Control Collection Manager System Requirements

The Cisco Service Control Collection Manager and its database are software components that run on a server platform. They can be installed on any of these configurations:

All configurations use a 32-bit Java Virtual Machine (JVM).

NoteThe Collection Manager must run on its own machine. You cannot run the Collection Manager on the same machine as the Subscriber Manager and other applications. The Collection Manager must run on its own machine. You cannot run the Collection Manager on the same machine as the Subscriber Manager and other applications.

These sections describe the Collection Manager system requirements:

Checking a System’s Prerequisites

The CM distribution contains a script, check_prerequisites.sh, located in the install_scripts directory:

check_prerequisites.sh [ --sybhome = SYBHOME ] [ --cmhome = CMHOME ] [ --datadir = DATADIR ]

The script helps to determine if a system meets the requirements for installing a CM or the bundled Sybase database. It also checks the overall readiness of the system for a Collection Manager or Sybase installation. The main prerequisites that are checked are:

  • CPU speed
  • Amount of RAM
  • OS version (Red Hat Enterprise Linux 5 or 6)
  • Additional required and optional packages
  • Python installed and executable in path
  • Free space for CM
  • Names for all the network interface cards (NICs)
  • Locale and time zone formats

Table 8 describes the options available in the check_prerequisites.sh script.

 

Table 8 check_prerequisites.sh Script Options

Script Options
Descriptions
--cmhome = CMHOME

Intended home directory for CM installation.

NoteAll the directories listed in All the directories listed in Table 8 must be created before running the check_prerequisites.sh script.

 

Red Hat Linux Requirements

Collection Manager Version 5.0.x or later can be installed on any x64 running Red Hat Linux that conforms to the requirements listed in these sections:

Hardware

The hardware requirements are:

  • Minimum 800 MHz CPU
  • Minimum 2 GB RAM per CPU
  • Hard disk:

– One hard disk, at least 18 GB

  • Minimum 100BASE-T network interface

Software and Environment

The software and environment requirements are:

  • Red Hat Linux 5.0:

– glibc-2.5-12 or later

– compat-libstdc++-33-3.2-61 or later 6:48 PM

– kernel-2.6.18-8.el5 or later 6:49 PM

– RHEL 5.x

  • Red Hat Linux 6.0:

– kernel-2.6.18-8.el5

– glibc-2.5-12

– compat-libstdc++-33-3.2-61

  • Red Hat Enterprise Base Installation.
  • Apply the latest recommended patches from Red Hat.
  • Reserve at least 8 GB free on the partition where the Collection Manager is to be installed. (This is used for CSV storage and persistent buffers.)
  • If you are using database periodic delete, the scmscm user should be able to schedule and run cron jobs.

Setting the Locale and Time Zone

For correct Collection Manager, U.S. English locale (en_US) must be used.

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 or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)

© 2014 Cisco Systems, Inc. All rights reserved.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco