Table Of Contents
Release Notes for the Cisco PDSN Feature in Cisco IOS Release 12.3(14)YX2
Determining the Software Version
Upgrading to a New Software Release
Upgrading PDSN Image from YF-based Image to 12.3(14)YX Image
Packet Data Serving Node Software Features in Release 12.3(14)YX2
Unresolved Caveats Prior to 12.3(14)YX2
Unresolved Caveats Prior to Cisco IOS 12.3(14)YX1
Unresolved Caveats Prior to Cisco IOS 12.3(14)YX
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF3
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF2
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF1
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF
Unresolved Caveats Prior to Cisco IOS Release 12.3(8)XW3
Unresolved Caveats Prior to Cisco IOS Release 12.3(8)XW2
Resolved Caveats Prior to 12.3Y(14)YX2
Caveats Resolved Prior to Cisco IOS Release 12.3(14)YX1
Caveats Resolved Prior to Cisco IOS Release 12.3(14)YX
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF3
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF3
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF2
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF1
Resolved Caveats Prior to IOS Release 12.3(11)YF
Resolved Caveats Prior to IOS Release 12.3(8)XW3
Cisco IOS Software Documentation Set
Release 12.3 Documentation Set
Obtaining Technical Assistance
Software Configuration Tips on the Cisco Technical Assistance Center Home Page
Release Notes for the Cisco PDSN Feature in Cisco IOS Release 12.3(14)YX2
18 May 2006
Cisco IOS Release 12.3(14)YX2 is a special release that is based on Cisco IOS Release12.3, with the addition of enhancements to the Cisco Packet Data Serving Node (Cisco PDSN) feature. The Cisco IOS Release 12.3(14)YX2 is a release optimized for the Cisco PDSN feature on the Cisco 7206VXR router, the Cisco 7609 Internet Router, the Cisco NPE-G1 router, and Cisco 6500 Catalyst Switch platform.
Contents
These release notes include important information and caveats for the Cisco PDSN software feature provided in Cisco IOS 12.3(14)YX2 for the Cisco 7206VXR series router, the Cisco 7609 Internet Router, and Cisco 6500 Catalyst Switch platforms.
Caveats for Cisco IOS Release 12.3 can be found on CCO at:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/tsd_products_support_series_home. html
Release notes for Cisco 7000 Family for Release 12.3T can be found on CCO at:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/prod_release_notes_list.html
Release notes for the Cisco 6000 Family for 12.3T can be found on CCO at:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/prod_release_notes_list.html
This release note includes the following topics:
•
Upgrading to a New Software Release
•
•
Introduction
Cisco PDSN is an IOS software feature that enables a Cisco 7206VXR router, or a Multi-Processor WAN Application Module (MWAM) on a Catalyst 6500 Switch or 7600 Internet router, or the Cisco NPE-G1 router to function as a gateway between the wireless Radio Access Network (RAN) and the Internet. With Cisco PDSN enabled on a router, a stationary or roaming mobile user can access the Internet, a corporate network intranet, or Wireless Application Protocol (WAP) services. Cisco PDSN supports both Simple IP operation and Mobile IP operation.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.3(14)YX2:
•
•
•
Memory Requirements
Table 1 shows the memory requirements for the PDSN Software Feature Set that supports the Cisco 7206VXR router, the MWAM card on the Cisco 6500 Catalyst Switch platform and 7600 Internet router platform, and the Cisco NPE-G1 router. The table also lists the memory requirements for the IP Standard Feature Set (for the Home Agent [HA]).
Hardware Supported
Cisco IOS Release 12.3(14)YX2 is optimized for the Cisco PDSN feature on the Cisco 7206VXR router, the MWAM card on the Cisco 6500 Catalyst Switch platform and 7600 Internet router platform, and the Cisco NPE-G1 router.
A Hardware-Software Compatibility Matrix is available on CCO for users with CCO login accounts. This matrix allows users to search for supported hardware components by entering a Cisco platform and IOS Release. The Hardware-Software Compatibility Matrix tool is available at the following URL:
http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi
Software Compatibility
Cisco IOS Release 12.3(14)YX2 is a special release that is developed on Cisco IOS Release 12.3.
Cisco IOS Release 12.3(14)YX2 supports the same features that are in Cisco IOS Release 12.3, with the addition of the Cisco PDSN feature.
Determining the Software Version
To determine the version of Cisco IOS software running on your router, log in to the router and enter the show version EXEC command:
Router#show versionRouter#sh verCisco IOS Software, MWAM Software (MWAM-C6IS-M), Version 12.3(14)YX, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2005 by Cisco Systems, Inc.Compiled Mon 25-Jul-05 15:24 by ssearchROM: System Bootstrap, Version 12.2(11)YS2 RELEASE SOFTWARERouter uptime is 2 hours, 9 minutes System returned to ROM by reload at 07:35:31 UTC Wed Jul 6 2005 System restarted at 02:31:05 UTC Tue Jul 26 2005 System image file is "svcmwam-c6is-mz"Cisco MWAM (MWAM) processor with 473088K/32768K bytes of memory.SB-1 CPU at 700MHz, Implementation 1025, Rev 0.2Last reset from power-on1 Gigabit Ethernet interface511K bytes of non-volatile configuration memory.Configuration register is 0x4Router#Upgrading to a New Software Release
The following sections contain details on how to upgrade your Cisco Mobile Wireless Home Agent:
•
•
•
•
•
Upgrading PDSN Image from YF-based Image to 12.3(14)YX Image
If you are upgrading the PDSN from a YF-based image to a 12.3(14)YX image, you first need to upgrade the SUP image from a SXB-based image to the recommended SXE-based image.
Note
For more information on the 12.2(18)SXE3 Supervisor image, please refer to the following URL: http://www.cisco.com/en/US/products/hw/switches/ps708/prod_release_note09186a00801c8339.html
After you upgrade the SUP image, you can then upgrade the PDSN image.
Upgrading the Supervisor Image
To upgrade the Supervisor image, perform the following procedure:
Step 1
Step 2
boot system disk0:s72033-advipservicesk9_wan-mz.122-18.SXE3.bin
Note
Step 3
Step 4
Both active and standby SUP will reload simultaneously and come up with the SXE3-based image.
Note
Upgrading the PDSN Image on MWAM
To upgrade an image on the Cisco MWAM, you will need a compact flash card that has the MP partition from the current image or later, and a recent supervisor image. To locate the images, please go to the Software Center at Cisco.com (http://www.cisco.com/public/sw-center/)
Upgrading the Controller PDSN on MWAM:
To upgrade to an IOS 12.3(14)YX image on the PDSN controller, perform the following procedure:
Step 1
Log onto the supervisor and boot the MP partition on the PC.
SUP-PDSN#hw-module module 8 reset cf:1Device BOOT variable for reset = <cf:1>Warning: Device list is not verified.Proceed with reload of module?[confirm]% reset issued for module 8SUP-HA#SUP-HA#Nov 10 18:01:29.624: %SNMP-5-MODULETRAP: Module 8 [Down] TrapNov 10 18:01:29.624: SP: The PC in slot 8 is shutting down. Please wait ...Nov 10 18:01:55.252: SP: PC shutdown completed for module 8Nov 10 18:01:55.256: %C6KPWR-SP-4-DISABLED: power to module in slot 8 set off (Reset)Nov 10 18:04:00.195: SP: OS_BOOT_STATUS(8) MP OS Boot Status: finished bootingNov 10 18:04:42.299: %SNMP-5-MODULETRAP: Module 8 [Up] TrapNov 10 18:04:42.271: %DIAG-SP-6-BYPASS: Module 8: Diagnostics is passedNov 10 18:04:43.143: %OIR-SP-6-INSCARD: Card inserted in slot 8, interfaces are now onlineSUP-PDSN#Step 2
copy tftp: tftp file location pclc# linecard #-fs:
The upgrade file uses a special format that makes this process slow. The following example illustrates the upgrade process output:
SUP-PDSN#$/10.77.155.10/pdsn/images/c6svc5fmwam-h1is-mz.R30_11092005 pclc#8-fs:Destination filename [c6svc5fmwam-h1is-mz.R30_11092005]?Accessing tftp://10.77.155.10/pdsn/images/c6svc5fmwam-h1is-mz.R30_11092005...Loading pdsn/images/c6svc5fmwam-h1is-mz.R30_11092005 from 10.77.155.10 (via Vlan10): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!![OK - 24168088 bytes]24168088 bytes copied in 192.376 secs (125629 bytes/sec)SUP-PDSN#Nov 10 18:09:03.903: %SVCLC-SP-5-STRRECVD: mod 8: <Application upgrade has started>Nov 10 18:09:03.903: %SVCLC-SP-5-STRRECVD: mod 8: <Do not reset the module till upgrade completes!!>Nov 10 18:09:42.022: %SVCLC-SP-5-STRRECVD: mod 8: <Application upgrade has succeeded>Nov 10 18:09:42.022: %SVCLC-SP-5-STRRECVD: mod 8: <You can now reset the module>SUP-PDSN#Step 3
SUP-PDSN#hw-module module 8 reset cf:4Device BOOT variable for reset = <cf:4>Warning: Device list is not verified.Proceed with reload of module?[confirm]% reset issued for module 8SUP-PDSN#Nov 10 18:10:34.831: %SNMP-5-MODULETRAP: Module 8 [Down] TrapNov 10 18:10:34.831: SP: The PC in slot 8 is shutting down. Please wait ...Nov 10 18:10:57.387: SP: PC shutdown completed for module 8Nov 10 18:10:57.391: %C6KPWR-SP-4-DISABLED: power to module in slot 8 set off (Reset)Nov 10 18:12:13.370: SP: OS_BOOT_STATUS(8) MWAMNov 10 18:14:30.447: %SNMP-5-MODULETRAP: Module 8 [Up] TrapNov 10 18:14:30.434: %DIAG-SP-6-BYPASS: Module 8: Diagnostics is passedNov 10 18:14:31.293: %OIR-SP-6-INSCARD: Card inserted in slot 8, interfaces are now onlineStep 4
7600a-cont2# show cdma pdsn cluster controller member loadSecs until Seq seeks Member(past) seek no reply IPv4 Addr State Load Sessions-------------------------------------------------------------------2 0 20.20.10.2 ready 0 158 0 20.20.10.1 ready 0 15-------------------------------------------------------------------Controller IPv4 Addr 20.20.101.1057600a-cont2# show cdma pdsn cluster controller session count30 session recordsStep 5
Step 6
Step 7
7600a-cont1#show cdma pdsn cluster controller member loadSecs until Seq seeks Member(past) seek no reply IPv4 Addr State Load Sessions-------------------------------------------------------------------2 0 20.20.10.2 ready 0 158 0 20.20.10.1 ready 0 15-------------------------------------------------------------------Controller IPv4 Addr 20.20.101.1057600a-cont1# show cdma pdsn cluster controller session count30 session records
Note
Note
Note
Upgrading the Member PDSN on MWAM
To upgrade to the 12.3(14)YX image on the PDSN, perform the following procedure:
Step 1
7600a-pdsn1(config)# cdma pdsn cluster member prohibit administrativelyThe calls, which are already connected to the member, will be alive until the mobile node disconnects the call. Alternatively, the calls can be forcibly cleared on the prohibited member using the following command:
7600a-pdsn1(config)# clear cdma pdsn session allStep 2
Log onto the supervisor and boot the MP partition on the PC.
SUP-PDSN# hw-module module 8 reset cf:1Device BOOT variable for reset = <cf:1>Warning: Device list is not verified.Proceed with reload of module?[confirm]% reset issued for module 8SUP-HA#SUP-HA#Nov 10 18:01:29.624: %SNMP-5-MODULETRAP: Module 8 [Down] TrapNov 10 18:01:29.624: SP: The PC in slot 8 is shutting down. Please wait ...Nov 10 18:01:55.252: SP: PC shutdown completed for module 8Nov 10 18:01:55.256: %C6KPWR-SP-4-DISABLED: power to module in slot 8 set off (Reset)Nov 10 18:04:00.195: SP: OS_BOOT_STATUS(8) MP OS Boot Status: finished bootingNov 10 18:04:42.299: %SNMP-5-MODULETRAP: Module 8 [Up] TrapNov 10 18:04:42.271: %DIAG-SP-6-BYPASS: Module 8: Diagnostics is passedNov 10 18:04:43.143: %OIR-SP-6-INSCARD: Card inserted in slot 8, interfaces are now onlineSUP-PDSN#Step 3
copy tftp: tftp file location pclc# linecard #-fs:The upgrade file uses a special format that makes this process slow. The following example illustrates the upgrade process output:
SUP-PDSN#$/10.77.155.10/pdsn/images/c6svc5fmwam-h1is-mz.R30_11092005 pclc#8-fs:Destination filename [c6svc5fmwam-h1is-mz.R30_11092005]?Accessing tftp://10.77.155.10/pdsn/images/c6svc5fmwam-h1is-mz.R30_11092005...Loading pdsn/images/c6svc5fmwam-h1is-mz.R30_11092005 from 10.77.155.10 (via Vlan10): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!![OK - 24168088 bytes]24168088 bytes copied in 192.376 secs (125629 bytes/sec)SUP-PDSN#Nov 10 18:09:03.903: %SVCLC-SP-5-STRRECVD: mod 8: <Application upgrade has started>Nov 10 18:09:03.903: %SVCLC-SP-5-STRRECVD: mod 8: <Do not reset the module till upgrade completes!!>Nov 10 18:09:42.022: %SVCLC-SP-5-STRRECVD: mod 8: <Application upgrade has succeeded>Nov 10 18:09:42.022: %SVCLC-SP-5-STRRECVD: mod 8: <You can now reset the module>SUP-PDSN#Step 4
SUP-PDSN#hw-module module 8 reset cf:4Device BOOT variable for reset = <cf:4>Warning: Device list is not verified.Proceed with reload of module?[confirm]% reset issued for module 8SUP-PDSN#Nov 10 18:10:34.831: %SNMP-5-MODULETRAP: Module 8 [Down] TrapNov 10 18:10:34.831: SP: The PC in slot 8 is shutting down. Please wait ...Nov 10 18:10:57.387: SP: PC shutdown completed for module 8Nov 10 18:10:57.391: %C6KPWR-SP-4-DISABLED: power to module in slot 8 set off (Reset)Nov 10 18:12:13.370: SP: OS_BOOT_STATUS(8) MWAMNov 10 18:14:30.447: %SNMP-5-MODULETRAP: Module 8 [Up] TrapNov 10 18:14:30.434: %DIAG-SP-6-BYPASS: Module 8: Diagnostics is passedNov 10 18:14:31.293: %OIR-SP-6-INSCARD: Card inserted in slot 8, interfaces are now onlineStep 5
7600a-pdsn1(config)# no cdma pdsn cluster member prohibit administratively
Note
Note
Changing Configuration on the PDSN in a Live Network
If you need to change the working configuration on a PDSN in a live network environment, perform the following procedure:
Step 1
7600a-Stdy(config)# no cdma pdsn redundancyStep 2
Step 3
Step 4
Step 5
7600a-Stdy#show standby briefP indicates configured to preempt.|Interface Grp Prio P State Active Standby Virtual IPGi0/0.101 300 110 Standby 20.20.101.10 local 20.20.101.1017600a-Stdy# show cdma pdsn redundancyCDMA PDSN Redundancy is enabledCDMA PDSN Session Redundancy system statusPDSN state = STANDBY HOTPDSN-peer state = ACTIVECDMA PDSN Session Redundancy StatisticsLast clearing of cumulative counters neverTotal CurrentSynced from active ConnectedSessions 15 15SIP Flows 15 15MIP Flows 0 0PMIP Flows 0 07600a-Stdy#show redundancy inter-deviceRedundancy inter-device state: RF_INTERDEV_STATE_STDBYScheme: StandbyGroupname: pdsn-rp-sr1 Group State: StandbyPeer present: RF_INTERDEV_PEER_COMMSecurity: Not configured7600a-Stdy#show redundancy statesmy state = 8 -STANDBY HOTpeer state = 13 -ACTIVEMode = DuplexUnit ID = 0Split Mode = DisabledManual Swact = EnabledCommunications = Upclient count = 9client_notification_TMR = 30000 millisecondsRF debug mask = 0x07600a-Stdy#Step 6
Note
Step 7
Note
Note
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
MIBs
Old Cisco Management Information Bases (MIBs) will be replaced in a future release. Currently, OLD-CISCO-* MIBs are being converted into more scalable MIBs—without affecting existing Cisco IOS products or NMS applications. You can update from deprecated MIBs to the replacement MIBs as shown in Table 2.
Cisco IOS Feature Sets
The Cisco IOS software is packaged in feature sets consisting of software images—depending on the platform. Each feature set contains a specific set of Cisco IOS features.
Cisco IOS Release 12.3(14)YX2 supports the same feature sets as Cisco Release 12.3, with the exception that Cisco Release 12.3(14)YX2 includes the PDSN feature. The PDSN feature is optimized for the Cisco 7206VXR router, the Cisco MWAM card on the 6500 Catalyst Switch and 7600 Internet router, and the Cisco NPE-G1 router.
Caution
Packet Data Serving Node Software Features in Release 12.3(14)YX2
The Cisco IOS Release 12.3(14)YX2 supports the same feature sets as Cisco Release 12.3, with the exception that Cisco Release 12.3(14)YX2 includes the PDSN feature. The Cisco PDSN feature is optimized for the Cisco 7206VXR router, the Cisco MWAM card on the 6500 Catalyst Switch and 7600 Internet Router, and the Cisco NPE-G1 router, and includes the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
All other software features in Cisco IOS Release 12.3 are described in the documentation for Cisco IOS Release 12.3, which can be found at:
http://www.cisco.com/en/US/products/sw/iosswrel/tsd_products_support_category_home.html
Caveats
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
Caveats for Cisco IOS Releases 12.3 can be found on CCO at http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_release_notes_list.html
The "Open Caveats" section lists open caveats that apply to the current release and might also apply to previous releases.
The "Resolved Caveats" section lists caveats resolved in a particular release, which may have been open in previous releases.
Note
Open Caveats
The following caveats are unresolved in Cisco IOS Release 12.3(14)YX2:
•
The SNMP get for the MIB object cCdmaHDLCoGRESessionTotal is not returning any value. getmany on cCdmaHDLCoGRESessionTotal returns nothing.
Workaround: none.
•
On a Cisco router running 12.3(14)YX1 PDSN software, the standby cluster controller reloaded when unconfiguring the controller interface, this is not seen consistently.
Workaround: none.
•
SNMP walk on MIB variable cmiFaAdvertChallengeValue (OID: .1.3.6.1.4.1.9.9.174.1.1.2.2.1.2), the query falls into an infinite loop.
Workaround: none.
Unresolved Caveats Prior to 12.3(14)YX2
The following caveats are unresolved in Cisco IOS Release 12.3(14)YX1:
•
The first start airlink record received after setup is not synced to the standby.
Workaround: there is no workaround. Since the setup airlink record is synced to the standby, sending the attributes in the setup airlink record could be a possible workaround.
•
On a Cisco router the Cisco IOS Release 12.3(14)YX1 image, when a Closed-RP simple-ip session gets closed due to session timeout, the PPP Termination Counter under the RP statistics does not get incremented.
This condition occurs on a PDSN configuration using the IOS 12.3(14)YX1 image.
Workaround: none.
•
On a Cisco router running version 2.1 of the PDSN software, the memory held by the PPP Events and PPP Hooks processes may increase continiously.
This condition occurs when PPP sessions are being opened and closed.
Workaround: none.
•
The PDSN reloads due to a bus error.
This condition occurs on a MWAM running the 12.3(11)YF4 software. The PDSN reloads after a packet pool corruption error message is logged on to the console. This is observed in the following scenario:
–
–
–
–
Workaround: none.
•
On a Cisco router running the 12.3(14)YX1 software, the ip mobile cdma command chain was broken.
Workaround: none.
Unresolved Caveats Prior to Cisco IOS 12.3(14)YX1
The following caveats are unresolved in Cisco IOS Release 12.3(14)YX:
•
On a Cisco PDSN running the Cisco IOS 12.3(14) YX PDSN Image, AAA debugs are not prefixed with username when conditional debugging for the username is enabled.
Workaround: none.
•
On a Cisco PDSN running the Cisco IOS 12.3(14) YX PDSN Image, the PPP connection success is not getting incremented after the connection comes up.
This happens only when IPv6 session is opened.
Workaround: disable cdma ipv6 support.
•
On a Cisco PDSN running the Cisco IOS 12.3(14) YX PDSN Image, the Interface-ID is not being negotiated during ipv6cp negotiation by PDSN when PDSN is configured under passive mode.
This happens when the PDSN is configured in passive mode.
Workaround: configure the PDSN in active mode.
•
On a Cisco router running PDSN Software, when framed IP address is configured in AAA for a user and a session is opened, the standby ODAP client allocates address from its leased subnet.
This occurs only when Framed IP address is used from AAA and ODAP is configured for address allocation.
Workaround: none.
•
On a Cisco PDSN running the Cisco IOS 12.3(14)YX PDSN Image, the following issues occur:
a.
b.
Workaround: none.
•
On a Cisco PDSN running the Cisco IOS 12.3(14)YX PDSN Image, traceback is seen on PDSN while opening the PMIP flow due to improper word alignment.
This is not continuously reproducible.
Workaround: none.
•
On a Cisco PDSN running the Cisco IOS 12.3(14)YX PDSN Image, ipcp and ccp negotiations under ppp are not prepended with username when conditional debugging is enabled.
Workaround: none.
•
On a Cisco router running Packet Data Serving Node(PDSN), tracebacks are occasionally seen on the members of a 8-member SR cluster when a PDSN transitions from the standby to the active state with SIP and MIP sessions being flapped at 500 and 350 CPS respectively.
Workaround: none.
•
On Cisco router running Packet Data Serving Node(PDSN), the following issues are seen with the session and accounting counters when cdma pdsn ipv6 is configured:
a.
b.
c.
d.
Workaround: none.
•
On a Cisco PDSN running the Cisco IOS 12.3(14)YX PDSN Image, "CdmaRpUpdTransmittedReqs" counter values does not match with the sum of "CdmaRpUpdateAccepted", "CdmaRpUpdateDenied" and "CdmaRpUpdateNotAcked" counters.
This issue is seen only in a rare scenario.
Workaround: none.
•
On a Cisco router running Packet Data Serving Node (PDSN) with cdma pdsn ipv6 and IPv6 cef enabled, when a dual stack MN tries to bring up IPCP and IPv6CP, if the IPv4 address allocation fails due to any reason, the PDSN tears down the IPv6 flow too, for the MN.
This behavior is not seen consistently
Workaround: none.
•
On Cisco router running 12.3(14)YX PDSN software, the F13 attribute not sent in accounting stop, when a dormant session is torn down.
This issue is seen only when the session is closed during dormant state.
If the session is torn down while it is in active state, then no issues seen.
Workaround: none.
•
On a Cisco router running PDSN IOS release 12.3(11)YF software, if the PPP re-negotiation starts for the mobile during the handoff, the PDSN deletes the Old PCF details.
Workaround: enable the following command on the PDSN: cdma pdsn compliance is835a handoff.
•
On Cisco router running 12.3(14)YX PDSN software, RRQs are being re-transmitted before retransmit timeout and with different HA address for PMIP flow with HA-SLB. Also there is no command to configure re-transmit value for RRQ incase of PMIP flow.
Workaround: None
•
On Cisco router running 12.3(14)YX Packet Data Serving Node (PDSN) with cdma pdsn ipv6 and ipv6 cef enabled, the ingress address filtering feature does not work for ipv6 sessions.
This issue is seen only when ipv6 cef is enabled on the PDSN.
Workaround: disable ipv6 cef on the PDSN.
•
On Cisco router running 12.3(14)YX Packet Data Serving Node (PDSN), when AAA broadcast accounting is used in conjunction with periodic accounting, the periodic accounting interval will be n times slower then configured, where n is the number of servers in the broadcast accounting list. The workaround is to.
Workaround: compensate by configuring a periodic interval 1/n times the desired interval.
Unresolved Caveats Prior to Cisco IOS 12.3(14)YX
The following caveats are unresolved in Cisco IOS Release 12.3(11)YF3:
•
Total flow count displayed in the show cdma pdsn output does not match the actual number of flows present on the box.
This occurs only for prepaid sessions on Cisco PDSN.
Workaround: none.
•
On a Cisco PDSN running the Cisco IOS 12.3(8)XW R2.0 PDSN image, on opening a session with radius debugs enabled, the "AAA Unsupported Attr" debug messages are printed even though no functionality is affected.
Workaround: none.
•
Downstream packet throughput for the Cisco PDSN R2.0 release has degraded. Throughput on the 7200 NPE-G1 and MWAM platform is 10% lower than target numbers.
This condition occurs when packet size is 512 Bytes and traffic is pumped on all 20K sessions.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, when multiple prepaid flows are opened for the same user and traffic is sent through a single flow so as to cross the threshold and quota granted, the PDSN does not close the flow. However, traffic through the flow is not switched as expected.
This symptom occurs when prepaid accounting is enabled, and multiple Mobile IP prepaid flows are opened for the same user.
Workaround: none.
•
A Mobile IP session, created with UDP tunneling between the HA and PDSN, does not get cleared when the session is closed from MN.
Workaround: use other modes of tunneling like, IPINIP or GRE between the PDSN and HA.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) Software, the CISCO-CDMA-PDSN-MIB counter cCdmaSessionPdsnMaxFailHistory accepts a value of zero (0) when configured through NMS.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, for a volume based prepaid proxy mobile IP flow with resource revocation enabled, when the PDSN deletes prepaid flow on receiving the resource revocation request from the HA, the PDSN sets the "disconnect reason" as "client service termination" instead of "remote forced disconnect" in online access-request.
This symptom occurs for revocation enabled proxy mobile IP prepaid flows alone.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, an MSID flow is opened when the quota allocated by HAAA has both volume and duration attributes
This symptom only occurs for MSID flows.
Workaround: none.
•
On a Cisco Router running Release 2.0 PDSN software, an MSID flow is opened without prepaid capability when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
The session should have been terminated in this case.
This symptom occurs for msid flow, when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
Workaround: none.
•
Cisco PDSN Release 2.0 currently supports CDMA IPSec only for non-VRF MIP flows. The PDSN needs to support CDMA IPSec for VRF flows also.
Workaround: none.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) or Home Agent Software, the CISCO-MOBILE-IP-MIB counters "cmiFaRegVisitorRegFlagsRev1" and "cmiSecAssoc" table entries show incorrect values.
Workaround: none.
•
On a Cisco Router running PDSN R2.0 software with CDMA IPSec configured, if the outgoing interface is changed (example due to OSPF cost), then packets from PDSN go unencrypted.
Workaround: ensure that all MIP packets are sent over the interface on which crypto maps get applied. For interface redundancy, port channel configuration may be used.
•
On a Cisco router running Release 2.1 PDSN software, with the cdma pdsn compliance is835c account ipmobile control-packets CLI configured to account for Mobile IP control packets on G1 and G2 counters, the values displayed on G1 and G16 do not match.
This issue occurs on R2.1 PDSN images. Opening a MIP flow, we found that the values displayed on G1 and G16 do not match. Given that, there is no traffic sent through the flow, these values should be the same.
Workaround: none.
•
When a closed RP session is opened and closed on the Packet Data Service Node (PDSN), the statistics counter update reason "other" shows invalid value.
This condition is seen only when a closed RP session is opened and closed
Workaround: none. Since the A11 update counter is not used for closed RP sessions on the PDSN, this counter can be ignored.
•
On a Cisco router running PDSN R2.0 image configured as Cluster Controller, the Session-down counter is incremented even if there are no active sessions on any of its members.
Workaround: none.
•
Cluster members are displayed twice in the show cdma pdsn cluster controller member load command.
This condition occurs only when all members except one are removed from the controller.
Workaround: none.
•
The Cisco PDSN closes the IPsec tunnel and cannot decrypt and process revocation acknowledgements from the Home Agent under the following scenario:
–
–
–
Workaround: none. This is a cosmetic issue; it happens rarely and not processing revocation acknowledgements does not break any functionality.
•
On a Cisco router running PDSN software, traceback is found while configuring the cdma pdsn cluster controller interface interface-name command.
This issue occurs under the following conditions:
a.
b.
Workaround: none.
•
Cisco PDSN running 12.3(11)YF image may crash while handoff of a session happens from one PCF to another.
This issue occurs during a PCF to PCF handoff; however, this is a rare condition.
Workaround: issue the cdma pdsn compliance is835a handoff command.
•
Cisco PDSN enabled for Closed RP feature reloads, when the Closed RP PCF opens multiple L2TP tunnels with the PDSN and distributes the Closed RP sessions among these L2TP tunnels.
Workaround: none.
•
On Cisco router running Release 2.0 PDSN software, the PDSN Member Info is not getting synched from the active to the standby PDSN controller if the redundancy inter-device command has been configured on the controller. This rules out the possibility of configuring the ODAP server redundancy on the PDSN controllers.
This behavior is seen only if the redundancy inter-device command has been configured on the processor. The PDSN controller redundancy works fine if this CLI is not configured on the processor.
Workaround: do not configure ODAP server redundancy on the controllers.
•
When uploading files from a Mobile IP client to a server through the PDSN, packets that are larger than 1480 bytes (and the DF bit is set) are dropped by the PDSN. The PDSN does not send ICMP UNFRAG error to MIP client, and fails to learn the smaller mtu path. The MIP client will continue to send packets larger than 1480 and it will never get to the server. SIP clients are not affected.
The IP MTU setting for the IP/IP tunnel between the FA and HA is 1480 bytes.
Workaround: issue the no ip mobile tunnel path-mtu-discovery command to disable path MTU discovery on the PDSN.
•
On Cisco router running R2.1 PDSN software, the active controller was idle for sometime, and suddenly the following traceback was seen:
tb1-7600a-cont1#Jun 24 23:51:27.327: %SCHED-3-STUCKTMR: Sleep with expired timer 221E9418, time 0xAC91BF0 (00:00:00 ago).-Process= "masterPdsn", ipl= 5, pid= 137-Traceback= 20698F7C 20799884 20799C54 2036C51CWorkaround: none.
•
On a Cisco router running R2.1 PDSN software, after a dormant handoff, the PDSN sends "watchdog" packets to the Radius Server periodically in a scenario were the Accounting-response received from the Radius server are of out of sequence.
This Issue occurs during dormant handoffs, only if the "Accounting-Reponse" for Accounting-Stop was received first, followed by Accounting-Response for Accounting-Start.
Workaround: none.
•
A Cisco router running PDSN software will send MPPC compressed packets out of sequence towards a client.
This condition occurs when MPPC compression is enabled on the PDSN.
Workaround: alternate compression methods such as STAC can be used, or data can be sent uncompressed.
•
A crash may occur on the PDSN running IOS 12.3(11)T3 resulting in "System returned to ROM by bus error."
Workaround: none.
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF3
The following caveats are unresolved in Cisco IOS Release 12.3(11)YF2:
•
Total flow count displayed in the show cdma pdsn output does not match the actual number of flows present on the box.
This occurs only for prepaid sessions on Cisco PDSN.
Workaround: none.
•
Downstream packet throughput for the Cisco PDSN R2.0 release has degraded. Throughput on the 7200 NPE-G1 and MWAM platform is 10% lower than target numbers.
This condition occurs when packet size is 512 Bytes and traffic is pumped on all 20K sessions.
Workaround: none.
•
When CDMA IPSec is configured on the PDSN and CLI IPSec is configured on the HA, in the absence of a IPSec user MIP tunnel, normal IP traffic is dropped because no crypto tunnel is established between PDSN and HA.
This symptom has been observed on the PDSN and HA routers running Cisco IOS release 12.3T.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, when multiple prepaid flows are opened for the same user and traffic is sent through a single flow so as to cross the threshold and quota granted, the PDSN does not close the flow. However, traffic through the flow is not switched as expected.
This symptom occurs when prepaid accounting is enabled, and multiple Mobile IP prepaid flows are opened for the same user.
Workaround: none.
•
A Mobile IP session, created with UDP tunneling between the HA and PDSN, does not get cleared when the session is closed from MN.
Workaround: use other modes of tunneling like, IPINIP or GRE between the PDSN and HA.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) software, the CISCO-CDMA-PDSN-MIB counter "cCdmaSessionPdsnMaxFailHistory" accepts a value of zero when configured through NMS.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, for a volume based prepaid proxy mobile IP flow with resource revocation enabled, when the PDSN deletes prepaid flow on receiving the resource revocation request from the HA, the PDSN sets the "disconnect reason" as "client service termination" instead of "remote forced disconnect" in online access-request.
This symptom occurs for revocation enabled proxy mobile IP prepaid flows alone.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, an MSID flow is opened when the quota allocated by HAAA has both volume and duration attributes
This symptom only occurs for MSID flows.
Workaround: none.
•
On a Cisco Router running Release 2.0 PDSN software, an MSID flow is opened without prepaid capability when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
The session should have been terminated in this case.
This symptom occurs for msid flow, when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
Workaround: none.
•
Rp counters are not incrementing in a Cisco router running 12.3T R2.0 Release PDSN software.
The PDSN rejects an RRQ with Active Stop if a prior record is not started or stopped.
Workaround: none.
•
When a closed RP session is opened and closed on the Packet Data Service Node (PDSN), the statistics counter update reason "other" shows invalid value.
This condition is seen only when a closed RP session is opened and closed
Workaround: none. Since the A11 update counter is not used for closed RP sessions on the PDSN, this counter can be ignored.
•
The Cisco PDSN closes the IPsec tunnel and cannot decrypt and process revocation acknowledgements from the Home Agent under the following scenario:
–
–
–
Workaround: none. This is a cosmetic issue; it happens rarely and not processing revocation acknowledgements does not break any functionality.
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF2
The following caveats are unresolved in Cisco IOS Release 12.3(11)YF1:
•
Total flow count displayed in the show cdma pdsn output does not match the actual number of flows present on the box.
This occurs only for prepaid sessions on Cisco PDSN.
Workaround: none.
•
Downstream packet throughput for the Cisco PDSN R2.0 release has degraded. Throughput on the 7200 NPE-G1 and MWAM platform is 10% lower than target numbers.
This condition occurs when packet size is 512 Bytes and traffic is pumped on all 20K sessions.
Workaround: none.
•
When CDMA IPSec is configured on the PDSN and CLI IPSec is configured on the HA, in the absence of a IPSec user MIP tunnel, normal IP traffic is dropped because no crypto tunnel is established between PDSN and HA.
This symptom has been observed on the PDSN and HA routers running Cisco IOS release 12.3T.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, when multiple prepaid flows are opened for the same user and traffic is sent through a single flow so as to cross the threshold and quota granted, the PDSN does not close the flow. However, traffic through the flow is not switched as expected.
This symptom occurs when prepaid accounting is enabled, and multiple Mobile IP prepaid flows are opened for the same user.
Workaround: none.
•
A Mobile IP session, created with UDP tunneling between the HA and PDSN, does not get cleared when the session is closed from MN.
Workaround: use other modes of tunneling like, IPINIP or GRE between the PDSN and HA.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) software, the CISCO-CDMA-PDSN-MIB counter "cCdmaSessionPdsnMaxFailHistory" accepts a value of zero when configured through NMS.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, for a volume based prepaid proxy mobile IP flow with resource revocation enabled, when the PDSN deletes prepaid flow on receiving the resource revocation request from the HA, the PDSN sets the "disconnect reason" as "client service termination" instead of "remote forced disconnect" in online access-request.
This symptom occurs for revocation enabled proxy mobile IP prepaid flows alone.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, an MSID flow is opened when the quota allocated by HAAA has both volume and duration attributes
This symptom only occurs for MSID flows.
Workaround: none.
•
On a Cisco Router running Release 2.0 PDSN software, an MSID flow is opened without prepaid capability when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
The session should have been terminated in this case.
This symptom occurs for msid flow, when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
Workaround: none.
•
Rp counters are not incrementing in a Cisco router running 12.3T R2.0 Release PDSN software.
The PDSN rejects an RRQ with Active Stop if a prior record is not started or stopped.
Workaround: none.
•
When a closed RP session is opened and closed on the Packet Data Service Node (PDSN), the statistics counter update reason "other" shows invalid value.
This condition is seen only when a closed RP session is opened and closed
Workaround: none. Since the A11 update counter is not used for closed RP sessions on the PDSN, this counter can be ignored.
•
The Cisco PDSN closes the IPsec tunnel and cannot decrypt and process revocation acknowledgements from the Home Agent under the following scenario:
–
–
–
Workaround: none. This is a cosmetic issue; it happens rarely and not processing revocation acknowledgements does not break any functionality
•
The Cisco PDSN is not taking the configured a11 session update timeout value into consideration while retransmitting the a11 session update message.
This condition occurs when the Cisco router is configured for PDSN.
Workaround: none.
•
When an SDB airlink record is received after a SETUP/START airlink record, the RRQ is rejected with an error code of 86H, with the following debug printed:
"Bad Airlink record. Received SDB airlink after SETUP/START".
Workaround: none.
•
The Cisco PDSN cannot parse A11 Registration request message from a PCF that contains attribute value 32 in SDB airlink record.
This condition occurs when the PCF sends attribute value 32 in the SDB airlink record.
Workaround: none.
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF1
The following caveats are unresolved in Cisco IOS Release 12.3(11)YF:
•
Total flow count displayed in the show cdma pdsn output does not match the actual number of flows present on the box.
This occurs only for prepaid sessions on Cisco PDSN.
Workaround: none.
•
Downstream packet throughput for the Cisco PDSN R2.0 release has degraded. Throughput on the 7200 NPE-G1 and MWAM platform is 10% lower than target numbers.
This condition occurs when packet size is 512 Bytes and traffic is pumped on all 20K sessions.
Workaround: none.
•
When CDMA IPSec is configured on the PDSN and CLI IPSec is configured on the HA, in the absence of a IPSec user MIP tunnel, normal IP traffic is dropped because no crypto tunnel is established between PDSN and HA.
This symptom has been observed on the PDSN and HA routers running Cisco IOS release 12.3T.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, when multiple prepaid flows are opened for the same user and traffic is sent through a single flow so as to cross the threshold and quota granted, the PDSN does not close the flow. However, traffic through the flow is not switched as expected.
This symptom occurs when prepaid accounting is enabled, and multiple Mobile IP prepaid flows are opened for the same user.
Workaround: none.
•
A Mobile IP session, created with UDP tunneling between the HA and PDSN, does not get cleared when the session is closed from MN.
Workaround: use other modes of tunneling like, IPINIP or GRE between the PDSN and HA.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) software, the CISCO-CDMA-PDSN-MIB counter "cCdmaSessionPdsnMaxFailHistory" accepts a value of zero when configured through NMS.
Workaround: none.
•
On a Cisco router running R2.0 PDSN software, the CISCO-CDMA-PDSN-MIB counter cCdmaPcfSoRpUpdOtherReaReqs shows incorrect values.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, for a volume based prepaid proxy mobile IP flow with resource revocation enabled, when the PDSN deletes prepaid flow on receiving the resource revocation request from the HA, the PDSN sets the "disconnect reason" as "client service termination" instead of "remote forced disconnect" in online access-request.
This symptom occurs for revocation enabled proxy mobile IP prepaid flows alone.
Workaround: none.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) software, the CISCO-CDMA-PDSN-MIB counters "cCdmaActiveSessions", "cCdmaDormantSessions", and "cCdmaPcfSoRpUpdOtherReaReqs" show incorrect values.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, an MSID flow is opened when the quota allocated by HAAA has both volume and duration attributes
This symptom only occurs for MSID flows.
Workaround: none.
•
On a Cisco Router running Release 2.0 PDSN software, an MSID flow is opened without prepaid capability when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
The session should have been terminated in this case.
This symptom occurs for msid flow, when the SelectedforSession attribute has an incorrect value and PPAQ value is received in Access Accept.
Workaround: none.
•
Rp counters are not incrementing in a Cisco router running 12.3T R2.0 Release PDSN software. RP counters and poorly formed Request are not incrementing in the PDSN.
The RP counters in the PDSN are not incremented when a different GRE with no setup was sent by simulator.
Workaround: none.
•
Rp counters are not incrementing in a Cisco router running 12.3T R2.0 Release PDSN software.
The PDSN rejects an RRQ with Active Stop if a prior record is not started or stopped.
Workaround: none.
•
On Cisco router running Release 2.1 PDSN software, the router reloads while disabling conditional debugging feature for Prepaid Accounting.
The symptom occurs when prepaid accounting is enabled with conditional debugging.
Workaround: none.
•
On a Cisco Router running PDSN R2.0 software with CDMA IPSec configured, if the outgoing interface is changed (example due to OSPF cost), then packets from PDSN go unencrypted.
Workaround: ensure that all MIP packets are sent over the interface on which crypto maps get applied. For interface redundancy, port channel configuration may be used.
•
PDSN closes IPsec tunnel and so cannot decrypt and process revocation acknowledgements from Home Agent under the following conditions:
–
–
–
Workaround: none. This is a cosmetic issue, as it happens rarely and not processing revocation acknowledgement does not break any functionality
•
The PDSN sends a session update message to the PCF when RN-PDIT downloaded <= RN-PDIT stored.
This condition occurs when the second MIP flow is opened for a user and the same RN-PDIT, Always-On values are downloaded from RADIUS server.
Workaround: none.
•
On Cisco PDSN running 12.3(8)XW03, when VPDN flows are opened on the A11 session, the PDSN acting as LAC will send an ICRQ to the LNS. In the ICRQ message PDSN will include the Calling Station ID received in the A11 Registration Request. When the Calling Station ID is sent from PDSN, the last character of Calling Station ID is not encoded in the ICRQ to the LNS.
This condition occurs for all VPDN flows opened over the A11 session.
Workaround: none.
Unresolved Caveats Prior to Cisco IOS Release 12.3(11)YF
The following caveats are unresolved in Cisco IOS Release 12.3(8)XW3
•
Some configuration commands fail, do not operate properly, or cause dead memory when using batch mode config download or config-mode supervisor.
This problem occurs when the MWAM processor is configured for supervisor config-mode.
Workaround: Use config-mode local on MWAM.
•
Cisco PDSN Release 2.0 currently supports CDMA IPSec only for non-VRF MIP flows. The PDSN needs to support CDMA IPSec for VRF flows also.
Workaround: none.
•
On a Cisco router running R2.0 Home Agent Software 12.3(8)XW, the ip radius source-interface command does not work. Even if you configure ip radius source-interface xyz, the router still sends the address of the physical interface connected to the radius server, rather than the interface configured in the command (xyz).
Workaround: Configure the ip radius source-interface at the server-group level.
•
On a Cisco PDSN running the 12.3(8)XW R2.0 PDSN image on MWAM platform, configuring the radius-server attribute 44 include-in-access-req command, or the ip rad source-interface command causes an error message "% Can't insert AAA config node for vrf=", if the aaa accounting system default start-stop command is configured on the MWAM, and the MWAM config mode is the supervisor mode.
Workaround: This issue is not seen if the configuration aaa accounting system default start-stop command is not configured on the MWAM or if the MWAM config mode is local.
•
On a Cisco Router running PDSN R2.0 software with CDMA IPSec configured, MIP flows will not come up if the Mobile IP tunnel endpoint is different that of IPSec tunnel end point. This issue is seen only for MIP flows, and not for PMIP flows.
Workaround: Configure the IPSec tunnel end point as the MIP tunnel end point.
Unresolved Caveats Prior to Cisco IOS Release 12.3(8)XW3
The following caveats are unresolved in Cisco IOS Release 12.3(8)XW2
•
A Cisco router running 12.3T R2.0 Release PDSN software, sometimes produces tracebacks while sending bidirectional traffic from mobile node to the reflector in SIP flow with compress stack enabled and cef switched.
Workaround: none.
•
When the last mobile tunnel binding is brought down on the Cisco HA, a revocation message is sent from the HA and the CDMA IPSec tunnel is brought down without waiting for a revocation acknowledgement message from the PDSN.
This symptom has been observed on a router that is running Cisco IOS release 12.3T software.
Workaround: none.
•
Total flow count displayed in show cdma pdsn output does not match the actual number of flows present on the box.
This occurs only for prepaid sessions on Cisco PDSN.
Workaround: none.
•
Framed-IP-Address in the Access-Request for MIP flows is not sent even if the ip mobile foreign-agent send-mn-address command is configured on the Cisco PDSN (PDSN) and Home Agent (HA).
The radius-server attribute 8 include-in-access-req command is also configured along with CLI ip mobile foreign-agent send-mn-address, and it is not sending the "Framed-IP-Addr" attribute in its Access Request to AAA.
Workaround: unconfigure the radius-server attribute 8 include-in-access-req command on the box.
•
On a Cisco PDSN running the Cisco IOS 12.3(8)XW R2.0 PDSN image, on opening a session with radius debugs enabled, the "AAA Unsupported Attr" debug messages are printed even though no functionality is affected.
Workaround: none.
•
Downstream packet throughput for Cisco PDSN R2.0 release has degraded. Throughput on 7200 NPE-G1 and MWAM platform is 10% lower than target numbers.
The following conditions exist for this problem: packet size is 512 Bytes and traffic is pumped on all 20K sessions.
Workaround: none.
•
When CDMA IPSec is configured on PDSN and CLI IPSec is configured on HA, in the absence of IPSec user MIP tunnel, normal IP traffic is dropped as no crypto tunnel is established between PDSN and HA.
This symptom has been observed on PDSN and HA routers that are running Cisco IOS release 12.3T.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software, when multiple prepaid flows are opened for the same user and traffic is sent through a single flow so as to cross the threshold and quota granted, the PDSN does not close the flow. However, traffic through the flow is not switched as expected.
This symptom occurs when prepaid accounting is enabled and multiple mobile IP prepaid flows are opened for the same user.
Workaround: none.
•
A mobile IP session, created with UDP tunneling between the HA and PDSN, does not get cleared when the session is closed from MN.
Workaround: Use other modes of tunneling like, IPINIP or GRE between PDSN and HA.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) Software, the CISCO-CDMA-PDSN-MIB counter cCdmaSessionPdsnMaxFailHistory accepts a value of zero (0) when configured through NMS.
Workaround: none.
•
On a Cisco router running R2.0 PDSN Software, the CISCO-CDMA-PDSN-MIB counter cCdmaPcfSoRpUpdOtherReaReqs show incorrect values.
Workaround: none.
•
On Cisco router running Release 2.0 PDSN software, during Point-to-Point (PPP) negotiation, the IPCP control packets sent downstream to the Mobile Node from PDSN are encapsulated using GRE and then sent to Mobile Node. The DSCP marking on Type of Service (TOS) filed in the outer header, found be a non-zero (Garbage) value.
This behavior is seen only when the PPP negotiations happens.If traffic is sent over the established tunnel, those packets are marked with correct (TOS =0) value.
Workaround: none.
•
On a Cisco router running Release 2.0 PDSN software for a volume-based prepaid proxy mobile IP flow with resource revocation enabled, when the PDSN deletes a prepaid flow on receiving the resource revocation request from the HA, the PDSN sets the "disconnect reason" as "client service termination" instead of "remote forced disconnect" in online access-request.
This condition occurs for revocation enabled proxy mobile IP prepaid flows alone
Workaround: none.
•
On Cisco router running Release 2.0 PDSN software, upon reload of the MWAM processor where the PDSN is loaded, the Accounting OFF message is not sent towards the AAA. Also the Accounting ON message is not sent when the processor comes up after reload.
This problem exists under the following conditions:
–
–
Workaround: Include the "Broadcast" keyword in the following accounting configuration of PDSN:
aaa accounting system default start-stop broadcast group group name.
Additionally, the MWAM config-mode should be set to "Local".
•
On a Cisco Router running Release 2.0 PDSN Software, the MSID flow is opened when the quota allocated by HAAA has both volume and duration attributes.
This symptom only occurs for MSID flows.
Workaround: none.
•
On a Cisco Router running Release 2.0 PDSN Software, a MSID flow is opened without prepaid capability when the "SelectedforSession" attribute has an incorrect value, and the PPAQ value is received in Access Accept.
In this case, the session should have been terminated.
This symptom occurs for MSID flows when the "SelectedforSession" attribute has an incorrect value and PPAQ value is received in Access Accept.
Workaround: none.
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) or Home Agent Software, the CISCO-MOBILE-IP-MIB counters "cmiFaRegVisitorRegFlagsRev1" and "cmiSecAssoc" table entries show incorrect values.
Workaround: none.
•
On the Packet Data Service Node (PDSN), when the Generic Routing Encapsulation (GRE) packets received from the Packet Control Function (PCF), they are dropped intermittently, if these packets are fragmented.
Packets drops are seen on the PDSN when the PPP negotiation between the PDSN and Mobile Node Terminates the Compression Control Protocol (CCP) and then during the data transfer the Mobile Node sends another CCP ConfReq to the PDSN.
Workaround: by disabling compression on PDSN Virtual Template packet drop was not observed
•
On a Cisco router running PDSN R2.0 image configured as Cluster Controller, the Session-down counter is incremented even if there are no active sessions on any of its members.
Workaround: none.
•
Cluster members are displayed twice in the show cdma pdsn cluster controller member load command. This condition occurs only when all members except one are removed from the controller.
Workaround: none.
•
On a Cisco router running the PDSN R2.0 image, a mismatch of cluster statistics is encountered. Statistics of the total number of sessions displayed in the show cdma pdsn cluster controller member load command do not match with statistics of the show cdma pdsn cluster controller session count command.
Workaround: none.
•
When conditional debugging is enabled on Cisco PDSN running Cisco IOS 12.3(8)XW image, RADIUS related debugs are not shown sometimes for a Mobile IP flow that is opened on the box.
This condition occurs when conditional debugging is set for RADIUS related debugs.
Workaround: none.
•
Some extra mobile IP debugs are printed on a Cisco PDSN, running Cisco IOS 12.3(08)XW software, when mobile IP conditional debugging is enabled on it. Debugs that get printed are not corresponding to the user.
This condition occurs when conditional debugging for mobile IP is turned on.
Workaround: none.
Unresolved Caveats Prior to Cisco IOS Release 12.3(8)XW2
The following caveats are unresolved in Cisco IOS Release 12.3(8)XW
•
Cisco routers running Packet Data Serving Node software may show traceback when the compression stack is enabled while opening simple IP sessions.
Workaround: none.
•
On clearing the IP mobile bindings manually on PDSN, ipsec tunnel goes down before waiting for the acknowledgement for the Resource Revocation from HA
This condition is observed under the following conditions
a.
b.
c.
Workaround: none.
3. CSCed86144—Tracebacks Found in Clustering (Clustering)
A Cisco router running Packet Data Serving Node (PDSN) software in cluster controller member environment may show tracebacks on backup controller.
This occurs under the rare condition when controllers are present in a redundancy environment with a active and standby controller, and simple IP sessions are opened. Tracebacks may appear on the backup controller after sessions are opened.
Workaround: none.
•
A Cisco router running 12.3T R2.0 Release PDSN software sometimes produces tracebacks while sending bidirectional traffic from mobile node to reflector in SIP flow with compress stack enabled and CEF switched
The condition occurs when sending bidirectional traffic from mobile node to reflector in SIP flow with compress stack enabled, and CEF switched tracebacks can be seen on PDSN console.
Workaround: none.
•
A Cisco router running PDSN 2.0 Release software (Cisco IOS 12.3T) has a lower CPS rate for Mobile IP calls
The number of MIP calls that can be established per second is below 30.
Workaround: none.
Resolved Caveats
The following caveats are resolved in Cisco IOS Release 12.3(14)YX2:
•
For a Cisco router running 12.3(14)YX1 PDSN software, global statistics, show cdma pdsn stat ppp can encounter a mismatch such as, requests less than sum of success, failure and aborted.
This condition occurs in the presence of certain kind of mobile, that connects as simple ip users, and then re-negotiates ppp as vpdn users.
Workaround: none.
•
A vulnerability exists in certain Cisco IOS software release trains running on the Cisco IAD2400 series, Cisco 1900 series Mobile Wireless Edge Routers and Cisco VG224 Analog Phone Gateways. Vulnerable versions may contain a default hard-coded Simple Network Management Protocol (SNMP) community string when SNMP is enabled on the device. The default community string is a result of inadvertently identifying these devices as supporting Data Over Cable Service Interface Specification (DOCSIS) compliant interfaces. The consequence of this error is that an additional read-write community string may be enabled if the device is configured for SNMP management, allowing a knowledgeable attacker the potential to gain privileged access to the device.
Cisco is making free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20060920-docsis.shtml.
•
Cisco devices running Cisco IOS, which support voice and are not configured for Session Initiated Protocol (SIP) are vulnerable to a crash under yet to be determined conditions, but isolated to traffic destined to User Datagram Protocol (UDP) 5060. SIP is enabled by default on all Advanced images which support voice and do not contain the fix for CSCsb25337. Devices which are properly configured for SIP processing are not vulnerable to this issue. Workarounds exist to mitigate the effects of this problem. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070131-sip.shtml
•
On a Cisco router running version 2.1 of the PDSN software, processor memory held by the PPP Bind, PPP Events and PPP Hooks processes may increases continuously.
This condition only occurs when VPDN sessions are terminated by the PDSN due to idle timeout.
Workaround: do not configure an idle timeout for the VPDN sessions in PDSN.
•
On a Cisco router running 12.3(14)YX1 PDSN software, during execution of the show cdma pdsn stat ppp command, a failure reason counter mismatch between total and subcounter is observed.
"Failure reason - Other" counter was not incrementing, and remain at 0.
This is a normal operation.
Workaround: none.
•
On a Cisco router running the 12.3(14)YX1 PDSN software, the ip mobile cdma ... CLI chain option is not supported.
Workaround: none.
Resolved Caveats Prior to 12.3Y(14)YX2
The following caveats are resolved in Cisco IOS Release 12.3(14)YX1:
•
A PDSN with MEID support reloads when a mip flow is opened with or without MEID in the RRQ.
The issue ocurrs when no service alignment detection is configured on the PDSN.
Workaround: do not configure no service alignment detection on the PDSN.
•
If the PPP re-negotiation starts for the mobile during the handoff, the PDSN deletes the old PCF details.
Workaround: enable the cdma pdsn compliance is835a handoff command on the PDSN.
•
On Cisco router running the PDSN software, the counters in the show cdma pdsn statistic ppp command do not increment as expected.
This occurs under normal conditions.
Workaround: none.
•
When the uplink or downlink data transfer volume for a PDSN call exceeds 4 Gigabytes (2^32 bytes), Acct-Input-Gigawords or Acct-Output-Gigawords attributes should be included in RADIUS Accounting requests. However, these attributes may not be present.
In addition, input and output byte counters in the show interface Virtual-Access command may simply roll over to 0. Counters seen in the show cdma pdsn accounting command, on the other hand, will show correct values.
This issue occurs in a PDSN configuration using IOS 12.3(11)YF.
Workaround: none.
•
On Cisco router running 12.3(14)YX PDSN software, the F13 attribute is not sent in an accounting stop when a dormant session is made to tear down.
The F13 attribute is not sent in accounting stop only when the session is closed during dormant state If you tear down the session while it is in active state, no issues occured.
Workaround: none.
•
Sessions created during an active-active scenario do not get synced up after its recovery.
This condition occurs whenever link failure in an HSRP group happens, and a call is made through the PDSN that takes the active role.
Workaround: none.
•
A PDSN running the 12.3(11)YF2 based engineering special is reloaded due to bus error.
A reload occurs while deleting the PPP conditional debug. This is a rare event, as the bus error occurs only when the deletion of PPP conditional debug happens simultaneously with the connection deletion.
Workaround: none.
•
On a Cisco PDSN, when mobile nodes open a VPDN service type flow, the PDSN sends a ICRQ message to LNS. In this message the PDSN includes the MSID of the mobile. When the Calling Station (MSID) AVP is added, the PDSN adds an extra "0x00" character at the end of MSID. This may cause the ICRQ to be rejected on the LNS, since the length field in the Calling Station AVP does not include the extra character.
This condition occurs whenever VPDN service type is provided to the mobiles on the PDSN.
Workaround: none.
•
The standby PDSN stores an incorrect MEID value in UDR.
This condition occurs when a different MEID value is received in setup and stop records with PDSN redundancy enabled.
Workaround: ensure that PCF does not send different MEID values in airlink records when PDSN redundancy is enabled.
•
On a Cisco router running the Cisco IOS 12.3(14)YX PDSN image, "CdmaRpUpdTransmittedReqs" counter values do not match with the sum of "CdmaRpUpdateAccepted", "CdmaRpUpdateDenied" and "CdmaRpUpdateNotAcked" counters.
This condition may be the result of a race condition on the PDSN.
Workaround: none.
•
In the PDSN 3.0 EFT Image, the show cdma pdsn stat ppp command shows inconsitent counter values when IPV4 and IPV4 stack co-exist.
This condittion occurs when the cdma pdsn ipv6 command is configured.
Workaround: do not configure the cdma pdsn ipv6 command.
Caveats Resolved Prior to Cisco IOS Release 12.3(14)YX1
The following caveats are resolved in Cisco IOS Release 12.3(14)YX:
•
On a Cisco router running R2.0 Home Agent software, PPP connection Status (Connection Aborted counter) increments on creating Simple IP Session with Incorrect MSID value.
Workaround: none.
•
On a Cisco router running the PDSN image, the connection aborted counter is incrementing instead of failure counter during auth timeout.
Workaround: none.
•
On a Cisco router running PDSN Cisco IOS Release 12.3(11) software, counters displayed by show cdma pdsn statistics ppp pcf are not correct.
This issue occurs during handoff.
Workaround: none.
•
On a Cisco router running PDSN Cisco IOS Release 12.3(11) software, it is observed that the connection req field in show cdma pdsn stat ppp pcf is an unreasonably large value.
Workaround: none.
•
A Cisco PDSN running the 12.3(11)YF image may reload while handoff of a session happens from one PCF to another.
This is a rare scenario during the inter-pcf handoff.
Workaround: Configure the cdma pdsn compliance is835a handoff command.
•
On a Cisco router running PDSN IOS Release 12.3(11) software, when uploading files from a Mobile IP client to a server through the PDSN, packets that are larger than 1480 bytes and the DF bit is set are dropped by the PDSN. The PDSN does not send ICMP UNFRAG error to MIP client, therefore it fails to learn the smaller mtu path. The mip client will continue to send packets larger than 1480, and it will never get to the server. SIP clients are not affected.
The IP MTU setting for the IP/IP tunnel between the FA and HA is 1480 bytes.
Workaround: configure no ip mobile tunnel path-mtu-discovery to disable path MTU discovery on the PDSN.
•
The Cisco IOS Stack Group Bidding Protocol (SGBP) feature in certain versions of Cisco IOS software is vulnerable to a remotely-exploitable denial of service condition. Devices that do not support or have not enabled the SGBP protocol are not affected by this vulnerability.
Cisco has made free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability.
Cisco has published a Security Advisory on this issue; it is available at http://www.cisco.com/warp/public/707/cisco-sa-20060118-sgbp.shtml
•
On a Cisco router running PDSN IOS Release 12.3(11) software, it is found that the PDSN is sending MPPC compressed packets out of sequence towards client.
This issue occurs only when MPPC is enabled.
Workaround: none.
•
A Cisco 7609-MWAM Router running the "svcmwam-c6is-mz.123-11.YF3" image reloaded due to a Bus Error at invalid address. This occurs because of a race condition that the session gets deleted while receiving traffic. This is a rare scenario.
Workaround: none.
Caveats Resolved Prior to Cisco IOS Release 12.3(14)YX
The following caveats are resolved in Cisco IOS Release 12.3(11)YF4:
•
Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability. Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution.
Cisco has made free software available that includes the additional integrity checks for affected customers.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20051102-timers.shtml.
•
Through normal software maintenance processes, Cisco is removing deprecated functionality from the OS boot routine. These changes have no impact on system operation or feature availability.
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF3
The following caveats are resolved in Cisco IOS Release 12.3(11)YF3 and are listed by component:
PDSN
•
When CDMA IPSec is configured on the PDSN and CLI IPSec is configured on the HA, in the absence of a IPSec user MIP tunnel, normal IP traffic is dropped because no crypto tunnel is established between PDSN and HA.
This symptom has been observed on the PDSN and HA routers running Cisco IOS release 12.3T.
Workaround: none.
•
Rp counters are not incrementing in a Cisco router running 12.3T R2.0 Release PDSN software.
The PDSN rejects an RRQ with Active Stop if a prior record is not started or stopped.
Workaround: none.
•
CISCO-ENHANCED-MEMORY-POOL objects are not populated in Release 2.1
No specific condition.This happens when the objects of this MIB is queried.
Workaround: none.
•
On a Cisco PDSN the simple IP flow is deleted incorrectly due to mobile ip registration request timeout. The race condition for deleting the session incorrectly only if all the following condition matches
Mobile Node in the initial PPP negotiation rejects PPP Authentication and during the IPCP stage does not include the IP Address options in the IPCP ConfReq.
Mobile Node before the initial Mobile IP registration request (cdma pdsn timeout mobile-ip-registration) timeout occurs, does PPP renegotiation. During the PPP renegotiation the mobile request for PPP authentication and includes IP address options in the IPCP stage because of which Simple IP flow is created.
Workaround: none. The mobile needs to be configured to do PPP authentication.
•
On Cisco router running R2.1 PDSN software, the PPPoGRE session is dropped for VPDN flows if PPP-acfc packet is received with FF03.
This issue is seen only for VPDN session and for SIP.
Workaround: none.
•
On Cisco PDSN software running 12.3(11)YF1 image with Closed RP feature enabled and the no cdma pdsn a10 ahdlc trailer command is configured. If AHDLC packets with Bad CRC errors are received then IO memory allocated for the packets are not released which may leads to low IO memory situation on the PDSN.
Workaround: configure the cdma pdsn a10 ahdlc trailer CLI.
•
After dormant handoff, with cdma pdsn accounting send start-stop configured, the PDSN starts sending out interim accounting records to the RADIUS server.
In IOS, RADIUS watchdog records are not triggered after an accounting STOP is sent to the RADIUS server. They are only sent after an accounting START is sent. However, it is observed that after dormant handoff, with cdma pdsn accounting send start-stop configured, the PDSN starts sending out interim accounting records to the AAA server. This is not expected, as an accounting STOP is sent to the AAA server during the dormant handoff process.
In the case of dormant handoffs with cdma pdsn accounting send start-stop configured, the following is observed:
a.
b.
c.
Now, when a dormant handoff is executed:
a.
b.
c.
Workaround: none.
•
Statistics counter corresponding to Abort in show cdma pdsn statistics ppp pcf does not increment.
This condition occurs on a Cisco router configured for PDSN.
Workaround: none.
•
On Cisco Packet Data Service Node(PDSN) when TCP header compression is enabled and mobile negotiates TCP header compression, then incorrect accounting is done on the packet bytes by the PDSN for the downstream direction.
Workaround: none.
•
A 7200 PDSN running 12.3(4)T and configured for MPPC might crash by Bus error.
Right before the reload, the following Alignment Error is displayed:
%ALIGN-1-FATAL: Illegal access to a low address
This condition occurs on a PDSN running IOS version 12.3(4)T or later, that is configured for MPPC.
Workaround: none.
•
On Cisco router running PDSN software, the PDSN throws parsing error if g10 attribute received before y4 in the SDB record.
The PDSN should be able to parse the SDB records in whatever order the data arrives.
This issue occurs in PDSN YF release images, and also when ios4.1 compliance for SDB record is enabled.
Workaround: none.
MWAM
•
MWAM processor appears to be hung. However it does send out HSRP hellos now and then causing its peer to not takeover or cause RF induced reloads on peer (based on HSRP priority). So, SR system does not recover completely. Note that this affects the partner processors in the same complex as well.
This condition occurs when too many debug or error messages are printed.
Workaround: configure no logging console guaranteed to avoid lock up of the console, or the logger process hijacking the CPU.
NAT
•
Spurious memory accesses and tracebacks are generated on a Cisco 831.
This symptom is observed when NAT/PAT is configured.
Workaround: none.
•
A router may reload with a bus error exception, the crashinfo file shows an address error (a load or instruction fetch), and there is a spurious access in the crashinfo file.
These symptoms are observed on a Cisco router that performs NAT on H.323 voice traffic.
Workaround: none.
•
When the user configures the ip nat service fullrange udp port number command, the port-allocation logic is broken. If a PAT port is taken the next-port logic fails.
The ip nat service fullrange CLI is only for specific customers, and the regular port-allocation logic is not affected. Only when this command is enabled are things broken as explained above.
Workaround: disable the ip nat service fullrange CLI if it is enabled.
Miscellaneous
•
Remote Authentication Dial In User Service (RADIUS) authentication on a device that is running certain versions of Cisco Internetworking Operating System (IOS) and configured with a fallback method to none can be bypassed.
Systems that are configured for other authentication methods or that are not configured with a fallback method to none are not affected.
Only the systems that are running certain versions of Cisco IOS are affected. Not all configurations using RADIUS and none are vulnerable to this issue. Some configurations using RADIUS, none and an additional method are not affected.
Cisco has made free software available to address this vulnerability. There are workarounds available to mitigate the effects of the vulnerability.
More details can be found in the security advisory which posted at the following URL http://www.cisco.com/warp/public/707/cisco-sa-20050629-aaa.shtml
•
An ISA encryption card is not activated when you boot the router.
This symptom is observed on a Cisco 7200 series that runs Cisco IOS Release 12.3(11)T or interim Release 12.3(11.4) and that is configured with an NPE-400. Note that the symptom does not occur when the router is configured with an NPE-G1.
Workaround: none.
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF3
The following caveats are resolved in Cisco IOS Release 12.3(11)YF2:
•
A Cisco 7200 router with VAM2 will display many output authentication errors and invalid packet errors.
This condition occurs under high stress and when QOS pre-classify is configured.
Workaround: Disable QOS or reduce the traffic rate.
•
A Cisco Home Agent router may report the tunnel source and destination, for a dynamically created Mobile IP-IP Tunnel, as "UNKNOWN" in the show interface command output.
Router# show interface t1Tunnel1 is up, line protocol is upHardware is TunnelInterface is unnumbered. Using address of Ethernet0/0 (10.1.1.1)MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation TUNNEL, loopback not setKeepalive not setTunnel source UNKNOWN, destination UNKNOWNWorkaround: none.
•
This DDTS is not a bug. The diffs for this DDTS provide functionality that is utilized by the fix for bug CSCeh14272.
Since CSCeh14272 needs to go into a throttle, CSCeg17877 will also need to go into a throttle.
(The commit moves duplicate functionality out of a pair of drivers into the common code for help with maintainability.)
•
This behavior is seen when a timeout value is configured on the PDSN for a PPP session, and the PCF terminates the session. Since the timeout value is configured for the session, the PDSN does not respond to the LCP term req until the timeout value. If a RRQ with lifetime zero is received for the session, the PDSN terminates the session immediately and removes the timer. In this scenario, the cdma_release_ind, which is one of the 3gpp2 radius attributes, was not set properly. Ideally this needs to be set to "PPP Termination".
This condition occurs when RRQ 0 is received before the timeout expiry in the PDSN for session termination.
Workaround: none.
•
The Cisco Packet Data Serving Node(PDSN) running 12.2(08)ZB01 image may reject registration request (RRQ) received on the Packet control function (PCF) and PDSN signalling interface(A11) by setting reply code to 8DH in the A11 registration reply (RRP)sent back to PCF.
This condition exists when an A11 RRQ with two airlink records (setup airlink record and start airlink record) is retransmitted, and the airlink sequence numbers in the airlink records is same as received in the previous A11 RRQ.
Workaround: none.
•
Some extra mobile IP debugs are printed on Cisco PDSN running 12.3(08)XW software when mobile IP conditional debugging is enabled on it. Debugs that get printed are not corresponding to the user.
Workaround: none.
•
The Cisco PDSN cannot parse A11 Registration request message from PCF that contains attribute value 32 in SDB airlink record.
This conditions exists when the PCF sends attribute value 32 in SDB airlink record.
Workaround: none.
•
The Cisco PDSN is not taking the configured a11 session update timeout value into consideration while retransmitting the a11 session update message.
This condition occurs when the Cisco router is configured for the PDSN.
Workaround: none.
•
When an SDB airlink record is received after a SETUP/START airlink record, the RRQ is rejected with an error code of 86H, with the following debug printed:
"Bad Airlink record. Received SDB airlink after SETUP/START".
Workaround: None.
•
In the following PDSN scenario, the interim accounting update interval is not working properly.
This problem occurs when the following conditions exist:
a.
b.
c.
d.
Workaround: none.
•
The Active Session Counter and Dormant Session Counter carry junk values upon handoffs. The junk values are observed in the following scenarios:
Scenario 1:
–
–
–
Scenario 2:
–
–
–
–
–
Workaround: none.
•
An SA-VAM2 stops processing all packets.
This condition is observed sporadically on a Cisco 7200 series that is configured with an NPE-G1 when the SA-VAM2 is configured for AES 192 or AES 256.
Workaround: Reset the SA-VAM2 by entering the no crypto engine accelerator command followed by crypto engine accelerator command. If the symptom persists, disable the SA-VAM2 by entering the no crypto engine accelerator command. Doing so causes the router to switch to software encryption.
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF2
The following caveats are resolved in Cisco IOS Release 12.3(11)YF1:
•
On a Cisco router running R2.0 Packet Data Serving Node (PDSN) software, the CISCO-CDMA-PDSN-MIB counters "cCdmaActiveSessions", "cCdmaDormantSessions", and "cCdmaPcfSoRpUpdOtherReaReqs" show incorrect values.
Workaround: none.
•
On Cisco router running Release 2.1 PDSN software, the router reloads while disabling conditional debugging feature for Prepaid Accounting.
The symptom occurs when prepaid accounting is enabled with conditional debugging.
Workaround: none.
•
On a Cisco router configured for PDSN, the "release total" counter might increase by 2 instead of 1 in the output of show cdma pdsn statistics ppp command.
Workaround: none.
•
On Cisco Packet Data Service Node (PDSN), when VPDN calls are made from the Mobile Node (MN), the PDSN in the downstream path (packets destined to the mobile) does not include the Address and Control Field (ACF - FF03) in the packet.
Workaround: none.
•
When closed RP sessions are opened and closed at a high rate on the PDSN, a memory leak occurs.
This condition occurs only when closed RP sessions are opened and closed.
Workaround: none.
•
The Cisco PDSN does not include a Message-Authenticator attribute in the online Access Requests that are being sent by prepaid sessions for quota retrieval.
Workaround: none.
•
When the ip mobile foreign-agent skip-aaa-reauthentication command is configured, the ip mobile foreign-agent nat traversal force command also gets configured. This causes the initial RRQ from the PDSN to the HA to fail.
Workaround: unconfiguring the ip mobile foreign-agent nat traversal force command will help correct this.
•
The Cisco PDSN sends session update message to PCF when the RN-PDIT downloaded is less than RN-PDIT stored.
This condition occurs when the second MIP flow is opened for a user and the same RN-PDIT, Always-On values are downloaded from radius server.
Workaround: none.
•
On Cisco PDSN running 12.3(8)XW3, when VPDN flows are opened on the A11 session, the PDSN acting as LAC will send an ICRQ to the LNS. In the ICRQ message PDSN will include the Calling Station ID received in the A11 Registration Request. When the Calling Station ID is sent from PDSN, the last character of Calling Station ID is not encoded in the ICRQ to the LNS.
This condition occurs for all VPDN flows opened over the A11 session.
Workaround: none.
•
The MWAM processor returns a sysObjectId of "ciscoWsSvcMWAM1" instead of "cevC6xxxMWAMBlade". Because of this, the network management station running RME 4.0 may not be able to identify the device successfully.
This condition occurs when the MWAM processor is running a Cisco IOS image 123(11)YF, or later.
Workaround: none.
Caveats Resolved Prior to Cisco IOS Release 12.3(11)YF1
The following caveats are resolved in Cisco IOS Release 12.3(11)YF:
•
Some configuration commands fail, do not operate properly, or cause dead memory when using batch mode config download or config-mode supervisor.
This problem occurs when the MWAM processor is configured for "supervisor" config-mode.
Workaround: use config-mode local on MWAM.
•
When using config on supervisor with the MWAM, the processors are not able to retrieve their configurations from the supervisor.
This problem was first seen when using supervisor release 122-18.2.2.SX. This defect would be present in all future supervisor releases when mated with an MWAM IOS image that did not contain this fix.
Workaround: configure an arbitrary tftp-server (for example, tftp-server nvram:startup-config) on the supervisor. It does not matter what file you serve up, even one of the mwam configs. If you do serve up one of the MWAM configs, be sure to add the alias: "tftp-server bootflash:SLOTxPCy.cfg alias SLOTxPCy.cfg".
Supervisor release 122-18.2.2.SX changed the mechanism used by the MWAM processors to retrieve their configurations. This ddts changed the mechanism used by the MWAM processors to be compatible with the supervisor IOS change. This ddts is also backwards compatible with previous supervisor images.
•
The MWAM reloads while sending fragmented downstream packets.
This problem occurs when you send downstream data with more fragmented packets.
Workaround: disable cef.
•
Cisco Packet Data Service Node (PDSN) Release 1.2 will reload when parsing a Messaging pending selection message from a peer participating in a peer-peer model of selection (under the condition explained below), if the PDSN address communicated in the message is not present in its load list.
This condition occurs when the Peer-Peer mode of selection with load balancing is enabled, and a PDSN receives a MSG_PENDING CVSE and the PDSN address communicated in the message is not present in its load list.
Workaround: disable load balancing in peer-peer mode of selection.
Resolved Caveats Prior to IOS Release 12.3(11)YF
The following caveats are resolved in Cisco IOS Release 12.3(8)XW3:
•
A Cisco router running 12.3T R2.0 Release PDSN software sometimes produces tracebacks while sending bidirectional traffic from mobile node to reflector in SIP flow with compress stack enabled and cef switched
This condition occurs while sending bidirectional traffic from mobile node to reflector in SIP flow with compress stack enabled and cef switched.
Workaround: none.
•
When the last mobile tunnel binding is brought down on HA, a revocation message is sent from HA and CDMA IPSec tunnel is brought down without waiting for a revocation acknowledgement message from the PDSN.
This condition has been observed on a router that is running Cisco IOS release 12.3T software.
Workaround: none.
•
On Cisco router running Release 2.0 PDSN software, during Point to Point (PPP) negotiation, the IPCP control packets sent downstream to the Mobile Node from PDSN are encapsulated using GRE, and then sent to Mobile Node.
The DSCP marking on the Type of Service (TOS) filed in the outer header, was found to be a non-zero (Garbage) value.
This behavior is seen only when the PPP negotiations happens. If we send traffic over the established tunnel, those packets are marked with correct (TOS =0) value.
Workaround: none.
•
On the Packet Data Service Node (PDSN), when the Generic Routing Encapsulation (GRE) packets received from the Packet Control Function (PCF), they are dropped intermittently if the packets are fragmented.
Packets drops are seen on the PDSN when the PPP negotiation between the PDSN and Mobile Node Terminates the Compression Control Protocol (CCP), and then during the data transfer the Mobile Node sends another CCP ConfReq to the PDSN.
Workaround: By disabling compression on PDSN Virtual Template, packet drop was not observed
•
When conditional debugging is enabled on Cisco PDSN running 12.3(8)XW image, RADIUS related debugs are not shown sometimes for a Mobile IP flow that is opened on the box.
This condition occurs when conditional debugging is set for RADIUS related debugs.
Workaround: none.
•
Some extra mobile IP debugs are printed on Cisco PDSN running 12.3(08)XW software when mobile IP conditional debugging is enabled on it. Debugs that get printed are not corresponding to the user.
This condition occurs when conditional debugging for Mobile IP is turned on.
Workaround: none.
Resolved Caveats Prior to IOS Release 12.3(8)XW3
The following caveats are resolved in Cisco IOS Release 12.3(8)XW2:
•
Cisco router running Packet Data Serving Node (PDSN) Software in redundant cluster controller member environment may show tracebacks on active controller and may lead to a reload.
This condition occurs under a rare condition when controllers are present in redundancy environment with active and standby controller and simple IP sessions are opened. On the active controller preemption is enabled and this has the higher priority. If active is brought down and recovers, when it tries to take control back from the standby, tracebacks may appear on active controller and may lead to a reload.
Workaround: Disable preemption on the active controller.
•
When the Cisco Packet Data Service Node (PDSN) has multiple MIP flows for the same user and receives a Packet of Disconnect (POD) request with IMSI for the user, it deletes only a single flow for the IMSI. One flow for the IMSI is deleted each time the POD request is resent.
This problem is only seen when multiple flows with the same username exists for the session.
Workaround: none.
•
On Cisco 7600 running HA Release 2.0 image, lease time is not sync on Active and Standby HA's. This will result into out of sync between Active and Standby HA.
Open 25 k bindings on active and standby HA reload active mwam standby HA become active, and try to renew lease, some subnets are out of sync with server. Unable to renew lease. Server is deleting subnets after lease expiry. Due to this both active and standby bindings are deleted
Workaround: none.
•
PPP sessions may get stuck in the TERMSENT state. This symptom is observed on a Cisco platform that has a high CPU utilization.
Workaround: Clear the underlying layer (VPDN, PPPoA, or PPPoE).
•
Tracebacks were seen when a standby controller was added to the cluster.
Workaround: none.
•
A Cisco PDSN running R2.0 S/W incorrectly displays a NACK message being sent even though it correctly sends an ACK message to RADIUS server in response to a POD request.
This condition occurs when the POD feature is enabled, and the PDSN receives a POD request from RADIUS server with only NAI and NAS-ID and no session identification attributes in it.
Workaround: none
•
Cisco router configured with the ip tcp adjust-mss command may fail to set the value for outbound packets.
The command works on 12.3(7)T2 code, but fails on 12.3(8)T code. This issue is currently seen on a 3700 router.
Workaround: disable cef.
Note
•
A Cisco router running 12.3(7)T3 R1.2 Release of the PDSN software reloads when you unconfigure the cdma pdsn cluster member interface command.
Workaround: none.
•
On a Cisco 7600 running the HA R2.0 Image, the lease time is not synchronized on active and standby HAs. This causes the active and standby HAs to be out of sync.
The following conditions must exist for this problem to occur:
–
–
–
–
Workaround: none.
•
On Cisco router running Release 2.0 PDSN software, when Proxy MIP flow is opened in a setup with HA-SLB, the MIP tunnel endpoint for the session on the PDSN is incorrect. This causes re-registrations and data transfer through this session to fail.
This symptom occurs when Proxy MIP flow is opened with HA-SLB. This issue is not seen when HA SLB is not used.
Workaround: none.
•
The router reloaded by bus error when the customer issued command no ip mobile host nai @xxx.xxx.xxx.xxx address pool local ha-pool interface FastEthernet x/x aaa after configuring ip mobile host nai @xxx.xxx.xxx.xxx address pool local ha-pool interface FastEthernet x/x aaa.
Workaround: none.
•
On a Cisco Packet Data Service Node (PDSN), when Mobile IP flows are opened at the rate of 1000 cps, some of Mobile IP flows are closed.
This occurs when the Mobile IP registration lifetime in the Registration Request is not INFINITE (65535).
Workaround: none.
•
On Cisco Packet Data Serving Node (PDSN), calls per second on a cluster of 8 Members and 2 Controllers is lower than the PRD requirement.
Workaround: none.
•
Cisco Packet Data Service Node (PDSN) Rel 1.2 sends an invalid PPP call fail reason for authentication fail scenario.
This condition occurs when sending of PPP call fail reason to a Proprietary PCF is enabled and MN fails authentication in PPP authentication phase.
Workaround: none.
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 Cisco IOS Release 12.3T:
•
http://www.cisco.com/en/US/products/sw/wirelssw/ps4341/tsd_products_support_series_home.html
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.3T, which contain caveats applicable to all platforms for all maintenance releases of Release 12.3.
On CCO at:
Technical Documents: Cisco IOS Software Configuration: Cisco IOS Release 12.3: Caveats
Note
•
Technical Documents
Platform-Specific Documents
Documentation specific to the Cisco 7206 Router is located at the following locations:
•
Documentation specific to the Cisco 7600 Router is located at the following location:
•
Documentation specific to the Cisco Catalyst 6500 Switch is located at the following location:
•
Feature Modules
Feature modules describe new features supported by Release 12.3 and are updates to the Cisco IOS documentation set. A feature module consists of a brief overview of the feature, benefits, configuration tasks, and a command reference. As updates, the feature modules are available online only. Feature module information is incorporated in the next printing of the Cisco IOS documentation set.
On CCO at:
Technical Documents: Cisco IOS Software Configuration: Cisco IOS Release 12.3: New Feature Documentation
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.2: Configuration Guides and Command References
Release 12.3 Documentation Set
Table 3 describes the contents of the Cisco IOS Release 12.3 software documentation set, which is available in electronic form and in printed form when ordered.
Note
On CCO at:
Technical Documents: Documentation Home Page: Cisco IOS Software Configuration: Cisco IOS Release 12.3
Note
Obtaining Documentation
World Wide Web
You can access the most current Cisco documentation on the World Wide Web (WWW) at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Ordering Documentation
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Obtaining Technical Assistance
Cisco.com provides a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center (TAC). All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many Cisco printed documents, or by sending mail to Cisco.
Technical Assistance Center
The Cisco TAC is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use http://www.cisco.com/public/support/tac.
To contact by e-mail, use one of the following addresses:
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
Software Configuration Tips on the Cisco Technical Assistance Center Home Page
If you have a CCO login account, you can access the following URL, which contains links and tips on configuring your Cisco products:
http://www.cisco.com/kobayashi/technotes/serv_tips.shtml
This URL is subject to change without notice. If it changes, point your Web browser to CCO and click on this path: Technical Assistance Center: Technical Tips.
The following sections are provided from the Technical Tips page:
•
•
•
•
•
•
•
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate and value your comments.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, 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 Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0601R)
Copyright © 2006, Cisco Systems, Inc.
All rights reserved.
Guest
