Guest

Cisco Mobile Wireless Center for Cisco Mobile Exchange

Release Notes for Mobile Wireless Center for Cisco Mobile Exchange 4.1.2

Hierarchical Navigation

Downloads

Table Of Contents

Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange, Release 4.1.2

Contents

Introduction

What's New in This Release

Prerequisites for Installing the Service Managers

Minimum Server Platform Requirements

Client Requirements

Supported Browsers

Sun Patches and Packages Requirements

Determining the Software Versions Currently on Your System

Installing the MWC for Cisco Mobile Exchange

Installation Sequence

Installing the LMS

Installing the CiscoView Package

Installing RME Updates

Uninstalling the Mobile Wireless Fault Mediator

Installing the Service Managers

Installing the Mobile Wireless Transport Manager 6.0

Installing the Mobile Wireless Transport Manager 6.0.1 Patch

Configuring the Mobile Wireless Transport Manager

Backing Up and Restoring Service Manager Data

Types of Data Backed Up

Backing Up Existing Data

Restoring Backup Data

Restoring Data for All MWC for Cisco Mobile Exchange Applications

Restoring Data for an Individual Service Manager

Example Output from the Restore Tool

Reinstalling the Service Managers

Hostname Changes

Uninstalling Release 4.1.2

Uninstalling a Service Manager

Uninstalling the Service Manager Core

Limitations and Restrictions

Software Version Considerations

Configuring Two Device Groups Simultaneously

Synchronizing Device Inventories

Unsupported Special Characters in Field Names

Refreshing the Config Viewer Window

MWAM Preparation Notes

SAMI Preparation Notes

Supported Device Matrix

Device Preparation Notes

Resource Manager Essentials Preparation Notes

Assigning Adhoc Tasks to Users

Managing Device Inventory

Adding Devices

Managing Inventory Jobs

Tuning RME Configuration Management

Configuring Transport Settings

Enabling Periodic Polling and Collection

Purging Configuration Archives

Configuring RME to Run Parallel Jobs

Configuring RCP for SWIM

Configuring Purge Policies

Closing the Batch Window

Help System Files

Release 4.1.1 Content

Release 4.1.2 Content

Resolved Caveats

Open Caveats and Workarounds

Documentation Support

Product Documentation

Related Documentation

Additional Information Online

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange, Release 4.1.2

Revised: August 2007, OL-13307-01

The Mobile Wireless Center (MWC) for the Cisco Mobile Exchange is a suite of applications that run on the Solaris 2.9 platform. Each of these applications facilitates device management of a particular kind of device in the Cisco Mobile Exchange network, including service activation or deactivation.

These release notes contain important information for Release 4.1.2 of the MWC for Cisco Mobile Exchange.

Contents

This document contains the following sections:

•Introduction

•What's New in This Release

•Prerequisites for Installing the Service Managers

•Installing the MWC for Cisco Mobile Exchange

•Backing Up and Restoring Service Manager Data

•Reinstalling the Service Managers

•Hostname Changes

•Uninstalling Release 4.1.2

•Limitations and Restrictions

•MWAM Preparation Notes

•SAMI Preparation Notes

•Device Preparation Notes

•Resource Manager Essentials Preparation Notes

•Resolved Caveats

•Open Caveats and Workarounds

•Supported Device Matrix

•Documentation Support

•Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

The Mobile Wireless Center for Cisco Mobile Exchange is a suite of powerful element-management tools that provide fault, configuration, and troubleshooting capabilities to mobile operators transitioning their wireless service delivery networks from second-generation (2G) circuit-based traffic to 2.5G- and 3G-based services. MWC for Cisco Mobile Exchange applications complement the CiscoWorks LAN Management Solution (LMS) to provide end-to-end management of the Cisco Mobile Exchange.

Table 1 shows the MWC for Cisco Mobile Exchange applications that are currently available.

Table 1 MWC for Cisco Mobile Exchange Applications

Application
Description

CiscoWorks LAN Management Solution (LMS) 2.6

A prerequisite suite of applications. The LMS includes:

•Common Services 3.0.5 with CiscoView 6.1.5

•Resource Manager Essentials (RME) 4.0.5

Note The LMS 2.6 also includes Internet Performance Monitor (IPM), Device Fault Manager, and Campus Manager, but the MWC for Cisco Mobile Exchange does not require these applications.

Cisco Gateway GPRS Support Node Service Manager (GGSN SM)

A service manager application for managing inventory, configuring service-activation features, and doing basic troubleshooting of Gateway GPRS Support Node devices.

Cisco Home Agent Service Manager (HA SM)

A service manager application for managing inventory, configuring service-activation features, and doing basic troubleshooting of Home Agent devices.

Cisco Content Services Gateway Service Manager (CSG SM)

A service manager application for managing inventory, configuring service-activation features, and doing basic troubleshooting of Content Services Gateway devices.

Cisco Packet Data Serving Node Service Manager (PDSN SM)

A service manager application for managing inventory, configuring service-activation features, and doing basic troubleshooting of Packet Data Serving Node devices.

Cisco Mobile Wireless Transport Manager (MWTM) 6.0.1

Provides alarm and trap support for these mobile wireless devices: GGSN, CSG, and CSG2.


The service managers provide service-activation features for a specific mobile wireless application (for instance, GGSN or HA). As shown in Figure 1, each service manager relies on an underlying service-manager core, which is dependent on the underlying LMS framework. The MTWM supports the service managers on the host platform.

Figure 1 Service Manager Architecture

The service-manager core uses the Device Credentials Repository (DCR) of Cisco Common Services (CS) and Resource Manager Essentials (RME) functions to provide configuration retrieval, download operations, and data inventory for each service manager.

Each component shown in Figure 1 is installed separately on the server platform. The service-manager installation script checks for the presence of the service manager core module and the LMS bundle of applications.

The PDSN, HA, and GGSN devices can reside on a Multiprocessor WAN Application Module (MWAM). The MWAM card has five processors, so one MWAM card can accommodate five devices. All devices on a single MWAM card must be of the same type. (For example, you can have five PDSNs on one MWAM card, but not three PDSNs and two HAs.) Important restrictions exist for MWAMs. See MWAM Preparation Notes, for more information.

The CSG device can reside on the following cards:

•A CSG card—CSG 7.5 and earlier releases

•Service and Application Module for IP (SAMI) card—CSG2, Release 1.0

Note To install and configure the SAMI card, see the Service and Application Module for IP User Guide:

