Guest

Cisco Content Services Gateway Service Manager

Release Notes for Cisco Content Services Gateway Service Manager

  • Viewing Options

  • PDF (385.9 KB)
  • Feedback
Release Notes for Content Services Gateway Service Manager Release 2.2

Table Of Contents

Release Notes for Content Services Gateway Service Manager Release 2.2

Contents

New Features

Product Documentation

Related Documentation

Overview

Content Services Gateway

Content Services Gateway Service Manager

CSG Group Definition

RME Configuration Archive Interface

Service Activation and Deactivation

Configuration Display

Synchronization Report

Batch Mode Feature

Minimum Hardware Requirements

Supported Devices

Supported Browsers

Limitations, Restrictions, and Prerequisites

Installing the CSG Service Manager

Prerequisite Environment

Installation Order

Solaris Patches

Installation Procedure

Configuring the CSG Service Manager

Configure Network Elements

Understanding Device Interactions

Syslog Notification

Community Strings

VTY Connections

Configure group.dat File

Configure RME

Update Downloader Properties File

Add Device to RME Inventory

Configure Archive Purging

Define Message Filter for Subordinate Devices

Verify CSG Service Manager Configuration

Monitor Jobs with RME Job Browser

Set Default Data

Debug Levels

Number of Log Files

Known and Resolved Problems

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Content Services Gateway Service Manager Release 2.2


78-16959-01

March 2, 2005

Contents

These Release Notes contain important information for the Content Services Gateway (CSG) Service Manager, Release 2.2. The CSG Service Manager enables the service provider to provision service activation features for CSG releases 5.3, 5.4, and 5.5. The following topics are covered:

"New Features" section

"Product Documentation" section

"Related Documentation" section

"Overview" section

"Minimum Hardware Requirements" section

"Supported Devices" section

"Supported Browsers" section

"Limitations, Restrictions, and Prerequisites" section

"Installing the CSG Service Manager" section

"Configuring the CSG Service Manager" section

"Known and Resolved Problems" section

"Obtaining Documentation" section

"Documentation Feedback" section

"Obtaining Technical Assistance" section

"Obtaining Additional Publications and Information" section

New Features

The Content Services Gateway (CSG) Service Manager, Release 2.2, contains the following new features:

Batch Mode—A window into which multiple service activation configurations can be pasted, edited, and then downloaded at once. See "Batch Mode Feature" section.

Product Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 1 describes the product documentation that is available.

Table 1 Product Documentation 

Document Title
Available Formats

Release Notes for Content Services Gateway Service Manager, Release 2.2

PDF on Cisco.com at this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/mwc-201

User Guide for Content Services Gateway Service Manager, Release 2.2

PDF on Cisco.com at this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/mwc-201

Context-sensitive online help

Select an option from the navigation tree, then click Help.

Click the Help button in the dialog box.


Related Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 2 describes the additional documentation that is available.

Table 2 Related Documentation 

Document Title
Description and Available Formats

Release Notes for Resource Manager Essentials 3.5

Describes the release contents for the Resource Manager Essentials, Release 3.5. This document is available on Cisco.com at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/e_3_x/3_5/rel_note/index.htm

User Guide for Resource Manager Essentials 3.5

Describes user information for the Resource Manager Essentials, Release 3.5. This document is available on Cisco.com at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/e_3_x/3_5/u_guide/index.htm

Cisco Content Services Gateway Installation and Configuration Guide

Describes how to install and configure the Content Services Gateway using the Command Line Interface. This document is available on Cisco.com at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wireless/moblwrls/csg/csgr5/index.htm

Release Notes for Cisco Content Services Gateway

Describes the release contents for the Content Services Gateway. This document is available on Cisco.com at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/wireless/moblwrls/csg/csgr5/index.htm

Release Notes for Cisco IOS Release 12.2SX on the Catalyst 6500 and Cisco 7600 Supervisor Engine 720 and Supervisor Engine 2

Describes the release contents for Release 12.2SX. This document is available on Cisco.com at the following URL:

http://www.cisco.com/en/US/products/hw/switches/ps708/prod_release_note09186a00801c8339.html#wp1693686


Overview

The release notes are for the Content Services Gateway Service Manager (CSGMgr), Release 2.2.

Content Services Gateway

The Cisco Content Services Gateway (CSG) provides user-aware accounting and content billing features for the Cisco Catalyst 6000/6500 and Cisco 7600 Router platforms. The CSG is typically positioned at the edge of the Internet Service Provider (ISP) network and provides IP flow accounting and content accounting by examining URLs and header information. The CSG also collects usernames and usage statistics to enable differentiated billing for individual transactions.

