Table Of Contents
Release Notes for the Cisco PDSN 2.1 Feature in Cisco IOS Release 12.3(11)YF1
Determining the Software Version
Upgrading to a New Software Release
Packet Data Serving Node Software Features in Release 12.3(11)YF1
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
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 2.1 Feature in Cisco IOS Release 12.3(11)YF1
February 2005
Cisco IOS Release 12.3(11)YF1 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. Cisco IOS Release 12.3(11)YF1 is optimized for the Cisco PDSN Release 2.1 feature on the Cisco 7206VXR router, the Cisco 7206VXR Router with Cisco NPE-G1 Network Processing Engine, the Cisco Multi-Processor WAN Application Module on the Cisco 6500 Catalyst switch platform, the Cisco 7609 Internet 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(11)YF1 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/univercd/cc/td/doc/product/software/ios123/index.htm
Release notes for Cisco 7000 Family for Release 12.3T can be found on CCO at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123relnt/7000/index.htm
Release notes for the Cisco 6000 Family for 12.3T can be found on CCO at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123relnt/cat6000/index.htm
This release note includes the following topics:
•
Packet Data Serving Node Software Features in Release 12.3(11)YF1
•
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(11)YF1:
•
•
•
Memory Requirements
Table 1 shows the memory requirements for the PDSN Software Feature Set that supports the Cisco 7206VXR router, the Cisco 7206VXR Router with Cisco NPE-G1 Network Processing Engine, the Cisco Multi-Processor WAN Application Module on the Cisco 6500 Catalyst switch platform, the Cisco 7609 Internet Router, and Cisco 6500 Catalyst Switch platform. 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(11)YF1 is optimized for PDSN Release 2.1 on the Cisco 7206VXR router, the Cisco 7206VXR Router with Cisco NPE-G1 Network Processing Engine, the Cisco Multi-Processor WAN Application Module on the Cisco 6500 Catalyst switch platform, the Cisco 7609 Internet Router, and Cisco 6500 Catalyst Switch platform.
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(11)YF1 is a special release that is developed on Cisco IOS Release 12.3.
Cisco IOS Release 12.3(11)YF1 supports the same features that are in Cisco IOS Release 12.3, with the addition of the PDSN Release 2.1 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 versionCisco Internetwork Operating System SoftwareIOS (tm) MWAM Software (MWAM-C6IS-M), Version 12.3(11)YF, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) Synched to technology version 12.3(8)TTAC Support: http://www.cisco.com/tacCopyright (c) 1986-2004 by cisco Systems, Inc.Upgrading to a New Software Release
For information on upgrading to a new software release, see the product bulletin Cisco IOS Software Upgrade Ordering Instructions located at:
http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm
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(11)YF1 supports the same feature sets as Cisco Release 12.3, with the exception that Cisco Release 12.3(11)YF1 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(11)YF1
The Cisco IOS Release 12.3(11)YF1 supports the same feature sets as Cisco Release 12.3, with the exceptions that Cisco Release 12.3(11)YF1 includes the PDSN feature. The PDSN 2.1 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/univercd/cc/td/doc/product/software/ios123/index.htm
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/univercd/cc/td/doc/product/software/ios123/123relnt/xprn123t/123tcavs.htm
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(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 fromthe 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 nosetup 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 phsical 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(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 HAto 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 behaviour is seen only when the PPP negotiations happens. If we send traffic over the established tunne, those packets are marked with correct (TOS =0) value.
Workaround: none.
•
On the Packet Data Service Node (PDSN), when the Genric 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/univercd/cc/td/doc/product/software/ios123/123newft/123limit/123y/123yf/123yf11/pdsn21/index.htm
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 provides CCO as 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.
Cisco Connection Online
CCO is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
•
•
•
–
–
You can e-mail questions about using CCO to cco-team@cisco.com.
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, 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, ASIST, 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, Empowering the Internet Generation, 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, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the 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. (0501R)
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.
Guest