http://www.cisco.com/en/US/products/hw/modules/ps5510/products_installation_and_configuration_
guide_book09186a0080875d19.html

Also see SAMI Preparation Notes.

What's New in This Release

Patch Release
What's New

4.1.1

Batch mode scheduling feature (see Batch Mode Scheduling).

4.1.2 (this release)

New version of the CSG on the SAMI card (CSG2). See the Release Notes for the Content Services Gateway Service Manager 4.1.2.


Prerequisites for Installing the Service Managers

This section describes the following prerequisites for installing the MWC for Cisco Mobile Exchange:

•Minimum Server Platform Requirements

•Client Requirements

•Supported Browsers

•Sun Patches and Packages Requirements

•Determining the Software Versions Currently on Your System

Minimum Server Platform Requirements

Table 2 describes the minimum server platform requirements to support the LMS 2.6 and MWC for Cisco Mobile Exchange applications.

Table 2 Minimum Server Platform Requirements

Item
Minimum Requirement

System hardware

Dual processor UltraSPARC IIIi

UltraSPARC III Cu Processor

2 @ 1.015 GHz

External Cache per processor

8 MB

Memory

4 GB (4 @ 1-GB DIMMS)

Disk Drive

2 @ 36 GB

Swap space

8 GB


Caution Allocate at least 10 GB for the /var partition. This amount of space will accommodate large backup files, making it possible to purge the archives less frequently.

For information on diagnosing problems with the server, refer to:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_chapter
09186a008022f962.html.

Client Requirements

Refer to the LMS 2.6 Client and Server requirements at:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/products_quick_start
09186a008073eddf.html#wp1027299

Supported Browsers

Refer to the LMS 2.6 browser requirements at:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/products_quick_start
09186a008073eddf.html#wp1027494

Sun Patches and Packages Requirements

Refer to the LMS 2.6 requirements for Sun patches and packages at:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/products_quick_start
09186a008073eddf.html#wp1027585

Determining the Software Versions Currently on Your System

To determine the version of packages that are installed on your CiscoWorks server:

Step 1 On the CiscoWorks Homepage, choose Common Services > Software Center > Software Update. The Software Updates page appears.

Step 2 Check the software version listed in the Version field of the Products Installed table.

Installing the MWC for Cisco Mobile Exchange

This section covers the following topics:

•Installation Sequence

•Installing the LMS

•Installing the CiscoView Package

•Uninstalling the Mobile Wireless Fault Mediator

•Installing the Service Managers

•Installing the Mobile Wireless Transport Manager 6.0

•Installing the Mobile Wireless Transport Manager 6.0.1 Patch

•Configuring the Mobile Wireless Transport Manager

Installation Sequence

Installation Sequence
Installation Instructions

1. CiscoWorks LMS bundle

Installing the LMS

2. CiscoView device package for SAMI card1

Installing the CiscoView Package

3. RME updates for SAMI card

Installing RME Updates

4. MWFM (uninstall)

Uninstalling the Mobile Wireless Fault Mediator

5. Service managers

Installing the Service Managers

6. MWTM 6.0

Installing the Mobile Wireless Transport Manager 6.0

7. MWTM 6.0.1 patch

Installing the Mobile Wireless Transport Manager 6.0.1 Patch

8. MWTM configuration

Configuring the Mobile Wireless Transport Manager

1 Cat6000IOS Device Package, Version 27.0.


Installing the LMS

To install the MWC for Cisco Mobile Exchange solution, you must first install the applications of the LMS 2.6 bundle. Install each LMS 2.6 application in the correct order. Click this link for the order of installation and instructions for installing each LMS application:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/products_quick_start
09186a008073eddf.html#wp1028612

In addition to the LMS applications that are required for the MWC for Cisco Mobile Exchange, the LMS Release 2.6 includes the Internet Performance Monitor (IPM), Device Fault Manager, and Campus Manager applications. These applications do not interact with the MWC for Cisco Mobile Exchange.

Caution After installing the LMS 2.6 applications, be sure to install LMS 2.6 updates, if any. These updates ensure that you will be able to support the latest new devices such as the SAMI card. Get the latest device updates from http://www.cisco.com/kobayashi/sw-center/cw2000/lan-planner.shtml.

Installing the CiscoView Package

The CiscoView package enables the CiscoView application to recognize the SAMI card. To install the CiscoView package (Cat6000IOS Device Package, Version 27.0), follow these instructions:

http://www.cisco.com/en/US/products/sw/cscowork/ps4565/products_user_guide_chapter09186a0080842ed0.html#wp1044664

Installing RME Updates

The RME updates listed in this section enable the RME application to recognize the SAMI card (WS-SVC-SAMI-BB). The required software package is Rtr7000.RME40.v7-0.zip. This package is available at:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme

The installation instructions are in this Readme document:

http://ftp-sj.cisco.com/cisco/cw2000/patches/rme/Rtr7000.RME40.v7-0.readme.pdf

The Readme document lists the following packages as prerequisites for RME 4.0.5:

•SharedInventoryRouter.RME40.v1-5-1.zip

•SharedInventoryCatSwitch.RME40.v1-7-1.zip

•SharedSwimIOS.RME40.v1-11-1.zip

•LibInventory.RME40.v1-11-1.zip

•LibSwim.RME40.v1-8-1.zip

•LibCommon.RME40.v1-3-1.zip

Note Install the prerequisite packages before installing the Rtr7000.RME40.v7-0.zip package.

Uninstalling the Mobile Wireless Fault Mediator

The MWC for Cisco Mobile Exchange 4.1.2 eliminates the requirement for the Mobile Wireless Fault Mediator (MWFM). Instead, trap and fault management for this solution is provided by the MWTM 6.0.1 patch (see Installing the Mobile Wireless Transport Manager 6.0.1 Patch).

To uninstall the MWFM from your server:

Step 1 From the root directory, enter:

cd /opt/CSCOpx/bin

Step 2 From the command line, run the uninstall script by entering:

./uninstall.sh

The script prompts you with a list of software that is installed on the host machine.

Step 3 Select the choice that corresponds to the Mobile Wireless Fault Mediator.

Step 4 Confirm the choice.

A confirmation message appears after a successful uninstallation.

Note The uninstall script shuts down and restarts the CiscoWorks processes to unregister the MWFM. Refer to the /var/adm/CSCOpx/log/dmgtd.log file for the status of CiscoWorks process startup.