Content Services Gateway Service Manager

The CSG Service Manager provides the operator with a Graphical User Interface (GUI) to configure CSG modules with the following service activation features:

Mapping

Policy

Content

Ruleset

Billing services

Billing plans


Note Only those CiscoWorks users having System Administrator or Network Administrator privileges can access the service activation features (screens under the CSG Activation and Delete Activation folders).


The CSG Service Manager combines the parameter values entered by the operator with a configuration template to generate a configuration command set. The command set is downloaded to update the running configuration of the selected device. The operator can also save the running configuration to the start-up configuration.

The CSG Service Manager Release 2.2 supports CSG Releases 5.4 and 5.5 with the following features:

Definition and initialization of a CSG group

Interface with RME configuration archive

CSG service activation and deactivation

CSG configuration display

CSG synchronization report

CSG Group Definition

A CSG group consists of two or four Cisco 6500/7600 chassis containing CSG modules that are uniformly configured with the same service activation features. The operator defines a CSG group by entering the following information in the group.dat file:

Group Name

CSG Version (5.3, 5.4, or 5.5)

Slot Numbers (slots 2-11)

Device identifier (host name or IP address)

A sample group.dat file is shown below:

GROUP_NAME = GroupOne
CSG_VERSION = 5.3
DEVICE = 192.168.122.68 
SLOTS = 4,5,6,7,8
DEVICE = 192.168.122.114 
SLOTS = 4,5,6,7,8


Note A CSG group must have two or four chassis symmetrically equipped with CSG modules, (i.e., containing the same number of modules in each chassis and in the same slots).


RME Configuration Archive Interface

The CSG Service Manager uses the RME cwconfig netconfig command to submit a CSG configuration to the RME Job Manager. The RME Job Manager downloads the configuration to the CSG modules. When the configuration is successfully downloaded, the RME uploads the latest running configuration from the device to the RME configuration archive. The CSG Service Manager refreshes its cache with the running configuration. This internal operation ensures that the CSG device configuration is synchronized with the configuration in the CSG Service Manager.

Service Activation and Deactivation

Service activation and deactivation functions are based on the values entered by the operator in the CSG Service Manager GUI. The operator input is validated and configuration files are generated using templates. The files are downloaded to the CSG modules, and the RME configuration archive is updated.

Configuration Display

The CSG Service Manager displays only those configuration command sets that are related to the CSG. Other IOS configurations are filtered out and not displayed.

Synchronization Report

The Synchronization Report (Sync Report) feature allows the operator to determine if configuration differences exist among the devices in a CSG group.

CSG Group Definition

The CSG Service Manager defines a group as a collection of four chassis each containing CSG modules. The CSG service activation configurations are the same for all the CSGs in the group. A CSG group is initially defined by the operator in the /opt/CSCOpx/cgi-bin/csgmgr/etc/group.dat file.

Master and Subordinate Devices

The first device entered in each group is considered the master device for the group. Subsequent devices listed in the group.dat file are subordinate devices. Each of the subordinate devices has the same configuration that exists on the master device. An example of the group.dat file is listed below:

GROUP_NAME = GroupOne
CSG_VERSION = 5.3
DEVICE = 192.168.122.68 <<<<<<<<-- Master Device
SLOTS = 7,8,9,10,11
DEVICE = 192.168.122.114 <<<<<<<<-- Subordinate Device
SLOTS = 7,8,9,10,11
DEVICE = 192.168.145.157 <<<<<<<<-- Subordinate Device
SLOTS = 7,8,9,10,11
DEVICE = 192.168.145.165 <<<<<<<<-- Subordinate Device
SLOTS = 7,8,9,10,11

Failure conditions (e.g., unreachable device, device in error state, or connectivity problems) could cause differences between the device configurations within a group. The operator can run a synchronization report (Sync Report) from the CSG Service Manager GUI to determine if differences exist.

The Sync Report feature evaluates the CSG configurations for a selected group and determines if differences exist between the master device and the subordinate devices in the group. The results are displayed graphically for each of the subordinate devices. If the status of a subordinate device is green, no difference exists between it and the master device. If the status is yellow, differences exist, and the operator can display them by clicking the Show Diff button. Red indicates that the device is unreachable.

Resolving Configuration Differences

Configuration differences discovered by the Sync Report feature must be resolved by the operator. See Table 3 for operator actions to resolve configuration differences.

Table 3 Resolving Configuration Differences 

 
Desired Method to Resolve Difference
Operator Action to Invoke
Difference on master

Remove configuration difference from the master device.

Note The master device configuration downloads to the subordinate devices.

