Table Of Contents
Introduction to GGSN 4.0 on the Cisco MWAM
Hardware and Software Requirements
Determining the Software Version
Upgrading to a New Software Release
Limitations, Restrictions, and Important Notes
New Implementations and Behavior Changes in Cisco IOS Release 12.3(2)XB1
Bulk Storage of MWAM Configurations on Supervisor Bootflash and Remote Console for MWAMs
3GPP RADIUS Attributes Support for PPP PDP Contexts
Support for Sending MSISDN to LNS for PPP-Regeneration
Caveats with Cisco IOS Release 12.3(2)XB1
Cisco MWAM Caveats with Cisco IOS Release 12.3(2)XB1
Cisco IOS Software Documentation Set
Release 12.3 Documentation Set
Documentation Roadmap for Implementing GGSN Release 4.0 on the Cisco MWAM
Obtaining Technical Assistance
Release Notes for GGSN 4.0 on the
Catalyst 6000 / Cisco 7600 MWAM for
Cisco IOS Software Release 12.3(2)XB1
December 11, 2003
Cisco IOS Release 12.3(2)XB1
OL-5266-01
These release notes for the Cisco GGSN 4.0 on the Cisco Multi-processor WAN Application Module (MWAM) describe the enhancements provided in Cisco IOS Release 12.3(2)XB1. These release notes are updated as needed.
For a list of the software caveats that apply to Cisco IOS Release 12.3(2)XB1, see the "Caveats with Cisco IOS Release 12.3(2)XB1" section and Caveats for Cisco IOS Release 12.3 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.2 located on Cisco.com and the Documentation CD-ROM.
Documentation Survey
Is Cisco documentation helpful? Click here to give us your feedback or go to the following URL to give us your feedback:
http://www.cisco.com/warp/public/732/docsurvey/rtg/ to give us your feedback .Contents
These release notes describe the following topics:
•
Introduction to GGSN 4.0 on the Cisco MWAM
•
•
•
•
•
•
Introduction to GGSN 4.0 on the Cisco MWAM
The following sections describe GGSN 4.0 and the Catalyst 6500 / Cisco 7600 Multi-processor WAN Application Module (MWAM).
GGSN 4.0 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:
•
•
The GGSN R4.0 release provide the combined 2.5G and 3G packet gateway support and interworking capability on the same node. For more information about the features available in GGSN 4.0, refer to the following URL:
Cisco MWAM Overview
With Cisco IOS Software Release 12.3(2)XB and later, GGSN 4.0 can run on the Cisco MWAM.
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.3(2)XB1 and includes the following sections:
•
•
•
Memory Recommendations
Hardware and Software Requirements
Cisco IOS Release 12.3(2)XB1 requires the following hardware and software:
•
•
With Cisco IOS Release 12.2(14)ZA5 on the Supervisor, GGSN 4.0 supports the "Bulk Storage of MWAM Configurations on Supervisor Bootflash" and "Remote Console for MWAMs" features.
•
Note
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 Internetwork Operating System SoftwareIOS (tm) MWAM Software (MWAM-G4JS-M), Version 12.3(2)XB1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)TAC Support: http://www.cisco.com/tacCopyright (c) 1986-2002 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.
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.3(2)XB1 with the Cisco MWAM, observe the following:
•
•
•
•
•
•
GGSN <config># ppp hold-queue queue-size
The recommended queue-size is 20k to 50k.
•
New Implementations and Behavior Changes in Cisco IOS Release 12.3(2)XB1
The following sections describe new implementations and behavior changes since the last release of the Cisco IOS GGSN software.
Bulk Storage of MWAM Configurations on Supervisor Bootflash and Remote Console for MWAMs
When Cisco IOS Release 12.2(14)ZA5 or higher is installed on the Catalyst 6500 / Cisco 7609 Supervisor module, this release of GGSN 4.0 (Cisco IOS 12.3(2)XB1) supports the "Bulk storage of MWAM Configurations on the Supervisor Bootflash" and "Remote Console for MWAM" features.
For detailed information on these MWAM features, see the Cisco MWAM Installation and Configuration Note at:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/cfgnotes/servmod/mwam_icn.htm
Packet of Disconnect
In previous releases, the IMSI and NASPI attributes were mandatory in the Packet of Disconnect (POD) request to identify every session. In Cisco IOS Release 12.3(2)XB1 and later, these two attributes are no longer mandatory.
Additionally, in Cisco IOS Release 12.3(2)XB1 and later, the Acct-Session-Id attribute is supported in the POD.
Route Probe
With this release, once a PDP context has been established, the GGSN can send a route probe to a specified destination. The source IP address of the probe packet is the PDP context IP address.
To enable the route probe feature, issue the following command while in global configuration mode:
ip probe path address protocol udp [ port port ttl ttl ]
Note
L2TP over VRF
Note
With Cisco IOS Release 12.3(2)XB1, the GGSN supports VRF-aware L2TP.
When using VRF-aware L2TP, when GTP tries to open an L2TP tunnel for a PPP context on an APN, it initiates a tunnel with the LNS at the address within the address range of the VRF configured. Once this tunnel is established, all subsequent L2TP-encapsulated packets are sent within this VRF.
Note
Configuration Example
GGSN Configuration
The following is the configuration example for multiple APNs in different L2TP VRFs.
!ip vrf apn-vrf1rd 1:1!ip vrf apn-vrf2rd 1:2!interface Gi1ip forwarding vrf apn-vrf1ip address 1.1.1.2 255.255.0.0!interface Gi2ip forwarding vrf apn-vrf2ip address 2.1.1.2 255.255.0.0!vpdn-group 1request-dialinprotocol l2tpdomain www.apn1.cominitiate-to ip 1.1.1.1vpn vrf apn-vrf1!vpdn-group 2request-dialinprotocol l2tpdomain www.apn2.cominitiate-to ip 2.1.1.1vpn vrf apn-vrf2!gprs access-point-list gprsaccess-point 1access-point-name www.apn1.comvrf abc1!access-point 2access-point-name www.apn2.comvrf abc2!RADIUS Configuration
Note
The following is a configuration example of the tunnel configurations on the RADIUS server:
www.apn1.com Password = "cisco"Service-Type = Outbound-User,cisco-avpair = "vpdn:tunnel-type=l2tp",cisco-avpair = "vpdn:ip-addresses=1.1.1.1",cisco-avpair = "vpdn:vpn-vrf=apn-vrf1"Limitations
When using the L2TP over VRF feature, the following limitations apply:
1.
2.
3.
TFTP/FTP over VRF
Note
With Cisco IOS Release 12.3(2)XB1 and later, GGSN 4.0 supports TFTP/FTP over VRF.
To enable this feature, issue the following configuration command where interface is the interface that has the required VRF associated with it:
ip [t]ftp source-interface interface
Note
3GPP RADIUS Attributes Support for PPP PDP Contexts
In previous releases, the 3GPP RADIUS attributes were only supported for IP PDP contexts. With this release, 3GPP RADIUS attributes are also sent for PPP PDP contexts.
Improved DHCP Performance
With this release of the Cisco IOS GGSN software, with route aggregation configured under the access point, DHCP performance is approximately 50 activations per second.
Support for Sending MSISDN to LNS for PPP-Regeneration
With Cisco IOS Release 12.3(2)XB1, the calling_station_id (MSISDN) is sent over L2TP tunnels for PPP-Regeneration users.
Caveats with Cisco IOS Release 12.3(2)XB1
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.
This section contains only open and resolved caveats for the current Cisco IOS maintenance release.
All caveats in Cisco IOS Release 12.3 and Cisco IOS Release 12.3 T are also in Cisco IOS Release 12.3(2)XB1.
For information on caveats in Cisco IOS Release 12.3, see Caveats for Cisco IOS Release 12.3.
For information on caveats in Cisco IOS Release 12.3 T, see Caveats for Cisco IOS Release 12.3T, which lists severity 1 and 2 caveats and select severity 3 caveats and is located on Cisco.com and the Documentation CD-ROM.
Using the Bug Navigator II
If you have an account with Cisco.com, you can use Bug Navigator II to find caveats the most current list of caveats of any severity for any software release. To reach Bug Navigator II, Login to Cisco.com and click Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go directly to http://www.cisco.com/support/bugtools.
Open Caveats
This section documents possible unexpected behavior by Cisco IOS Release 12.3(2)XB1 and describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Description: During periods of high PPP PDP activation/deactivation on the GGSN when a local DHCP server has been assigned to allocate IP addresses, a mismatch of the number of open PPP PDP contexts and the number of DHCP IP addresses after all the PDP contexts are deleted.
Workaround: Configure an external DHCP server or local pool on the GGSN for IP address allocation.
•
Description: For PPP, PDP, PPP over L2TP, and PPP-Regen, the PDP contexts are deleted by the GGSN when the idle purger timer expires based on values configured on the GGSN, not from those defined in the RADIUS user profile.
Workaround: There is currently no known workaround.
•
Description: After creating and deleting 60,000 PDPs and 600,000 CDRs are open and sent to the charging gateway, the GGSN might display an incorrect charging counter value.
Workaround: There is currently no workaround.
•
Description: On a Cisco router running the GGSN software, if transport control protocol (TCP) is used as a path protocol to a charging gateway (CG) that is ACTIVE, if the CG is deconfigured, the TCP connection to the gateway is not terminated. Therefore, a TCP connection is seen on the GGSN even though there is no CG that owns it.
Workaround: After deconfiguring the CG, clear the associated TCP connection using the clear tcp tcb address command.
Resolved Caveats
The caveats listed in this section are resolved in Cisco IOS Release 12.3(2)XB1. This section describes only severity 1 and 2 caveats and select severity 3 caveats.
•
Description: If a Cisco router running the GGSN software receives a create PDP context request that contains faulty IPCP options in the protocol configuration options (PCO) information element (IE), the router might reload.
•
Description: A high PPP PDP for L2TP activation/deactivation rate during periods of high traffic and charging enabled, might cause a small memory leak to occur on the VPDN.
•
Description: During periods of high open/close IP PDP processing, on rare occasions, free process memory might drop below the memory threshold configured on the GGSN. When this condition is occurring, the output for the show processes cpu command will show PDP cleanup process using close to 100% of the CPU.
•
Description: The show gprs gtp pdp command is not a complete command.
•
Description: When a charging redirection-request is sent with a large "length" value in the information element (instead of the correct value of 4 for IPV4), the GGSN will reload.
•
Description: During period of a high rate of PPP PDP activation with external DHCP server assigning IP addresses, the GGSN takes some time to insert routes for MS.
•
Description: GGSN cannot fallback to GTP version 0 when it receives a "version not supported message" as a response to version 1 signalling message.
•
Description: The Cisco GGSN running Releases 3.1 or 4.0 software, uses code 02 (CONF ACK) instead of 03 (CONF NACK) when sending back IPCP address related option(s) (IPCP address, primary/secondary DNS/NBNS address) in the PCO of Create PDP Context Response message, even though the address(es) in the response message is/are different from that in the PCO of Create PDP Request message.
For more information on the resolution of this caveat, see X, in the X section.
•
Description: When GGSN detects that an MS moves to a new SGSN belonging to a different PLMN, it closes the current CDR but does not open a new one.
•
Description: When a ISRAU is received with a different QoS, the first container in the second CDR repeats the byte counts that have already been reported in the last container of the previous CDR.
•
Description: When a downstream CEF switch fails the packet punt to process level, the GTP sequence number increments by 2.
•
Description: When a GGSN responds with a NACK to a POD from a Cisco RADIUS simulator, the RADIUS simulator complains that the NACK packet has an invalid attribute with length 40.
•
Description: Cisco GGSN shows wrong "activated gtpv0 pdp"/"activated gtpv1 pdp" in the gtp status display after many GTPv1<->GTPv0 handoff's under low memory condition. This problem occurs when the configured low memory threshold is reached.
•
Description: The NAS ID sent in the authentication and accounting requests for the same session (PDP) differs. This is when Per APN NAS ID is configured under the APN and a global NAS ID is being sent for all other APNs.
•
Description: The Cisco GGSN reloads when configuring or deconfiguring the default aggregate configuration using SNMP Objects GgsnDefaultAggregRowStatus (defined in CISCO-GGSN-MIB) and then reconfiguring.
•
Description: Periods of very high rates of IP PDP open/close on a GGSN, causes a process memory leak.
•
Description: The Cisco GGSN does not attempt to connect to the CG at the configured value for the same. Instead, it makes a connection at a much earlier time.
•
Description: When a create PDP context request with a new restart count comes on an existing PDP context, the Cisco GGSN deletes the PDP context without creating a new one and sending back a response.
•
Description: Cisco GGSN does not delete the corresponding PDP context when receiving an Error Indiction message. This happens if the source port of the Error Indication is not the well-known port.
•
Description: On a Cisco router running GGSN software, the call data record (CDR) might be incorrectly closed when a routing area update (RAU) is received with a different routing area identity (RAI) information element (IE) in a PDP update request.
•
Description: When sending an Echo Response with Private Extension IE, the Cisco GGSN includes a wrong length field (8 instead of 5) in the IE.
•
Description: The charging in a Cisco GGSN Release 4.0 router sends the wrong QoS information to the charging gateway when GGSN receives a GTP v1 create PDP context request that contains 4-byte R97/98 QoS. This occurs only when the charging release is configured as R97/98.
•
•
Description: Cisco GGSN may crash while displaying APN contents with the show gprs access-point index command. This can happen if concurrently other management tools are being used to create/delete APN on the GGSN.
•
Description: When GGSN receives a Create PDP Context Request with a header length less than the total GTP packet length, the GTP message "too short" counter does not increment.
•
Description: Cisco GGSN might drop uplink packets for PPP PDP type when the Gi interface is configured under a VRF and CEF is enabled.
•
Description: When traffic is sent from any mobile to another which uses the PPP PDP type, during the redirection of this traffic away from the egress APN to a Gi interface, the number of bytes in the redirected packets is accounted incorrectly on the GGSN.
•
Description: When a GGSN receives the RAU to change the data address of the serving SGSN, the downstream traffic for the PPP PDP interface might fail to reach the SGSN and traffic might be dropped.
•
Description: Cisco GGSN keeps the TCP connection to both the Primary and Secondary CG as UP and in ESTAB state during periods of high activity or when memory is low.
•
Description: On rare occasions, a very small memory leak might occur on a Cisco router running as a GGSN when a DHCP server responds with a NAK to an initial address request.
•
Description: When the GGSN service is started and stopped repeatedly (using the service gprs ggsn and no service gprs ggsn global configuration commands), a memory leak occurs.
•
Description: If, for an extended period of time, delete requests are sent to PDPs that are under the process of being deleted by another method (such as deactivation of PDPs when access-violation occurs), the GGSN will run out of IO memory and the CPU will be consumed by the GTP PDP cleanup process.
•
Description: When sending PPP PDP with ACFC (i.e. no 0xFF03) for upstream traffic, if rejected due to the access-list configuration on the GGSN a traceback could occur.
•
Description: A Cisco router running GGSN software might reload when sending Accounting records under stress conditions.
•
Description: GGSN shows invalid characters in the show gprs gtp ms all command output.
•
Description: A Cisco router running GGSN might reload due to access to an illegal address.
•
Description: CPU utilization peaks when downlink traffic is sent at a high rate (more than 30k ppps).
•
Description: GGSN crashes with the following traceback:
0x60798124:free(0x6079809c)+0x88 0x60024680:gtp_gtpsock_free(0x60024658)+0x28 0x60025CDC:gtp_io_cleanup_gtpsock(0x60025ca0)+0x3c 0x600263D8:gtp_io_process_message(0x600260ec)+0x2ec 0x60026850:gtp_io_process(0x60026704)+0x14c•
Description: GGSN SNMP agent expects the InetAddress to be in dotted decimal when it should rather be in hexadecimal string.
•
Description: On the Cisco GGSN, US byte counts (rcv_byte_count/cef_up_byte) do not increment properly when CEF is enabled in the case of PPP term. session.
•
Description: PPP-Regen sessions are not properly cleaned if the creation fails because of some reason like user/tunnel authentication fails resulting in a stale session.
•
Description: The GGSN does not increment the "optional_ie_incorrect" counter of the show gprs gtp statistics command output when it receives a redirection request with an incorrect optional IE. Instead, it increments the "ie_unknown" counter.
•
Description: The Cisco GGSN sends an incorrect flow label in create PDP context response while creating a session.
•
Description: The Cisco GGSN leaks IO and processor memory if a CG switchover occurs during CDR transmission.
•
Description: Cisco router running a GGSN Release 4.0 image leaks memory after querying the following Simple Network Management Protocol (SNMP) MIBS:
–
–
–
–
•
Description: When the Cisco GGSN receives a create PDP request for a PPP-Regeneration context with nameserver (DNS/NetBIOS) address request in the PCO, it might not return a create PDP context response to the SGSN even though PPP comes up between GGSN and LNS (L2TP Network Server).
•
Description: The Cisco GGSN software does not send recovery IE information in the update response when it receives an update request to a non-existing PDP.
•
Description: A Cisco router running GGSn Release 4.0 might reject PDP context requests in error when GGSN receives R99 QoS profile that contains 0xFF for guaranteed bit rate (GBR).
•
Description: The ToS byte of the IP header in a downlink T-PDU packet is incorrectly marked.
Closed Caveats
The following caveat is closed in Cisco IOS Release 12.3(2)XB1:
•
Description: When a PPP PDP context is created on a GGSN, the accounting information and charging data is wrong for upstream traffic.
Cisco MWAM Caveats with Cisco IOS Release 12.3(2)XB1
This section lists the Cisco MWAM caveats that are open and resolved for Cisco IOS Release 12.3(2)XB1.
Open Caveats
The following is a list of Cisco MWAM caveats that are open for Cisco IOS Release 12.3(2)XB:
•
Description: Unable to display the name of the MWAM image from the Supervisor console.
Workaround: Use the show version command to view the IOS image from the MWAM processor.
•
Description: MWAM VLAN interfaces stop responding when the Cisco 7609 router is rebooted. Ping packets sent from the Supervisor to the MWAM fail.
Workaround: Reset the MWAM from the Supervisor using the hw-module module slot reset command.
•
Description: A reset of the CPUs from the PC can occur at any time with respect to processing on the CPUs. If a CPU is in the middle of updating the Flash, the contents of the flash can become corrupted.
•
Description: The PC may occasionally hang without any error message on the console, preventing session establishment to any of the MWAM processors.
Workaround: There is currently no known workaround.
•
Description: SNMP query for CISCO-FLASH-MIB does not populate values. The fields of the CISCO-FLASH-MIB are currently not populated for the flash devices dedicated to each of the processors of the MWAM. When the CISCO-FLASH-MIB of a MWAM processor is queried, the fields of this MIB will incorrectly appear as if there is no flash device for this processor.
Workaround: There is currently no known workaround.
Closed Caveats
The following is a list of Cisco MWAM caveats that have been resolved for Cisco IOS Release 12.3(2)XB:
•
Description: When an MWAM is removed from a slot, the MWAM configuration files remain with the MWAM. A replacement MWAM in the same slot must then be fully reconfigured. Also, when an MWAM is moved from one slot to another, the configuration files move with the MWAM instead of being associated with the original slot.
•
Description: During periods of high traffic, drops might occur when writing to NVRAM.
•
Description: Cannot copy a file to the bootflash of MWAM CPU with an existing name.
An attempt to copy a file to the bootflash:partition of an MWAM processor with a destination filename that already exists on this partition will fail. A copy cannot be made to a file that already exists. The following error message is displayed:
%Error opening bootflash:/running-config (File exists)•
Description: Because each MWAM has up to 6 CPUs running Cisco IOS software, monitoring or viewing logging information on all of the MWAM CPUs is difficult.
•
Description: When traffic is being received at 100% CPU, MWAM processors reload.
•
Description: MWAM traffic shaping does not function with MWAM Gigabit Ethernet interfaces. Traffic shaping configurations on MWAM gig0/0 interface has no effect. The driver for MWAM gig0/0 interface does not support traffic shaping.
•
Description: The GGSN does not send a teardown indicator in delete request when the DHCP address lease expires and cannot be extended. Therefore, the condition might occur where a primary and secondary PDP context exist for the same IMSI and the IP address is release back to the DHCP server despite having on PDP context still using it.
•
•
Description: When a chassis is reloaded and contains multiple MWAMs that are running in the Supervisor configuration mode (i.e., MWAM configurations stored on the Supervisor bootflash), some of MWAM processors may not receive their configurations from the Supervisor bootflash.
•
Description: SNMP query for variable chassisType(1.3.6.1.4.1.9.3.6.1) returns -1 for MWAM module.
•
Description: If a system should crash, the crashinfo file on Flash might not be written to Flash.
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 Documents: Cisco IOS Software Configuration: Cisco IOS Release 12.3: Release Notes: Cross-Platform Release Notes
•
See Caveats for Cisco IOS Release 12.3 and Caveats for Cisco IOS Release 12.3T, which contain caveats applicable to all platforms for all maintenance releases of Release 12.3 and Release 12.3 T.
On CCO at:
Technical Documents: Cisco IOS Software Configuration: Cisco IOS Release 12.3: Caveats
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.3: Caveats
Note
•
Technical Documents
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 and the Documentation CD-ROM, two master hot-linked documents provide information for the Cisco IOS software documentation set.
On CCO at:
Technical Documents: Cisco IOS Software Configuration: Cisco IOS Release 12.3: Configuration Guides and Command References
Release 12.3 Documentation Set
You can find the most current Cisco IOS documentation on CCO and the Documentation CD-ROM. These electronic documents may contain updates and modifications made after the hard-copy documents were printed.
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.3
Note
Documentation Roadmap for Implementing GGSN Release 4.0 on the Cisco MWAM
The following sections list related documentation (by category and then by task) that will be useful when implementing the Cisco GGSN on the Cisco MWAM platform.
General Overview Documents
Core Cisco 7609 Documents:
http://www.cisco.com/en/US/products/hw/routers/ps368/prod_technical_documentation.html
Navigating from Cisco.com: Products & Services / Routers / Cisco 7600 Series Router / Technical Documentation
Cisco 7609 Product Literature (white papers, data sheets, brochures):
http://www.cisco.com/en/US/products/hw/routers/ps368/prod_literature.html
Navigating from Cisco.com: Products & Services / Routers / Cisco 7600 Series Router / Product Literature
Cisco IOS Software Mainline Documentation:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_technical_documentation.html
Navigating from Cisco.com: Products & Services / IOS Software / Cisco IOS Software Releases / Cisco IOS 12.3 Mainline / Technical Documentation
Miscellaneous Cisco IOS Software Documentation:
http://www.cisco.com/en/US/products/sw/iosswrel/products_ios_cisco_ios_software_category_home.html
Documentation List by Task
Getting Started
•
http://www.cisco.com/en/US/products/hw/routers/ps368/products_quick_start09186a0080092248.html
•
http://www.cisco.com/en/US/products/hw/rproducts_regulatory_approvals_and_compliance09186a00800f0e46outers/ps368/.html
Unpack and install the Cisco 7609 router:
•
http://www.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://www.cisco.com/en/US/products/hw/routers/ps368/products_module_installation_guide_book09186a008007cd9d.html
•
http://www.cisco.com/en/US/products/hw/routers/ps368/products_configuration_guides_books_list.html
Install and complete the basic Cisco MWAM configuration:
•
http://www.cisco.com/en/US/products/hw/routers/ps368/products_module_installation_guide_book09186a008007cd9d.html
•
http://www.cisco.com/en/US/products/hw/routers/ps368/prod_module_install_config_guide_list.html
Download the Cisco IOS software image containing the GGSN 4.0 feature and configure the GGSNs on the MWAM:
•
http://www.cisco.com/en/US/products/sw/wirelssw/ps873/prod_technical_documentation.html
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
•
•
•
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0304R)
Copyright © 2003, Cisco Systems, Inc.
All rights reserved.
Guest