Installing the Service Managers

To install the service managers, follow the installation sequence listed in Table 3.

Table 3 Service Manager Installation Sequence and Steps

Service Manager Installation Sequence
Installation Steps

1. Install 4.1 service-manager core. (If 4.1 is already installed, skip to Step 3.)

2. Install 4.1 service manager(s).

3. Install 4.1.1 service-manager core. (If 4.1.1 is already installed, skip to Step 5.)

4. Install 4.1.1 service manager(s).

5. Install 4.1.2 service-manager core.

6. Install 4.1.2 service manager(s).

1. Download the .zip file from:

http://www.cisco.com/cgi-bin/tablebuild.pl/mwc-cmx

2. Extract the files to a temporary location.

3. Change to the /disk1 directory.

4. Run the setup.sh file.

5. Respond to the interactive prompts until the installation program ends. A confirmation message appears after a successful installation.

Note If an error occurs during installation, check the most recent installation log file in the /var/tmp directory to determine the cause of the error.


Installing the Mobile Wireless Transport Manager 6.0

To install MWTM 6.0 on the server:

Step 1 Download the installation .zip file from:

http://www.cisco.com/cgi-bin/tablebuild.pl/MWTM-3D

Step 2 Extract the files to a temporary directory.

Step 3 Change to the directory containing the 6.0 setup script. For example:

cd /temp/MWTM60/solaris

Step 4 Run the setup script. For example:

./setup.sh

Step 5 Respond to system prompts and choose the appropriate options. For detailed instructions, see:

http://www.cisco.com/en/US/products/ps6472/products_installation_guide_book09186a00807f45b6.
html

Installing the Mobile Wireless Transport Manager 6.0.1 Patch

Step 1 Download the installation .zip file from:

http://www.cisco.com/cgi-bin/tablebuild.pl/MWTM-3D

Step 2 Extract the files to a temporary directory.

Step 3 Change to the directory containing the 6.0.1 setup script. For example:

cd /temp/MWTM60/solaris

Step 4 Run the setup script for the 6.0.1 patch:

./setup.sh

Step 5 Respond to system prompts and choose the appropriate options.

Step 6 (Optional) Enable the Secure Sockets Layer (SSL) to communicate between the MWTM server and the MWTM client. For detailed instructions, see:

http://www.cisco.com/en/US/products/ps6472/products_user_guide_chapter09186a00807f45f6.html#wp1191016

Configuring the Mobile Wireless Transport Manager

Now that all of the required components have been installed (see Installation Sequence), you must configure the MWTM to:

•Manage CSG, CSG2, and GGSN network types

•Integrate the CiscoWorks server with the MWTM server

Tip To display the syntax of any MWTM command listed in this procedure, enter:

./mwtm help command

For example, to display the syntax of the mwtm manage command, enter:

./mwtm help manage

To configure the MWTM:

Step 1 Enable the MWTM to manage traps and alarms for CSG, CSG2, and GGSN devices by adding the following statements to the IOS configuration for these devices: 

snmp-server community <SNMP_COMMUNITY_STRING> RO 1

snmp-server enable traps

snmp-server host <SNMP_SERVER_HOST_IP_ADDRESS> version 2c <SNMP_COMMUNITY_STRING>

Step 2 Log in to the MWTM server as the root user.

Step 3 Change to the /opt/CSCOsgm/bin directory:

cd /opt/CSCOsgm/bin

Step 4 Determine the currently enabled network type:

./mwtm manage status

Step 5 If the status output shows that ITP and RAN-O are enabled, then disable these network types:

./mwtm manage itp disable

./mwtm manage ran-o disable

Note Ignore system prompts to restart the MWTM server. You will perform a server restart in Step 8.

Step 6 Enable the network types that you want the MWTM to manage. For example:

./mwtm manage csg enable

./mwtm manage csg2 enable

./mwtm manage ggsn enable

Note Ignore system prompts to restart the MWTM server. You will perform a server restart in Step 8.

Step 7 Integrate the CiscoWorks server with the MWTM by running the mwtm cwsetup command. This command will prompt you to enter the CiscoWorks server name and port numbers. For example: 

# ./mwtm cwsetup


Integrate CiscoWorks with MWTM ? [y] y


Enter server name for CiscoWorks Server: [ems-svr199] ems-svr200


Enter port number for CiscoWorks Web Server on ems-svr200: [1741] 1741


Enter secure port number for CiscoWorks Web Server on ems-svr200: [443] 443

Step 8 Restart the MWTM server:

./mwtm restart

Step 9 On the CiscoWorks server, create a CiscoWorks export file of the nodes that you want the MWTM to manage. You must specify CSV file format. See the User Guide for CiscoWorks Common Services 3.0.5:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_chapter09186a00806feeb5.html#wp1143124

Step 10 Transfer the CiscoWorks export file to a temporary directory on the MWTM server. For example, use File Transfer Protocol (FTP) to put the export file in /tmp/export.txt on the MWTM server.

Step 11 On the MWTM server, run the mwtm importcw command on the export file. For example:

./mwtm importcw /tmp/export.txt

This command adds the SNMP configurations of the imported nodes to the MWTM and prompts you to discover the nodes.

Step 12 (Optional) To add or modify the SNMP configurations for these nodes, use the mwtm snmpsetup command.

Step 13 (Optional) To verify the SNMP configurations you entered, use the mwtm showsnmpcomm command.

Note For complete details about setting up your MWTM server, see the User Guide for the Cisco Mobile Wireless Transport Manager 6.0, available at Cisco.com.

Backing Up and Restoring Service Manager Data

Backing up and restoring information makes use of the Common Services (CS) backup tool. This tool backs up and restores CS and all applications registered with it. With this release, you also can back up and restore service manager-specific data.

Backup data contains all the information for service managers registered with CS 3.0 and above in the backup folder.

Before executing a backup, you must manually stop the CS management daemon dmgtd and then restart it once the procedure is complete. The instructions that follow include these steps.

This section includes these topics:

•Types of Data Backed Up

•Backing Up Existing Data

•Restoring Backup Data

Types of Data Backed Up

As in CS, the backup tool backs up the followings types of data:

•CiscoWorks user information

•Single Sign-on configuration

•Device and Credential Repository (DCR) configuration

•Peer Certificates and Self-Signed certificates

•Peer Server Account information

•Login Module settings

•Software Center map files

•License data

•Core Client Registry

•System Identity Account configuration

•Cisco.com user configurations