Use the Delete Configuration feature in the CSG Service Manager.

Note Only the configuration data that exists on the master device can be selected for deletion.

Add the configuration difference that exists on the master device to the subordinate devices.

View the RME Job Browser for failed jobs. If failed jobs exist, rerun them.

Alternately, resubmit the job from the CSG Service Manager.

Difference on subordinate

Remove configuration difference from the subordinate device or devices.

Use the CLI to resolve the configuration difference on the device(s).

Add the configuration difference that exists on the subordinate device to all devices (master and subordinates) in the group.

View the RME Job Browser for failed jobs. If failed jobs exist, rerun them.

Alternately, resubmit the job from the CSG Service Manager.


Batch Mode Feature

The CSG Service Manager, Release 2.2, introduces the batch mode feature. This feature simplifies CSG service activation by providing a Batch Mode window into which multiple service activation configurations can be pasted, edited, and then downloaded at once.

For example, if you are configuring multiple CSG maps, you would select CSG Service Manager > CSG Activation > Map. You would enter a map name, select other parameters, then click Next to create the map configuration. But instead of clicking Finish to download the map, you would copy and paste it into the Batch Mode window. Then you would create the remaining maps, pasting them into the Batch Mode window. When completed, you would click the Download button. So instead of multiple jobs, one for each map, you are downloading one job for all the maps by using the Batch Mode window.


Caution The CSG Service Manager does not validate the configurations downloaded from the Batch Mode window. Follow the standard workflow, observe feature dependencies (e.g., configuring maps before policies), and check for typographical errors when using the Batch Mode window. Do not use the Batch Mode feature for end-to-end service activation.


Note The Batch Mode window cannot be used for applying a ruleset on the card.


Minimum Hardware Requirements

The table below displays the minimum hardware requirements.

Item
Minimum Requirement

Server model

SunFire 280R

UltraSPARC III Cu Processor

2 @ 1.015 GHz

External Cache per processor

8 MB

Memory

4 GB (4 @ 1GB DIMMS)

Disk Drive

2 @ 36 GB

Swap space

8 MB

Free disk space needed to install

5 MB


Supported Devices

The table below displays the supported releases.

CSG Version
Supervisor II Image

CSG 5.3

12.2(17d)SXB01

CSG 5.4

12.2(17d)SXB5

CSG 5.5

12.2(18)SXD3


Supported Browsers

The table below displays the supported browsers.

Browser
Browser Version
Operating System

Internet Explorer

6.0 and 6.0 SP1

Windows

Netscape Navigator1

7.1, 4.78, and 4.79

Windows

Netscape Navigator1

7.0 and 4.76

Solaris (Sun server hosting the MWC)

1 The Java plugin version must be 1.4.1_02 or higher.


Limitations, Restrictions, and Prerequisites


Caution Failure to observe the following list of limitations, restrictions, and prerequisites could cause unexpected results when using the CSG Service Manager.

The following limitations, restrictions, and prerequisites apply to Release 2.2 of the CSG Service Manager:

The IOS versions of the Catalyst 6500 switch/Cisco 7600 router and the CSG card must be the same.

Configure Virtual Local Area Networks (VLANs) on the switch fabric before configuring VLANs on the CSG. The VLAN IDs defined for the CSG module must match the VLAN IDs configured on the switch fabric.

Configure network preparation features (e.g., VLANs, server farms, quota server, and RADIUS server) on the CSGs before using the CSG Service Manager.


Note See the Cisco Content Services Gateway Installation and Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/wireless/moblwrls/csg/csgr5/index.htm


Configure CSG VLANs before using the CSG Service Manager (see CSG caveat CSCef70677).

Configure RLB server farms with server balancing set to predictor forward and with no Network Address Translation on both client and server.

Configure CSG weight definition (ip csg weight command) and CSG refund policies (ip csg refund command) using the CLI. Then you can use the CSG Service Manager to associate weights and refund policies to content definition in the Billing Services screen.

Install CiscoWorks LMS 2.2 with IDU9 before installing the CSG Service Manager (RME 3.5 is included in LMS 2.2 and is a prerequisite for CSG Service Manager 2.2).

Add CSG devices to the RME inventory before using the CSG Service Manager.

The system hosting the CSG Service Manager must meet the minimum requirements of the Mobile Wireless Center, Release 2.0.1. These requirements include Common Services 2.2 with CiscoView 5.5, Resource Manager Essentials (RME) 3.5 with Incremental Device Update (IDU) 9, and Campus Manager (CM) 3.3 with IDU 8.

Only one CSG Service Manager operator should be active at any time. Unexpected results can occur when multiple clients attempt to configure CSGs at the same time.

