Release Notes for Cisco GGSN Release 7.0 on the Cisco MWAM, Cisco IOS Software Release 12.4 XG Releases
Available Languages
Table Of Contents
Release Notes for Cisco GGSN Release 7.0
on the Cisco MWAM,
Cisco IOS Software Release 12.4(9)XGTechnical Documentation Ideas Forum
Introduction to Cisco GGSN on the Cisco MWAM
Hardware and Software Requirements
Determining the Software Version
Upgrading to a New Software Release
Limitations, Restrictions, and Important Notes
GTP Session Redundancy Limitations, Restrictions, and Important Notes
Enhanced Service-Aware Billing Limitations, Restrictions, and Important Notes
New and Changed Information in Cisco IOS Release 12.4(9)XG5
New and Changed Information in Cisco IOS Release 12.4(9)XG4
New and Changed Information in Cisco IOS Release 12.4(9)XG3
New and Changed Information in Cisco IOS Release 12.4(9)XG2
New and Changed Information in Cisco IOS Release 12.4(9)XG1
New and Changed Information in Cisco IOS Release 12.4(9)XG
Cisco GGSN Caveats, Cisco IOS Release 12.4 XG
Caveats—Cisco IOS Release 12.4(9)XG5
Resolved Miscellaneous Caveats
Caveats—Cisco IOS Release 12.4(9)XG4
Caveats—Cisco IOS Release 12.4(9)XG3
Caveats—Cisco IOS Release 12.4(9)XG2
Caveats—Cisco IOS Release 12.4(9)XG1
Caveats—Cisco IOS Release 12.4(9)XG
Cisco MWAM Caveats—Cisco IOS Release 12.4 XG
Caveats—with Cisco IOS Release 12.4(9)XG5
Caveats—with Cisco IOS Release 12.4(9)XG3
Caveats—with Cisco IOS Release 12.4(9)XG2
Caveats—with Cisco IOS Release 12.4(9)XG1
Caveats—with Cisco IOS Release 12.4(9)XG
Cisco IOS Software Documentation Set
Documentation Roadmap for Implementing GGSN Release 6.0 on the Cisco MWAM
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco GGSN Release 7.0
on the Cisco MWAM,
Cisco IOS Software Release 12.4(9)XG
November 17, 2009
Cisco IOS Release 12.4(9)XG5
These release notes for the Cisco Gateway GPRS Support Node (GGSN) Release 7.0 on the Cisco Multi-processor WAN Application Module (MWAM) describe the enhancements provided in Cisco IOS Release 12.4(9)XG5. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.4(9)XG, see the "Cisco GGSN Caveats, Cisco IOS Release 12.4 XG" section and Caveats for Cisco IOS Release 12.4 T. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.4 located on Cisco.com.
Technical Documentation Ideas Forum
Suggest ways Cisco technical documentation can be improved and better serve your needs. Participate in the Technical Documentation Ideas forum at: http://www.cisco.com/go/techdocideas
Contents
These release notes describe the following topics:
•
Introduction to Cisco GGSN on the Cisco MWAM
•
•
•
•
•
•
Introduction to Cisco GGSN on the Cisco MWAM
The following sections describe Cisco GGSN and the Catalyst 6500 / Cisco 7600 Multi-processor WAN Application Module (MWAM).
Cisco GGSN Overview
Gateway GPRS support node (GGSN) is a service designed for Global System for Mobile Communications (GSM) networks. GSM is a digital cellular technology that is used worldwide, predominantly in Europe and Asia. GSM is the world's leading standard in digital wireless communications.
GPRS is standardized by the European Telecommunications Standards Institute (ETSI). The most common application of GPRS is expected to be Internet/intranet access. Cisco Systems' GPRS solution enables mobile wireless service providers to supply their mobile subscribers with packet-based data services in GSM networks.
GPRS introduces the following two new major network elements:
•
•
Combined 2.5G and 3G packet gateway support and interworking capability on the same node was introduced in Cisco GGSN Release 4.0.
Cisco MWAM Overview
With Cisco IOS Software Release 12.3(2)XB and later, Cisco GGSN software can run on the Cisco MWAM installed in a Catalyst 6500 series switch or Cisco 7600 series router.
The MWAM provides three processor complexes with dual processors used in two of the complexes and a single processor used in the remaining processor complex. This architecture provides five mobile wireless applications on one module.
The MWAM does not provide external ports but is connected to the switch fabric in the Catalyst 6500/Cisco 7600 chassis. An internal Gigabit Ethernet port provides an interface between each processor complex and the Supervisor module. Virtual Local Area Networks (VLANs) direct traffic from external ports via the Supervisor module to each mobile wireless application instance.
The MWAM provides an interface to the IOS image on the Supervisor module. The Supervisor module software enables a single session to be established to each application on the MWAM(s) in the chassis. Each session is used for configuring, monitoring, and troubleshooting application. For information on establishing sessions to mobile wireless application instances on the MWAM, refer to the Cisco Multi-Processor WAN Application Module Installation and Configuration Notes:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/cfgnotes/mwam_icn.htm
Note
The software image that provides the mobile wireless application feature is downloaded through the Supervisor module and distributed to each processor complex on the MWAM(s). The same image is installed on all the processors in the MWAM.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.4(9)XG5 and includes the following sections:
•
•
•
Memory Recommendations
Hardware and Software Requirements
Implementing Cisco GGSN Release 7.0 on the Cisco 7600 series Internet router platform requires the following hardware and software.
•
•
or
Cisco 7600 Series Supervisor Engine 32, with a Multilayer Switch Feature Card, running Cisco IOS Release 12.2(18)SXF or later.
For details on upgrading the Cisco IOS release running on the supervisor engine, refer to the Upgrading to a New Software Release" section in the Release Notes.
•
•
Note
GTP-Session Redundancy
In addition to the required hardware and software above, implementing GTP-Session Redundancy (GTP-SR) requires at minimum:
•
•
Enhanced Service-Aware Billing
In addition to the required hardware and software, implementing enhanced service-aware billing requires a Cisco Content Services Gateway (CSG) module in each Cisco 7600 series router. The CSGs must be running the same Cisco CSG software release, Release 3.1(3)C6(1) or later.
GTP Access Point Name-Aware Server Load Balancing
Support for GTP access point name (APN)-aware serer load balancing (SLB) requires Cisco IOS Release 12.2(18) SRB and later on the supervisor engine module.
Note
http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi
Determining the Software Version
To determine the version of Cisco IOS software running on your Cisco MWAM, log in to the router on one of the MWAM processors and enter the show version EXEC command:
Router# show versionCisco IOS Software, MWAM Software (MWAM-G8IS-M), Version 12.4(9)XG5, RELEASE SOFTWARE Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2008 by Cisco Systems, Inc.Upgrading to a New Software Release
For information on upgrading to a new software release, see the product bulletin Cisco IOS Software Upgrade Ordering Instructions located at:
http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm
Upgrading IOS Image on MWAM
For information on upgrading IOS images on the MWAM, refer to the Cisco Multi-Processor WAN Application Module Installation and Configuration Notes:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/cfgnotes/mwam_icn.htm
Note
Upgrading ROMMON Software
To perform an ROMMON software upgrade, use the procedure provided in the Cisco Multi-Processor WAN Application Module Installation and Configuration Notes.
Feature Support
Cisco IOS software is packaged in feature sets that consist of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. Each feature set contains a specific set of Cisco IOS features.
Caution
The feature set tables have been removed from the Cisco IOS Release 12.4 release notes to improve the usability of the release notes documentation. The feature-to-image mapping that was provided by the feature set tables is available through Cisco Feature Navigator.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
http://tools.cisco.com/RPF/register/register.do
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp
For frequently asked questions about Cisco Feature Navigator, see the FAQs at the following URL:
http://www.cisco.com/support/FeatureNav/FNFAQ.html
Determining Which Software Images (Feature Sets) Support a Specific Feature
To determine which software images (feature sets) in Cisco IOS Release 12.4 support a specific feature, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:
Step 1
Step 2
Step 3
Note
Repeat this step to add additional features. A maximum of 20 features can be chosen for a single search.
Step 4
Step 5
Step 6
Step 7
Determining Which Features Are Supported in a Specific Software Image (Feature Set)
To determine which features are supported in a specific software image (feature set) in Cisco IOS Release 12.4, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
MIBs
Current MIBs
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Limitations, Restrictions, and Important Notes
When using Cisco IOS Release 12.4(9)XG5, observe the following:
•
•
Note
The Cisco MWAM can support up to 60,000 IPv4 PDP contexts per GGSN instance, with a maximum of 300,000 IPv4 PDP contexts per MWAM on which five GGSNs are configured, and up to 8,000 IPv6 PDP contexts per GGSN instance, with a maximum of 40,000 IPv6 PDP contexts per MWAM on which five GGSN are configured.
•
•
•
•
•
•
–
–
–
!interface Virtual-Template1description GGSN-VTip unnumbered Loopback0encapsulation gtpno logging event link-statusgprs access-point-list gprsendGTP Session Redundancy Limitations, Restrictions, and Important Notes
When configuring GTP-SR, note the following additional limitations and restrictions:
•
•
•
•
•
•
–
–
–
•
When a PDP context is recreated on the Standby GGSN, the session timer is restarted with the elapsed time subtracted from the initial session timer value. Once the session expires on the Standby GGSN, the PDP context is deleted.
•
If a GGSN reload occurs, all counters are set back to zero.
•
•
•
For information on disabling GTP-SR, see the "Configuring GTP Session Redundancy" chapter of the Cisco GGSN Release 6.0 Configuration Guide.
•
Enhanced Service-Aware Billing Limitations, Restrictions, and Important Notes
When configuring a service-aware GGSN, note the following additional limitations and restrictions:
•
•
•
•
•
Specifically the SGSN N3*T3 must be greater than:
2 x RADIUS timeout + N x DCCA timeout + CSG timeout
where:
–
–
New and Changed Information
The following section lists new features and changed information in the Cisco IOS Release 12.4 XG releases:
•
•
•
•
•
•
New and Changed Information in Cisco IOS Release 12.4(9)XG5
There are no new implementations or behavior changes in Cisco IOS Release 12.4(9)XG5.
New and Changed Information in Cisco IOS Release 12.4(9)XG4
There are no new implementations or behavior changes in Cisco IOS Release 12.4(9)XG4.
New and Changed Information in Cisco IOS Release 12.4(9)XG3
There are no new implementations or behavior changes in Cisco IOS Release 12.4(9)XG3.
New and Changed Information in Cisco IOS Release 12.4(9)XG2
Support for the following new feature is introduced in Cisco GGSN Release 7.0, Cisco IOS Release 12.4(9)XG2:
•
To eliminate delays when deleting PDP contexts that occur because the SGSN is not responding to the delete PDP context requests, with Cisco IOS Release 12.4(9)XG2 and later, you can clear a PDP context without waiting for a response from the SGSN, or you can delete PDP contexts locally without sending a delete PDP context requests to the SGSN at all.
For detailed information about the Fast PDP Delete features, see the "Deleting Sessions" section in Chapter 3, "Configuring GTP Services on the GGSN" of the Cisco GGSN Release 7.0 Configuration Guide.
The following amendments and corrections will be made to the Cisco GGSN Release 7.0Configuration Guide:
General Documentation Change
The documentation states that when a change from a Standby to an Active GGSN occurs, all counters are set back to zero. However, this statement is incorrect.
Please note that if a switchover occurs, status counters, such as "cgprsAccPtSuccMsActivatedPdps," and some statistics counters will have a non-zero value that is the value of the counter at the time the switchover occurred. All other counters will be reset to zero.
If a GGSN reload occurs, all counters are set back to zero.
Configuring Diameter/DCCA Interface Support
In the "Configuring Diameter/DCCA Interface Support" section of the "Configuring Enhanced Service-Aware Billing" chapter, the Abort Session Request / Abort Session Answer messaging description should include the following:
•
Configuring the DCCA Client Process on the GGSN
In the "Configuring the DCCA Client Process on the GGSN" section of the "Configuring Enhanced Service-Aware Billing" chapter, the description for the ccfh command is incorrect.
Currently, the ccfh command description is incorrectly documented as follows:
The correct ccfh command description is the following:
The following amendments and corrections will be made to the Cisco GGSN Release 7.0 Command Reference:
General Documentation Change
The documentation states that when a change from a Standby to an Active GGSN occurs, counters are set back to zero. However, this statement is incorrect. Please note that some counters, such as "cgprsAccPtSuccMsActivatedPdps," are not set back to zero.
When a GGSN reload occurs, all counters are set back to zero.
The ccfh Command Description
The retry_terminate keyword option description in the ccfh command description is incorrect.
Currently, the retry_terminate keyword option is incorrectly documented as follows:
The correct description for the retry_terminate keyword option is as follows:
New and Changed Information in Cisco IOS Release 12.4(9)XG1
There are no new implementations or behavior changes in Cisco IOS Release 12.4(9)XG1.
New and Changed Information in Cisco IOS Release 12.4(9)XG
Support for the following new features is introduced in Cisco GGSN Release 7.0, Cisco IOS Release 12.4(9)XG:
•
The maximum number of authentication, authorization, and accounting (AAA) method lists supported by the GGSN has been increased to 500. This enables up to 500 access-points to each have their own AAA method list.
•
The IP local pool holdback timer enables you to configure the GGSN to wait a specific amount of time before returning a newly-released IP address to the local pool when using a local IP address pool for allocating addresses to mobile stations.
The hold back timer ensures that an IP address recently released when a PDP session was deleted is not re-assigned to another PDP context before the IP-to-user relationship has been deleted from all back-end components of the system.
•
Cisco GGSN supports IPv6 primary PDP context activation, and SGSN-initiated modification and deactivation procedures via IPv6 stateless autoconfiguration (as specified by RFC 2461 and RFC 2462). IPv6 over IPv4 tunnels configured on the Cisco 7600 supervisor engine module establish connectivity between isolated or remote IPv6 networks over an existing IPv4 infrastructure.
•
GTP APN-aware load balancing enables requests to be balanced across APNs. With GTP APN-aware load balancing, Cisco IOS SLB GTP maps that group APNs can be created and associated with a server farm under the virtual template. Multiple server farms can be defined in one virtual server, each supporting a different set of APNs.
•
The Cisco GGSN supports public land mobile network ID (PLMN-ID) and radio access technology (RAT) triggers for service-aware PDPs.
Note
•
New commands have been introduced or existing commands have been modified, to support the following featurettes introduced in Cisco GSSN Release 7.0, Cisco IOS Release 12.4(9)XG.
–
The new clear gprs statistics all command clears all global and per-APN GPRS statistics cleared by the following commands:
- clear gprs gtp statistics
- clear per-path statistics
- clear gprs access-point statistics all
- clear gprs service-aware statistics (includes CSG statistics)
- clear ggsn quota-server statistics
–
To assist in troubleshooting and diagnostics, the Cisco GGSN tracks various GTP global statistics on a per SGSN-path basis. These data path and control path counters can be displayed using the show gprs gtp path statistics remote-address privileged EXEC command.
Additionally, the GGSN can be configured to maintain a history for deleted paths. The data path and control path statistics for a deleted path can be displayed using the show gprs gtp path statistics history privileged EXEC command. To configure the maximum number of path entries for which you want the GGSN to maintain a history of the statistics, use the gprs gtp path history global configuration command.
For detailed information about the counters displayed using the show gprs gtp path statistics history command and the show gprs gtp path statistics command, refer to the command descriptions in the Cisco GGSN Command Reference.
•
To support IPv6 PDPs, the cgprsAccPtSecSrcViolNotif trap, sent when a security violation has occurred, has been enhanced to send the notifications for IPv6 PDPs in addition to IPv4 PDPs.
The IPv6 support requires that the ipv6 security verify source access-point configuration command has been configured.
Cisco GGSN Caveats, Cisco IOS Release 12.4 XG
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.
All caveats in Cisco IOS Release 12.4 and Cisco IOS Release 12.4 T are also in Cisco IOS Release 12.4(2)XG4.
For information on caveats in Cisco IOS Release 12.4, see Caveats for Cisco IOS Release 12.4.
http://www.cisco.com/en/US/products/ps6350/prod_release_notes_list.html
For information on caveats in Cisco IOS Release 12.4 T, see Caveats for Cisco IOS Release 12.4T, which lists severity 1 and 2 caveats and select severity 3 caveats and is located on Cisco.com and the Documentation CD-ROM.
http://www.cisco.com/en/US/products/ps6441/prod_release_notes_list.html
Note
Table 1 summarizes the Cisco IOS Release 12.4 XG caveat activity:
Caveats—Cisco IOS Release 12.4(9)XG5
This section contains the following types of caveats for the Cisco GGSN, Cisco IOS Release 12.4(9)XG5 maintenance release:
•
Open Caveats
There are no known caveats open in Cisco IOS Release 12.4(9)XG5, Cisco GGSN Release 7.0.
Resolved GGSN Caveats
The following GGSN caveats are resolved in the Cisco IOS Release 12.4(9)XG5 image. This section describes only severity 1 and 2 caveats, and select severity 3 and 4 caveats.
•
Description: The Cisco GGSN rejects Create PDP Context requests when more than 16Mb Guaranteed Bit Rate (GBR) is requested. This condition occurs only when the requested GBR is more than the supported bit rate for each PDP.
•
Description: Due to missing 3GPP specifications, the Cisco GGSN might mix two PDP sessions into one when one of the following scenarios occurs:
–
–
•
Description: Under rare condition, a fatal error may occur with GTP parsing of PPP.
Resolved Miscellaneous Caveats
The following miscellaneous caveats are resolved in the Cisco IOS Release 12.4(9)XG5 image. This section describes only severity 1 and 2 caveats, and select severity 3 and 4 caveats.
•
Description: A router running Cisco IOS may unexpectedly reload. The crashes can be very different in nature, but the crashinfo should show the IP Input process as the currently running process:
---- Partial decode of process block ----
Pid 84: Process "IP Input" stack 0x46C3C080 savedsp 0x46758540
This is seen when the router is configured for NAT and receives a fragmented skinny packet that it needs to reassemble and translate.
•
Description: The Open Shortest Path First (OSPF) process might receive a fatal error when the router receives invalid OSPF messages.
•
Description: A particular malformed OSPF message might cause the device to fail or operate unpredictably. This condition is seen when the OSPF receives a malformed OSPF message and the possible effects include the following:
–
–
–
–
•
Summary: A vulnerability exists in the Session Initiation Protocol (SIP) implementation in Cisco IOS® Software that could allow an unauthenticated attacker to cause a denial of service (DoS) condition on an affected device when the Cisco Unified Border Element feature is enabled.
Cisco has released free software updates that address this vulnerability. For devices that must run SIP there are no workarounds; however, mitigations are available to limit exposure of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml.
Note: The September 23, 2009, Cisco IOS Security Advisory bundled publication includes eleven Security Advisories. Ten of the advisories address vulnerabilities in Cisco IOS Software, and one advisory addresses a vulnerability in Cisco Unified Communications Manager. Each advisory lists the releases that correct the vulnerability or vulnerabilities detailed in the advisory. The following table lists releases that correct all Cisco IOS Software vulnerabilities that have been published on September 23, 2009, or earlier.
http://www.cisco.com/warp/public/707/cisco-sa-20090923-bundle.shtml
Individual publication links are in "Cisco Event Response: Semiannual Cisco IOS Software Advisory Bundled Publication" at the following link:
http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_sep09.html
•
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.
•
Cisco IOS Software configured with Authentication Proxy for HTTP(S), Web Authentication or the consent feature, contains a vulnerability that may allow an unauthenticated session to bypass the authentication proxy server or bypass the consent web page.
There are no workarounds that mitigate this vulnerability.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml
Caveats—Cisco IOS Release 12.4(9)XG4
This section contains the following types of caveats for the Cisco GGSN, Cisco IOS Release 12.4(9)XG4 maintenance release:
Open Caveats
This section documents possible unexpected behavior by Cisco IOS Release 12.4(2)XG4 and describes only severity 1 and 2 caveats and select severity 3 caveats.
There are no caveats are open in Cisco IOS Release 12.4(9)XG4, Cisco GGSN Release 7.0.
Resolved Caveats
The following caveats are resolved in Cisco IOS Release 12.4(9)XG4. This section describes only severity 1 and 2 caveats, and select severity 3 and 4 caveats.
•
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding. Cisco has released free software updates that address this vulnerability. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.
•
Description: The Cisco GGSN appears to not respond to node alive requests sent by the secondary charging gateways using a TCP path. Additionally, if the node alive request is sent over UDP from the active charging gateway, the GGSN sends the response over TCP, if the TCP link is up.
These conditions exist for charging gateways using a TCP path.
•
Multiple Cisco products are affected by denial of service (DoS) vulnerabilities that manipulate the state of Transmission Control Protocol (TCP) connections. By manipulating the state of a TCP connection, an attacker could force the TCP connection to remain in a long-lived state, possibly indefinitely. If enough TCP connections are forced into a long-lived or indefinite state, resources on a system under attack may be consumed, preventing new TCP connections from being accepted. In some cases, a system reboot may be necessary to recover normal system operation. To exploit these vulnerabilities, an attacker must be able to complete a TCP three-way handshake with a vulnerable system.
In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.
Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090908-tcp24.shtml.
•
Description: When a Cisco GGSN receives a Credit Control Answer (CCA) with a 5012 result code for a service, it does not correctly process the CCA, and keeps "service in waiting" for the CCA state, and doe not send any response to the CSG.
•
Description: If the user location information element (IE) is not received in a Create PDP Context request, the Cisco GGSN does not include USER-LOCATION-INFO AVP when requesting quota for a prepaid service.
This condition is seen when the user location information IE is not received in a Create PDP Context request even though the Routing Area Identity (RAI) is sent in the Create PDP Context request.
•
Description: Issuing the clear gprs statistics command when there are active PDP contexts might cause subsequent SNMP GETS for the cgprsAccPtActivePdps OID to report a value that is too high.
For example, if there are 100 active PDP contexts when the clear gprs statistics command is issued, and later these 100 active PDP contexts are disconnected, and even later, 50 new PDP contexts connect, the cgprsAccPtActivePdps will show 150 active PDP contexts while the show command will display the correct value of 50. Counters clear after a reload.
•
Description: The Cisco GGSN does not encode the International Mobile station Equipment Identity Software Version (IMEISV) value in the format required by the 3GPP Release 7 specification.
This condition is seen when a GTP message from the SGSN includes the IMEISV value.
Caveats—Cisco IOS Release 12.4(9)XG3
This section contains the following types of caveats for the Cisco GGSN, Cisco IOS Release 12.4(9)XG3 maintenance release:
Open Caveats
This section documents possible unexpected behavior by Cisco IOS Release 12.4(2)XG3 and describes only severity 1 and 2 caveats and select severity 3 caveats.
There are no caveats are open in Cisco IOS Release 12.4(9)XG3, Cisco GGSN Release 7.0.
Resolved Caveats
The following caveats are resolved in Cisco IOS Release 12.4(9)XG3. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Description: During a GGSN switchover, a Cisco RF-MIB trap is sent to the management station that indicates that the GGSN instance 1 changed its state: unit state is displayed as "negotiation," and the peer unit state is "disabled" when it should be "active." Also the ".1.3.6.1.4.1.9.9.176.2.0.1: Switch of activity occurred (cRFStatusUnitId=0, sysUpTime=31-8, ...." should not be expected when the switchover occurs.
•
Description: When a PDP context is created with a remote port other than the default port (2123/2152), the Cisco GGSN will not display path statistics. Also, the show gprs gtp path all command displays the wrong remote ports.
•
Description: The Cisco GGSN might not send the quotaPushFail trap when GGSN quota server debugging, enabled using the debug ggsn quota-server command, is disabled.
•
Description: The Cisco GGSN does not decrement the time-to-live (TTL) value before sending the packet towards the Gigabit interface.
This condition occurs when the IP packet is fragmented. If the IP packet is not fragmented, the GGSN decrements the TTL by 1 to 127 before sending it out to the Gigabit interface.
•
Description: On an access point (APN) enabled for PPP regeneration, creating an L2TP from the GGSN to the L2TP network server (LNS) shows inconsistent behavior in time-to-live (TTL) handling between the uplink and downlink.
Configuration: MS Client—SGSN—(GTP)—GGSN—(L2TP)—LNS
Scenario 1: The MS client sends an Internet Control Message Protocol (ICMP) packet with 1432 bytes of ICMP data. No IP fragmentation occurs.
Scenario 2: The MS client sends an ICMP packet with 1433 bytes of ICMP data. IP fragmentation occurs.
When packets from Scenario 2 enter the GTP tunnel or the L2TP tunnel, the total size is 1501 bytes and the packet must be fragmented by tunnel endpoints (the SGSN, GGSN, and LNS).
Protocol header calculation:
–
–
In the uplink direction, from the SGSN, to the GGSN, to the LNS, the TTL value of the packet is always 128 for Scenarios 1 and 2. So the TTL is not decreased at the GGSN. In the downlink direction, from the LNS, to the GGSN, to the SGSN, the behavior is different. In the case of Scenario 1, the TTL value is decreased by 1 by the GGSN. In the case of Scenario 2, the TTL is not changed by the GGSN. The TTL value stays the same.
•
Description: A Cisco router running the Cisco GGSN Release 7.0 software exhibits the following incorrect behavior when a protocol error is received in a CCA.
a.
b.
c.
•
Cisco IOS software configured for Cisco IOS firewall Application Inspection Control (AIC) with a HTTP configured application-specific policy are vulnerable to a Denial of Service when processing a specific malformed HTTP transit packet. Successful exploitation of the vulnerability may result in a reload of the affected device.
Cisco has released free software updates that address this vulnerability.
A mitigation for this vulnerability is available. See the "Workarounds" section of the advisory for details.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-iosfw.shtml.
•
A series of segmented Skinny Call Control Protocol (SCCP) messages may cause a Cisco IOS device that is configured with the Network Address Translation (NAT) SCCP Fragmentation Support feature to reload.
Cisco has released free software updates that address this vulnerability. A workaround that mitigates this vulnerability is available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sccp.shtml.
•
Description: On a Cisco MWAM running the Cisco GGSN software, if an SGSN does not include a recovery IE in its initial signaling requests, and then it includes the recovery IE in subsequent requests, the GGSN will initiate a path cleanup (deleting all existing PDPs on the path) because the path recovery changed.
This condition exists only when the SGSN does not include the recovery IE in the initial requests and includes it in subsequent requests.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities addressed in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to provide voice over IP services.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sip.shtml.
•
Description: On a Cisco router running the Cisco GGSN software, the router might reload during the rare situations when a heavy traffic load is occur along with the following conditions:
–
–
•
Description: The Cisco GGSN charging release configuration can be modified using the gprs charging release global configuration command while there are charging records pending in the system.
•
Description: The Cisco GGSN allows charging destination port to be changed using the gprs charging port command when there are CDRs in the pending queue or in a closed state.
•
Description: When there is data being processed through PDP contexts, and the contexts are deleted at the same time, the GGSN reloads. This condition occurs when the timing is within the few milliseconds the PDP is being deleted.
•
Description: The PDP create and last access time displayed in the output of the show gprs gtp pdp-context tid command becomes incorrect after two GGSN failovers.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities addressed in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to provide voice over IP services.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sip.shtml.
•
Description: The Cisco GGSN does not send pending CDRs from the pending queue to the charging gateway. This condition is seen when the TCP connection has terminated due to no response from charging gateway for the DTR and not even after subsequent node alives.
•
Description: On a Cisco MWAM processor running the Cisco GGSN application, there is a possibility of an input queue wedge on the GTP virtual access interface preventing data traffic for the affected APNs. This condition occurs only if the access point (APN) is configured with the redirect-all feature and the mobile station sends upstream packets with the TTL option in the IP header set to 1.
•
Description: If a mobile subscriber includes 3 B containing 0x0 at the end of the QoS IE, the GGSN logs the following message, and fails to establish a tunnel:
%GTP-0-GTPv1PACKETPARSINGERROR : GSN: GSN: [IP_address], TEID: [hex], APN: [chars], Reason:The mandatory IE is incorrect•
Description: If a Service-Auth request is received for a service in IDLE state while the PDPs are being deleted, the service-aware PDP contexts become stuck on the GGSN and cannot be deleted. This condition occurs only if the Service-Auth request is received for a service in IDLE state when a PDP is in the process of being deleted.
•
Description: On a Cisco router running the Diameter application, parsing of a capabilities exchange answer (CEA) fails if the Diameter server includes the origin-state-id attribute with the mandatory bit set.
This condition occurs only if the server includes the origin-state-id attribute with the mandatory bit set.
•
Description: On a Cisco router running the Diameter credit control application (DCCA), parsing of capabilities exchange answer (CEA) fails if the Diameter server includes the origin-state-id attribute with the mandatory bit set. Additionally, if the GGSN does not send the origin-state-id attribute in the credit control response (CCR) and the attribute is received in credit control answer (CCA), it is ignored.
These conditions occur only if the Diameter server includes the origin-state-id attribute with the mandatory bit.
•
Description: When reporting usage owing to the Quota Holding Timer (QHT) expiry, the Cisco GGSN includes the Requested-Service-Unit AVP in the Multiple Services Credit Control (MSCC).
This condition is seen when the GGSN is sending a CCR-Update owing to the QHT expiration.
Caveats—Cisco IOS Release 12.4(9)XG2
This section contains the following types of caveats for the Cisco GGSN, Cisco IOS Release 12.4(9)XG2 maintenance release:
Open Caveats
This section documents possible unexpected behavior by Cisco IOS Release 12.4(9)XG2 and describes only severity 1 and 2 caveats and select severity 3 caveats.
The following caveats are open in the Cisco IOS Release 12.4(9)XG2, Cisco GGSN Release 7.0.
•
Description: At bandwidths below 50 Mbps, packet drops are seen for IPV6 PDP contexts on GGSN.
With 8,000 PDP contexts across 500 VRF APNs with 16 IPv6 PDP's per VRF APN, these drops are seen as follows:
1. With 128-byte packet size, the drops occur at 7.2 Mbps.
2. With 256-byte packet size, drops occur at 11.1 Mbps.
3. With 512-byte packet size, drops are seen at 22.94 Mbps.
4. With 1400-byte packet size, drops are seen at 47.02 Mbps.
Workaround: There is currently no known workaround.
•
Description: A Cisco router running the Cisco GGSN Release 7.0 software exhibits the following incorrect behavior when a protocol error is received in a CCA.
a.
b.
c.
Workaround: There is currently no known workaround.
•
Description: When a CDR transfer fails, the charging gateway is not changed to an UNDEFINED state. This condition occurs when the path protocol is TCP and the charging gateway is brought down by shutting the interface.
Workaround: There is currently no known workaround.
Resolved Caveats
The following caveats are resolved in Cisco IOS Release 12.4(9)XG2. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Devices running Cisco IOS versions 12.0S, 12.2, 12.3 or 12.4 and configured for Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) or VPN Routing and Forwarding Lite (VRF Lite) and using Border Gateway Protocol (BGP) between Customer Edge (CE) and Provider Edge (PE) devices may permit information to propagate between VPNs.
Workarounds are available to help mitigate this vulnerability.
This issue is triggered by a logic error when processing extended communities on the PE device.
This issue cannot be deterministically exploited by an attacker.
Cisco has released free software updates that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-vpn.shtml.
•
Description: During the opening of 8000 PPP regenerated PDPs at 20 cps, the CPU reaches more than 90% after 5000 PDPs are opened.
•
Description: A Cisco GGSN passes IPv4 data of less than 100 Mbps. This condition occurs for packets less than 512 bytes when there are 500 VRFs.
•
Description: The "rcvd ipv6 signal msg" counter displayed in the show gprs gtp statistics command output is incremented twice when a duplicate GTPv1 IPv6 create PDP context request is received.
•
Description: The GGSN takes a long time to delete thousands of PDPs when the PDPs are cleared using the clear gprs gtp pdp-context command. This condition occurs when the SGSN does not respond to the delete PDP context requests sent by the GGSN.
For more information about the fix for this defect, see the "Configuring GTP Services on the GGSN" chapter of the Cisco GGSN Release 7.0 Configuration Guide.
•
Description: Fast deleting service-aware PDPs stops after the internal delete credit is reached (default 1000 PDPs).
This condition occurs with only service-aware PDPs when the no-wait-sgsn or the local-delete keyword options have been specified with the clear gprs gtp pdp-context access-point command and the SGSN is responding (not a condition for using the Fast PDP Delete feature).
•
Description: The counters that are displayed in the show gprs gtp path statistics remote-address command output that are related to roaming PDPs are not incremented. With this fix, three new counters, Roaming trusted PDPs, Roaming non-trusted PDPs, and Non-roaming PDPs replace the previous roaming PDP counter.
•
Description: When a Cisco GGSN is configured to allocate IP addresses for an APN from a RADIUS server, if the RADIUS server does not return an IP address for a particular user, there might be an incorrect syslog message displayed that indicates that no RADIUS server is available.
•
Description: When a GTP update request is received from an SGSN without a change of SGSN address or change of QoS, and with only any of the following attributes changes, ms-timezone, RAT, and User Location Info, the accounting interim record sent to the AAA server as part of the update request procedure does not include new values for these attributes.
•
Description: The "cef_up_byte" count in the show gprs gtp pdp tid command output for a PPP PDP which is terminating at the GGSN shows 4 bytes less. The upstream data count in the CDR also shows 4 bytes less. This condition is experienced only for a PPP PDP in a CEF path.
•
Description: The common counters for the uplink and downlink traffic PDUs are not incremented in the show gprs access-point statistics command output for IPv6 traffic.
•
Description: When redundant GGSNs and system accounting are configured, and the Active GGSN is reloaded using the reload command, the Active GGSN sends an Accounting-Off message to the AAA server. This condition occurs only when a redundant configuration exists, system accounting is enabled, and the reload command is issued on the Active GGSN.
•
Description: When a path is created without the recover information element (IE) being received from the SGSN, and the path is updated later with a valid recovery IE, the standby GGSN does not update the recover IE with the new value.
This condition occurs only if the SGSN is incapable of sending a recovery IE in the create PDP context request.
•
Description: When a PPP PDP (terminated on GGSN) is created with duplicate mobile IP address, the request is not rejected. This condition occurs only for PPP PDPs.
•
Description: On a Cisco router running the Cisco GGSN software, source and destination address validation of TPDUs is not occurring in the case of PPP-PDP terminating on the GGSN and PPP-regenerated PDPs when security verify source, destination, or access list is configured under APN. This validation is also not occurring when traffic is initiated from a network behind mobile station. This condition is observed when ip cef is configured.
•
Description: The GGSN allows the DCCA feature and the OCS server selection feature to be configured simultaneously. These features do not work together and the GGSN should print an error message to the screen when either one of the features is already configured and an attempt is made to configure the other.
•
Description: The Cisco GGSN Redirect All feature (enabled using the ipv6 redirect all access point configuration command) and the Redirect Inter-Mobile feature (enabled using the ipv6 redirect intermobile access point configuration command) do not work as expected for IPv6 PDP contexts.
•
Description: The no ipv6 ipv6-address-pool command does not negate the ipv6 ipv6-address-pool command configuration. Therefore, the dynamic address allocation method cannot be restored to the default value. This condition occurs when the no ipv6 ipv6-address-pool command is used.
•
Two crafted Protocol Independent Multicast (PIM) packet vulnerabilities exist in Cisco IOS software that may lead to a denial of service (DoS) condition. Cisco has released free software updates that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-multicast.shtml.
•
Description: When defining an IP SLA probe with a reaction event of TIMEOUT or CONNECTION LOSS and setting the probe to generate a trap, a syslog message is not generated when it should be.
•
Description: When the gprs radius attribute quota-server ocs-address global configuration command is configured and a prepaid PDP context is created with an external quota server interfacing with the Cisco CSG in a enhanced service-aware billing configuration, the service-aware details of the PDP context displays the DCCA profile name even though the DCCA is not used for this user.
•
Description: The ipv6 ipv6-access-group command's uplink and downlink keyword options are not registered correctly in the running configuration. Instead, the keywords "up" and "down" are used.
•
Description: The "redirect-all" counter displayed in the show gprs gtp pdp tid command output might not increment for IPv6 PDPs.
This condition occurs when IPv6 redirect is enabled on an APN.
•
Description: When a PDP context is created for a pre-paid APN, the encoding of quota push is incorrect and the PDP is held in a PENDING_QP category state. Therefore, there is no GTP response returned to the SGSN.
•
Description: Spurious memory access might be seen when configuring the encapsulation gtp command under the virtual template. Additionally, the gprs access-point-list command might not take effect.
This condition occurs when configuring GTP under the virtual template.
•
Description: The GGSN might reload while performing multiple SNMP operations.
•
Description: When a Neighbor Advertisement is sent by the GGSN in response to a unicast Neighbor Solicitation, the "S" bit in the response is not set.
This condition occurs when a Neighbor Solicitation is sent by an IPv6 PDP to the SGSN.
•
Description: The show gprs gtp pdp tid command display is incorrect for a PDP with a Release 98 QoS profile.
•
Description: When certain GGSN security features are enabled, GTP byte and packet counters are not updated correctly. Also, ICMP redirects are not sent in some cases.
•
Description: The MIB objects cgprsAccPtName and cgprsAccPtMsIsdnSuppressedValue might not accept a null string.
•
Description: When a Standby GGSN becomes active, and there is a pending PDP request, the GGSN doesn't clear the counter after it becomes active.
•
Description: When the Diameter server experiences delayed responses and the Cisco GGSN keeps generating new authorization requests, the Gi0/0 interface on the Cisco MWAM shows the input queue size increase all the way to the maximum value. This causes the GGSN to encounter a path failure to the SGSN and the active PDP contexts are deleted. This condition occurs only when responses from the Diameter server are delayed.
•
Description: The total data dropped counter does not increment for IPv6 PDPs. This condition occurs when a TPDU is dropped at the GGSN for an IPv6 PDP.
•
Description: The ACL matches counter does not increment for IPv6 PDPs. This condition occurs when an IPv6 ACL is added to an IPv6 APN in the downlink direction.
•
Description: The "ms init ipv6 pdp activation" counter displayed for access point statistics does not increment for GTPv0 IPv6 PDPs. This condition occurs only with GTPv0 IPv6 PDPs.
•
Description: The "unexpected_data_msg" counter increments incorrectly in the show gprs gtp statistics command output.
This condition occurs when data messages are dropped at the GGSN.
•
Description: When multiple PDPs with different IMSI s and the same MSIDNs are created on an APN using DHCP addressing, the second create PDP context request deletes the PDP on the Standby GGSN, but the PDP remains on the Active GGSN.
•
Description: The GGSN might not respond to an IPv6 router solicitation from the MS when IPv6 redirect is enabled. This condition occurs only when an IPv6 PDP is created on an APN which has the IPv6 redirect-all feature enabled.
•
Description: A Cisco GGSN responds to out-of-order GTP packets from the CSG for non-existent PDP contexts with a cause code of 201. This condition does not affect the correct functioning of the system, and occurs only when the CSG is experiencing periods of overload.
•
Description: SNMP small chunk leaks while setting the ACC-PT-MIB objects. This condition occurs when a "set" is performed for any of the objects belong to the cgprsAccPtTable and all the tables augmented to cgprsAccPtTable.
The chunk leaks can be observed by issuing the show memory deb leaks chunk command after a "set."
•
Description: When an APN is configured to generate a probe using the ip probe path command, when a PDP context is established, the following might occur:
1.
A downstream RLB does not have the framed-IP address when the probe arrives and will either drop (ip slb route framed-ip deny) the probe packet or forward it to the routing table. The FWLB behind the load-balanced real is respectively not populated, or incorrectly populated 50% (if there are two reals) of the time because the routing table will point to one load-balanced real address. If server-initiated traffic is generated before preceding client originated traffic, traffic will go to the wrong real 50% of the time.
2.
Regardless of IP address allocation (local pool or RADIUS server), the framed-IP address is available either in the access-accept message or the accounting-start message, and not in the access-request message. Therefore, there is no dynamic workaround.
•
Description: The "signalling_msg_dropped" counter in the gprs gtp statistics command output is not incremented and the GGSN does not process the packet further if the comprehension bit is not set.
This condition occurs when the GGSN processes messages with an unsupported extension header.
•
Description: On a Cisco router running the Cisco GGSN software, path history (show gprs gtp path history command) is not being deleted when a lower value is set using the gprs gtp path history global configuration command. This issue is seen when GPRS service is disabled and enabled again.
•
Description: The APN name might display with some junk characters in the running configuration when the object cgprsAccPtName is set to null through SNMP.
This condition occurs after setting cgprsAccPtName to null through SNMP.
•
Description: Traffic for PPP regenerated PDP fails with CEF.
•
Description: Incorrect response from the GGSN occurs for any traffic sent over TCP for the charging gateway.
•
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.
•
Description: %ALIGN-1-FATAL:Illegal access to a low address on signalling stress test
System crash and tracebacks occur during a signalling stress test (60,000 PDPs, send updates, perform handoffs, delete PDPs, and repeat). After several hours of this activity, the crash and tracebacks occurred.
•
Description: The behavior of the gprs slb vserver ip next-hop ip ip command and the corresponding MIB object cGgsnSlbVserNextHopAddress might be inconsistent.
•
Description: Setting cgprsCgPartialCdrGenEnableAll to true or false might not work as expected in certain scenarios.
•
Description: Tracebacks are seen (via the show alignment command) in the GGSN when GTPv0 PPP PDPs are created, and then, if the no service alignment detection command is configured, the GGSN crashes.
•
Description: Static PDPs are created without user-requested IPCP values.
•
Description: When a redirect request is sent from the primary charging gateway (CG) with a secondary CG as the address of the recommended node, the Cisco GGSN does not send the redirect response to the primary CG. The CG which sends the redirect request expects a redirection response from the GGSN, however the GGSN sends the redirection response to the recommended node. Therefore, there is a sequence number mismatch on the GTP header and the CG that sent the request goes into "waiting for a redirect response" state.
•
Description: The Cisco GGSN reports spurious memory access when the TCP socket use for charging functions is being cleared. This condition occurs only for the TCP charging path and when there are pending CDRs.
•
Description: On a Cisco router running the Cisco GGSN software, MS-requested primary and secondary DNS values are not honored. This condition is seen when the create PDP context request is for an IPv6 static PDP.
•
Description: On a Cisco MWAM running the Cisco GGSN software, if an ACL is configured under the APN for inspection of mobile traffic, and if this ACL includes the ttl option, the ACL will not be applied. This condition occurs only if the ACL is defined for inspection of ttl in the mobile IP packets.
•
Description: On a Cisco router running the Cisco GGSN software, when a create PDP context is received with an extension header to the GTP header, and the extension header has a length of 0 bytes, the GGSN might reload. The conditions that lead to this reload rarely occur.
•
Description: When a Redirection Request message is sent from the primary charging gateway, the GGSN does not send the Redirection Response message to the primary gateway and the "Redirect Resp Rcvd" field is not incremented.
•
Description: On a Cisco router running the Cisco GGSN software in redundant mode, after a switchover occurs, the newly active GGSN cannot forward traffic on PDP contexts that belong to some access point. This condition occurs only on a few APNs after a switchover from a current active to the standby GGSN occurs.
•
Description: The Fast Delete feature command options are not available when the GGSN is in global maintenance mode and the APNs are not in maintenance mode.
This condition occurs when the APNs are not in maintenance mode.
•
Description: On a Cisco MWAM running the Cisco GGSN software, if an Error-Indication is received from an SGSN on a GTPv1 path, which leads to PDP context deletion on the GGSN, the corresponding Accounting-Stop will have the Acct-Terminate-Cause as "Unknown," instead of "Nas-Error." This condition occurs only when an error-indication is received on a GTPv1 path. If the SGSN path is a GTPv0, the Acct-Terminate-Cause is "Nas-Error."
•
Description: The CDRs sent to the charging gateway accumulate volume counter values including values sent in prior CDRs. This condition occurs when the charging profile configured in the GGSN does not have SGSN change limit and when the configured send buffer limit is reached as a result of a sequence of SGSN change messages. The CDR is closed and sent but without reseting the counters.
Closed Caveat
The following caveat is closed in Cisco IOS Release 12.4(9)XG2.
•
Description: Throughput measurement for all IPv4 packet sizes differs base on two types of flows. This difference occurs when traffic is sent across 60,000 PDPs on the Cisco GGSN, created across 500 VRF APNs with 120 PDPs per VRF APN, at 80%:20% downstream:upstream.
–
–
Caveats—Cisco IOS Release 12.4(9)XG1
This section contains the following types of caveats for the Cisco GGSN, Cisco IOS Release 12.4(9)XG1 maintenance release:
Open Caveats
This section documents possible unexpected behavior by Cisco IOS Release 12.4(9)XG1 and describes only severity 1 and 2 caveats and select severity 3 caveats.
The following caveats are open in Cisco IOS Release 12.4(9)XG1, Cisco GGSN Release 7.0.
•
Description: A Cisco GGSN passes IPv4 data of less than 100 Mbps. This condition occurs for packets less than 512 bytes when there are 500 VRFs.
Workaround: Implement fewer VRFs.
•
Description: Throughput measurement for all IPv4 packet sizes differs base on two types of flows. This difference occurs when traffic is sent across 60,000 PDPs on the Cisco GGSN, created across 500 VRF APNs with 120 PDPs per VRF APN, at 80%:20% downstream:upstream.
–
–
Workaround: There is currently no known workaround.
•
Description: At bandwidths below 50 Mbps, packet drops are seen for IPV6 PDP contexts on GGSN.
With 8,000 PDP contexts across 500 VRF APNs with 16 IPv6 PDP's per VRF APN, these drops are seen as follows:
1. With 128-byte packet size, the drops occur at 7.2 Mbps.
2. With 256-byte packet size, drops occur at 11.1 Mbps.
3. With 512-byte packet size, drops are seen at 22.94 Mbps.
4. With 1400-byte packet size, drops are seen at 47.02 Mbps.
Workaround: There is currently no known workaround.
•
Description: A Cisco router running the Cisco GGSN Release 7.0 software exhibits the following incorrect behavior when a protocol error is received in a CCA.
a.
b.
c.
Workaround: There is currently no known workaround.
•
Description: A Cisco GGSN responds to out-of-order GTP packets from the CSG for non-existent PDP contexts with a cause code of 201. This condition does not affect the correct functioning of the system, and occurs only when the CSG is experiencing periods of overload.
Workaround: There is currently no known workaround.
Resolved Caveats
The following caveats are resolved in Cisco IOS Release 12.4(9)XG1. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Description: A Cisco MWAM processor crashes during bootup. This condition occurs during periods of high CPU from large amounts of information being printed on the processor (for example, when there is a lot of unsupported configuration), or when traffic is being sent while the processor is booting up.
•
Description: Starting calendar year 2007, daylight savings summer-time rules might cause Cisco IOS to generate timestamps (such as in syslog messages) that are off by one hour.
By default, the Cisco IOS configuration clock summer-time zone recurring command uses United States standards for daylight savings time rules. The Energy Policy Act of 2005 (H.R.6.ENR), Section 110 changes the start date from the first Sunday of April to the second Sunday of March, and it changes the end date from the last Sunday of October to the first Sunday of November.
•
Description: If the value of the SGSN PLMN-ID is not received from the SGSN, or is invalid, then the "sGSNPLMNIdentifier" information element (IE) with a value of "000000" is included in the ServiceRecord when it should be omitted from the ServiceRecord like it is with G-CDRs.
This condition occurs only if the value for the RAT type is valid and the value for the PLMN ID field is wrong. If the values for both the RAT type and PLMN ID fields are invalid, the ServiceRecord IE is processed correctly.
•
Description: When the Cisco GGSN generates a Diameter server "Up/Down" trap, the value for the Local ID field is missing when the name that was configured for the Diameter origin host should be used.
•
Description: Packet drops due to interface throttles are seen on the Cisco GGSN running the release 7.0 image. These throttles occur when bi-directional traffic of 70 Mbps, in the ratio of 1:4 upstream:downstream, is sent for over 60,000 IPv4 PDPs across 500 VRF APNs.
•
Description: The following SNMP MIBs are not functioning properly:
–
–
•
Description: When a create PDP context request with a static MS address that matches the ms-address of an already active PDP context on the GGSN is received, the GGSN deletes the existing PDP, and the newer PDP becomes the active PDP context.
This condition occurs only when a create PDP context request with a static ms-address that matches the ms-address of an already existing PDP context on the GGSN. The correct behavior would be for a duplicate IP address check to occur on the GGSN, and for a reject response to be sent to the SGSN for the offending create PDP context request.
•
Description: The DHCP lease values are invalid/wrong on the standby GGSN when create PDP context update is received on the GGSN for a PDP that is created on an APN on which DHCP addressing is configured.
This condition occurs only when a create PDP context update is received on the GGSN.
•
Description: An MWAM processor running as Cisco GGSN in a GTP-SR configuration might encounter a software exception during a failover.
This exception occurs with the following condition:
a.
b.
c.
d.
•
Description: The Cisco GGSN does not take into account the time that has elapsed when it reclaims an IP address which was still in a "hold" state. This condition occurs when DHCP is allocating the IP address and the session is torn down and brought back up just before the renewal 2 to 3 times.
Caveats—Cisco IOS Release 12.4(9)XG
This section documents possible unexpected behavior by Cisco IOS Release 12.4(9)XG and describes only severity 1 and 2 caveats and select severity 3 caveats.
The following caveats are open in Cisco IOS Release 12.4(9)XG, Cisco GGSN Release 7.0.
•
Description: While opening of 8,000 PPP Regen PDPs at 20cps on Cisco GGSN running the release 7.0 image, high CPU (more than 70%) is noticed when the number of opened sessions is close to 8000.
Workaround: There is currently no known workaround.
•
Description: When sending intermediate rate of data packets for all opened 8000 PPP Regen PDP contexts, the CPU is more than 90% on the Cisco GGSN running the release 7.0 image.
Workaround: There is currently no known workaround.
•
Description: During periods of a high rate of create/delete IP PDP contexts with the SGSN sending different restart counters, the Cisco GGSN running the release 7.0 image begins to experience some hanging mobile sessions. These hanging mobile sessions can be deleted by issuing the clear command from the GGSN. This condition rarely occurs.
Workaround: There is currently no known workaround.
•
Description: The GGSN quota interface to the CSG fails and the GGSN becomes nonfunctional for a few minutes. This condition occurs when low quota validity (for example, 60) is configured and a medium load (6,000 PDPs) with low traffic exists.
Workaround: There is currently no known workaround. If possible, avoid assigning low quota validity.
•
Description: During periods of overload conditions, the Cisco GGSN experiences a hanging SWIDB. This condition occurs during periods of heavy overload conditions, during which there is a mixture of IPv4 and IPv6 PDP contexts and the IPv6 sessions are close to twice the supported values.
Workaround: There is currently no known workaround.
•
Description: The Cisco GGSN, running the release 7.0 image, does not send a delete notification message to the Cisco IOS SLB when a PDP context is rejected because there is no memory available.
Workaround: There is currently no known workaround.
•
Description: The Cisco GGSN sends an Accounting Stop message with the cause value as "Lost Carrier." This condition occurs when the PDP context type is PPP PDP or PPP Regen.
Workaround: There is currently no known workaround.
•
Description: The Cisco GGSN sends periodic router advertisements (RAs) for IPv6 PDP contexts at the default interval of 200 seconds instead of the interval configured on the base virtual template.
Workaround: There is currently no known workaround.
•
Description: A couple of issues exist in the way the GGSN security feature is working when CEF is enabled (ip cef command) in the process path.
a.
When CEF is enabled, the CEF drop count is not incremented in the show gprs gtp pdp tid command output. The cef_drop count, rcv_pkt_count, and rcv_bytes_count counters are not incremented, as well as the corresponding counters displayed by the show gprs access-point and show gprs gtp statistics commands that reflect how much the GGSN received from the SGSN.
When CEF is disabled, for source addressing the user is being charged. Also, for GTPv1 PDP contexts, 70 bytes of data is being sent, but the show gprs gtp pdp tid and show gprs access-point statistics commands display the byte count as 74.
b.
When CEF is enabled, the user is not charged when they should be. The cef_drop count, rcv_pkt_count, and rcv_bytes_count counters are not incremented, as well as the corresponding counters displayed by the show gprs access-point and show gprs gtp statistics commands that reflect how much the GGSN received from the SGSN in the upstream.
When CEF is disabled, for GTPv1 PDP contexts, 70 bytes of data is being sent, but the show gprs gtp pdp tid and show gprs access-point statistics commands display the byte count as 74.
c.
When CEF is not enabled, the GGSN sends an ICMP redirect message to the MS. When CEF is enabled, no message is sent.
d.
No ICMP redirect is sent back to the MS with or without CEF enabled.
•
Description: When the object cgprsAccPtPdpInServicePolicyName is set to a value, the resulting configuration on the GGSN may be incorrect. Also, a "get" on this object might not return any value. When deconfigured, spurious access may be seen. This condition occurs when the cgprsAccPtPdpInServicePolicyName is set to a value.
Workaround: There is currently no known workaround.
•
Description: The Cisco GGSN might throw spurious memory errors and reload while unconfiguring the service-policy under the APN and policy maps through SNMP.
Workaround: There is currently no known workaround.
•
Description: The show ip local pool command output, without a pool name, may have an empty line as the first line.
Workaround: There is currently no known workaround.
Cisco MWAM Caveats—Cisco IOS Release 12.4 XG
This section lists the Cisco MWAM caveats that are open and resolved with the Cisco GGSN Release 7.0, Cisco Release 12.4 XG releases.
Caveats—with Cisco IOS Release 12.4(9)XG5
This section contains the following types of Cisco MWAM caveats as they apply to the Cisco GGSN Release 7.0, Cisco IOS Release 12.4(9)XG5 maintenance release:
Open Caveat
The following caveat is open with Cisco IOS Release 12.4(9)XG5.
•
Description: When booting multiple MWAMs on the chassis, the link status traps conveying Up, Down are sometimes seen in a different order for each module.
Workaround: There is currently no known workaround.
Resolved Caveats
The following caveats are resolved with Cisco IOS Release 12.4(9)XG3.
•
Description: The Cisco MWAM processor reloads when all the VTY lines are used and a command is executed on the supervisor remotely using the MWAM Remote Console and Logging (RCAL) feature.
The output of the command does not display on the supervisor console. Instead, the output is printed on the MWAM processor console, and after the display is complete, the MWAM processor reloads.
This condition occurs when all the VTY lines are in use. If only a few are in use, then the RCAL feature works as designed and the output is displayed on the supervisor console.
•
Description: Executing a command on a Cisco MWAM processor remotely from the supervisor (using the execute-on command, Remote Console and Logging [RCAL] feature) causes packet buffer leak on the processor. Memory from middle buffer pool allocated for this is not released.
This buffer leak occurs when commands are executed remotely from the supervisor on the MWAM processor using the execute-on command.
Caveats—with Cisco IOS Release 12.4(9)XG3
This section contains the following types of Cisco MWAM caveats as they apply to the Cisco GGSN Release 7.0, Cisco IOS Release 12.4(9)XG3 maintenance release:
Open Caveat
The following caveat is open with Cisco IOS Release 12.4(9)XG3.
•
Description: When booting multiple MWAMs on the chassis, the link status traps conveying Up, Down are sometimes seen in a different order for each module.
Workaround: There is currently no known workaround.
Resolved Caveats
The following caveats are resolved with Cisco IOS Release 12.4(9)XG3.
•
Description: The Cisco MWAM processor reloads when all the VTY lines are used and a command is executed on the supervisor remotely using the MWAM Remote Console and Logging (RCAL) feature.
The output of the command does not display on the supervisor console. Instead, the output is printed on the MWAM processor console, and after the display is complete, the MWAM processor reloads.
This condition occurs when all the VTY lines are in use. If only a few are in use, then the RCAL feature works as designed and the output is displayed on the supervisor console.
•
Description: Executing a command on a Cisco MWAM processor remotely from the supervisor (using the execute-on command, Remote Console and Logging [RCAL] feature) causes packet buffer leak on the processor. Memory from middle buffer pool allocated for this is not released.
This buffer leak occurs when commands are executed remotely from the supervisor on the MWAM processor using the execute-on command.
Caveats—with Cisco IOS Release 12.4(9)XG2
This section contains the following types of Cisco MWAM caveats as they apply to the Cisco GGSN Release 7.0, Cisco IOS Release 12.4(9)XG2 maintenance release:
Open Caveats
The following caveats are open with Cisco IOS Release 12.4(9)XG2.
•
Description: When you reset several MWAM modules, a few of them might go to a PowerDown state with the:
%C6KPWR-SP-X-DISABLED: power to module in slot 5 set off (Module Failed SCP dnld)message on the supervisor engine console.
Workaround: Power enable the module with the hw-module module module-number reset command. If it does not enable the card, issue the power enable module module-number command while in configuration mode.
•
Description: The session from the supervisor engine to the SiByte processor on the MWAM is lost if the no ip routing command is executed and a default gateway is configured on the processor.
This condition occurs only when IP routing and a default gateway are configured and the no ip routing command is executed.
Workaround: Log into the processor control (PC) complex on the MWAM and reset the processor.
•
Description: While remotely executing commands on the MWAM processors from the supervisor engine, a debuginfo file might be written to the supervisor engine bootflash and the remote console operation might abort. If this condition occurs, memory fragmentation, malloc failure messages, and tracebacks might also be seen.
This condition occurs when the output of the remote command operation is very large.
Workaround: Possible alternatives that can be used include the following:
a.
b.
c.
•
Description: When booting multiple MWAMs on the chassis, the link status traps conveying Up, Down are sometimes seen in a different order for each module.
Workaround: There is currently no known workaround.
•
Description: When using the execute-on command to an MWAM processor, the supervisor engine returns an error in the format of:
%Command to slot <slot> cpu <MWAM processor number> already busy, retry laterThis condition happens randomly and a processor might stay in the same state for days. There is no command pending for execution to the affected MWAM processor, even though the show logging slot command shows the affected processors have "command-Active:Yes" at the same time.
Workaround: Reset the entire MWAM.
•
Description: The upgrade rom-monitor command displays an "ambiguous error" when the invalidate keyword option is not specified, even thought the invalidate keyword option is the only upgrade rom-monitor command option.
Workaround: Specify the upgrade rom-monitor command with the invalidate keyword option.
•
Description: The Cisco GGSN running on an MWAM processor completely lose its configuration when certain conditions occur. This loss occurs when the processor is in local configuration mode, the GGSN Release 7.0 image is loaded with the GGSN Release 7.0 configuration and then the image is changed to a GGSN Release 6.0 image, and the configuration is saved by issuing the write memory command.
Workaround: Do not switch between GGSN Release 6.0 and Release 7.0 images from local-config mode and download the startup configuration via TFTP.
Resolved Caveats
There have been no Cisco MWAM caveats resolved for Cisco IOS Release 12.4(9)XG2.
Caveats—with Cisco IOS Release 12.4(9)XG1
This section contains the following types of Cisco MWAM caveats as they apply to the Cisco GGSN, Cisco IOS Release 12.4(9)XG1 maintenance release:
Open Caveats
This following caveats are open with Cisco IOS Release 12.4(9)XG1.
•
Description: When you reset several MWAM modules, a few of them might go to a PowerDown state with the:
%C6KPWR-SP-X-DISABLED: power to module in slot 5 set off (Module Failed SCP dnld)message on the supervisor engine console.
Workaround: Power enable the module with the hw-module module module-number reset command. If it does not enable the card, issue the power enable module module-number command while in configuration mode.
•
Description: The session from the supervisor engine to the SiByte processor on the MWAM is lost if the no ip routing command is executed and a default gateway is configured on the processor.
This condition occurs only when IP routing and a default gateway are configured and the no ip routing command is executed.
Workaround: Log into the processor control (PC) complex on the MWAM and reset the processor.
•
Description: While remotely executing commands on the MWAM processors from the supervisor engine, a debuginfo file might be written to the supervisor engine bootflash and the remote console operation might abort. If this condition occurs, memory fragmentation, malloc failure messages, and tracebacks might also be seen.
This condition occurs when the output of the remote command operation is very large.
Workaround: Possible alternatives that can be used include the following:
a.
b.
c.
•
Description: When booting an MWAM, Admin Down messages are received for the internal interfaces Gig8/1, Gig8/2, Gig8/3 for the MWAM on slot 8. These interfaces are internal interfaces that cannot be configured by the user for disabling traps. Therefore the interfaces should be always shown as Admin Up, and Admin down traps should not be sent.
Additionally, when booting different MWAMs on the chassis, the link status traps conveying Up, Down, and Admin Down (which should not be seen) are seen coming in different order for each module. These traps are seen for the internal interface of each MWAM when the MWAM is reset.
Workaround: There is currently no known workaround.
•
Description: The MWAM is unable to see the supervisor engine as its CDP neighbor. This condition occurs when CDP is enabled on the subinterfaces of the MWAM. While the MWAM is unable to see the supervisor engine as its CDP neighbor, the MWAM subinterface is seen in the supervisor engine's CDP neighbor table.
Workaround: Enable CDP on the main interface, not the subinterfaces.
•
Description: When using the execute-on command to an MWAM processor, the supervisor engine returns an error in the format of:
%Command to slot <slot> cpu <MWAM processor number> already busy, retry laterThis condition happens randomly and a processor might stay in the same state for days. There is no command pending for execution to the affected MWAM processor, even though the show logging slot command shows the affected processors have "command-Active:Yes" at the same time.
Workaround: Reset the entire MWAM.
•
Description: The upgrade rom-monitor command displays an "ambiguous error" when the invalidate keyword option is not specified, even thought the invalidate keyword option is the only upgrade rom-monitor command option.
Workaround: Specify the upgrade rom-monitor command with the invalidate keyword option.
•
Description: The Cisco GGSN running on an MWAM processor completely lose its configuration when certain conditions occur. This loss occurs when the processor is in local configuration mode, the GGSN Release 7.0 image is loaded with the GGSN Release 7.0 configuration and then the image is changed to a GGSN Release 6.0 image, and the configuration is saved by issuing the write memory command.
Workaround: Do not switch between GGSN Release 6.0 and Release 7.0 images from local-config mode and download the startup configuration via TFTP.
Resolved Caveats
There have been no Cisco MWAM caveats resolved for Cisco IOS Release 12.4(9)XG1.
Caveats—with Cisco IOS Release 12.4(9)XG
This section contains the following types of Cisco MWAM caveats as they apply to the Cisco GGSN, Cisco IOS Release 12.4(9)XG maintenance release:
Open Caveats
The following caveats are open with Cisco IOS Release 12.4(9)XG.
•
Description: When you reset several MWAM modules, a few of them might go to a PowerDown state with the:
%C6KPWR-SP-X-DISABLED: power to module in slot 5 set off (Module Failed SCP dnld)message on the supervisor engine console.
Workaround: Power enable the module with the hw-module module module-number reset command. If it does not enable the card, issue the power enable module module-number command while in configuration mode.
•
Description: The session from the supervisor engine to the SiByte processor on the MWAM is lost if the no ip routing command is executed and a default gateway is configured on the processor.
This condition occurs only when IP routing and a default gateway are configured and the no ip routing command is executed.
Workaround: Log into the processor control (PC) complex on the MWAM and reset the processor.
•
Description: While remotely executing commands on the MWAM processors from the supervisor engine, a debuginfo file might be written to the supervisor engine bootflash and the remote console operation might abort. If this condition occurs, memory fragmentation, malloc failure messages, and tracebacks might also be seen.
This condition occurs when the output of the remote command operation is very large.
Workaround: Possible alternatives that can be used include the following:
a.
b.
c.
•
Description: Upon booting an MWAM, Admin Down messages are received for the internal interfaces Gig8/1, Gig8/2, Gig8/3 for the MWAM on Slot 8. These interfaces are internal interfaces that cannot be configured by the user for disabling traps. Therefore the interfaces should be always shown as Admin Up, and Admin down traps should not be sent.
Additionally, on booting different MWAMs on the chassis, the link status traps conveying Up, Down (and Admin Down which should not be seen) are seen coming in different order for each module.
These traps are seen for the internal interface of each MWAM when the MWAM is reset.
Workaround: There is currently no known workaround.
•
Description: The MWAM is unable to see the supervisor engine as its CDP neighbor. This condition occurs when CDP is enabled on the subinterfaces of the MWAM. The MWAM is unable to see the supervisor engine as its CDP neighbor, however, the MWAM subinterface is seen in the supervisor engine's CDP neighbor table.
Workaround: Enable CDP on the main interface, not the subinterfaces.
•
Description: When using the execute-on command to an MWAM processor, the supervisor engine returns an error in the format of:
%Command to slot <slot> cpu <MWAM processor number> already busy, retry laterThis condition starts happening randomly and a processor may stay in the same state for days. There is no command pending for execution to the affected MWAM processor, even though the show logging slot command shows the affected processors have "command-Active:Yes" at the same time.
Workaround: Reset the entire MWAM.
•
Description: The upgrade rom-monitor command displays an "ambiguous error" when the invalidate keyword option is not specified, even thought the invalidate keyword option is the only upgrade rom-monitor command option.
Workaround: Specify the upgrade rom-monitor command with the invalidate keyword option.
•
Description: The Cisco GGSN running on an MWAM processor completely lose its configuration when certain conditions occur. This loss occurs when the processor is in local configuration mode, the GGSN Release 7.0 image is loaded with the GGSN Release 7.0 configuration and then the image is changed to GGSN Release 6.0, and the configuration is saved by issuing the write memory command.
Workaround: Do not switch between GGSN Release 6.0 and Release 7.0 images from local-config mode and download the startup configuration via TFTP.
Resolved Caveats
There have been no Cisco MWAM caveats resolved for Cisco IOS Release 12.4(9)XG.
Related Documentation
Except for feature modules, documentation is available as printed manuals or electronic documents. Feature modules are available online on CCO and the Documentation CD-ROM.
Use these release notes with these documents:
•
Release-Specific Documents
The following documents are specific to Release 12.3 and are located on CCO and the Documentation CD-ROM:
•
•
On CCO at:
Technical Support and Documentation: Technical Support and Documentation: Cisco IOS Software: Cisco IOS Software Releases 12.4 Mainline: Release Notes: Cross-Platform Release Notes
•
See Caveats for Cisco IOS Release 12.4 and Caveats for Cisco IOS Release 12.4T, which contain caveats applicable to all platforms for all maintenance releases of Release 12.4 and Release 12.4T.
On CCO at:
Technical Support and Documentation: Technical Support and Documentation: Cisco IOS Software: Cisco IOS Software Releases 12.4 T: Release Notes: Cross-Platform Release Notes
Note
•
Technical Support and Documentation: Technical Support and Documentation: Cisco IOS Software: Cisco IOS Software Mainline
Platform-Specific Documents
These documents are available for the Catalyst 6500/Cisco 7600 series platforms on Cisco.com and the Documentation CD-ROM:
•
•
–
–
–
•
–
–
–
Catalyst 6500 Series Switch Documentation is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm
Cisco 7600 Series Routers Documentation is available at the following URL:
http://www.cisco.com/en/US/products/hw/routers/ps368/products_installation_guides_books_list.html
Cisco IOS Software Documentation Set
The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that are shipped with your order in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed versions.
Documentation Modules
Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference. Chapters in a configuration guide describe protocols, configuration tasks, Cisco IOS software functionality, and contain comprehensive configuration examples. Chapters in a command reference provide complete command syntax information. Use each configuration guide with its corresponding command reference.
On CCO at:
Technical Support and Documentation: Technical Support and Documentation: Cisco IOS Software: Cisco IOS Software Releases 12.4 Mainline: Command References
Technical Support and Documentation: Technical Support and Documentation: Cisco IOS Software: Cisco IOS Software Releases 12.4 Mainline: Configuration Guides
Note
Documentation Roadmap for Implementing GGSN Release 6.0 on the Cisco MWAM
The following sections list related documentation (by category and then by task) that will be useful when implementing a Cisco GGSN on the Cisco MWAM platform.
General Overview Documents
Core Cisco 7609 Documents:
http://cisco.com/en/US/products/hw/routers/ps368/tsd_products_support_series_home.html
Navigating from Cisco.com:
Technical Support and Documentation: Technical Support and Documentation: Routers: Cisco 7600 Series Routers
Documentation List by Task
For the most up-to-date list of documentation on the Cisco 7600 series router, refer to the Cisco 7600 Series Routers Documentation Roadmap on Cisco.com at:
http://cisco.com/en/US/products/hw/routers/ps368/products_documentation_roadmap09186a00801ebed9.html
Getting Started
•
http://cisco.com/en/US/products/hw/routers/ps368/products_quick_start09186a0080092248.html
•
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/rcsi/index.html
Unpack and install the Cisco 7609 router:
•
http://cisco.com/en/US/products/hw/routers/ps368/products_installation_guide_book09186a008007e036.html
Install the Supervisor module and configure the router (basic configuration—VLANs, IP, etc.) using the following documentation:
•
http://cisco.com/en/US/products/hw/routers/ps368/products_module_installation_guide_book09186a008007cd9d.html
•
Install and complete the basic Cisco MWAM configuration:
•
http://cisco.com/en/US/products/hw/routers/ps368/products_module_installation_guide_book09186a008007cd9d.html
•
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/cfgnotes/mwamicn/index.htm
Download the Cisco IOS software image containing the GGSN feature set and configure the GGSNs on the MWAM:
•
http://cisco.com/en/US/products/sw/wirelssw/ps873/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, 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
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Release Notes for Cisco GGSN Release 7.0 on the Cisco MWAM, Cisco IOS Release 12.4(15)XG5
Copyright © 2009 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)