Cisco GPRS Gateway Support Node Service Manager

Table Of Contents

Release Notes for the Gateway GPRS Support Node Service Manager 4.1.3

Contents

Introduction

Prerequisites for Installing the GGSN Service Manager

Installing the GGSN Service Manager

What's New in This Release

GGSN Service Activation

IPv6 PDP Type

QoS, SGSN, PLMN, and RAT Change Triggers for Charging Profile

PLMN and RAT Change Triggers for DCCA Profile

Batch Mode Scheduling

Open Caveats and Workarounds

Supported Device Versions

Prerequisites for Configuring GGSN Devices

Documentation Support

Product Documentation and Related Documentation

Product Documentation

Related Documentation

Additional Information Online

Obtaining Documentation, Obtaining Support, and Security Guidelines

Release Notes for the Gateway GPRS Support Node Service Manager 4.1.3

---

Revised: October 2007, OL-14527-01

The Cisco Gateway 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 4.1.3 of the GGSN SM. These notes include the installation procedure and information on resolved and open caveats.

Contents

This document covers the following topics:

•Introduction

•Prerequisites for Installing the GGSN Service Manager

•Installing the GGSN Service Manager

•What's New in This Release

•GGSN Service Activation

•Batch Mode Scheduling

•Open Caveats and Workarounds

•Supported Device Versions

•Prerequisites for Configuring GGSN Devices

•Documentation Support

•Obtaining Documentation, Obtaining Support, and Security Guidelines

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:

•Inventory Manager—Manages and displays device group information

•Service Manager—Activates and manages the various services in a GGSN device group

•Troubleshooting Engine—Troubleshoots GGSN devices