Do not attempt changes to an existing CSG group configuration unless you first run a synchronization report to verify that all devices are synchronized. Failure to observe this restriction could cause unexpected results and extend the configuration differences that already exist.

Each CSG group must have two or four chassis symmetrically equipped with CSG modules, (i.e., containing the same number of modules in each chassis and in the same slots).

The CSG Service Manager supports the configuration of one CSG group of devices in Release 2.2.

The CSG Service Manager supports up to 50 CSG content instances.

Configure the web browser as follows:

For Microsoft Internet Explorer:

Tools > Internet Options > Temporary Internet Files > Settings > Check for newer versions of stored pages

Choose Every visit to the page.

For Netscape Navigator:

Edit > Preferences > Advanced > Cache > Compare the page in the cache to the page on the network

Choose Every time I view the page.

Do not use the Batch Mode window to apply rulesets.

Installing the CSG Service Manager

Prerequisite Environment

Installation Order

The CSG Service Manager is installed on the server that hosts the Mobile Wireless Center (MWC) in pre-existing deployments. The latest MWC release is 2.0.1. The CSG Service Manager requires the CiscoWorks Common Services application bundled with the LAN Management Solution (LMS), Release 2.2. The Resource Manager Essentials (RME) 3.5 with Incremental Device Update 9 (IDU9) is also required for the CSG Service Manager.

For new installations, always install the CiscoWorks LMS bundle first. Then install the MWC components. Finally, install the CSG Service Manager.

Solaris Patches

The installation script alerts the user of missing, mandatory patches. When installing the CiscoWorks LMS bundle, warnings like the following cause the installation to abort:

WARNING: 108921-14
WARNING: Product will fail without these patches or superseding patches.

Patches for Sun Solaris are not provided by Cisco. The system administrator should ensure that the latest Sun patch cluster is installed.

Installation Procedure


Note The CSG Service Manager, Release 2.0, is a prerequisite for installing the CSG Service Manager, Release 2.2.



Step 1 Log into the server as root user.

Step 2 Extract the CSG-SM 2.2 <filename>.gz file.

Step 3 Uncompress the gzip file.

gunzip CSGMgr2_2.tar.gz

Step 4 Uncompress the tar file.

tax -xvf CSGMgr2_2.tar


Note This step creates the directory disk1.


Step 5 Change to the disk1 directory:

cd disk1

Step 6 Run the setup script:

./setup.sh

SETUPDIR=/tmp/disk1
======================================================================
Started : Sat Jan 15 12:46:32 GMT 2005
======================================================================
===============- Software Install Tool Started. -=====================
===- Welcome to the CSG Service Manager 2.2 Setup program.
======================================================================
INFO: Checking group entry casusers.....
INFO: Checking user entry casuser.....
INFO: casuser for installable packages exists.
INFO: No user added to the system.
INFO: Use admin file /tmp/cscotmp/CSCO.admin.
Daemon Management stopping. This may take a few minutes.
INFO: Waiting up to 10 minute(s) for all our daemons to stop...

INFO: OS major is 5 and OS minor is 8
INFO: OS major or minor patch version not set.


INFO: Checking for syslog server...
INFO: Using syslog facility, local1.
INFO: /tmp/disk1/packages/CSCOcsgpm/pkginfo

INFO: /tmp/disk1/info
Loading properties from info files, working...
Making a list of dependencies, working...
INFO: UPGRADE for CSG Service Manager from 2.0 to 2.2.
INFO: Checking swim jobs, please wait... INFO: No active swim jobs.

INFO: performing prerequisite: CSCOcsgpm: /tmp/disk1/packages/CSCOcsgpm/

INFO: Checking if RME 3.5 and IDU 9.0 are installed on this machine.
INFO: These are requirements for installing CSG Service Manager.2.0


INFO: RME 3.5 and IDU 9.0 are installed. Proceed with installation of the CSG Service 
Manager package.

INFO: A recommended computer model.

INFO: No Recommended disk space. Please refer to the
INFO: prerequisites chapter of the install guide.

INFO: total size (MB) required = 1
COPYOUT_INROOT_MB=0
INFO: Sufficient disk space.


INFO: CMFEnable.pl: wantSystem=1; wantNetwork=1;wantCore=0
INFO: [EnableAndDisableBundles] will SystemEnable::Enable
ProcCall: Start to enable system service...
ProcRetn: ...Done enabling system service.
INFO: [EnableAndDisableBundles] will NetworkEnable::Enable
INFO: result of CMF enable is 0
INFO: performing pkgadd -a /tmp/cscotmp/CSCO.admin -d /tmp/disk1/packages CSCOcsgpm
/opt/CSCOpx