•Proxy user configurations

•Database (Jobs and Resources data, DCR data, Groups data, and other data stored in the database)

Backing Up Existing Data

To back up existing data:

Step 1 Log in as the root user.

Step 2 Stop the dmgtd process:

/etc/init.d/dmgtd stop

Step 3 Back up the existing data. For example:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl backupdir

Follow the instructions that the backup script provides.

Step 4 Restart the dmgtd process:

/etc/init.d/dmgtd start

Restoring Backup Data

You have two options for restoring backup data:

•You can restore all MWC for Cisco Mobile Exchange applications.

•You can restore one service manager at a time.

Before executing a restore, you must manually stop dmgtd and then restart it once the procedure ends. The instructions that follow include this step.

Restoring Data for All MWC for Cisco Mobile Exchange Applications

Note Previous releases provided this command to restore data:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d

This command restores all backed-up data, including data for RME, CS, and Campus. The resulting restore took close to an hour, and therefore was not a preferred course of action for many users. The following procedure restores data only from the MWC for Cisco Mobile Exchange service managers.

To restore data for all MWC for Cisco Mobile Exchange applications:

Step 1 Log in as the root user.

Step 2 Stop the dmgtd process:

/etc/init.d/dmgtd stop

Step 3 Run the restore backup script:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl backup_dir

Step 4 Restart the dmgtd process:

/etc/init.d/dmgtd start

Restoring Data for an Individual Service Manager

To restore data for an individual service manager:

Step 1 Log in as the root user.

Step 2 Stop the dmgtd process:

/etc/init.d/dmgtd stop

Step 3 Run the restore backup script: 

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/cmx/ServiceManager/restorebackup.pl -d /backup_dir/0

Step 4 Restart the dmgtd process:

/etc/init.d/dmgtd start

Example Output from the Restore Tool

The following example shows output from the Restore Tool for one of the MWC for Cisco Mobile Exchange service managers. 

Restore started at : 2006/02/23 16:28:08 

Please see '/var/adm/CSCOpx/log/restorebackup.log' for status. 



     OS of the backup archive ................ : Unix 

     Generation of data to be restored .............. : 0 

     Backup taken from............................... : /opt/CSCOpx/backup 

     Backup archive data taken from.................. : CDONE 3.0 


     Directory where Common Services is installed.... : /opt/CSCOpx 

     Temp folder for this restore program............ : /opt/CSCOpx/tempBackupData 

     Applications installed on this machine .... : [Common Services][Resource Manager 
Essentials][Content Services Gateway Service Manager][Packet Data Service Node Service 
Manager][Home Agent Service Manager][Gateway GPRS Support Node Service Manager] 

     Applications you are going to restore ........ : [Packet Data Service Node Service 
Manager] 



              Do you want to continue the Restore operation  (y-continue or n-quit, y/n)?y 


     Applications to be restored are............ : Packet Data Service Node Service 
Manager 


     Available disk space in NMSROOT............ : 28733296 Kb 

     Required disk space in NMSROOT............. : 7 Kb 

     (The temp and NMSROOT are on same device, therefore this required disk space includes 
temp space) 


  Copying the backup files to the temporary location [/opt/CSCOpx/tempBackupData] 


  preRestore of [Packet Data Service Node Service Manager] has started. 

  preRestore of [Packet Data Service Node Service Manager] has completed. 


  doRestore of [Packet Data Service Node Service Manager] has started. 

  doRestore of [Packet Data Service Node Service Manager] has completed. 


  postRestore of [Packet Data Service Node Service Manager] has started. 

  postRestore of [Packet Data Service Node Service Manager] has completed. 


Restored successfully

Reinstalling the Service Managers

You may need to reinstall the software if an installation attempt is interrupted or fails. If reinstallation is required, repeat the procedures in Installing the Service Managers.

Hostname Changes

If you must change the IP address or hostname of the server after installation, you must also modify the hostname in certain files. See this location for more information:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_chapter
09186a008022f962.html#wp1078582

Uninstalling Release 4.1.2

If, for any reason, you must remove the 4.1.2 patch, uninstall the software in reverse order from installation.

The release notes for each service manager provide specific uninstallation instructions for that service manager. You can find links to the online version of each service manager's release notes in Documentation Support.

This section provides information on:

•Uninstalling a Service Manager

•Uninstalling the Service Manager Core

Uninstalling a Service Manager

The release notes for each service manager provide specific uninstallation instructions for that service manager. You can find links to the online version of each service manager's release notes in Documentation Support.

In general, the uninstallation procedure is:

Step 1 From the root directory, enter:

cd /opt/CSCOpx/bin

Step 2 From the command line, run the uninstall script by entering:

./uninstall.sh

The script prompts you with a list of software that is installed on the host machine.

Step 3 Select the choice that corresponds to the service manager that you want to uninstall.

Step 4 Confirm the choice.

A confirmation message appears after a successful uninstallation.

Uninstalling the Service Manager Core

To uninstall the service-manager core module:

Step 1 From the root directory, enter:

cd /opt/CSCOpx/bin

Step 2 From the command line, run the uninstall script by entering:

./uninstall.sh

The script prompts you with a list of software that is installed on the host machine.

Step 3 Select the choice that corresponds to the service-manager core package.

Step 4 Follow the interactive prompts until the program ends.

A confirmation message appears after a successful uninstallation.

Limitations and Restrictions

This section provides information on:

•Software Version Considerations

•Configuring Two Device Groups Simultaneously

•Synchronizing Device Inventories

•Unsupported Special Characters in Field Names

•Refreshing the Config Viewer Window

•Closing the Batch Window

•Help System Files

Software Version Considerations

Cisco does not support mixed versions of software on the same system. That is, if you upgrade one service manager to Release 4.1.2, you must upgrade all service managers to the same version.

Configuring Two Device Groups Simultaneously

You cannot perform operations on two device groups at the same time within the same login session. If you would like to perform operations on two device groups simultaneously, open two Internet Explorer browser sessions and log in to CiscoWorks in each window. Access the service manager from each browser window and perform the simultaneous operations on the separate groups.

Note Netscape and Mozilla do not allow simultaneous device group configuration. You must use Internet Explorer to perform this operation.

Synchronizing Device Inventories

When you make device inventory changes through the Common Services DCR (Common Services > Device and Credentials > Device Management), the service managers do not automatically update your changes. To synchronize a service manager with any DCR changes that you make, click Get Latest from DCR on the List Devices dialog box of the service manager (Inventory > Group Mgmt > List Devices). Also, recreate any service-manager device groups that consist of devices that have been changed through the Common Services DCR.

