Table Of Contents
Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange, Release 4.0.1
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
Backing Up and Restoring Service Manager Data
Example Output From the Restore Tool
Upgrading from Release 4.0 to Release 4.0.1
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
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Cisco Publications and Information
Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange, Release 4.0.1
OL-9766-03
September, 2006
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.0.1 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 migrating 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 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 MWFM 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 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 an Multiprocessor WAN Application Module (MWAM). (The CSG resides on its own card.) The MWAM card has five processors on it, so one MWAM card can accommodate five devices. All devices on a single MWAM card must be of the same type. Be aware, however, that there are some important restrictions regarding MWAMs. See MWAM Preparation Notes, for more information.
Prerequisites for Installing the Service Managers
This section describes the following prerequisites to installing the MWC for Cisco Mobile Exchange:
•
•
•
Minimum Server Platform Requirements
Table 2 describes the minimum server platform requirements to support the LMS 2.5.1 and MWC for Cisco Mobile Exchange applications.
Caution
For for information on diagnosing problems with the server, refer to
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/
products_user_guide_chapter09186a008022f962.html.Client Requirements
Refer to LMS 2.5.1 Client and Server requirements:
Supported Browsers
Refer to LMS 2.5.1 browser requirements:
Sun Patches and Packages Requirements
Refer to LMS 2.5.1 requirements for Sun patches and packages:
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 provides information on:
•
•
Installation Order
Release 4.0.1 is an upgrade from Release 4.0. This upgrade requires that the 4.0 core and 4.0 Service Managers be present.
The CiscoWorks Common Services, including the LAN Management Solution (LMS), Release 2.5.1, is prerequisite to MWC for Cisco Mobile Exchange.
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.
Back-up data contains all Service Manager information for Service Managers registered with CS 3.0 and above in the back-up folder.
Before running a back-up, 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.
Note
Types of Data Backed Up
As in CS, the back-up 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 instructions provided by the backup script.
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 Manager. 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 for 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/0
Step 4
/etc/init.d/dmgtd start
Example Output From the Restore Tool
Here is example 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 successfullyUpgrading from Release 4.0 to Release 4.0.1
Release 4.0.1 is an upgrade from Release 4.0. This upgrade requires that you have installed:
•
•
To perform this upgrade:
Step 1
Step 2
The file is available at:
http://www.cisco.com/cgi-bin/tablebuild.pl/mwc-cmx
Step 3
unzip CMXCORE401-CD-SOL-2006-0222-FCS.zip
Step 4
cd disk1
Step 5
. /setup.sh
The setup script starts an interactive installation. Respond to prompts to complete the installation.
Step 6
Reinstalling Release 4.0.1
To reinstall the Service Manager 4.0.1 after an interrupted or failed installation attempt, use this order:
1.
2.
3.
4.
Note
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 the following URL for more information:
Uninstalling Release 4.0.1
These release notes cover Release 4.0.1 of the MWC for Cisco Mobile Exchange. To uninstall Release 4.0.1, you run a script, then select the Service Managers you wish to uninstall.
Caution
To uninstall Release 4.0.1 of the MWC for Cisco Mobile Exchange:
Step 1
cd /opt/CSCOpx/bin
Step 2
./uninstall.sh
The script prompts you with a list of software that is installed in the host machine. For example:
1) CiscoView 6.1.22) Mobile Wireless Fault Mediator 4.1.13) Integration Utility 1.64) CiscoWorks Common Services 3.0.35) Resource Manager Essentials 4.0.36) PDSN Service Manager 4.0.17) HA Service Manager 4.0.18) CSG Service Manager 4.0.19) GGSN Service Manager 4.0.110) All of the aboveSelect one or more of the items using its number separated by comma or enter q to quit [q]Step 3
Limitations and Restrictions
This section provides information on:
•
•
•
•
•
Software Version Considerations
Cisco does not support mixed versions of software on the same system. That is, if you upgrade one Service Manager to 4.0.1, you must upgrade all Service Managers to the same version.
cmxTe.log File Size
The Service Managers do not automatically control the size of the cmxTe.log file. File size can increase rapidly if you have enabled devices for debugging and viewing syslogs. If this file becomes bigger than 10MB, the following warning message appears:
The log file: /var/adm/CSCOpx/log/cmxTe.log has exceeded the maximum recommended file size; performance might be impacted. To setup an automation log rotation facility, refer to: http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html
Use the logrot utility against /var/tmp/CSCOpx/log/cmxTe.log.
Note
You can access information about the logrot utility at: http://www.cisco.com/en/US/products/sw/cscowork/ps3996/
products_user_guide_chapter09186a008022f958.html#wp271846.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 (;), and backslash (\) 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_book09186a008046c3e7.htmlSupported Device Matrix
Table 3 shows a matrix of supported devices and IOS versions.
Device Preparation Notes
When preparing the device, set up:
•
•
•
–
–
•
•
–
–
–
Resource Manager Essentials Preparation Notes
This section provides procedures to prepare and integrate the RME to interoperate with the Service Manager(s). The following subsections are included:
•
•
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 do this:
Step 1
Resource Manager Essentials > Config Mgmt > NetConfig > Assigning Tasks
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 email 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 > Admin > 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 2.5.1 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 user name, 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
Open Caveats and Workarounds
Table 5 lists the ID number, summary, and any available workaround for each open caveat in this release.
Note
Table 4 Open Caveats and Workarounds
CSCsb32820
The Service Managers do not automatically control the size of the cmxTe.log file. File size can increase rapidly if you have enabled devices for debugging and viewing Syslogs. If this file becomes bigger than 10MB, the following warning message appears:
The log file: /var/adm/CSCOpx/log/
cmxTe.log has exceeded the maximum recommended file size; performance might be impacted. To setup an automation log rotation facility, refer to: http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.htmlUse the logrot utility against /var/tmp/CSCOpx/log/cmxTe.log.
You may wish to implement this action in a cron job.
You can access the logrot utility at http://www.cisco.com/en/US/
products/sw/cscowork/ps3996/
products_user_guide_chapter
09186a008022f958.html#wp271846.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 DC in the List Devices window. This updates the device information in the Service Manager, but permits the older version to remain in the group.
To update the group details:
1.
2.
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 file name.
CSCsb67002
When running more than one Service Manager simultaneously, log messages are written to the log file of the Service Manager that was instantiated first.
None
CSCsb79084
A Service Manager group display shows nonexistent devices. This 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 in a Service Manager shows a previous master device. This 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.
CSCsd10466
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, you are prompted to save the batch file and warned 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.
CSCsd18808
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.0.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 in 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 checkbox.
Avoid the use of spaces when entering device names in Common Services.
Documentation Support
Note
Product Documentation
Table 5 describes the product documentation that is available.
Table 5 Product Documentation
Release Notes for Mobile Wireless Center for Cisco Mobile Exchange (this document)
On Cisco.com at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/
mwc4cmx/Release Notes for the Gateway GPRS Support Node Service Manager for this release
•
•
http://www.cisco.com/en/US/products/ps6454/
prod_release_notes_list.htmlCisco Gateway GPRS Support Node Service Manager User Guide for this release
•
•
http://www.cisco.com/en/US/products/ps6454/
products_user_guide_list.htmlRelease Notes for the Home Agent Service Manager for this release
•
•
http://www.cisco.com/en/US/products/ps6506/
prod_release_notes_list.htmlCisco Home Agent Service Manager User Guide for this release
•
•
http://www.cisco.com/en/US/products/ps6506/
products_user_guide_list.htmlRelease Notes for Content Services Gateway Service Manager for this release
•
•
http://www.cisco.com/en/US/products/ps6399/
prod_release_notes_list.htmlCisco Content Services Gateway Service Manager User Guide for this release
•
•
http://www.cisco.com/en/US/products/ps6399/
products_user_guide_list.htmlRelease Notes for PDSN Service Manager for this release
•
•
http://www.cisco.com/en/US/products/ps6696/
prod_release_notes_list.htmlCisco PDSN Service Manager User Guide for this release
•
•
http://www.cisco.com/en/US/products/ps6696/
products_user_guide_list.htmRelease Notes for Cisco Mobile Wireless Fault Mediator for this release
•
•
http://www.cisco.com/univercd/cc/td/doc/
product/rtrmgmt/mwc4cmx/mwfm/Cisco Mobile Wireless Fault Mediator User Guide
•
•
http://www.cisco.com/univercd/cc/td/doc/
product/rtrmgmt/mwc4cmx/mwfm/Context-sensitive online help
•
•
Related Documentation
Note
Table 6 describes the additional documentation that is available.
Table 6 Related Documentation
The Cisco Content Services Gateway documentation set
On Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/wirelssw/ps779/
index.htmlRelease Notes for Mobile Wireless Center for Cisco Mobile Exchange for this release
On Cisco.com at:
http://www.cisco.com/en/US/products/ps6401/
prod_release_notes_list.htmlUser Guide for CiscoWorks Common Services 3.0.3 (With LMS 2.5.1)
On Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps3996/
products_user_guide_book09186a008053eabf.htmlUser Guide for Resource Manager Essentials 4.0.3 (With LMS 2.5.1)
On Cisco.com at this URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/
products_user_guide_book09186a008055b137.htmlThe CiscoWorks documentation set
On Cisco.com at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/
cw2000/index.htm
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 into 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 can also obtain any published patches from the download site.
You can find information about all supported devices on Cisco.com at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/mgt_pix/fwmc_1_3/px_sd_13.htm
You also may be interested in the additional Cisco information described in Obtaining Additional Cisco Publications and Information.
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/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Cisco will continue to support documentation orders using the Ordering tool:
•
http://www.cisco.com/en/US/partner/ordering/
•
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco 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-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.htm
The link on this page has the current PGP key ID in use.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.htm
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation 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, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation 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
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 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 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-2447For 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 Cisco Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the Documentation Support.
Release Notes for Mobile Wireless Center for Cisco Mobile Exchange, Release 4.1© 2006 Cisco Systems, Inc. All rights reserved.