Processing package instance <CSCOcsgpm> from </tmp/disk1/packages>

CSG Service Manager
(sparc) 2.2
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
   1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for setuid/setgid programs.

Installing CSG Service Manager as <CSCOcsgpm>

## Installing part 1 of 1.
/opt/CSCOpx/cgi-bin/csgmgr/DownloadCfgGui.pl
/opt/CSCOpx/cgi-bin/csgmgr/DownloadPreCfgGui.pl
/opt/CSCOpx/cgi-bin/csgmgr/DownloadRuleSetCfgGui.pl
/opt/CSCOpx/cgi-bin/csgmgr/batch_cfg.pl
/opt/CSCOpx/cgi-bin/csgmgr/batch_process.pl
/opt/CSCOpx/cgi-bin/csgmgr/etc/version.txt
/opt/CSCOpx/htdocs/XML/System/maintree/CsgMgr.xml
/opt/CSCOpx/htdocs/help/csgmgr/CSG_SvcMgr.pdf
/opt/CSCOpx/htdocs/help/csgmgr/CSG_SvcMgrOLHIX.hhk
/opt/CSCOpx/htdocs/help/csgmgr/CSG_SvcMgrOLHTOC.hhc
/opt/CSCOpx/htdocs/help/csgmgr/oview5.html
/opt/CSCOpx/htdocs/help/csgmgr/using.html
/opt/CSCOpx/htdocs/help/csgmgr/using27.html
/opt/CSCOpx/htdocs/help/mappingfiles/CSGMgr.hlp
/opt/CSCOpx/htdocs/help/search/CSGMgr.sch
[ verifying class <pxcsgpm> ]
## Executing postinstall script.

Installation of <CSCOcsgpm> was successful.
application CSCOcsgpm      CSG Service Manager
INFO: Configuring JRun properties...
syslog service starting.
INFO: Testing syslog: sending a msg to local0.debug...
INFO: waiting for 12 seconds for syslog to process a test message...

INFO: CMFEnable.pl: wantSystem=1; wantNetwork=1;wantCore=0
INFO: [EnableAndDisableBundles] will SystemEnable::Enable
ProcCall: Start to enable system service...
ProcRetn: ...Done enabling system service.
INFO: [EnableAndDisableBundles] will NetworkEnable::Enable
INFO:backed up /var/adm/CSCOpx/log/daemons.log to /var/adm/CSCOpx/log/daemonsbackup.log
Daemon Management 3.5 starting. Log=(syslog) /var/adm/CSCOpx/log/dmgtd.log
=================================================================
Finished: Sat Jan 15 12:53:06 GMT 2005
=================================================================
===============- Software Install Tool Completed. -==============
=================================================================
===================- Possible Errors Encountered -===================
No Errors were encountered during installation.
=====================================================================


Step 7 See the following log to investigate any problems that might have occurred with the installation:

/var/tmp/CSGMgr2.2_Install.log.<date and time stamp>


Configuring the CSG Service Manager

After successful installation, the operator must configure the CSG Service Manager for operation. Configuration is performed in these phases:

Configure Network Elements

Configure group.dat File

Configure RME

Verify CSG Service Manager Configuration

Monitor Jobs with RME Job Browser

Set Default Data

Configure Network Elements

All chassis (Catalyst 6500 switch/Cisco 7600 router) in a CSG group must be running the same CSG version, (Release 5.3, 5.4, or 5.5). The following prerequisites must be met for the RME and the CSG Service Manager to discover CSG device groups:

IP connectivity (IP address for management)

Simple Network Management Protocol (SNMP) community strings

User IDs and passwords

Understanding Device Interactions

The CSG Service Manager obtains the running configuration from a CSG device in one of two ways:

From the CSG device—The RME retrieves the latest running configuration from the device (unless no difference exists between the device configuration and the configuration in the RME archive). This method is used in the following CSG Service Manager functions:

Select Group

Delete CSG Config

CSG Activation (Map, Policy, Content Ruleset, Billing Plans, or Billing Services)

From the RME archive—The RME does not poll the CSG device. This method is used in the following CSG Service Manager functions:

Display Config

Sync Report

List and Fetch buttons in the CSG Activation folder

Syslog Notification

Enable Syslog notification in the Catalyst 6500 switch/Cisco 7600 router devices. With Syslog notification enabled, the RME is notified when a configuration change occurs and retrieves the latest running configuration from the device.

The following command line sends Syslogs to the RME server:

logging <RME_host_name>

