Release Notes

5
Release Notes for Cisco PDSN Release 5.2 in IOS Release 12.4(22)XR7
OL-23372-01
Migration to Cisco PDSN
Migration Scenarios for Cisco PDSN 5.2
Based on Table 1, there are many possible migration scenarios. This section focuses on those scenarios
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 these migration plans, both hardware and software configurations have significant changes. This
requires prudent operation planning and network redesign. The Migration Steps section describes the
possible migration steps to minimize both network reconfiguration and service disruption.
Table 2 lists the most common migration scenarios.
Table 2 Migrations Scenarios for Cisco PDSN Release 5.2
Scenario Migration From To Remarks Downtime
1
Non-SR
Non-clustering
7600 chassis
Each processor can act as an
individual Cisco PDSN
Non-SR
Non-clustering
7600 chassis
One Cisco PDSN
per blade (single IP
architecture)
Erase existing configuration in all
processors.
After upgrading to Cisco PDSN
Release 5.2, ensure that the
configuration is done only on the
PCOP (that is, processor 3).
IP address-pool requirements in
Cisco PDSN Release 5.2 (at the
blade level) are five times that
configured in Cisco PDSN Release
4.0 (at the processor level).
Yes