Table Of Contents
Release Notes for the Cisco PDSN 4.1 Feature in Cisco IOS Release 12.4(15)XR9
Migration Scenarios for Cisco PDSN 4.1
Upgrading to New Software Release
Determining the Software Version
Upgrading the Supervisor Image
Changing Configuration on Cisco PDSN in a Live Network
Cisco PDSN Software Features in Release 12.4(15)XR9
Unresolved Caveats in Cisco IOS Release 12.4(15)XR2
Unresolved Caveats in Cisco IOS Release 12.4(15)XR1
Unresolved Caveats Cisco IOS Release 12.4(15)XR
Resolved Caveats in Cisco IOS Release 12.4(15)XR8
Resolved Caveats in Cisco IOS Release 12.4(15)XR7
Resolved Caveats in Cisco IOS Release 12.4(15)XR6
Resolved Caveats in Cisco IOS Release 12.4(15)XR5
Resolved Caveats in Cisco IOS Release 12.4(15)XR4
Resolved Caveats in Cisco IOS Release 12.4(15)XR3
Resolved Caveats in Cisco IOS Release 12.4(15)XR2
Resolved Caveats Prior to Cisco IOS Release 12.4(15)XR1
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco PDSN 4.1 Feature in Cisco IOS Release 12.4(15)XR9
Published: July 06, 2010, OL-23064-01Cisco IOS Release 12.4(15)XR9 is based on Cisco IOS Release 12.4, with enhancements to the Cisco Packet Data Serving Node (Cisco PDSN) feature. This Cisco PDSN Release 4.1 update based on IOS Release 12.4(15)XR9 is optimized for the Cisco PDSN feature on the Cisco Service and Application Module for IP (SAMI) card on the Cisco 7609 Series Router.
Contents
These release notes include important information and caveats for the Cisco PDSN software feature provided by Cisco IOS 12.4(15)XR9 for the Cisco 7609 Series Router platform.
This release note describes:
•Upgrading to New Software Release
•Cisco PDSN Software Features in Release 12.4(15)XR9
•Obtaining Documentation and Submitting a Service Request
Introduction
Cisco PDSN is an IOS software feature that enables a Cisco SAMI card on a Cisco 7600 Series 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 intranet, or Wireless Application Protocol (WAP) services. Cisco PDSN supports both simple IP and mobile IP operations.
System Requirements
This section describes the system requirements for running Cisco IOS Release 12.4(15)XR9 to support Cisco PDSN 4.1:
•Cisco PDSN Software Features in Release 12.4(15)XR9
Memory Requirements
To install Cisco PDSN 4.1 that supports the SAMI card on the Cisco 7600 Series Router, ensure that you meet the following memory requirements:
•Platform: Cisco 7600 Series Router
•Bundled Image Filename: 12.4(15)XR- c7svcsami-c6ik9s-mz.124-15.XR9
•Required Memory:
–Flash: 256 MB
–DRAM: 2048 MB
Hardware Supported
Cisco IOS Release 12.4(15)XR9 is optimized for the SAMI card on the Cisco 7600 Series Router. You can use the Hardware-Software Compatibility Matrix tool to search for hardware components that are supported on a Cisco platform and an IOS release.
Note You must have a valid Cisco.com account to log in to this tool: http://www.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi
Software Compatibility
Cisco IOS Release 12.4(15)XR9 is developed on Cisco IOS Release 12.4 and supports the features included in Cisco IOS Release 12.4(15)T, with the addition of the Cisco PDSN feature.
For information on the new and existing features, see Cisco PDSN Software Features in Release 12.4(15)XR9.
MIBs
Old Cisco MIBs will be replaced in a future release. Currently, OLD-CISCO-* MIBs have been converted to more scalable MIBs—without affecting existing Cisco IOS products or NMS applications. You can update deprecated MIBs to the replacement MIBs, as shown in Table 1.
Migration to Cisco PDSN
This section describes the migration paths and scenarios for Cisco PDSN 4.1:
•Migration Path for Cisco PDSN
•Migration Scenarios for Cisco PDSN 4.1
Migration Path for Cisco PDSN
Table 2 lists currently available Cisco PDSN releases and the migration path to the SAMI card.
:
Migration Scenarios for Cisco PDSN 4.1
Based on Table 2, there are many possible migration scenarios. This section focuses on those scenarios that are closest to existing customer deployments. You must determine the migration path based on your end-to-end deployment.
Note We recommend that you perform the migration during a maintenance window in your deployment. You can also use this window for the following network redesign activities:
•Redesigning IP address scheme.
•Configuring the routing protocols.
•Configuring network connectivity between Cisco PDSN and the Home Agent (HA).
•Configuring application connectivity between Cisco PDSN and AAA servers.
•Configuring routing on the new SAMI Cisco PDSN or the HA.
Note For all the migration plans, both hardware and software configurations have significant changes. This requires prudent operation planning and network redesign. The Migration Steps section describes possible migration steps to minimize both network reconfiguration and service disruption.
Table 3 lists the most common migration scenarios.
Migration Steps
Migration to the Cisco PDSN Release 4.1 image is more than replacing Multi-processor WAN Application Module (MWAM) cards with SAMI modules. Ensure that you plan your migration such that migration activities have a minimal impact on an existing mobile subscriber's service connections.
Table 4 lists the migration tasks that are based on the scenarios established in the previous section.
Upgrading to New Software Release
The following sections describe how to determine the existing software version and how to upgrade your Cisco PDSN:
•Determining the Software Version
•Upgrading the Supervisor Image
•Changing Configuration on Cisco PDSN in a Live Network
For information on upgrading to a new software release, see the product bulletin 957 Cisco IOS Software Upgrade Ordering Instructions, located at:
http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm
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 command in the EXEC mode:
Router# show version
Cisco IOS Software, SAMI Software (SAMI-C6IK9S-M), Experimental Version 12.4(20090828:113927) [sgontla-dtho_xr7 102]Copyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Fri 28-Aug-09 17:09 by sgontlaROM: System Bootstrap, Version 12.4(15r)XQ1, RELEASE SOFTWARE (fc1)mwtcp_ftb9-pdsn-93 uptime is 9 minutesSystem returned to ROM by SUP request at 17:40:14 UTC Tue Aug 18 2009System restarted at 14:04:25 UTC Mon Aug 31 2009System image file is "c7svcsami-c6ik9s-mz.xr7-dtho"This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.A summary of U.S. laws governing Cisco cryptographic products may be found at:If you require further assistance please contact us by sending email toCisco Systems, Inc. SAMI (MPC8500) processor (revision 2.2) with 786432K/262144K bytes of memory.Processor board ID SAD114203KXFS8548H CPU at 1250MHz, Rev 2.0, 512KB L2 Cache1 Gigabit Ethernet interface65536K bytes of processor board system flash (AMD S29GL256N)Configuration register is 0x2102Router#Upgrading the Supervisor Image
To upgrade the Supervisor image:
Step 1 Copy the SUP image to the disks (for example, disk0: / slavedisk0:).
Step 2 Add the following command to the running-configuration boot system disk0: SUP-image-name. For example:
boot system disk0:s72033-advipservicesk9_wan-mz.122-18.SXE3.bin
Note To enable the image to reload, remove previously configured instances of this command.
Step 3 Run the write memory command to save the running-configuration on the active and standby SUP.
Step 4 Run the reload command on the active SUP.
Both active and standby SUP reload simultaneously and come up with the SXE3-based image.
Running the reload command on the active SUP causes both the active and standby Supervisors to reload simultaneously, causing some downtime during the upgrade process.
Upgrading the SAMI Software
To upgrade an Cisco PDSN image on the SAMI card, follow the directions at:
Changing Configuration on Cisco PDSN in a Live Network
To change the working configuration on a Cisco PDSN in a live environment:
Step 1 Bring the standby Cisco PDSN out of service.
For example, to isolate the standby Cisco PDSN from the session redundancy setup, you must run the no cdma pdsn redundancy command.
7600a-Stdy(config)# no cdma pdsn redundancy
Step 2 Run the write memory command to save the configuration.
Step 3 Make the necessary configuration changes on the standby Cisco PDSN, and save the configuration.
Step 4 Run the cdma pdsn redundancy command again and save the configuration.
Step 5 Issue the reload command to bring the standby Cisco PDSN back into the session redundancy setup with the changed configuration. Verify if the processor comes back in the session redundancy setup using the following show commands:
7600a-Stdy# show standby brief
P 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 redundancy
CDMA 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-device
Redundancy inter-device state: RF_INTERDEV_STATE_STDBYScheme: StandbyGroupname: pdsn-rp-sr1 Group State: StandbyPeer present: RF_INTERDEV_PEER_COMMSecurity: Not configured7600a-Stdy# show redundancy states
my 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 Configure the standby Cisco PDSN to take over as active by reloading the current active Cisco PDSN.
Caution Before proceeding with the configuration changes, we recommend that you disable the HSRP preemption configuration on the active and standby PDSN.
Because of a change of configuration following this step, an outage may occur on existing calls on the active PDSN (which is now being taken out of service) when synchronized with new active units.
Step 7 Configure the current standby PDSN using the procedure described from Step 1 to Step 5.
Note For Cisco PDSN session redundancy to work properly, ensure that configurations on the active and standby Cisco PDSNs are identical.
Cisco PDSN Software Features in Release 12.4(15)XR9
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.
Caution Cisco IOS images with strong encryption (including but not limited to 168-bit (3DES) data encryption feature sets) are subject to United States government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay due to United States government regulations. When applicable, purchaser or user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com.
Cisco IOS Release 12.4(15)XR9 supports the same feature sets as Cisco Release 12.4; additionally, it supports the Cisco PDSN feature. Cisco PDSN 12.4(15)XR9 is optimized for the SAMI card on the Cisco 7600 Router, and includes the following new and existing features:
•Attribute support
–Served MDN
–Framed pool
–3GPP2 DNS server IP
•Virtual Route Forwarding (VRF) with subinterfaces support
•Conditional debugging enhancements for Cisco PDSN Release 4.1
•IOS 5.0 call flow for HRPD
•QoS features based on IS-835-D
•Per-flow accounting
•MIB enhancements
•Call Admission Control (CAC)
•Home area, maximum authorized aggregate bandwidth, and inter-user priority attributes downloaded from AAA
•Mobile Equipment Identifier (MEID) support
•Simple IPv6 access
•Session redundancy infrastructure
•RADIUS server load balancing
•Closed-RP or open-RP integration
•Domain-based subscriber authorization
•PPP counters
•RP counters
•Trace functionality
•Mobile IP dynamic home address deletes older sessions with different IMSI
•Protocol layering and RP connections
•PPPoGRE RP interface
•A11 session update
•SDB indicator marking
•Resource revocation for mobile IP
•Packet of disconnect
•IS-835 prepaid support
•Prepaid billing
•Mobile IP call processing per second improvements
•IS-835-B compliant static IPsec
•Always-On feature
•Cisco PDSN cluster controller or member architecture
•Cisco PDSN MIB enhancement
•Cisco proprietary prepaid billing
•3DES encryption
•Mobile IP IPsec
•Hardware IPsec acceleration using IPsec acceleration module—Static IPsec
•1xEV-DO support
•Integrated Foreign Agent (FA)
•AAA support
•Packet transport for VPDN
•Proxy mobile IP
•Multiple mobile IP flows
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.4 are available on Cisco.com 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; they might also apply to previous releases.
The "Resolved Caveats" section lists caveats resolved in a particular release that may have been open in previous releases.
Note If you have an account with Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. You can access Bug Navigator II on Cisco.com at Software Center: Cisco IOS Software: Cisco Bug Toolkit: Cisco Bugtool Navigator II, or at http://www.cisco.com/support/bugtools.
Open Caveats
There are no unresolved caveats in the following releases:
•Cisco IOS Release 12.4(15)XR7
•Cisco IOS Release 12.4(15)XR6
•Cisco IOS Release 12.4(15)XR5
•Cisco IOS Release 12.4(15)XR4
•Cisco IOS Release 12.4(15)XR3
Unresolved Caveats in Cisco IOS Release 12.4(15)XR2
The following caveats are unresolved in Cisco IOS Release 12.4(15)XR2:
•CSCsv51151—For mobile IP Calls G15 and G16 for IP Flows in Not Sent Correctly
For mobile IP calls, G15 and G16 for IP flows are incorrectly sent. When a session is closed for IP flows, G15 and G16 send the same values as the session.
This issue occurs after the following steps:
–A mobile IP session is opened with forward and reverse IP flows.
–TFT is installed with forward and reverse packet filters (for opened IP flows).
–The session is closed.
Workaround: None.
•CSCsv23569—Domant-Dormant Handoff f1-f2, f6-f10, f14 are incorrectly sent to new PCF
After performing a dormant-dormant handoff, f1-f2, f6-f10, and f14 are sent as non-zero values in accounting records for the new PCF.
This issue occurs after the following steps:
–A session is opened.
–The session is made dormant by sending an active stop from the PCF.
–A dormant-dormant handoff is performed.
Workaround: None.
Unresolved Caveats in Cisco IOS Release 12.4(15)XR1
The following caveat is unresolved in Cisco IOS Release 12.4(15)XR1:
•CSCsu89978—Packet Drop Observed with Cisco PDSN
A packet drop seen in Cisco PDSN is more than the allowed No Drop Rate (NDR) with maximum sessions.
This condition occurs when a packet drop in the Cisco PDSN is more than the allowed 1 in 10,000 packets, when traffic is through the maximum number of sessions.
Workaround: None.
Unresolved Caveats Cisco IOS Release 12.4(15)XR
The following caveats are unresolved in Cisco IOS Release 12.4(15)XR:
•CSCsu56357—[acct] G9 Wrongly Sent in Final Acct-Stop After RevA-RevA Handoff
On a Cisco router running Cisco IOS Release 12.4(15)XR, the G9 attribute value is incorrectly sent in an accounting record (accounting stop) for main flow on closing the session after RevA-RevA handoff.
This issue occurs after the following steps:
–A session is opened.
–RevA-RevA handoff is performed.
–The session is closed.
Workaround: None.
•CSCsu59055—show cdma pdsn rp pcf stats Shows Incorrectly
The output for show cdma pdsn rp pcf stats shows incorrectly. Also the RP error statistics returned using the rp error stats command (such as Max Service Flows, Unsupported Service Option (SO), Non-Existent A10, and Bandwidth Unavailable) do not appear.
This symptom is observed on a Cisco router that runs on Cisco IOS Release 12.4(15)XR on the Cisco PDSN 4.0 SAMI.
Workaround: None.
•CSCsu62470—G9 Wrongly Sent in Acct-Stop to Old PCF after Dor-Act Handoff
The G9 attribute value is incorrectly sent in accounting records (Acct-stop) of IP flows to the AAA server for old PCF after a Domant-Active Handoff. It should appear as "0" but it appears as "1".
This issue occurs after the following steps:
–A session is opened.
–The session is made dormant and the IP flows are inactivated by sending active stop fom PCF.
–An active handoff is done.
–The session is closed.
Workaround: None.
Resolved Caveats
The following caveats are resolved in Cisco IOS 12.4(15)XR9:
•CSCso28310—Memory leak occurs at rate_limit_insert, while unconfiguring access list with rate limit. The behavior occurs when access list is configured and then unconfigured.
Workaround: None.
Resolved Caveats in Cisco IOS Release 12.4(15)XR8
•CSCtc35874—Cisco PDSN may reload when the time-of-day accounting is configured.
•CSCtb61757—Cisco PDSN(LAC) may reload when session timeout is configured for VPDN calls.
•CSCsr89422—In Cisco PDSN Release 4.0, the PDSN application reloads at ipip_decaps and gre_ip_decaps.
Resolved Caveats in Cisco IOS Release 12.4(15)XR7
•CSCsz38104
The H.323 implementation in Cisco IOS Software contains a vulnerability that can be exploited remotely to cause a device that is running Cisco IOS Software to reload. Cisco has released free software updates that address this vulnerability. There are no workarounds to mitigate the vulnerability apart from disabling H.323 if the device that is running Cisco IOS Software does not need to run H.323 for VoIP services. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-h323.shtml.
•CSCtb04493—Debug condition causes continuous log related to mobile IP reverse-tunnel.
•CSCsz58449—PDSN may reload in case of mobile IP randomized IMSI scenario.
•CSCtb33607—PDSN may reload while closing the last session of a mobile IP tunnel.
•CSCtb25549—In Cisco PDSN Release 4.0, L2TP Access Controller (LAC) reboots when the VPDN conditional debugs are enabled.
•CSCta23040—In per-PCF-PPP statistics, the current connections counter shows a higher value compared to the global one.
•CSCtb41772—Empty or corrupt Mobile Directory Number (MDN) field in the Call Data Record (CDR) for handoff with PPP renegotiation.
Resolved Caveats in Cisco IOS Release 12.4(15)XR6
The following caveats are resolved in Cisco IOS 12.4(15)XR6:
•CSCta23281—Proxy mobile IP call does not work when the Cisco FA is configured for mobile IP solution with other vendors' HA.
•CSCsz91376—Proxy mobile IP does not work because of a false ARP entry that is created by proxy mobile IP on Cisco PDSN.
•CSCta15511—Unnecessary RADIUS debugs are displayed on console (one extra line for each MN call closure) when conditional debugs are enabled.
•CSCta23143—Airlink Active time is sent as zero during handoff.
•CSCta23040—In per-PCF-PPP statistics, the current connections counter shows a higher value compared to the global one.
•CSCsz86656—SAMI does not set the DBUS trust bit to one, which in turn causes the 7600 to re-mark the DSCP of the packets.
•CSCta15087—FA sends the Revocation Acknowledgement to port 434, instead of the source port.
•CSCsz74877—The CLI command no ip mobile tunnel path-mtu-discovery is lost after a reload.
•CSCta22610—During Proxy mobile IP call closure, FA sends a revocation message to the HA.
•CSCta49336—PPP options corrupted by Cisco PDSN relaying them to the LNS. This behavior is observed only for EVDO users.
Resolved Caveats in Cisco IOS Release 12.4(15)XR5
The following caveats are resolved in Cisco IOS 12.4(15)XR5:
•CSCsz21562—DSCP re-marking does not occur for main A10 EVDO calls in downstream.
•CSCsy92461—DSCP re-marking does not occur for main A10 of EVDO calls.
•CSCsz67185—A11 RRQ is rejected when both BSID and HRPD subnet elements are present.
Resolved Caveats in Cisco IOS Release 12.4(15)XR4
The following caveats are resolved in Cisco IOS 12.4(15)XR4:
•CSCta23228—Cisco PDSN reloads occasionally when deregistering a mobile IP flow.
•CSCsk41593—PAK_SUBBLOCK error found when packets are pinged with greater than 1500-byte over cellular interface.
•CSCsk64158—Cisco IOS software multiple features crafted UDP packet vulnerability.
•CSCsm27071—Cisco IOS software multiple features IP sockets vulnerability.
•CSCsm45113—RIB installs duplicate routes for the same prefix.
•CSCsm97220—Input queue blocked by MIPv6 packets.
•CSCsr29468—Cisco IOS software multiple features crafted TCP sequence vulnerability.
•CSCsw78831—(MIB) cCdmaFlowVpdnFailures always showing zero.
•CSCsw78901—The per-PCF counter shows wrong value.
•CSCsw79258—Cisco PDSN (LAC) fails to bring up the VPDN calls after stressing for long time.
Resolved Caveats in Cisco IOS Release 12.4(15)XR3
This caveat is resolved in Cisco IOS 12.4(15)XR3: CSCin61592—Allow Service Type=Authorize only for prepaid.
Resolved Caveats in Cisco IOS Release 12.4(15)XR2
The following caveats are resolved in Cisco IOS Release 12.4(15)XR2:
•CSCsu56357—G9 wrongly sent in final Acct-stop after Rev A-Rev A handoff.
•CSCsu59055—show cdma pdsn rp pcf stats showing incorrectly.
•CSCsu62470—G9 wrongly sent in Acct-stop to old PCF after Dor-Act handoff.
•CSCsu69297—Cisco PDSN reloads after Rev A-1x handoff.
Resolved Caveats Prior to Cisco IOS Release 12.4(15)XR1
There are no resolved caveats before Cisco IOS Release 12.4(15)XR1.
Related Documentation
Table 5 describes the related documentation that is available:
Table 5 Related Documentation
Document Title Available FormatsCisco IOS Mobile Wireless Packet Data Serving Node Configuration Guide, Release 12.4T
•On Cisco.com at
http://www.cisco.com/en/US/docs/ios/mwpdsn/
configuration/guide/12_4t/mwp_12_4t_book.htmlDocumentation on Cisco 7600 Router
•On Cisco.com at
http://www.cisco.com/en/US/products/hw/routers/ps368/
tsd_products_support_series_home.htmlDocumentation on Cisco Catalyst 6500 Switch
•On Cisco.com at
http://www.cisco.com/en/US/products/hw/switches/ps708/
tsd_products_support_series_home.htmlDocumentation on Caveats for Cisco IOS Release 12.4
•On Cisco.com at
http://www.cisco.com/en/US/products/ps6350/
prod_release_notes_list.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)
© 2009 Cisco Systems, Inc.
All rights reserved.