The following command line enables Syslog notification (%SNMP-3-AUTHFAI) if the CSG Service Manager and the RME have the wrong community strings:

logging snmp-authfail

The following command line places a date and time stamp in the log file (SYSLOGS):

service timestamps log datetime

Community Strings

The following community strings must be matched at the RME:

snmp-server community <word> RO
snmp-server community <word> RW

VTY Connections

Determine the number of VTY connections to allow. For multiple simultaneous connections, use the line vty command. In the following configuration example, four simultaneous Telnet sessions are allowed:

line vty 0 4
 password mwc
 login

Configure group.dat File

The group.dat file defines one or more CSG groups and the devices that belong to each group. Each CSG group contains either two or four devices, symmetrically equipped with CSG modules.

To configure the group.dat file, complete the following steps:


Step 1 Log into the server that hosts the CSG Service Manager as a root user.

Step 2 Change to the directory of the group.dat file:

cd /opt/CSCOpx/cgi-bin/csgmgr/etc

Step 3 Use a text editor to open the group.dat file. For example:

vi group.dat

#######################################################################
# This file contains the following information:
# 1. CSG Server Group - Alpha-numeric string
# 2. CSG version - 5.3 or 5.5
# 3. Device IP or  hostname - one group can contain one or more devices
# 4. Slots containing CSG cards - per device
#
# Format is as follows (An example with 2 groups shown below)
#
# GROUP_NAME = GROUP1
# CSG_VERSION = 5.3
# DEVICE = DEVICE1
# SLOTS = 3, 4, 6
# DEVICE = DEVICE2
# SLOTS = 3, 4, 6
~text elided~

Step 4 Define one or more CSG groups in the space immediately following the commented section of the file. For example:

GROUP_NAME = server_09
CSG_VERSION = 5.3
DEVICE = cat1of4
SLOTS = 4, 5, 6, 7, 8
DEVICE = cat2of4
SLOTS = 4, 5, 6, 7, 8
DEVICE = cat3of4
SLOTS = 4, 5, 6, 7, 8
DEVICE = cat4of4
SLOTS = 4, 5, 6, 7, 8


NoteThe first device in a group is considered the master device.

The value entered for DEVICE can be either the device name or the IP address of the device.

The values entered for SLOTS must be the same for each device in a group.


Step 5 Save and exit the file.

Step 6 Make a backup copy of the group.dat file and store it in a secure location.


Note If you must reinstall the CSG Service Manager for any reason or install a later version, the group.dat file in the /opt/CSCOpx/cgi-bin/csgmgr/etc directory is overwritten.



Configure RME

You must configure the RME to operate with the CSG Service Manager. The following tasks are required:

Update Downloader Properties File

Add Device to RME Inventory

Configure Archive Purging

Define Message Filter for Subordinate Devices

Update Downloader Properties File

A CSG device group contains either two or four CSG devices. In sites where four CSG devices are in a CSG group, the RME must be configured to accommodate the fourth device in its downloader properties file. This task is not required for CSG groups with only two devices.

To change the downloader properties file, complete the following steps:


Step 1 Log into the server as a root user.

Step 2 Change to the downloader directory:

cd /opt/CSCOpx/www/classpath/com/cisco/nm/config/cjm/downloader

Step 3 Use a text editor to open the downloader.properties file. For example:

vi downloader.properties

Step 4 Locate the following line in the downloader.properties file:

CDLNumOfThreads=3 

Step 5 Change the number of threads to 4:

CDLNumOfThreads=4 

Step 6 Save and exit the file.

Step 7 Stop and start CiscoWorks processes:

/etc/init.d/dmgtd stop
/etc/init.d/dmgtd start


Add Device to RME Inventory

Add each of the Catalyst 6500 switch/Cisco 7600 router devices that are in a CSG group to the RME inventory.


Note The group.dat file displays the devices that belong to a CSG group.


To add a device to the RME inventory, complete the following steps:


Step 1 Access the CiscoWorks desktop by pointing your browser the following address:

http://<server_hostname>:1741

Step 2 From the CiscoWorks desktop (left panel), select Resource Manager Essentials > Administration > Inventory > Add Devices.

a. In the dialog window, enter the device in the Device Name field, complete the other fields (if required), and click Next.

b. In the next dialog window, enter the community strings, usernames, and passwords used in Telnet Login mode. Click Next.

c. In the next dialog window, enter the usernames and passwords used in Telnet Enable mode. Then click Finish.

The device status displays in the Add/Import Status Summary window.

Step 3 If the device status is Pending, allow the server to process the request. Click the Update button periodically to refresh the status display. Eventually, the device moves to the Managed state.