Unsupported Special Characters in Field Names

The service managers do not support the use of the exclamation point (!), comma (,), colon (:), semicolon (;), backslash (\), and question mark (?) in field names. Using these unsupported characters can cause configuration failures.

Refreshing the Config Viewer Window

Operators sometimes use the Service Manager Config Viewer window to verify that service-activation operations generate configuration changes. The F5 function key normally activates a refresh sequence, causing the browser to retrieve the latest changes from the server. However, this function key does not work for the Config Viewer window. To view the latest configuration changes, relaunch the Config Viewer window by choosing Service Manager > Display Config and clicking Display Config.

MWAM Preparation Notes

The MWAM provides the equivalent of five mobile wireless applications (for example, five GGSNs) on one module.

For optimal performance:

•Enter MWAM processors into the Common Services DCR with routable IP addresses.

•Ensure that the ROM Monitor version is at least 12.2(11)YS2.

•Ensure that the Maintenance Partition (MP) is at least 3.1(2).

•Application Partition versions will vary depending on the application that is running on the MWAM.

•Ensure that approximately 25 MB is available on the Supervisor bootflash disk of the Catalyst 6500/Cisco 7600 chassis.

•Set up logging directly to the RME (not through the Supervisor).

•Set up the SNMP server host to be the MWTM server.

•Define the source subinterface to the MWAM (cdp source-interface GigabitEthernet0/0.xxx).

•Set up aaa new-model to enable user access to MWAM processors.

•Set up virtual terminal (VTY) access (line vty) by using the AAA model.

For more information about the MWAM, go to:

http://www.cisco.com/en/US/products/hw/modules/ps5510/products_user_guide_book09186a0080551cdd.html

SAMI Preparation Notes

The SAMI card provides the platform for the CSG2, Release 1.0. For optimal performance:

•Set up logging directly to the RME (not through the Supervisor).

•Set up the SNMP server host to be the MWTM server.

•When you make configuration changes on the SAMI card, verify that the RME:

–Recognizes the changes

–Updates its configuration archive

For more information about the SAMI card, see the Service and Application Module for IP User Guide.

Supported Device Matrix

Table 4 shows a matrix of devices and IOS versions supported by the service managers.

Table 4 Service Manager-Supported Device Matrix 

Management Application
Device
Device Platform
Minimum Image/IOS on Device
Minimum IOS on Supervisor
Supervisor Platform

CSG Service Manager 4.1.2 1

CSG 5.8

CSG card

c6csg-apc.31-3.C5.8.bin

12.2(18)SXDx

Sup 720

CSG 5.9

CSG card

c6csg-apc.31-3.C5.9.bin

12.2(18)SXDx

Sup 720

CSG 5.9a

CSG card

c6csg-apc.31-3.C5.9a.bin

12.2(18)SXDx

Sup 720

CSG 6.2

CSG card

c6csg-apc.31-3.C6.2.bin

12.2(18)SXEx

Sup 720

CSG 6.4

CSG card

c6csg-apc.31-3.C6.4.bin

12.2(18)SXEx

Sup 720

CSG 6.9

CSG card

c6csg-apc.31-3.C6.9.bin

12.2(18)SXEx

Sup 720

CSG 7.1

CSG card

c6csg-apc.31-3.C7.1.bin

12.2(18)SXFx

12.2(18)SXFx

Sup 720

Sup 32

CSG 7.2

CSG card

c6csg-apc.31-3.C7.2.bin

12.2(18)SXFx

12.2(18)SXFx

Sup 720

Sup 32

CSG 7.5

CSG card

c6csg-apc.31-3.C7.5.bin

12.2(18)SXFx

12.2(18)SXFx

Sup 720

Sup 32

CSG2 1.0

SAMI card

c7svcsami-csg-mz-12.4-11.MD

12.2(33)SRB

Sup 720

GGSN Service Manager 4.1.2 1

GGSN 6.0

MWAM

12.4(2)XB

12.2(18)SXE

Sup 720

7200 NPE-400

12.4(2)XB

N/A

N/A

7200 NPE-G1

12.4(2)XB

N/A

N/A

GGSN 7.0

MWAM

12.4(9)XG

12.2(18)SXF5

Sup 720, Sup 32

7200 NPE-400

12.4(9)XG

12.2(18)SXF5

7200 NPE-G1

12.4(9)XG

12.2(18)SXF5

HA Service Manager 4.1.2

HA 3.0

MWAM

12.3(14)YX

12.2(18)SXE3

Sup 720

12.3(14)YX3

12.2(18)SXF5

Sup 32

7200 NPE-400

12.3(14)YX

N/A

N/A

7200 NPE-G1

12.3(14)YX

N/A

N/A

PDSN Service Manager 4.1.2

PDSN 3.0

MWAM

12.3(14)YX

12.2(18)SXE3

Sup 720

12.3(14)YX3

12.2(18)SXF5

Sup32

7200 NPE-400

12.3(14)YX

N/A

N/A

7200 NPE-G1

12.3(14)YX

N/A

N/A

1 MWTM 6.0.1 enables you to manage traps and alarms for CSG, CSG2, and GGSN devices.


Device Preparation Notes

When preparing the device, set up:

•The Domain Naming System (DNS) hostnames for each device.

•The user logins and enable passwords for device access from LMS applications and service managers.

•The Simple Network Management Protocol (SNMP), which is required for interoperation with the Common Services DCR and RME management. You should:

–Enter the snmp-server system-shutdown command for RME Software Image Management (SWIM).

–Set up SNMP community read and write strings for server access to the devices.

•Logging to the RME host ID and enable Syslog notification to the RME.

•Tune logs, as required:

–To ensure that date and time stamps appear in log files, enter the service timestamps log datetime msec and service timestamps debug datetime msec commands.

–To configure Syslog to alert that DCR has the wrong community string, enter the logging snmp-authfail command.

–To enable service-manager debugging, configure the device with the logging trap debug command.

•The MWTM to manage traps and alarms (for CSG, CSG2, and GGSN devices) by adding the following statements to the IOS configuration for these devices: 

snmp-server community <SNMP_COMMUNITY_STRING> RO 1

snmp-server enable traps

snmp-server host <SNMP_SERVER_HOST_IP_ADDRESS> version 2c <SNMP_COMMUNITY_STRING>