The User Guide for Gateway GPRS Support Node Service Manager 4.1 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 Center (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 3.0 includes:

•Common Services 3.1 with CiscoView 6.1.6

•Resource Manager Essentials 4.1

---

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

---

Refer to the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange 4.1.3, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, for information on the 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 4.1.3, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, for information on MWC for Cisco Mobile Exchange hardware and software requirements, including information on Sun patches and package requirements.

Installing the GGSN Service Manager

Refer to the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange 4.1.3, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html.

That document describes the installation sequence of the MWC for Cisco Mobile Exchange for Release 4.1.3, which includes the GGSN Service Manager. The document also provides the steps for installing one or more service managers within the context of the overall solution.

What's New in This Release

Patch Release	What's New
4.1.1	Service Activation features: •IPv6 PDP Type •QoS, SGSN, PLMN, and RAT Change Triggers for Charging Profile •PLMN and RAT Change Triggers for DCCA Profile Batch mode scheduling feature (Batch Mode Scheduling)
4.1.2	The GGSN SM 4.1.2 provides a minor bug fix to the service manager core module. Compared to Release 4.1.1, Release 4.1.2 contains no functional changes.
4.1.3 (this release)	GGSN Service Manager 4.1.3 introduces no new functional changes. The difference between GGSN SM 4.1.2 and GGSN SM 4.1.3 is the underlying LMS platform. Release 4.1.2 uses the LMS 2.6 platform. Release 4.1.3 requires LMS 3.0, which includes updated versions of the RME (4.1) and CiscoView (6.1.6).

GGSN Service Activation

This section contains:

•IPv6 PDP Type

•QoS, SGSN, PLMN, and RAT Change Triggers for Charging Profile

•PLMN and RAT Change Triggers for DCCA Profile

IPv6 PDP Type

This feature enhances the APN Configuration screen in the 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 To create a new APN, choose Service Activation > APN.

The APN List appears. (See Figure 1.)

Figure 1 APN List

Step 2 Click Execute without selecting an APN.

The APN Wizard1 screen appears. (See Figure 2.)

Figure 2 APN Wizard1 Screen

Step 3 Enter the information, then click Next. The PPP Info entry screen (APN Wizard2) of the APN Wizard appears.

Step 4 Continue through to APN Wizard3 and APN Wizard4 by entering information and then clicking Next.

Step 5 The APN Wizard5 screen appears. (See Figure 3.)

Figure 3 APN Wizard5 Screen

Table 1 describes the fields in this screen.

Table 1 APN Wizard—Fields in the APN Wizard5 Screen 

Field	Description	Applies to version(s)
IPv6 Info
IPv6 PDP	Specifies the IPv6 Packet Data Protocol (PDP). Click one of the three radio buttons next to this field to choose one option: •Enable—Enables the IPv6 interface automatically. •Exclusive—Captures certain packets excluded. •None—Nothing selected.	7.0
IPv6 Address Pool	Specifies one of three dynamic address allocation methods for using the IPv6 address pools. Possible values are: •Disable—Disables the dynamic address allocation. •Local—Used in connection with IPv6 Local Pool to specify a locally configured IPv6 address pool. Note The Local text box is available only when the IPv6 Local Pool option is selected for the address pool. •Radius Client—Specifies that the IPv6 address pool is allocated by using a Radius server.	7.0
IPv6 Local Pool	Specifies a locally configured IPv6 address pool as the access-point IP address pool. This name can be up to 224 characters long.	7.0
IPv6 Uplink Access Group	Specifies the uplink access group name of the IPv6 access point. This name can be up to 224 characters long.	7.0
Downlink Access Group	Specifies the downlink access group name of the IPv6 access point. This name can be up to 224 characters long.	7.0
IPv6 Base Virtual Template Number	Specifies the virtual profiles by the IPv6 base virtual-template number. The range is between 1-1001.	7.0
IPv6 Primary DNS	Specifies the IP address of the IPv6 Primary DNS.	7.0
Secondary DNS	Specifies the backup IP address of the IPv6 Secondary DNS.	7.0
IPv6 Redirect	Specifies that the GGSN is to redirect traffic to an external IPv6 address. Possible values are: •All—Redirects all traffic. •Intermobile—Redirects mobile-to-mobile traffic.	7.0
Redirect IPv6 Address	Specifies the IPv6 address of the external device to which you want to redirect traffic.	7.0
IPv6 Security Verify	Specifies the security for the IPv6 to verify. Check the check box next to these fields to choose one option or both: •Destination—Specifies the destination of the traffic to be verified. •Source—Specifies the source of the traffic to be verified.	7.0

QoS, SGSN, PLMN, and RAT Change Triggers for Charging Profile

This feature enhances the Charging Profile Configuration screen in the GGSN SM. Four new check boxes have been added to the Charging Profile Service Activation window. 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:

•QoS

•SGSN

•PLMN

•RAT

Unchecking these options will remove the features from 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 To create a new charging profile, choose Service Activation > Charging Profile.

The GGSN Charging Profile List window appears. (See Figure 4.)

Figure 4 Charging Profile List Window

Step 2 Click Execute without selecting a profile.

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 The options that appear in Figure 5 differ depending on the version of the GGSN devices in the selected group. Different fields appear for different versions of GGSN. In Figure 5, the Charging Profile window includes the new options for GGSN 7.0.

---

Table 2 Features of the Charging Profile Configuration Window During Profile Creation 

Screen Area	Field, Check Box, or Button	Description	Applies to version(s)
Charging Profile section	Charging Profile No	Associates a default charging profile with an access point. This value 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 For configuring content postpaid plmn-change and content postpaid rat-change, the following CLI commands are prerequisite: gprs service aware, gprs charging service-record include plmn-id, and gprs charging service-record include rat.	7.0
	RAT-Change Trigger	Specifies that RAT changes trigger quota-reauthorization. Note See previous Note about PLMN-Change Trigger.	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 and 7.0.	5.2, 6.0, 7.0
	Volume Limit	Specifies the default volume threshold for post-paid users. This default 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 decisions 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 to fetch the configuration.	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 Duration Trigger	Clears the Duration trigger field.	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

Step 3 Enter your specifications, as appropriate, then click Next.

The Charging Profile configuration window displays the new configuration for confirmation.

---

PLMN and RAT Change Triggers for DCCA Profile

This feature enhances the DCCA Profile Configuration window in the GGSN SM. Two new check boxes have been added to the DCCA Profile Service Activation window. These check boxes are only visible for GGSN 7.0. Otherwise, they are absent from previous GGSN software releases.

The two new check boxes provide the following triggers for changing the DCCA profile:

•PLMN

•RAT

Unchecking 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 To create a new DCCA profile, choose Service Activation > DCCA Profile.

The DCCA Profile List window appears (see Figure 6).

Figure 6 DCCA Profile Window List

Step 2 Click Execute without selecting a profile.

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.

Table 3 Features of the DCCA Profile Window During Profile Creation 

Field or Check Box	Description
Profile Name	The GPRS DCCA profile name. This name can be up to 40 characters long. This is a required field. If you enter the name of an existing DCCA profile, a warning message appears. If you continue, your changes will overwrite the existing DCCA profile with that name.
Authorization	Defines the method list used to specify the Diameter AAA server groups. This name can be up to 239 characters long.
Credit Control	Configures the default Credit Control Failure Handling (CCFH) action to take on PDP contexts when a fault condition occurs. Possible values: •CONTINUE—Allows the PDP context and user traffic for the relevant category or categories to continue, regardless of the interruption. •TERMINATE—Terminates the PDP context and the CC session. This is the default. •RETRY—Allows the PDP context and user traffic for the relevant category or categories to continue.
Destination Realm	Specifies the destination realm to be sent in initial Credit Control Request (CCR) requests to the DCCA server. This name can be up to 235 characters long.
Timeout	Configures a timeout value (TX), in seconds. The DCCA client uses this parameter to monitor the communication of CCRs with a Diameter server. Possible values are 1-1,000.
QoS Change	Specifies that QoS changes trigger quota-reauthorization.
Session Failover	Specifies that a session should fail over to the alternate DCCA server.
SGSN Change	Specifies that SGSN changes trigger quota-reauthorization.
PLMN Change	Specifies that PLMN changes trigger quota-reauthorization.
RAT Change	Specifies that RAT changes trigger quota-reauthorization.

Batch Mode Scheduling

In previous releases, you used the Service Activation and Batch Mode features to deploy batch configurations to devices on demand. Release 4.1.1 introduced 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:

•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).

