Table Of Contents
Release Notes for the Gateway GPRS Support Node Service Manager, Release 4.1.1
Prerequisites for Installing the GGSN Service Manager
Installing the GGSN Service Manager
Reinstalling the GGSN Service Manager
QoS, SGSN, PLMN, and RAT Change Triggers for Charging Profile
PLMN and RAT Change Triggers for DCCA Profile
Caveats Resolved With This Release
Prerequisites for Configuring GGSN Devices
Product Documentation and Related Documentation
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Gateway GPRS Support Node Service Manager, Release 4.1.1
OL-11461-01
January 2007
The Cisco Gateway General Packet Radio Service (GPRS) Support Node Service Manager (GGSN SM) is a tool for managing the configuration of the Cisco Gateway GPRS Support Node (GGSN).
These release notes contain important information for Release 4.1.1 of the GGSN SM. These notes include the installation procedure and information on resolved and open caveats.
Contents
This document covers the following topics:
•
Prerequisites for Installing the GGSN Service Manager
•
•
•
•
•
Introduction
The GGSN SM provides an easy and intuitive way to provision service-activation features on a Cisco Gateway GPRS Support Node (GGSN) device. In addition to service-activation provisioning, you can use the GGSN SM to view the configurations in the device, and troubleshoot them by viewing and responding to debugging messages.
The GGSN SM includes:
•
•
•
The Gateway GPRS Support Node Service Manager User Guide provides complete information on these modules. See Product Documentation, for information on accessing the electronic version of this document on the Cisco website.
The GGSN SM is part of the Mobile Wireless Exchange (MWC) for Cisco Mobile Exchange, a suite of element-management applications that provide configuration and fault-monitoring capabilities to mobile wireless operators. The MWC for Cisco Mobile Exchange applications complement the CiscoWorks LAN Management Solution (LMS) to provide end-to-end management of the Cisco Mobile Exchange. The LMS is prerequisite to MWC for Cisco Mobile Exchange.
The LMS 2.6 includes:
•
•
•
Note
Refer to the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange for this release, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, for information on MWC for Cisco Mobile Exchange and the LMS requirement.
Prerequisites for Installing the GGSN Service Manager
Refer to the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange for this release, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, for information on MWC for CMX hardware and software requirements, including information on Sun patches and package requirements.
Installing the GGSN Service Manager
This section provides information on:
•
•
Installation Order
The GGSN SM requires that the CiscoWorks Common Services application be bundled with the LAN Management Solution (LMS), Release 2.6. The LMS is prerequisite to MWC for Cisco Mobile Exchange.
For new installations, always install in this order:
1.
2.
3.
Note
cmxinstall.log.12012006_14:04:INFO: Package CSCO<pkgnam> - Installed. Verifying - Failed. Modifying - Done.
Ignore this message.The Release Notes for Mobile Wireless Center for Cisco Mobile Exchange for this release, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, contains instructions for installing the LMS bundle and the CMX core. This section provides information on installing the GGSN SM.
Installation Procedure
To install the GGSN SM for the first time:
Step 1
Step 2
Step 3
Step 4
Step 5
./setup.shA confirmation message appears after a successful installation. If errors occur during installation, check the installation log file /var/tmp/ggsninstall.log.
Backing Up and Restoring Data
You can use the GGSN SM to back up and restore:
•
•
•
•
Backing up and restoring information makes use of the Common Services backup tool. This tool backs up and restores CS and all applications that are registered with it.
Refer to the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange Release at http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html for information on this procedure.
Reinstalling the GGSN Service Manager
To reinstall the GGSN SM after an interrupted or failed installation attempt:
Step 1
Step 2
Step 3
Step 4
Step 5
./setup.shA confirmation message appears after a successful installation. If errors occur during installation, check the installation log file: /var/tmp/ggsninstall.log.
Uninstalling the GGSN SM
To uninstall the GGSN SM:
Step 1
Step 2
cd /opt/CSCOpx/binStep 3
./uninstall.shA list of software that is installed in the host machine appears.
Step 4
Step 5
A confirmation message appears after a successful uninstallation.
What's New in GGSN SM 4.1.1
The following features were introduced in Release 4.1.1 of the GGSN SM which were released in GGSN (7.0):
Service Activation
•
•
Batch Mode Scheduling
CMX-GGSN Service Activation
IPv6 PDP Type
This feature enhances the APN Configuration screen in GGSN SM. A new wizard (APN Wizard5) has been added to the Service Activation menu tab. This new wizard configures the IPv6 parameters for the APN.
To access this new wizard, perform the following steps as you normally would, going through APN Wizard1 to APN Wizard4 until you come to APN Wizard5 (for more information about accessing the first four APN Wizards, see the User Guide for Cisco GGSN Service Manager):
Step 1
The APN List appears. (See Figure 1.)
Figure 1 APN List
Step 2
The APN Wizard1 screen appears. (See Figure 2.)
Figure 2 APN Wizard1 Screen
Step 3
Step 4
Step 5
Figure 3 APN Wizard5 Screen
Table 1describes the fields in this screen.
QoS, SGSN, PLMN, and RAT Change Triggers for Charging Profile
This feature enhances the Charging Profile Configuration screen in GGSN SM. Four new check boxes have been added to the Charging Profile Service Activation. These check boxes are only visible for GGSN 7.0; they are absent in previous GGSN software releases.
The four new check boxes provide the following triggers for changing the profile:
•
•
•
•
Unchecking these options will remove the features for the charging profile.
To access this new profile, perform the following steps as you normally would, by creating a new charging profile (for more information about accessing the charging profile, see the User Guide for Cisco GGSN Service Manager):
Step 1
The GGSN Charging Profile List appears. (See Figure 4.)
Figure 4 Charging Profile List
Step 2
The Charging Profile window appears. (See Figure 5.)
Figure 5 Charging Profile Window During Profile Creation
Table 2 describes the fields in the Charging Profile window.
Note
Table 2 Features of the Charging Profile Config Window During Profile Creation
Charging Profile section
Charging Profile No
Associates a default charging profile with an access point.
This is required. If you enter the number of an existing charging profile, a warning message appears. If you continue, your changes will overwrite the existing charging profile with that number.
5.0, 5.1, 5.2, 6.0, 7.0
Charging Category
Identifies the subscriber category to which a charging profile applies. Possible values are Flat, Hot, Normal, and Prepaid.
5.0, 5.1, 5.2, 6.0, 7.0
Description
Specifies the name or a brief description of a charging profile.
5.0, 5.1, 5.2, 6.0, 7.0
CDR Suppression
Specifies that CDRs be suppressed as a charging characteristic in a charging profile.
5.0, 5.1, 5.2, 6.0, 7.0
CDR Prepaid
Suppresses CDR for prepaid users
5.2, 6.0, 7.0
Tariff Time
Specifies that a charging profile use the tariff changes that you configure by using the GPRS charging tariff-time global configuration command.
5.0, 5.1, 5.2, 6.0, 7.0
QOS-Change Trigger
Specifies that QoS changes trigger quota-reauthorization.
7.0
SGSN-Change Trigger
Specifies that SGSN changes trigger quota-reauthorization.
7.0
PLMN-Change Trigger
Specifies that PLMN changes trigger quota-reauthorization.
Note
7.0
RAT-Change Trigger
Specifies that RAT changes trigger quota-reauthorization.
Note
7.0
Content section
DCCA
5.2, 6.0, 7.0
Time Limit
Field that specifies the default time threshold for post-paid (off-line billing) users. Possible values are 3,600-4,294,967,295.
5.2, 6.0, 7.0
Validity Limit
Specifies the validity time, in seconds. Possible values are 3,600-4,294,967,295 for 5.2 and 900-4,294,967,295 for 6.0.
5.2, 6.0, 7.0
Volume Limit
Specifies the default volume threshold for post-paid users. This is the maximum number of bytes that the GGSN maintains across all containers for a particular PDP context before closing and updating the GGSN call detail record (G-CDR). Possible values are 1-4,294,967,295.
5.2, 6.0, 7.0
Rulebase
Specifies the rulebase to use for defining categories of traffic. The GGSN bases decision such as whether to allow or disallow traffic and how to measure the traffic on rulebases. The GGSN maps Diameter Rulebase IDs to the charging profiles.
This name length can be up to 64 characters.
5.2, 6.0, 7.0
Fetch
Button that you click
5.2, 6.0, 7.0
Trigger Thresholds section
Duration
Specifies, as a trigger condition in a charging profile, the time duration limit that, when exceeded, causes the GGSN to collect upstream and downstream traffic byte counts and close and update the GGSN call detail record (G-CDR) for a particular PDP context.
5.0, 5.1, 5.2, 6.0, 7.0
Volume
Specifies, as a trigger condition in a charging profile, the maximum number of bytes that the GGSN maintains across all containers for a particular PDP context before closing and updating the GGSN call detail record (G-CDR).
5.0, 5.1, 5.2, 6.0, 7.0
SGSN Change
Specifies, as a trigger condition in a charging profile, the maximum number of SGSN changes that can occur before closing and updating the GGSN call detail record (G-CDR) for a particular PDP context.
5.0, 5.1, 5.2, 6.0, 7.0
Reset Volume Trigger
Clears the Volume Trigger field.
5.0, 5.1, 5.2, 6.0, 7.0
Reset Duration Trigger
Clears the Duration trigger field.
5.0, 5.1, 5.2, 6.0, 7.0
Step 3
The Charging Profile Config window displays the new configuration for confirmation.
PLMN and RAT Change Triggers for DCCA Profile
This feature enhances the DCCA Profile Configuration screen in GGSN SM. Two new check boxes have been added to the DCCA Profile Service activation. These check boxes are only visible for GGSN 7.0. Otherwise, they are absent in previous GGSN software releases.
The two new check boxes provide the following triggers for changing the DCCA profile:
•
•
Un-checking these options will remove the features for the DCCA profile.
To access this new profile, perform the following steps as you normally would, by creating a new charging profile (for more information about accessing the DCCA profile, see the User Guide for Cisco GGSN Service Manager):
Step 1
The DCCA Profile List appears (see Figure 6).
Figure 6 DCCA Profile Window List
Step 2
The DCCA Profile window appears. (See Figure 7.)
Figure 7 DCCA Profile Window During Profile Creation
Table 3 describes the fields in the DCCA profile window.
Batch Mode Scheduling
In previous releases, you used the Service Activation and Batch Mode features to deploy batch configurations to devices on demand. In patch release 4.1.1, you can use a new feature, Batch Mode Scheduling, 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 by clicking the:
•
•
Refer to the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange Release 4.1.1 at http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html for information on this procedure.
Caveats Resolved With This Release
Table 4 lists the ID number and summary of each caveat resolved with this release.
Table 4 Caveats Resolved With This Release
CSCsb3280
The Service Managers now control the size of the cmxTe.log file by adding that file to the Common Services logrot utility during installation of the Service Manager Core module. The cmxTe.log can increase rapidly if you have enabled devices for debugging and viewing Syslogs. If this file becomes larger than 10 MB, the logrot utility rotates the log file. If the rotation occurs while you are viewing the Debug window, you should close and reopen the window to observe the most recent log messages.
Find more information about the logrot utility at http://www.cisco.com/en/US/
products/sw/cscowork/ps3996/
products_user_guide_chapter
09186a008022f958.html#wp271846.CSCsb67002
When running more than one Service Manager simultaneously, log messages were being written to the log file of the Service Manager that was instantiated first.
This bug has been resolved.
Open Caveats and Workarounds
Note
Table 5 lists the ID number, summary, and any available workaround for each open caveat in this release.
Supported Device Versions
Table 6 lists the device versions that the GGSN SM 4.1.1 supports.
Review Prerequisites for Configuring GGSN Devices, for specific requirements relating to versions, switches, and cards.
You can find further 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
Prerequisites for Configuring GGSN Devices
To use the GGSN SM to configure a GGSN device, perform the following required actions. The optional actions that follow deal with configurations that may exist in the device, but that are not addressed by the GGSN SM.
For more information on any of these steps, see the GGSN Services Configuration Task List at: http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123limit/123x/123xu/
50xu1/ggsn50_c/ggsncfg.htm#wp1020149
Note
Required—Use of the GGSN SM requires you to:
1.
2.
3.
4.
5.
6.
For more information on the RME inventory function, see the section titled "Adding and Troubleshooting Devices Using Device Management" in the User Guide for Resource Manager Essentials 4.0.5 (With LMS 2.6) at http://www.cisco.com/en/US/products/sw/cscowork/ps2073/
products_installation_guide_book09186a008073d5dc.html.
Note
The Release Notes for Mobile Wireless Center for Cisco Mobile Exchange for this release, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, contains information on logging commands and other requirements.
Optional—While the GGSN SM does not address the following configuration issues, you might want to take these actions as well:
1.
2.
3.
Documentation Support
This section provides information on:
•
•
Note
Product Documentation and Related Documentation
This section provides information on:
Product Documentation
Table 7 describes the product documentation that is available.
Table 7 Product Documentation
User Guide for the Gateway GPRS Support Node Service Manager for this release
http://www.cisco.com/en/US/products/ps6454/
products_user_guide_list.htmlRelease Notes for Cisco GGSN Service Manager for this release (this document)
http://www.cisco.com/en/US/products/ps6454/
prod_release_notes_list.htmlContext-sensitive online help
•
•
Related Documentation
Table 8 describes related documentation that is available.
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 Read me 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 Publications and Information.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.
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
The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:
http://www.cisco.com/univercd/home/home.htm
The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Support site area by entering your comments in the feedback form available in every online document.
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 will find information about how to do the following:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at 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 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 encryption key 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.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.
Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive these announcements by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. Registered users can access the tool at this URL:
http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en
To register as a Cisco.com user, go to this URL:
http://tools.cisco.com/RPF/register/register.do
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Support 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 Support Website
The Cisco Support website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL:
http://www.cisco.com/en/US/support/index.html
Access to all tools on the Cisco Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Tip
If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. After using the Search box on the Cisco.com home page, click the Advanced Search link next to the Search box on the resulting page and then click the Technical Support & Documentation radio button.
To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.
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)—An existing 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 operations 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 the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/offer/subscribe
•
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
•
http://www.cisco.com/en/US/learning/index.html
