Cisco Cisco IOS Software Release 12.4(15)XM
5
Release Notes for the Cisco Mobile Wireless Home Agent Feature in Cisco IOS Release 12.4(15)XM2
System Requirements
000151: Apr 18 17:53:33.713 EDT: %C6KPWR-SP-4-DISABLED: power to module in slot 2 set off
(Reset)
000152: Apr 18 17:57:52.033 EDT: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been
disabled.
000153: Apr 18 17:57:51.513 EDT: %DIAG-SP-6-RUN_MINIMUM: Module 2: Running Minimal
Diagnostics...
000154: Apr 18 17:57:51.537 EDT: %DIAG-SP-6-DIAG_OK: Module 2: Passed Online Diagnostics
000155: Apr 18 17:57:52.073 EDT: %OIR-SP-6-INSCARD: SAMI inserted in slot 2, interfaces
are now online
000156: Apr 18 17:57:59.589 EDT: %SVCLC-5-FWTRUNK: Firewalled VLANs configured on trunks
Sup#
User Migration
With the end of life of the Home Agent software on the Cisco 7200 and MWAM, this section addresses
the migration path from old releases (R3.1, or prior) on either the Cisco 7200 or MWAM, to Home Agent
(HA) Release 4.0 on the SAMI platform.
the migration path from old releases (R3.1, or prior) on either the Cisco 7200 or MWAM, to Home Agent
(HA) Release 4.0 on the SAMI platform.
Here are several Migration scenarios that are possible:
Obviously, there are many possible migration scenarios. Typically, there are many foreign agents sharing
the same (one, or more) redundant or non-redundant home agents. The Mobile IP flow gets the home
agent address either through a statically configured mobile device, or a foreign agent configuration, or
user profile defined on AAA servers. In case of home agent SLB, the real home agent address is given
by the SLB server.
the same (one, or more) redundant or non-redundant home agents. The Mobile IP flow gets the home
agent address either through a statically configured mobile device, or a foreign agent configuration, or
user profile defined on AAA servers. In case of home agent SLB, the real home agent address is given
by the SLB server.
The actual migration path should be determined per-customer end-to-end deployment. This means that
migration should be engineered, and offers you the opportunity to redesign your network (for example,
redesigning IP address schemes and configuring routing protocols, network connectivity between
foreign agents and home agents, application connectivity between home agents and AAA servers,
routing on the new SAMI home agent, etc.). We recommend that you perform the migration in a
maintainence window. For example, if a mobile device is statically configured with the home agent IP
address, the migration should be well tested in the your environment. Making a home agent IP address
change aware to MS/FA may require massive network service provisioning.
migration should be engineered, and offers you the opportunity to redesign your network (for example,
redesigning IP address schemes and configuring routing protocols, network connectivity between
foreign agents and home agents, application connectivity between home agents and AAA servers,
routing on the new SAMI home agent, etc.). We recommend that you perform the migration in a
maintainence window. For example, if a mobile device is statically configured with the home agent IP
address, the migration should be well tested in the your environment. Making a home agent IP address
change aware to MS/FA may require massive network service provisioning.
Table 2
Migration Scenarios
HA R3.0 or Older
HA R3.1 or Older
HA R4.0
Platform
NPE400/NPE-G1
MWAM
SAMI
Chassis/Power
Supply, Fan Trays)
Supply, Fan Trays)
7200VXR
SUP-redundancy/SLB
SUP-redundancy/SLB
SUP IOS SX based
SUP IOS SRB based
SUP2/SUP720/SUP32
SUP720/RSP720
6500/7600
7600