Resource Manager Essentials Preparation Notes

This section provides procedures to prepare and integrate the RME to interoperate with the service managers. These procedures include:

•Assigning Adhoc Tasks to Users

•Managing Device Inventory

•Tuning RME Configuration Management

•Configuring RCP for SWIM

•Configuring Purge Policies

Assigning Adhoc Tasks to Users

New users are added through the Common Services graphical user interface (GUI). Users who will be performing service-activation tasks through the service managers must have the Adhoc task assigned to their usernames in the RME NetConfig window. To assign the task:

Step 1 To access the RME NetConfig window, choose Resource Manager Essentials > Config Mgmt > NetConfig > Assigning Tasks.

Step 2 Select Adhoc from the Available Tasks list and click Add to move it to the Selected Tasks list.

Step 3 Enter the username in the Username field and click Assign.

Managing Device Inventory

This section provides procedures for managing the device inventory.

Adding Devices

Before using the service managers, you must add the devices that they will manage to the Common Services DCR to ensure that the inventory of these devices is propagated to all applications (RME, Campus Manager, CiscoView, and service managers). To verify that devices are propagated, view the status of inventory collection at the RME by choosing:

Resource Manager Essentials > Devices > Inventory > View Inventory Collection Status

Also, ensure that the devices are in the Normal state by choosing:

Resource Manager Essentials > Devices > Device Management > Device Management State

Managing Inventory Jobs

By default, a System Inventory Polling job is scheduled to run daily. To verify that this job has run successfully, choose:

Resource Manager Essentials > Devices > Inventory > Inventory Jobs

Note This polling job does not appear until it ends the first time. It also launches System Inventory Collection jobs when inventory changes are detected.

To schedule inventory collection and polling jobs, and set up e-mail notification of these jobs, choose:

Resource Manager Essentials > Admin > Inventory > System Job Schedule

Tuning RME Configuration Management

This section provides information for tuning the RME for best performance with the service managers.

Configuring Transport Settings

You should configure transport settings for the Archive Mgmt and NetConfig applications. Select the:

•Trivial File Transfer Protocol (TFTP) to be first in the protocol order for Config Fetch.

•Telnet protocol to be first in the protocol order for Config Deploy.

Note A limitation exists when using TFTP for Config Deploy operation. Even if some or all of the configuration statements fail during the Config Deploy operation, TFTP still reports successful deployment.

To access configuration transport settings, choose Resource Manager Essentials > Administration > Config Mgmt.

Note The managed devices should be configured to support TFTP.

Enabling Periodic Polling and Collection

You use the RME to modify how and when to retrieve device configurations. Two methods are possible:

•Periodic Polling—If enabled, the RME performs an SNMP query of the device. You can set the query to run daily, weekly, or monthly. If no configuration changes are detected, the configuration is not retrieved (fetched).

•Periodic Collection—If enabled, the device configuration is fetched without checking for changes in the configuration.

Note Periodic polling and collection are disabled by default.

To access these options in the Config Collection Settings window, choose:

Resource Manager Essentials > Admin > Config Mgmt > Archive Mgmt > Collection Settings

Purging Configuration Archives

You should periodically purge archived configurations to free disk space (for example, /var) and keep your archives to a manageable size. Through the RME you can configure a purging policy for running configurations.

Note Purging archived configurations is disabled by default.

To purge configurations, use one of these methods:

•Maximum number of configurations to retain—The oldest configuration is purged when the maximum number of configurations is reached.

•Age of configurations—Configurations are purged if they are older than the number of days that you specify. If only two or fewer versions of the configuration files exist, no purging is performed.

Note Ensure that the schedule that you configure for purging configuration archives does not coincide with the schedule that you set for configuration change detection. (See Managing Inventory Jobs.)

To access these options in the Archive Purge Setup window, choose:

Resource Manager Essentials > Admin > Config Mgmt > Archive Mgmt > Purge Settings

Configuring RME to Run Parallel Jobs

The service manager operates at maximum efficiency when the RME job policy is set to run four jobs in parallel instead of serially. To configure RME to run four jobs in parallel:

Step 1 Change the CDLNumOfThreads setting to 4 in the following files:

•/opt/CSCOpx/MDC/etc/regdaemon.xml

•/opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/config/ccjs/executor/downloader/downloader.properties

Step 2 Change the max_threads_for_config_fetch setting to 4 in /opt/CSCOpx/MDC/etc/regdaemon.xml.

Step 3 Change the global job Execution Policy to Parallel Execution in the Job Policy window by choosing:

Resource Manager Essentials > Admin > Config Mgmt > Config Job Policies

Note Verify that the job policy is set to Parallel Execution for each of the three RME configuration-management applications: NetConfig, Archive Mgmt, and Config Editor. These applications are available as options in a drop-down menu in the Job Policy window.

Step 4 Stop and start CiscoWorks processes. Enter:

/etc/init.d/dmgtd stop

/etc/init.d/dmgtd start

Configuring RCP for SWIM

You use the Remote Copy Protocol (RCP) to copy files to and from a file system on a remote server. The server that hosts the LMS 2.6 bundle and service managers must be configured correctly if you use RCP for Software Image Management (SWIM).

Verify that the .rhosts file exists in the home directory with write permissions for the owner. For example: 

lms_server-> pwd

/opt/home/rcp

lms_server-> ls -la

total 6

drwxr-xr-x   2 sdrcp    casusers     512 Mar 14 15:46 .

drwxrwxrwx   3 root     other        512 Mar 14 15:03 ..

-rw-r--r--   1 sdrcp    casusers     174 Mar 14 15:03 .profile

-rw-rw-r--   1 sdrcp    casusers       0 Apr  5 15:37 .rhosts

To configure Common Services to set the RCP User to use sdrcp as a username, choose:

Common Services > Server > Admin > System Preferences

On the device, configure the command:

ip rcmd rcp-enable

Configuring Purge Policies

As you perform routine operations, the RME retains a record of them by default. You can set up a job-purge policy for each job type (for example, Netconfig Jobs) and schedule the job purges to occur periodically, based on your operational requirements.

To set up a job-purge policy for different job types, go to the Job Purge window by choosing:

Resource Manager Essentials > Admin > System Preferences > Job Purge

To set up a purge policy for Syslogs, go to the Purge Policy window by choosing:

Resource Manager Essentials > Admin > Syslog > Set Purge Policy

Closing the Batch Window