Step 4 To add another device to RME inventory, repeat these steps from Step 2.


Configure Archive Purging

To improve processing utilization, delete change records older than two days and schedule a job to weekly purge change records from the archive.


Step 1 From the CiscoWorks desktop (left panel), select Resource Manager Essentials > Administration > Configuration Management > General Setup.

Step 2 In the Archive Setup tab, set the Archive Purging Policy as follows:

a. Select the Older than check box and set it to 7 days.

b. Select the Maximum version to keep check box and set it to 5.

c. Select the Don't Purge Labelled Files check box.

d. Click Apply.

Step 3 In the Change Probe Setup tab, set up the following:

a. Select the Listen to Syslog Messages check box.

b. Select the Config Retrieval Schedule check box and set it to Every one weeks.

c. Click Apply.

Step 4 From the CiscoWorks desktop (left panel), select Resource Manager Essentials > Administration > Change Audit > Delete Change History.

Step 5 In the Change Audit - Filter Options window, do the following:

a. In the Views list, select All Devices. The devices appear in the Devices list.

b. In the Devices list, select the devices in the CSG group and click Add. The devices are added to the Selected Devices list.

c. Click Next.

Step 6 In the Change Audit - Delete Change History window, do the following:

a. From the Application pull-down list box, select NetConfig.

b. Click the Older than radio button and enter 2 in the Days text box.

c. Click Next.

Step 7 In the Change Audit - Schedule Jobs window, do the following:

a. Select Immediate from the Schedule Type pull-down list.

b. Click Finish.

This action creates a job to immediately delete all change records older than 2 days on the devices in the CSG group.

Step 8 Schedule a job to purge the change records weekly as follows:

a. From the CiscoWorks desktop (left panel), select Resource Manager Essentials > Administration > Change Audit > Delete Change History.

b. In the Change Audit - Filter Options window, select all devices in the CSG group and click Next.

c. In the Change Audit - Delete Change History window, click the Last Week radio button and click Next.

d. In the Change Audit - Schedule Jobs window, select Weekly from the Schedule Type pull-down list, set a Start Date and Start Time, then click Finish.

Step 9 To verify the scheduled job, select Server Configuration > Administration > Job Management from the CiscoWorks desktop (left panel). The name of the scheduled job appears in a list.


Define Message Filter for Subordinate Devices

The RME is configured to listen to Syslog messages that indicate a configuration change has been made to a device. However, configuration Syslogs are required only for the master device in a CSG group. You must define a message filter to suppress configuration Syslogs on the subordinate devices.


Step 1 From the CiscoWorks desktop (left panel), select Resource Manager Essentials > Administration > Syslog Analysis > Define Message Filter.

Step 2 In the Define Message Filter window, enter a name in the Filter Name text box. For example:

Suppress Config Syslogs on Subordinates Message Filter

Step 3 Select the Enable Filter check box.

Step 4 Select the Syslog Message Type of CONFIG_I.

Step 5 Click Add to add the CONFIG_I Syslog to the Filtered Messages list.

Step 6 Click the Advanced button. The Define Message Filter - Advanced window appears.

Step 7 In the Device Names text box, enter a comma-separated list of the subordinate devices. For example:

cat6513b,cat6513c,cat6513d


Caution Do not enter the master device in the Device Names text box!

Step 8 Click OK.

Step 9 In the Define Message Filter window, click Finish. The following message displays:

The message filter has been successfully added. However it might take up to 5 minutes to 
come into effect.

Step 10 You can verify that the message filter has been added by reselecting Resource Manager Essentials > Administration > Syslog Analysis > Define Message Filter. A list of defined message filters displays.


Verify CSG Service Manager Configuration

To verify that all configuration steps were successful, complete the following steps:


Step 1 Access the CiscoWorks desktop by pointing your browser the following address:

http://<server_hostname>:1741

Step 2 From the CiscoWorks desktop (left panel), select CSG Service Manager > Select Group.

The Select Group window displays the configured CSG devices with Status of Pending.

Step 3 Periodically click the Update button until all devices in the CSG group have been successfully selected.


Monitor Jobs with RME Job Browser

The CSG Service Manager can now be used to configure service activation features on the CSGs.

Sometimes you will perform multiple jobs in quick succession, entering data, clicking Finish, then using the Back button to begin a new job before the previous job completes. These jobs are queued in the RME for processing.

To monitor the status of the jobs you have submitted, complete the following steps:


Step 1 Access the CiscoWorks desktop by pointing your browser the following address:

http://<server_hostname>:1741

Step 2 From the CiscoWorks desktop (left panel), select Resource Manager Essentials > Configuration Management > NetConfig.

