Table Of Contents
Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange 4.1.3
Prerequisites for Installing the Service Managers
Minimum Server Platform Requirements
Sun Patches and Packages Requirements
Determining the Software Versions Currently on Your System
Installing the MWC for Cisco Mobile Exchange
Installing the Service Managers
Backing Up and Restoring Service Manager Data
Restoring Data for All MWC for Cisco Mobile Exchange Applications
Restoring Data for an Individual Service Manager
Sample Output from the Restore Tool
Reinstalling the Service Managers
Uninstalling a Service Manager
Uninstalling the Service Manager Core
Software Version Considerations
Configuring Two Device Groups Simultaneously
Synchronizing Device Inventories
Unsupported Special Characters in Field Names
Refreshing the Config Viewer Window
Resource Manager Essentials Preparation Notes
Assigning Adhoc Tasks to Users
Tuning RME Configuration Management
Configuring Transport Settings
Enabling Periodic Polling and Collection
Purging Configuration Archives
Configuring RME to Run Parallel Jobs
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange 4.1.3
Revised: October 2007, OL-14526-01The 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 4.1.3 of the MWC for Cisco Mobile Exchange.
Contents
This document contains the following sections:
•
Prerequisites for Installing the Service Managers
•
•
•
•
•
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.
The service managers provide service-activation features for a specific mobile wireless application (for example, GGSN). 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 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. Important restrictions exist for MWAMs. See MWAM Preparation Notes, for more information.
The CSG device can reside on the following cards:
•
•
Note
Also see SAMI Preparation Notes.
What's New in This Release
4.1.1
Batch mode scheduling feature (see Batch Mode Scheduling).
4.1.2
New version of the CSG on the SAMI card (CSG2). See the Release Notes for the Content Services Gateway Service Manager 4.1.2.
4.1.3 (this release)
Support for LMS 3.0, which includes RME 4.1 and CiscoView 6.1.6.
Note
Prerequisites for Installing the Service Managers
This section describes the following prerequisites for installing the MWC for Cisco Mobile Exchange:
•
•
•
Minimum Server Platform Requirements
Minimum server platform requirements to support the LMS 3.0 and MWC for Cisco Mobile Exchange applications are described here:
Caution
For information on diagnosing problems with the server, refer to:
Client Requirements
Refer to the LMS 3.0 client and server requirements at:
Note
Supported Browsers
Refer to the LMS 3.0 browser requirements at:
Sun Patches and Packages Requirements
Refer to the LMS 3.0 requirements for Sun patches and packages at:
Determining the Software Versions Currently on Your System
To determine the version of packages that are installed on your CiscoWorks server:
Step 1
Step 2
Installing the MWC for Cisco Mobile Exchange
This section covers the following topics:
•
Installation Sequence
Installing the LMS
To install the MWC for Cisco Mobile Exchange solution, you must first install the applications of the LMS 3.0 bundle. Install each LMS 3.0 application in the correct order. Click this link for the order of installation and instructions for installing each LMS application:
In addition to the LMS applications that are required for the MWC for Cisco Mobile Exchange, the LMS Release 3.0 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
Installing the Service Managers
To install the GGSN or CSG Service Manager, you must first install the service manager core module:
Step 1
http://www.cisco.com/pcgi-bin/tablebuild.pl/mwc-cmx
Step 2
Step 3
Step 4
Step 5
Step 6
Note
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.1 and later 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
As in CS, the backup tool backs up the followings types of data:
•
•
•
•
•
•
•
•
•
•
•
•
•
Backing Up Existing Data
To back up existing data:
Step 1
Step 2
/etc/init.d/dmgtd stop
Step 3
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl backupdir
Follow the instructions that the backup script provides.
Step 4
/etc/init.d/dmgtd start
Restoring Backup Data
You have two options for restoring backup data:
•
•
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
/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
Step 2
/etc/init.d/dmgtd stop
Step 3
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl backup_dir
Step 4
/etc/init.d/dmgtd start
Restoring Data for an Individual Service Manager
To restore data for an individual service manager:
Step 1
Step 2
/etc/init.d/dmgtd stop
Step 3
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/cmx/ServiceManager/restorebackup.pl -d /backup_dir/0Step 4
/etc/init.d/dmgtd start
Sample 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:08Please see '/var/adm/CSCOpx/log/restorebackup.log' for status.OS of the backup archive ................ : UnixGeneration of data to be restored .............. : 0Backup taken from............................... : /opt/CSCOpx/backupBackup archive data taken from.................. : CDONE 3.0Directory where Common Services is installed.... : /opt/CSCOpxTemp folder for this restore program............ : /opt/CSCOpx/tempBackupDataApplications 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)?yApplications to be restored are............ : Packet Data Service Node Service ManagerAvailable disk space in NMSROOT............ : 28733296 KbRequired 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 successfullyReinstalling the Service Managers
You may need to reinstall the software if an installation attempt is interrupted or fails. If reinstallation is required, repeat the procedure 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:
Uninstalling Release 4.1.3
If, for any reason, you must remove the 4.1.3 installation, 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
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
cd /opt/CSCOpx/bin
Step 2
./uninstall.sh
The script prompts you with a list of software that is installed on the host machine.
Step 3
Step 4
A confirmation message appears after a successful uninstallation.
Uninstalling the Service Manager Core
To uninstall the service-manager core module:
Step 1
cd /opt/CSCOpx/bin
Step 2
./uninstall.sh
The script prompts you with a list of software that is installed on the host machine.
Step 3
Step 4
A confirmation message appears after a successful uninstallation.
Limitations and Restrictions
This section provides information on:
•
•
•
•
•
Software Version Considerations
Cisco does not support mixed versions of the service managers on the same system.
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
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:
•
•
•
•
•
•
•
•
•
•
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:
•
•
•
–
–
For more information about the SAMI card, see the Service and Application Module for IP User Guide.
Supported Device Matrix
Table 2 shows a matrix of devices and IOS versions supported by the service managers.
Device Preparation Notes
When preparing the device, set up:
•
•
•
–
–
•
•
–
–
–
•
snmp-server community <SNMP_COMMUNITY_STRING> RO 1snmp-server enable trapssnmp-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
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
Step 2
Step 3
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
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:
•
•
Note
To access configuration transport settings, choose Resource Manager Essentials > Administration > Config Mgmt.
Note
Enabling Periodic Polling and Collection
You use the RME to modify how and when to retrieve device configurations. Two methods are possible:
•
•
Note
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
To purge configurations, use one of these methods:
•
•
Note
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
•
•
Step 2
Step 3
Resource Manager Essentials > Admin > Config Mgmt > Config Job Policies
Note
Step 4
/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 3.0 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/rcplms_server-> ls -latotal 6drwxr-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 .rhostsTo 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
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 a Batch Job from Batch Config Dialog Box
To schedule a batch job from the Batch Config dialog box:
Step 1
The Schedule button is dimmed (disabled) when you do not select a batch file or when you select multiple batch files.
Step 2
The Schedule button is enabled.
Step 3
The Batch File Scheduler dialog box appears.
Step 4
a.
b.
Step 5
a.
b.
c.
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
The Batch Mode dialog box appears.
Step 2
Step 3
The Batch File Scheduler dialog box appears.
Step 4
a.
b.
Step 5
a.
b.
c.
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
Step 2
Step 3
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
Step 2
Step 3
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.
Release 4.1.3 Content
The 4.1.3 release adds no new functionality to the service managers. The 4.1.3 release supports a new LMS platform (3.0), which includes RME 4.1 and CiscoView 6.1.6.
Resolved Caveats
Table 3 lists the ID number and summary of each caveat that has been resolved in this release.
Note
Table 3 Resolved Caveats
CSCsi71245
Core dump messages during 4.1.2 installation.
This is a rare problem that is a known Common Services bug (CSCsd37328).
Open Caveats and Workarounds
Table 4 lists the ID number, summary, and any available workaround for each open caveat in this release.
Note
Documentation Support
Note
Product Documentation
Table 5 lists the available product documentation.
Table 5 Product Documentation
Release Notes for Mobile Wireless Center for Cisco Mobile Exchange 4.1.3 (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.3
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 Content Services Gateway Service Manager 4.1.3
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
Related Documentation
Note
Table 6 lists the available related documentation.
Table 6 Related Documentation
The Content Services Gateway documentation
http://www.cisco.com/en/US/products/sw/wirelssw/ps779/tsd_products_support_series_home.html
CSG2 Command Reference
CSG2 Command History
Note
Service and Application Module for IP User Guide
The Gateway GPRS Support System documentation
http://www.cisco.com/en/US/products/sw/wirelssw/ps873/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
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/public/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.