Closing the batch window by using the X in the upper-right corner does not clear the contents of the batch file.

When you close the Batch dialog box by clicking Close, the service manager prompts you to save the batch file and warns you that all data will be lost if not saved. The batch file then opens as an empty file the next time you launch it. If instead you use the X in the upper-right corner of the dialog box, the Batch dialog box closes without a warning or a prompt. The next time you open the Batch dialog box, the original data is still present. New data is appended to this old data.

Click Close exclusively to close the Batch dialog box.

Help System Files

The online help system files are not updated for patch releases. This section documents the new features that have been added in the patch releases. The information documented in this section will be included in the online help system at the next major MWC release. New features are documented for:

•Release 4.1.1 Content

•Release 4.1.2 Content

Release 4.1.1 Content

The 4.1.1 release content includes the capability to schedule batch configurations. Because this feature affects all service managers, it is described in this document.

Batch Mode Scheduling

In previous releases, you could deploy batch configurations to devices on demand by using the Service Activation and Batch Mode features. In patch release 4.1.1, a new feature, Batch Mode Scheduling, allows you to schedule deployment of batch configurations at a future time. You can also monitor the configurations that you have scheduled.

You launch the Batch Mode Scheduling feature from:

•Schedule and Job Browser/History buttons in the Batch Config dialog box (choose Service Manager > Batch Config to access this dialog box)

•Schedule button in the Add to Batch dialog box (in the Service Activation windows)

Schedule a Batch Job from Batch Config Dialog Box

To schedule a batch job from the Batch Config dialog box:

Step 1 Choose Service Manager > Batch Config.

The Schedule button is dimmed (disabled) when you do not select a batch file or when you select multiple batch files.

Step 2 Select a batch file to schedule by checking the check box beside the batch filename.

The Schedule button is enabled.

Step 3 Click the Schedule button.

The Batch File Scheduler dialog box appears.

Step 4 To run the RME NetConfig job now:

a. In the Run Type field, select Immediate.

b. Click OK.

Step 5 To schedule the RME NetConfig job to run later:

a. In the Run Type field, select Later.

b. Enter a date and time that is greater than the current server time.

c. Click OK.

A progress bar shows the progress of the scheduling operation. When completed, a dialog box displays the RME NetConfig job ID.

Schedule a Batch Job from Add to Batch Dialog Box

To schedule a batch job from the Add to Batch dialog box:

Step 1 Click the Add to Batch button.

The Batch Mode dialog box appears.

Step 2 To save the batch file, click Save.

Step 3 Click the Schedule button.

The Batch File Scheduler dialog box appears.

Step 4 To run the RME NetConfig job now:

a. In the Run Type field, select Immediate.

b. Click OK.

Step 5 To schedule the RME NetConfig job to run later:

a. In the Run Type field, select Later.

b. Enter a date and time that is greater than the current server time.

c. Click OK.

A progress bar shows the progress of the scheduling operation. When completed, a dialog box displays the RME NetConfig job ID.

Display All Service Manager Jobs

To display a list of all the service-manager jobs in the RME NetConfig Job Browser:

Step 1 Choose Service Manager > Batch Config.

Step 2 Uncheck all check boxes in the batch file list.

Step 3 Click the Job Browser/History button.

The RME NetConfig Job Browser dialog box appears. The dialog box lists service-manager jobs only. The window shows when each job was scheduled or run.

Display Service Manager Jobs for Specific Batch File

To display service-manager jobs for a specific batch file in the RME NetConfig Job Browser:

Step 1 Choose Service Manager > Batch Config.

Step 2 Check the check box for the batch file you want to display.

Step 3 Click the Job Browser/History button.

The RME NetConfig Job Browser dialog box appears. The dialog box lists only those jobs that have been scheduled or run for the selected batch file.

Release 4.1.2 Content

The 4.1.2 release adds the capability to provision CSG2 devices. Because this feature affects only the CSG Service Manager, this feature is described in the Release Notes for the Content Service Gateway Service Manager 4.1.2.

Resolved Caveats

Table 5 lists the ID number and summary of each caveat that has been resolved in this release.

Note To obtain updated information about open caveats and workarounds, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl.

Table 5 Resolved Caveats 

Bug ID
Summary
Notes

CSCsd18792

Billing Service generates wrong command.

Resolved during new feature work.

CSCei28963

Enter key should activate Connect function for group select.

You can now press Enter or click Connect.

CSCin82636

The extractCsgConfigByType() function fetches extra configlets.

Resolved.

CSCsj03484

Display all configurations of one type in the Display Config window.

Choose Service Manager > Display Config, then click the Display Config button. Select Map, for example, to display a list of all Map configurations.


Open Caveats and Workarounds

Table 6 lists the ID number, summary, and any available workaround for each open caveat in this release.

Note To obtain updated information about open caveats and workarounds, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. You will be prompted to log in to Cisco.com.

Table 6 Open Caveats and Workarounds 

Bug ID
Summary
Workaround

CSCsb35170

Different versions of a device can appear in the same group.

The MWC for Cisco Mobile Exchange does not perform inventory collection or polling of devices for inventory changes. The service managers use the device inventory stored in the RME database. If you load a different image version onto a device, the service manager will not recognize the newly loaded image type and version until you update the service manager information by clicking Get Latest From DCR in the List Devices window. This action updates the device information in the service manager, but permits the older version to remain in the group.

To update the group details:

1. Go to the first group modification window of any service manager.

2. Click Get Latest from DCR.

This action synchronizes the device object with the RME inventory.

This action is required if the service-manager device inventory is not synchronized with RME. After that, you can modify the group with the latest value.

CSCsb41531

In any service manager, a debug job may fail without screen notification if you click Stop Debug. Failure depends on how far the job has progressed.

The log files for that service manager will show the job status. See that log for detailed job status. Refer to the release notes for the individual service managers for the log filename.

CSCsb79084

A service manager group display shows nonexistent devices. This situation occurs when devices originally placed in the group are removed.

Delete and create the group again. To get a refreshed list before recreating a group, click Get Latest from DCR from the inventory screen.

CSCsd09457

The Sync Report for a service manager shows a previous master device. This situation occurs when you run a Generate Diff process and change the master device for a group.

Click Generate Diff to cause the system to display the correct master device.

CSCsd18808

(Release 4.0.1) The Group Management dialog box does not show current data.

None.

CSCsd39181