The Network Configuration window appears.

Step 3 From the Jobs menu, select Job Browser.

The Job Browser window displays a queue of current jobs.

Step 4 If the Run Status of a job indicates Failed or Job failed: Download, select the job and click Job Details.

The Job Details window appears.

Step 5 In the Job Details window, expand the Device Details folder to display details of the job failure.


Note If a partial failure occurs (for example, a policy configlet is sent to three devices but fails to update the fourth device), you can either roll back the changes by deleting the configurations in the three devices or retry the failed job on the fourth device.


Step 6 To retry a failed job, click the Retry Job button. In the resulting pop-up, click Yes to continue.

Step 7 In the Retry Job window, perform the following tasks:

a. Select the device and click Next.

b. In the Apply Templates panel, click Next.

c. In the Job Properties panel, click Next.

d. In the Work Order panel, click Finish.

e. A dialog box indicates that the job was successfully created/updated. Click OK.

Step 8 In the Job Browser window, verify that the job starts. Monitor the job until it completes.


Set Default Data

You can set the default values for the CSG Service Manager debug level and the maximum number of log files that are archived.

Debug Levels

Three debug levels are available. Debug levels 1 and 2 allow basic application messages to be displayed. You can set the debug level to 3 to observe the detailed application messages that are desired when troubleshooting anomalies.


Caution Setting the debug level to 3 can affect the performance of the CSG Service Manager. When using debug level 3 to troubleshoot problems, be sure to reset the debug level to 1 or 2 when complete.

The CSG Service Manager debug level is set by the value of the Debug_Level property in the /opt/CSCOpx/cgi-bin/csgmgr/etc/default.dat file.

Number of Log Files

The CSG Service Manager provides a log file in the /var/adm/CSCOpx/log directory. The log file name is csgMgrCgi.log. When the log file size reaches 2 MB, the CSG Service Manager automatically makes a backup of the file in the same directory. A numerical identifier is appended to the file name. For example:

csgMgrCgi.log_1

You can set the maximum number of log files to keep by specifying a value for the MAX_NO_OF_LOG_FILES property in the /opt/CSCOpx/cgi-bin/csgmgr/etc/default.dat file.

To set default values for debug level and maximum number of log files, complete the following steps:


Step 1 Log into the server as a root user.

Step 2 Change directories.

cd /opt/CSCOpx/cgi-bin/csgmgr/etc

Step 3 Use a text editor to open the default.dat file.

Step 4 Modify the Debug_Level and MAX_NO_OF_LOG_FILES properties as required. For example:

Debug_Level = 1
MAX_NO_OF_LOG_FILES = 5

Step 5 Save and exit the file.


Known and Resolved Problems

Table 4 describes problems known to exist in this release.


Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)


Table 4 Known Problems in CSG Service Manager Release 2.2

Bug ID
Summary
Explanation

CSCeg68135

Launching Batch Mode window multiple times clears data

If the CSG SM 2.2 Batch Mode window is launched multiple times, any data pasted into the original window is erased and cannot be recovered.

To work around this problem, use only one Batch Mode window.

CSCeg73809

Marker for CLI syntax errors is incorrectly positioned in Batch Mode window

The Batch Mode window sometimes places the CLI syntax error marker incorrectly, and the user is unable to determine the location of the error.

Note The position of the marker is dependent on the font used.

To work around this problem, launch the RME Netconfig utility and select the details of the Job Number with the failure to determine the correct placement of the error marker.

CSCeh10022

RME IDU 11 breaks CSG SM call to cwconfig

If RME IDU 9, 10, or 11 is installed after CSG Service Manager installation, the Select Group function returns an error indicating that the device is not managed in the RME or that the password is incorrect.

Workaround:

Log in as root user and do the following:

cd /opt/CSCOpx/www/classpath/com/cisco/nm/config/archive

Back up the CfgArchiveImpl.class and Validator.class files in the archive directory. Then do the following:

cp /opt/CSCOpx/cgi-bin/csgmgr/tmp/Validator.class 
Validator.class

cp /opt/CSCOpx/cgi-bin/csgmgr/tmp/CfgArchiveImpl.class
CfgArchiveImpl.class

chmod 750 Validator.class
chmod 750 CfgArchiveImpl.class

chown casuser:casusers Validator.class
chown casuser:casusers CfgArchiveImpl.class

CSCeh10061

CSG not recognized in slot 1

When the Sup720 module is installed in slot 5 or 6 of the Catalyst 6500 switch/Cisco 7600 router, the CSG Service Manager does not recognize a CSG module that is installed in slot 1.

Workaround: None.


Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html