See the Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange 4.1.1, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, for information on this procedure.

Open Caveats and Workarounds

Table 4 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/pcgi-bin/Support/Bugtool/home.pl. You will be prompted to log in to Cisco.com.

---

Table 4 Open Caveats and Workarounds 

Bug ID	Summary	Workaround
CSCeh48597	Under load, configuration changes longer than desired.	None.
CSCsb79725	Tomcat process stopped running during GGSN SM post-FCS testing. This situation has a low probability of occurrence.	None.
CSCsb83338	Multiprocessor WAN Application Module (MWAM) deleted in DCR but still appears in the GGSN SM.	When you make changes in the DCR to devices that are members of a GGSN SM device group, delete and recreate that group.
CSCsg62533	The GGSN version display format is inconsistent between 6.0 and 7.0. When users have both GGSN 6.0 and 7.0 in DCR, the listed devices show "6" for GGSN 6.0 and "7.0.0" for GGSN 7.0.	None.

Supported Device Versions

Table 5 lists the devices that the GGSN SM supports.

Table 5 Supported Devices and Versions 

Device	Device Platform	Minimum Image/IOS on Device	Minimum IOS on Supervisor	Supervisor Platform
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 32 Sup 720

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/en/US/products/sw/cscowork/ps3992/products_device_support_tables_list.html

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/en/US/products/sw/iosswrel/ps5012/products_feature_guide_chapter09186a0080122d78.html#1020149

---

Note The MWC for Cisco Mobile Exchange has additional prerequisites. Refer to the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange Release 4.1.3, available at: http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html.

---

Required—Use of the GGSN SM requires you to:

1. Ensure that the IOS version of the Catalyst switch and the GGSN version match. See the Supported Device Matrix section in the Release Notes for Mobile Wireless Center for Cisco Mobile Exchange Release 4.1.3 at:

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

2. Enable GGSN service on the device. Without this service, the GGSN SM will not be able to identify the device as a Cisco GGSN device.

3. Configure GPRS Tunneling Protocol (GTP) encapsulation on the IOS device under the virtual template. This action is required for a device to function as a GGSN device.

4. Enable Simple Network Management Protocol (SNMP) so that the GGSN SM can check the version of the device.

5. Complete installation of the GGSN SM in the correct installation order. See the Release Notes for the Mobile Wireless Center for Cisco Mobile Exchange 4.1.3 at:

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

6. Ensure that the GGSN device to be configured has been added to the DCR and is managed by the RME Inventory Manager.

For more information on the RME inventory function, see the section "Adding and Troubleshooting Devices Using Device Management" in the User Guide for Resource Manager Essentials 4.1 (With LMS 3.0) at:

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

---

Note The gprs service aware command is a prerequisite for doing some service activations.

---

The Release Notes for Mobile Wireless Center for Cisco Mobile Exchange Release 4.1.3, http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html, contain 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. Complete all network preparation, such as configuring the required VLANs, VRFs, virtual templates, AAA servers, RADIUS server, and interface configurations, on all GGSN devices.

2. Complete all service preparation, such as enabling server farms and charging related configurations.

3. Configure load balancing.

Documentation Support

This section provides information on:

•Product Documentation and Related Documentation

•Additional Information Online

---

Note Cisco Systems sometimes updates printed and electronic documentation after original publication. Therefore, review the documentation on Cisco.com for any updates.

---

Product Documentation and Related Documentation

This section provides information on:

•Product Documentation

•Related Documentation

Product Documentation

Table 6 lists the available product documentation.

Table 6 Product Documentation 

Document Title	Cisco.com Location
User Guide for Gateway GPRS Support Node Service Manager 4.1	http://www.cisco.com/en/US/products/ps6454/ products_user_guide_list.html
Release Notes for Gateway GPRS Support Node Service Manager 4.1.3 (this document)	http://www.cisco.com/en/US/products/ps6454/prod_release_notes_list.html

Related Documentation

Table 7 lists the available related documentation.

Table 7 Related Documentation 

Document Title	Cisco.com Location
Release Notes for Mobile Wireless Center for Cisco Mobile Exchange 4.1.3	http://www.cisco.com/en/US/products/ps6401/prod_release_notes_list.html
The Gateway GPRS Support Node (GGSN) configuration guides	•For GGSN version 6.0, Cisco IOS Release 12.3(14)YU http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/ products_feature_guide_book09186a00804bf275.html •For GGSN version 6.0, Cisco IOS Release 12.4(2)XB http://www.cisco.com/en/US/products/ps6706/products_feature_guide_book09186a008069a742.html •For GGSN version 7.0 http://www.cisco.com/en/US/products/ps6706/products _feature_guide_book09186a0080788363.html
The CiscoWorks Common Services 3.1 documentation set	http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html
The Resource Manager Essentials (RME) 4.1 documentation set	http://www.cisco.com/en/US/products/sw/cscowork/ps2073/products_user_guide_list.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 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/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.