Release 4.0.x versions of the MWC for Cisco Mobile Exchange applications are incompatible with Release 4.1.1 versions.

You must uninstall any 4.0 versions of the service managers before installing the 4.1 versions. Failure to do so will cause software failure.

CSCsg07023

The Fetch Config dialog box indicates: 

Fetch Config Failed.

The Status field shows: 

Not Attempted.

The Cause field shows: 

Invalid device specified.

This case occurs when the device name, which is configured within Common Services, contains spaces. The failure occurs when you create a device group in the service manager, select it, and then check the Fetch Config check box.

Avoid the use of spaces when entering device names in Common Services.

CSCsg67845

Resource Manager Essentials (RME).

Retry and Stop buttons do not work in a scheduled job.

The problem is observed when only one row exists in the Job Browser/History output. If you select the only entry and click on either Retry or Stop, no error message pops up.

Create more than one entry in the Job Browser/History output to enable Retry or Stop buttons.

CSCsg64532

Package installed on the system is missing in the uninstall list.

When an expected failure occurs during uninstallation (for example, if the /var directory runs out of disk space because of large log files), the script prompts you about abandoning the uninstall procedure. If you respond No (do not abandon), the script reports that files were not deleted.

If you remove log files to make room on /var, and then rerun the uninstall script, the uninstall list no longer displays the package you want to uninstall.

Choose Yes to abandon the uninstall to avoid this problem. Then remove old log files to make room in /var, and rerun the uninstall script.

CSCsh00101

The uninstallation script stalls and does not complete.

When uninstalling one or more packages from the uninstall list, the script becomes unresponsive as it nears completion.

Manually kill the process.

Note The uninstallation script successfully removes the selected packages.

CSCsi72361

When installing the service-manager core or service manager 4.1.2 patch onto the service-manager core or service manager 4.1.1 patch, the following message appears: 

This appears to be an attempt to 
install the same architecture and 
version of a package which is already 
installed. This installation will 
attempt to overwrite this package.

You can safely ignore the message.

The installation process relies on the Sun Package command, pkgadd. The pkgadd command does not determine the version difference between 4.1.1 and 4.1.2, and generates this message.

CSCsi71245

Core dump messages during 4.1.2 installation.

This is a rare problem that is a known Common Services bug (CSCsd37328). It will be fixed in a future release of Common Services.


Documentation Support

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

Product Documentation

Table 7 lists the available product documentation.

Table 7 Product Documentation 

Document Title
Cisco.com Location

Release Notes for Mobile Wireless Center for Cisco Mobile Exchange 4.1.2 (this document)

http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html

Release Notes for the Gateway GPRS Support Node Service Manager 4.1.2

http://www.cisco.com/en/US/products/ps6454/prod_release_notes_list.html

User Guide for the Gateway GPRS Support Node Service Manager 4.1

http://www.cisco.com/en/US/products/ps6454/products_user_guide_book09186a0080624581.html

Release Notes for the Home Agent Service Manager 4.1.2

http://www.cisco.com/en/US/products/ps6506/prod_release_notes_list.html

User Guide for the Home Agent Service Manager 4.1

http://www.cisco.com/en/US/products/ps6506/products_user_guide_book09186a0080648c17.html

Release Notes for the Content Services Gateway Service Manager 4.1.2

http://www.cisco.com/en/US/products/ps6399/prod_release_notes_list.html

User Guide for the Content Services Gateway Service Manager 4.1

http://www.cisco.com/en/US/products/ps6399/products_user_guide_book09186a008063d897.html

Release Notes for Packet Data Serving Node Service Manager 4.1.2

http://www.cisco.com/en/US/products/ps6696/prod_release_notes_list.html

User Guide for Cisco Packet Data Serving Node Service Manager 4.1

http://www.cisco.com/en/US/products/ps6696/products_user_guide_book09186a008064b8ab.html

Release Notes for the Cisco Mobile Wireless Transport Manager 6.0.1

http://www.cisco.com/en/US/products/ps6472/prod_release_note09186a0080852e3e.html

User Guide for the Cisco Mobile Wireless Transport Manager 6.0

http://www.cisco.com/en/US/products/ps6472/products_user_guide_book09186a00807f458b.html


Related Documentation

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

Table 8 lists the available related documentation.

Table 8 Related Documentation 

Documentation
Cisco.com Location

The Content Services Gateway documentation

http://www.cisco.com/en/US/products/sw/wirelssw/ps779/tsd_products_support_series_home.html

CSG2 Command Reference

http://www.cisco.com/en/US/products/sw/wirelssw/ps779/products_configuration_guide_chapter09186a0080857aa9.html

CSG2 Command History

http://www.cisco.com/en/US/products/sw/wirelssw/ps779/products_configuration_guide_chapter09186a0080857aab.html

Note This reference describes the differences in commands between CSG and CSG2 devices.

Service and Application Module for IP User Guide

http://www.cisco.com/en/US/products/hw/modules/ps5510/products_installation_and_configuration_guide_book09186a0080875d19.html

The Gateway GPRS Support System documentation

http://www.cisco.com/en/US/products/sw/wirelssw/ps873/tsd_products_support_series_home.html

The Packet Data Serving Node documentation

http://www.cisco.com/en/US/products/sw/wirelssw/ps4341/tsd_products_support_series_home.html

The Home Agent documentation set

http://www.cisco.com/en/US/products/ps5940/tsd_products_support_series_home.html

CiscoWorks Common Services documentation

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/tsd_products_support_series_home.html

CiscoWorks Resource Manager Essentials documentation

http://www.cisco.com/en/US/products/sw/cscowork/ps2073/tsd_products_support_series_home.html

CiscoWorks Campus Manager documentation

http://www.cisco.com/en/US/products/sw/cscowork/ps563/tsd_products_support_series_home.html


Additional Information Online

Your application might support incremental device updates (IDUs). An IDU is a software package that enables an application to support new devices. An IDU might also contain bug fixes. You can download IDUs and their Readme files by logging in to Cisco.com at:

http://www.cisco.com/kobayashi/sw-center/cw2000/lan-planner.shtml

To determine which packages are installed on your CiscoWorks Server, go to your CiscoWorks page and choose Common Services > Software Center > Software Update.

You also can obtain any published patches from the download site.

You can find further information about all supported devices on Cisco.com at:

http://www.cisco.com/en/US/products/sw/cscowork/ps3992/products_device_support_tables_list.html

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2007 Cisco Systems, Inc. All rights reserved.