You are on page 1of 44

Technical

Information

MOTOROLA–CISCO PDN IOS
INTEGRATION
WHITE PAPER
CDMA

ENGLISH
NOV 2002
68P09301A55–A

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE
Notice
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any
inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been
carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Motorola,
Inc. reserves the right to make changes to any products described herein and reserves the right to revise this document and to make
changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not
assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others.
It is possible that this publication may contain references to, or information about Motorola products (machines and programs),
programming, or services that are not announced in your country. Such references or information must not be construed to mean
that Motorola intends to announce such Motorola products, programming, or services in your country.

Copyrights
This instruction manual, and the Motorola products described in this instruction manual may be, include or describe copyrighted
Motorola material, such as computer programs stored in semiconductor memories or other media. Laws in the United States and
other countries preserve for Motorola and its licensors certain exclusive rights for copyrighted material, including the exclusive
right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any
copyrighted material of Motorola and its licensors contained herein or in the Motorola products described in this instruction manual
may not be copied, reproduced, distributed, merged or modified in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or
otherwise, any license under the copyrights, patents or patent applications of Motorola, as arises by operation of law in the sale of a
product.

Usage and Disclosure Restrictions
License Agreement
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express license
agreement only and may be used only in accordance with the terms of such an agreement.

Copyrighted Materials
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or
documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or
computer language, in any form or by any means, without prior written permission of Motorola, Inc.

High Risk Activities
Components, units, or third–party products used in the product described herein are NOT fault–tolerant and are NOT designed,
manufactured, or intended for use as on–line control equipment in the following hazardous environments requiring fail–safe
controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life
Support, or Weapons Systems (“High Risk Activities”). Motorola and its supplier(s) specifically disclaim any expressed or implied
warranty of fitness for such High Risk Activities.

Trademarks

MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are
the property of their respective owners.
 Copyright 2002 Motorola, Inc.
Javat Technology and/or J2MEt: Java and all other Java–based marks are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
UNIXR: UNIX is a registered trademark of The Open Group in the United States and other countries.
REV091302

Foreword

Scope of manual
This manual is intended for use by cellular telephone system
craftspersons in the day-to-day operation of Motorola cellular system
equipment and ancillary devices.
This manual is not intended to replace the system and equipment
training offered by Motorola, although it can be used to supplement or
enhance the knowledge gained through such training.
Obtaining Manuals
To view, download, or order manuals (original or revised), visit the
Motorola Lifecycles Customer web page at http://services.motorola.com,
or contact your Motorola account representative.
If Motorola changes the content of a manual after the original printing
date, Motorola publishes a new version with the same part number but a
different revision character.
Text conventions
The following special paragraphs are used in this manual to point out
information that must be read. This information may be set-off from the
surrounding text, but is always preceded by a bold title in capital letters.
The four categories of these special paragraphs are:
NOTE
Presents additional, helpful, non-critical information that
you can use.

IMPORTANT

*

Presents information to help you avoid an undesirable
situation or provides additional information to help you
understand a topic or concept.

CAUTION
Presents information to identify a situation in which
damage to software, stored data, or equipment could occur,
thus avoiding the damage.

WARNING
Presents information to warn you of a potentially
hazardous situation in which there is a possibility of
personal injury.
NOV 2002

Motorola–Cisco PDN IOS Integration

i

Foreword – continued

The following typographical conventions are used for the presentation of
software information:
S In text, sans serif BOLDFACE CAPITAL characters (a type style
without angular strokes: for example, SERIF versus SANS SERIF)
are used to name a command.
S In text, typewriter style characters represent prompts and the
system output as displayed on an operator terminal or printer.
S In command definitions, sans serif boldface characters represent
those parts of the command string that must be entered exactly as
shown and typewriter style characters represent command output
responses as displayed on an operator terminal or printer.
S In the command format of the command definition, typewriter
style characters represent the command parameters.
Reporting manual errors
To report a documentation error, call the CNRC (Customer Network
Resolution Center) and provide the following information to enable
CNRC to open an MR (Modification Request):
– the document type
– the manual title, part number, and revision character
– the page number(s) with the error
– a detailed description of the error and if possible the proposed solution
Motorola appreciates feedback from the users of our manuals.
Contact us
Send questions and comments regarding user documentation to the email
address below:
cdma.documentation@motorola.com
Motorola appreciates feedback from the users of our information.
Manual banner definitions
A banner (oversized text on the bottom of the page, for example,
PRELIMINARY) indicates that some information contained in the
manual is not yet approved for general customer use.
24-hour support service
If you have problems regarding the operation of your equipment, please
contact the Customer Network Resolution Center (CNRC) for immediate
assistance. The 24 hour telephone numbers are:
North America
Europe, Middle East, Africa
Asia Pacific
Japan & Korea . . . . . . . . . . .
Latin American Countries

+1–800–433–5202
+44– (0) 1793–565444
+86–10–88417733
+81–3–5463–3550
+51–1–212–4020

For further CNRC contact information, contact your Motorola account
representative.
ii

Motorola–Cisco PDN IOS Integration

NOV 2002

S not replace components with power cable connected. Ground the instrument To minimize shock hazard. and intended use of the equipment. the equipment chassis and enclosure must be connected to an electrical ground. manufacture. NOV 2002 Motorola–Cisco PDN IOS Integration iii . If the equipment is supplied with a three-conductor ac power cable. or any internal adjustment. Do not operate in an explosive atmosphere Do not operate the equipment in the presence of flammable gases or fumes. Motorola. Inc. service. Safety depends on you!! The following general safety precautions must be observed during all phases of operation. the power cable must be either plugged into an approved three-contact electrical outlet or used with a three-contact to two-contact adapter.General Safety Remember! . assumes no liability for the customer’s failure to comply with these requirements. and repair of the equipment described in this manual. The power jack and mating plug of the power cable must meet International Electrotechnical Commission (IEC) safety standards. The safety precautions listed below represent warnings of certain dangers of which we are aware. should follow these warnings and all other safety precautions necessary for the safe operation of the equipment in your operating environment. Operation of any electrical equipment in such an environment constitutes a definite safety hazard. dangerous voltages may exist even with the power cable removed. NOTE Refer to Grounding Guideline for Cellular Radio Installations – 68P81150E62. Failure to comply with these precautions or with specific warnings elsewhere in this manual violates safety standards of design. Under certain conditions. S always disconnect power and discharge circuits before touching them. . The three-contact to two-contact adapter must have the grounding wire (green) firmly connected to an electrical ground (safety ground) at the power outlet. or component replacement. Only Factory Authorized Service Personnel or other qualified maintenance personnel may remove equipment covers for internal subassembly. . Keep away from live circuits Operating personnel must: S not remove equipment covers. You. as the user of this product.

Use caution when exposing or handling the CRT Breakage of the Cathode–Ray Tube (CRT) causes a high-velocity scattering of glass fragments (implosion). Contact Motorola Warranty and Repair for service and repair to ensure that safety features are maintained. are present in this equipment. avoid rough handling or jarring of the equipment. capable of rendering first aid and resuscitation. precede potentially dangerous procedures throughout this manual. capable of causing death. such as the example below. is present. WARNING Dangerous voltages.General Safety – continued Do not service or adjust alone Do not attempt internal service or adjustment. unless another person. The CRT should be handled only by qualified maintenance personnel. do not install substitute parts or perform any unauthorized modification of equipment. To prevent CRT implosion. Use extreme caution when handling. using approved safety mask and gloves. and adjusting . iv Motorola–Cisco PDN IOS Integration NOV 2002 . Instructions contained in the warnings must be followed. You should also employ all other safety precautions that you deem necessary for the operation of the equipment in your operating environment. Dangerous procedure warnings Warnings. testing. Do not substitute parts or modify equipment Because of the danger of introducing additional hazards.

Inc. Abstract: This document addresses the integration between Motorola RAN (Radio Access Network) and Cisco PDSN/HA running Release 1. Inter Vendor Verification and Validation Group 5555 N.0. Beach St. Fort Worth. Motorola.Motorola .2 using Cisco AR3. Texas 76137 Version 1.Cisco PDN IOS Integration White Paper Note: This is a dynamic document that is subject to change without notice.0 Motorola – Cisco IOS Network Integration Page 1 of 30 .

2002 Oct.Revision History This revision history page is intended to ensure that all parties are knowledgeable of the additions. and updates made to the white paper. Motorola – Cisco IOS Network Integration Page 2 of 30 .0 Version 1. 2002 Nov. 9.1 0.2 1. 14. additional information on upgrade strategy. corrections to config file statements. 2002 Authors Tracy McElvaney Tracy McElvaney Tracy McElvaney Description Initial Draft Updates after review by Cisco Dev/Test group Updates after review by TIPS and MOT development. 15. deletions. Version 0.0 Sections All All All Date Oct.

MPPC – Microsoft Point-to-Point Compression Protocol B BTS – Base Transceiver Station BVI – Bridged Virtual Interface N NAS – Network Address Server C CAT (6509) – Cisco Catalyst 6509 switch used in Motorola Access Node CBSC – Centralized Base Station Controller CCO – Cisco Connection Online CDG – CDMA Data Group CDMA – Code Division Multiple Access CDMA-Ix – CDMA RP interface defined on Cisco PDSN CLI – Command Line Interface O 1X . See also RP.0 S SA-ISA – IPSEC Service Adapter for Cisco PDSN/HA SIP – Simple Internet Protocol T TCP – Transfer Control Protocol TX .Transceiver U V VJ TCP/IP – Van Jacobsen TCP/IP Header Compression VLAN – Virtual Local Area Network VPDN – Virtual Private Dial-up Networking VPN – Virtual Private Networking Motorola – Cisco IOS Network Integration Page 3 of 30 .25MHz spread spectrum) OMC – Operations and Maintenance Center OSPF – Open Shortest Path First D P PA – Port Adapter PCF – Packet Control Function PDN – Packet Data Network PDSN – Packet Data Serv ing Node Pi – Payload Interface PPP – Point-to-Point Protocol E Q F FA – Foreign Agent (see also PDSN) FE – Fast Ethernet FTP – File Transfer Protocol R RAN – Radio Access Network RP – Radio Packet Interface (see also A10/A11) G H HA – Home Agent Home AR – AAA serving the Home Agent for MIP connections. Authorization and Accounting Server AN – Access Node AR – Access Registrar (see AAA) AREGCMD – Cisco Access Registrar Command Line Interface M MIP – Mobile Internet Protocol MN – Mobile Node MN-AAA – Mobile Node to AAA authentication (Mobile IP only). HSRP – Hot Standby Routing Protocol I IMSI – International Mobile Station Identity IOS – Inter-Operability Specification IP – Internet Protocol IPSEC – Internet Protocol Security IVVV – Inter-Vendor Verification and Validation L Local AR – AAA serving the PDSN/FA for local connections.RTT – CDMA 2000 Radio Transmission Technology (1 * 1. AAA – Authentication. Version 1.Glossary A A10 / A11 – IOS packet data interface between PCF and PDSN. MN-HA – Mobile Node to Home Agent Authentication (Mobile IP only).

0 Motorola – Cisco IOS Network Integration Page 4 of 30 . published by Cisco on CCO web site. ENG119255 version 2.cisco. * The Cisco CCO web site can be accessed at http://www. [5] Cisco-Motorola CDMA 1XRTT Packet Network Configuration. published internally to test groups by Cisco Systems [6] Cisco Access Registrar 3.2 feature in Cisco IOS release 12. published by Cisco on CCO web site.1 References [1] Cisco Packet Data Serving Node (PDSN) Release 1.2 feature in Cisco IOS release 12. [3] Cisco CDMA2000 Home Agent .2(8)BY . published by Cisco on CCO web site. published by Cisco on CCO web site.0 Documentation . published by Cisco on CCO web site. [2] Relase Notes for the Cisco PDSN 1.2(8)BY .2 .1.com Version 1. [4] Release Notes for the Cisco Home Agent 1.

.............................................20 5................................................................................... 30 Version 1.....................................................................................................................1 6..........................................................................2 PDSN Member Configuration.1 Add the VLANs............. 18 5.......................................................................................................................2 Distributed in Customer Network...... 28 HOME AAA CONSIDERATIONS....................24 5............23 5........................................6 LOCAL AAA DATABASE PROVISIONING..............................26 6.................................. 29 UPGRADE CONSIDERATIONS ......................................................3..................................................6 3 IVVV CISCO PDN TEST BED .................................... 30 UPGRADING THE AR...............................................................................................................................................5 AN DATABASE .................... 12 5..................Table of Contents 1 REFERENCES .................................................6...................................................................2 PEER-TO-PEER CLUSTERING ..................................................4 2 SCOPE...................................................................................................3 CONTROLLER/MEMBER CLUSTERING......................................................2 Peer-to-Peer Clustering.................................................................................................................................................................................................................................................................................4 CBSC DATABASE PROVISIONING........9 4.....................................................................................................................................15 5..............................6.....................9 4.............3 7 HA CONFIGURATION...............................................5..............1 Stand-alone Configuration (RAN PDSN Cluster Control) ...............................................................5.2 UPGRADING PDSN / HA DEVICES ..........................................................................................................................................1 Direct to AN .......................... 8 4...........11 5 SIMPLE IP DATABASE PROVISIONING...........................................20 5........1 PDSN Controller Configuration.........2...............................................................1 7...................................................................................2............................................................................3...................................................................................................................................................................24 5.....................................18 5.....................3...3 NETWORK CONFIGURATIONS. 15 5...........................................................12 5........................................22 5......................................................................3....................................1 Verify the PDSN Client has been added to the AR.........................................2 6..............30 7.7 4 PDN NETWORK OVERVIEW .......................25 6 MOBILE IP DATABASE PROVISIONING............................................................................................................................................................................................................................................................................................................................6.......................................................................................................... 19 5......................................................................9 4............ 15 5.........................................................................................................2............................................................................................................................................3 Verify the User Profile ..................3 Configure the Layer 2 Switched Ports..4 Configure the OSPF routing table......................... 9 4....................................................................1 SUPPORTED PDSN/HA CONFIGURATIONS .............................................................0 Motorola – Cisco IOS Network Integration Page 5 of 30 ......................................................................................................................................5..............................................................................2 Verify the User Record ....1 PDSN CONFIGURATION.................................... 23 5............................................................................................................................... 9 4................................................2 CLUSTER CONFIGURATIONS............5.......................................................................................................................................................................................................................................................2 Configure the VLAN interfaces......8 4...10 4........................... 26 PDSN M OBILE-IP CONFIGURATION.................................................................................................3 Controller/Member Clustering........................

0 Motorola – Cisco IOS Network Integration Page 6 of 30 . This paper will ensure the respective systems inter-operate through Motorola’s CDMA CDG A10/A11 IOS Interface. The integration process has been implemented and tested in the IVVV lab in Fort Worth. Since there is no Motorola specific requirement for the configuration of the Cisco AR. this document will not attempt to cover all possible configurations. It is intended to provide the guidance necessary to ensure successful integration of the Motorola RAN with the Cisco PDSN. The corresponding Cisco AR release used for this integration is 3.2 Scope This document is intended to provide a descriptio n of the steps required to integrate the Motorola CDMA 1X-RTT RAN and Cisco 7206 VXR NPE-400 running Cisco PDSN/HA Release 1.2. The relevant AR material required for configuration can be accessed by the hyperlink in the References section.0. It has been assumed that the necessary database is already data filled on CBSC and required IP planning is in place for the Cisco PDN and Access Node. All information in this document is based on experiences learned during the IVVV certification of the Cisco PDN Release 1. Disclaimer: This paper is not intended to replace installation/configuration documentation provided by either Motorola or Cisco. It is the end user’s responsibility to have at their disposal all related installation/configuration documentation provided by each company. This document is a technically oriented guide that will describe and explain the steps to deploy a Motorola-Cisco IOS system. Version 1. it will not be addressed in this document. Due to the complex nature of the networking equipment involved.2.

0 BTS -3 Motorola – Cisco IOS Network Integration Mobile Nodes: Motorola 120X Kyocera 2345 Qualcomm Twister Page 7 of 30 .3 IVVV Cisco PDN Test Bed FTP Server Fa2/0 Access Node Fa1/0 Fa0/0 Fa0/1 PCF-1 HA-1 / Controller-2 / PDSN-3 PCF-2 Controller-1 / HA-2 / PDSN-4 PCF-3 PDSN-1 Local AR Home AR PDSN-2 Internet DNX-11 Firewall Data Client: Win2K Win98 Linux BTS -2 BTS -1 Version 1.

while the other FE port adaptor will be configured to handle all outgoing traffic from the PDSN. depending on the performance.mz Basic PDSN w/ IPSEC Enhanced PDSN C7200-c6is. Image Name C7200-c5is. Prepaid support Controller/Member Clustering or Peer-toPeer Clustering. back office traffic redundancy. This recommended configuration takes into account port adaptor redundancy. Prepaid support. AAA and Network Management traffic will be handled by the two 10/100 Ethernet ports hosted on the I/O controller and configured using a BVI. For Motorola’s implementation. there are several types of PDSN / HA images. which uses OSPF routing.mz Description Basic PDSN Image C7200-c5ik9s.mz C7200-c6ik9s. clustering capabilities and extended features that will be supported. no prepaid. requires SA-ISA adapter Controller/Member Clustering or Peer-toPeer Clustering. it is recommended that one FE port adaptor will handle all incoming traffic to the PDSN.4 PDN Network Overview 4. no prepaid. The SA-ISA card should be in the identical slot as above (slot 4/1). For Release 1. If the PDSN/HA will support IPSEC. switching redundancy. and cluster controller redundancy. The following table will explain which image types are required for different PDSN/HA configurations.2.0 Enhanced PDSN w/ IPSEC Comments Peer-to-Peer Clustering. SA-ISA PA-FE-TX PA-FE-TX 1 port fast ethernet 1 port fast ethernet I / O Controller 2 10/100 TX Ethernet Ports 2 PCMCIA Slots Figure 1: Recommended Hardware Configuration for PDSN/HA The two Fast Ethernet port adaptors (PA-FE-TX) will be configured for RP and Pi traffic.mz Version 1. lower session capacity Peer-to-Peer Clustering. an SA-ISA service adaptor is required.1 Supported PDSN/HA Configurations The recommended hardware configuration for the Cisco 7200-VXR based PDSN/HA is given below. The SA-ISA card is not required for a PDSN controller. requires Motorola – Cisco IOS Network Integration Page 8 of 30 .

a redundant Controller can be configured. In the Controller/Member configuration. the customer will decide on one of two possible network design alternatives. 4. Using the HSRP protocol. The Controller will load balance and perform inter-PDSN handoff avoidance for all members in its cluster.1.2 introduces the Controller/Member clustering feature. 4. 4. With redundancy enabled.mz image *Note: Special export requirements apply to all IPSEC images which will be installed outside the United States. the PCF should be configured to have only the Controller in its Cluster IP list on the OMC.2.mz Basic HA image w/ Use with C7200-c5ik9s. and then a group of PCFs must be associated with that cluster list. the OMC database should be populated with a cluster list of PDSNs. 4. Controller/Member clustering is only supported by the c6 PDSN images.3 Network Configurations In the network design phase. the PCF will employ a userdefined selection scheme to distribute the load between all PDSN devices in a cluster. 3) ROUND ROBIN.SA-ISA adapter C7200-h1is-mz Basic HA Image Use with C7200-c5is.3 Controller/Member Clustering PDSN Release 1.2 Peer-to-Peer Clustering In the Peer-to-Peer Cluster. the PCF can have one or all of the PDSN devices in its cluster configuration. To configure a PDSN cluster. The choices for PCF-based PDSN selection are 1) ACTIVE/STANDBY. Redundant HSRP groups are also supported. In 16. 2) IMSI Hashing. the global session tables will be synchronized between the active and standby controllers. In Peer-to-Peer clustering.2. This cluster list will be used by all associated PCFs for distributing calls to the PDSN devices defined. which significantly improves the cluster capacity by provisioning a dedicated cluster controller or redundant cluster controller group. using multi-cast IP messages.0 Motorola – Cisco IOS Network Integration Page 9 of 30 .2.1 Stand-alone Configuration (RAN PDSN Cluster Control) In the stand-alone mode. No user traffic is handled by a Cluster Controller. a PDSN maintains only its local session information and cannot perform handoff avoidance or load balancing with other PDSN devices. The PDSN/HA/AR can either be “tethered” to an AN in which all devices will be Version 1.mz or C7200IPSEC support c6ik9s.mz or C7200-c6ismz image C7200-h1ik92. Load balancing and handoff avoidance will occur between the PDSNs based on global session information. This controller performs the PDSN selection function and maintains the global session tables for the entire cluster. This configuration is resource intensive and limits the capacity of the cluster because each PDSN has to maintain the global session information of the entire cluster.2 Cluster Configurations 4. The HSRP address is used in the OMC PDSN cluster configuration for a controller instead of the CDMA-Ix interface as with the stand-alone PDSN. Stand-alone configuration can be used with any PDSN image. each PDSN is configured to communicate its session information to all other PDSN devices in the cluster. Peer-to-Peer clustering is supported by both c5 and c6 PDSN images.

This VLAN will carry all AAA/NMS traffic to and from the PDSN/HA devices. which may enter on an opposite CAT interface.physically connected to a single AN. and VLAN-2 is also defined in CAT-2. three VLANs are set up on each CAT. The OSPF cost settings on corresponding PDSN/HA interfaces will be configured in the opposite fashion to control the flow of traffic out of the PDSN. with a lower OSPF cost in order to route all RP/Pi and MIP traffic out of the AN to the PDSN/HA devices.3. VLAN 1 is designated as the BVI VLAN. In the direct configuration. where the physical port is switched into the VLAN.0 Motorola – Cisco IOS Network Integration Page 10 of 30 . Any AR that is directly connected to the AN will be connected to the AR/NMS VLAN (VLAN1) on CAT-1. By defining each VLAN in both CATs. the PDSN/HA and AR devices (or any combination thereof) will be directly connected to the CAT 6509 routers in the Access Node. the VLANs will use the ISL trunk to route packets destined for that VLAN to the other CAT.1 Direct to AN In the direct configuration. This is to allow for OSPF routing of packets coming in from the PCF or network. VLAN 2 is designated as the outgoing RP/Pi and MIP VLAN. The routing should be configured using OSPF and VLANs so that redundancy and load sharing are maximized. This VLAN will be configured with a higher OSPF cost value than VLAN 2 in order to act as a redundant route to the outgoing RP/Pi and MIP traffic. or any combination of the devices can be configured in a distributed fashion such that the AN routes packets from the PCF to the customer network and on to a PDSN/HA/AR. If the Controller/Member clustering and/or redundant HA schemes are used. it recommended that a fourth VLAN be added as a Controller and HA BVI VLAN. Finally VLAN 3 is designated as the incoming RP/Pi and MIP VLAN. which is physically located remotely in the customer’s network. there are several configuration principles to consider. This means that Version 1. although no physical Ethernet ports will be switched into those VLANs on the opposite CAT. VLAN-2 RP/Pi or MIP to PDSN/HA CAT-1 AR / NMS Bridge VLAN-1 PDSN CAT-2 RP/Pi or MIP from PDSN/HA VLAN-3 Figure 2: Default Routing Diagram of PDSN directly connected to AN *Note that VLAN-3 is also defined in CAT-1. The PDSN controller and redundant HA configurations use an HSRP interface as the primary interface. In the direct configuration. This VLAN will be configured on the AN. 4.

An example of the Controller/HA connectivity diagram is below. a second BVI needs to be created to act as a virtual interface for the HSRP configuration. The remote configuration example will not be covered in this document.0 Motorola – Cisco IOS Network Integration Page 11 of 30 . Version 1. In the remote configuration. and configuration on the CAT-6509 devices will be much less complex than in the direct configuration.3. or the redundant approach can be followed even though a redundant device is not yet deployed. the PDSN/HA and AR devices (or any combination thereof) will be located remotely from the Access Node.OSPF routing on the FE Port Adapters will not be possible. In order to maintain port redundancy. as there are too many possibilities to consider. VLAN-4 RP / MIP Bridge CAT-1 AR/NMS Bridge VLAN-1 PDSN Controller / Redundant HA CAT-2 RP / MIP Bridge VLAN-4 This document will cover the redundant HA and Controller configurations.2 Distributed in Customer Network In the remote configuration. 4. The latter will provide for ease of migration if a redundant HA/Controller ever is deployed. For the nonredundant HA configuration. the PDSN example configuration can be used as a model for configuring the HA interfaces (fa1/0 and fa2/0) as they are identical to the PDSN. it is recommended that redundant links be configured on each CAT-6509 in the AN and that the OSPF priorities be set such that load sharing occurs between the CATs.

1 PDSN Configuration Listed below are the key actions which are required for basic PDSN operation. but IPSEC has not been configured. as there is no Motorola specific configuration documentation required. which will be known to the public network and used for Layer 3 routing purposes. version 12.0 Motorola – Cisco IOS Network Integration Page 12 of 30 . which will be used for Network Management. Define the Loopback interface. Enable RP Signaling. This template was verified and used during lab testing of Cisco 1. Define the CDMA-Ix Interface. Also.11 auth-port 1645 acct-port 1646 ! aaa authentication ppp default local group MOT Version 1.bin ! Configure AAA services aaa new-model ! ! aaa group server radius MOT server 5. this image is IPSEC capable. For IPSEC. please refer to the Cisco configuration documentation. The generic configuration file listed in Cisco’s PDSN documentation was taken and modified to fit Motorola’s generic configuration template. which will be used for terminating the PPP links of the mobile nodes.5 Simple IP Database Provisioning The following section has been formatted to cover the typical PDSN configuration for a Motorola network using OSPF routing.2. Define Virtual Template Interface for terminating PPP sessions.250. VPN or other enhanced features. AAA and Peer-to-Peer clustering communication (if supported). Note tha t this template enables the enhanced PDSN service with Controller/Member clustering. Configure the PDSN for AR communications.2 PDN in the IVVV lab. A sample configuration file of the basic PDSN is given below.2 service timestamps debug uptime service timestamps log uptime no service password-encryption service cdma pdsn ! hostname pdsn_A ! boot system flash disk0:c7200-c 6ik9s-mz. Define the Loopback interface. 5.122-8. The generic product documentation does not take into account the routing protocols that may be used by different vendors/customers. Define the Bridge Group Virtual Interface. o o o o o o o o Enable PDSN Services.BY. Prepaid. which will be the PDSN address known to a PCF in the RAN network.

255.254.255.255 ! ! Configure RP Interface interface CDMA-Ix1 description PDSN A RP Interface ip address 5.aaa authorization config-commands aaa authorization network default group MOT aaa authorization configuration default group MOT aaa accounting update periodic 60 aaa accounting network pdsn start-stop group MOT aaa session-id common enable password ivvv ! username pdsnA ip subnet-zero no ip gratuitous-arps ip cef ! controller ISA 4/1 ! ! Enable IRB routing protocol for bridge virtual interface bridge irb ! interface Loopback0 no ip address ! ! Configure PPP virtual loopback address interface Loopback1 ip address 5.255 no ip mroute-cache tunnel source 5.2.2.250.255.2.33 255.225 255.255.255.254.245 255.254.2.0 Motorola – Cisco IOS Network Integration Page 13 of 30 .240 ip ospf message-digest-key 1 md5 CISCO ip ospf cost 4 ip ospf hello-interval 30 Version 1.255.225 ! ! FA0/0 and FA0/1 will be for AR/NMS communications ! AR/NMS interfaces will be configured as a Virtual Bridge interface FastEthernet0/0 description AR/NMS to CAT1 fa3/5 no ip address duplex full speed 100 bridge-group 1 ! interface FastEthernet0/1 description AR/NMS to CAT2 fa3/5 no ip address duplex full speed 100 bridge-group 1 ! !FA1/0 and FA2/0 will be for RP/Pi traffic ! RP/Pi traffic will be routed into FA1/0 and out of FA2/0 using OSPF interface FastEthernet1/0 description RP/Pi in from CAT1 fa3/13 ip address 5.

0.0.0 area 200 ! ! Configure local IP pool for PPP ip local pool pdsna_sip 5.2.33 0.7 ip classless no ip http server ip pim bidir-enable ! ip radius source-interface BVI1 ! ! Configure RADIUS server (local AAA) radius-server host 5.240 ip ospf message-digest-key 1 md5 CISCO ip ospf cost 3 ip ospf hello-interval 30 duplex full ! ! Configure PPP Virtual Template interface Virtual-Template1 ip unnumbered Loopback1 ip ospf network point-to-point peer default ip address pool pdsna_sip ppp accm 0 ppp authentication chap pap optional ppp accounting none ppp timeout idle 2000 ! ! Configure Virtual Bridge Interface for AR/NMS interface BVI1 description AR/NMS Bridge ip address 5.250.255.2.254.2.250.255.2.255.0.2.2.49 0.250.11 auth-port 1645 acct-port 1646 key cisco radius-server retransmit 3 radius-server deadtime 5 radius-server vsa send accounting 3gpp2 radius-server vsa send authentication 3gpp2 ! Configure RP Interface paramters cdma pdsn virtual-template 1 cdma pdsn a10 max-lifetime 36000 cdma pdsn msid-authentication ! Define default security association for PCF devices cdma pdsn secure pcf default spi 100 key hex 31313131313131313131313131313131 ! Enable ieee bridge protocol and enable ip routing Version 1.0 Motorola – Cisco IOS Network Integration Page 14 of 30 .5 255.1 5.240 no ip mroute-cache ! ! Configure OSPF routing table router ospf 100 log-adjacency-changes area 200 authentication message-digest redistribute connected subnets passive-interface Virtual-Template1 network 5.255.250.0.49 255.254.2.0 area 200 network 5.duplex full ! interface FastEthernet2/0 description RP/Pi out to CAT2 fa3/13 ip address 5.250.

a 7206 VXR must be designated and configured as the Controller. then member PDSNs can be configured into the cluster. Version 1. Please do not enter these commands if the device is meant to operate in the stand-alone or Peer-to-Peer clustering modes.bridge 1 protocol ieee bridge 1 route ip call rsvp-sync ! mgcp profile default ! dial-peer cor custom ! gatekeeper shutdown ! line con 0 line aux 0 line vty 0 4 ! ntp clock-period 17180175 ntp server 5. Redundant OSPF routes will be configured to route Controller/Member signaling information. 5. The Controller does not carry any user traffic. Once the controller is enabled.1 PDSN Controller Configuration The following information details a basic configuration for a Controller in the Controller/Member configuration.0 Motorola – Cisco IOS Network Integration Page 15 of 30 . Please do not execute these commands if the PDSN is operating in stand-alone or in Controller/Member clustering mode. an HSRP address will be assigned to FA1/0.2.3. or if the Controller fails.2 Peer-to-Peer Clustering The following information should be entered into any PDSN participating in Peer-to-Peer communications. since it does not handle any user traffic.0. if communications to FA1/0 is lost. Controller redundancy is supported using the HSRP protocol.1 ! end 5.3 Controller/Member Clustering In order to enable Controller/Member clustering. ! ! Define the cluster security association cdma pdsn secure cluster default spi 100 key ascii cisco ! Define the interface to use for PDSN selection cdma pdsn selection interface CDMA-Ix1 ! Configure load parameters cdma pdsn selection session-table-size 8000 cdma pdsn selection load-balancing threshold 7500 5. If controller redundancy is configured (as in the following example). Note that the BVI will still be used by the Controller for NMS communications. Note that an SA-ISA card is not required for the controller. the standby controller will take over as primary. This means that.

BY.bin enable password ivvv ! username contA ip subnet-zero no ip gratuitous-arps ip cef ! ! ! Enable IRB routing protocol bridge irb ! ! ! FA0/0 and Fa0/1 will be used for NMS communications ! Controller does not communicate with AAA ! BVI 1 will be used as NMS bridge interface FastEthernet0/0 description AR/NMS to CAT1 fa3/3 no ip address duplex full speed 100 bridge-group 1 ! interface FastEthernet0/1 description AR/NMS to CAT2 fa3/3 no ip address duplex full speed 100 bridge-group 1 ! ! FA1/0 and FA2/0 will be used for RP proxy signalling to members ! BVI 2 will be used for RP signalling bridge interface FastEthernet1/0 description RP to CAT1 fa3/22 no ip address duplex full bridge-group 2 ! interface FastEthernet2/0 description RP to CAT2 fa3/22 no ip address duplex full Version 1.0 Motorola – Cisco IOS Network Integration Page 16 of 30 .2 service timestamps debug uptime service timestamps log uptime no service password-encryption service cdma pdsn ! hostname controller_A ! boot sys tem flash disk0:c7200-c6ik9s-mz.Current configuration : 1806 bytes ! ! Last configuration change at 15:35:42 UTC Tue Oct 1 2002 ! NVRAM config last updated at 15:35:42 UTC Tue Oct 1 2002 ! version 12.122-8.

2.0.0.1 ! end Version 1.0 5.2.240 no ip mroute-cache ! interface BVI2 description RP Bridge ip address 5.0 0.2.255.255.2.3 255.255.252.bridge-group 2 ! interface BVI1 description AR/NMS Bridge ip address 5.13 no ip http server ip pim bid ir-enable ! ! ! Define default PCF security association and cluster parameters cdma pdsn secure pcf default spi 100 key hex 31313131313131313131313131313131 cdma pdsn secure cluster default spi 100 key ascii cisco cdma pdsn cluster controller standby Control_Group_A cdma pdsn cluster controller interface BVI 2 cdma pdsn cluster controller timeout 10 cdma pdsn cluster controller window 2 bridge 1 protocol ieee bridge 1 route ip bridge 2 protocol ieee bridge 2 route ip call rsvp-sync ! ! mgcp profile default ! dial-peer cor custom ! gatekeeper shutdown ! ! line con 0 line aux 0 line vty 0 4 login ! ntp clock-period 17179958 ntp server 5.2.250.0.255.11 standby 2 priority 100 standby 2 name Control_Group_A ! ! Define Gateway of last resort so controller can route packets ip classless ip route 0.0.252.252.0 Motorola – Cisco IOS Network Integration Page 17 of 30 .0.3 255.0 no ip mroute-cache standby 2 ip 5.

000 to 255. add the PDSN cluster on the OMC CLI.2 PDSN Member Configuration The following data should be entered into each PDSN that will function as a member of a cluster.000. any number of PDSNs in Peer selection group (maximum of 16) can be added in one OMC PDSN cluster.3.11 cdma pdsn cluster member interface CDMA-Ix1 cdma pdsn cluster member timeout 10 cdma pdsn cluster member window 2 ! 5.4 CBSC Database Provisioning Using the following example.255.255.5.252.000.255. For Peer-to-Peer configurations and/or stand-alone configuration.000 to 255.255 surrounded by double quotes IPADDRESS= ? <IP Address of RP Interface> ?? CDMA-IX 1 for PDSN in stand alone or Peer-to-Peer ?? HSRP address for Controller expecting IP address (or subnet mask) from 000.0 Motorola – Cisco IOS Network Integration Page 18 of 30 . I3V-SUNOMC1-000642 > add pdsn-<cluster_id> ! expecting an integer number (from 1 to 16) NUMPDSNS= ? <number of PDSNs in cluster> ?? Stand Alone: between 1 and 16 PDSNs may be entered ?? Controller/Member: Only the controller address is needed expecting an integer number (from 0x00000100 to 0xffffffff) SPI= ? 0x100 Enter a string of characters surrounded with double quotes SECURITYKEY= ? “31313131313131313131313131313131” expecting an enumerated value: N Y SUMMARIZED= ? n expecting IP address (or subnet mask) from 000.255. For Controller-Member configurations.2.000. ! cdma pdsn secure cluster default spi 100 key ascii cisco ! Controller address should be the HSRP address of BVI 2 cdma pdsn cluster member controller 5. only the primary controller should be added to the OMC PDSN cluster.255 surrounded by double quotes SUBNETMASK= ? <subnet mask of PDSN network> expecting an integer number (from 1 to 32767) IPFROM= ? <indicates cluster which PDSN IP addresses are taken fro m (optional)> expecting an enumerated value: ACTIVESTANDBY IMSIHASHING ROUNDROBIN Version 1. Please do not enter this information into the Cluster Controller or into a PDSN that is meant to operate in the stand-alone or Peer-to-Peer clustering modes.000.

Once the PDSN cluster is defined. which PDSN will be Primary expecting an integer number (from 0 to 16) SECONDARYINDEX= ? <index if PDSN> ?? If ACTIVESTANDBY is used. Motorola – Cisco IOS Network Integration Page 19 of 30 . The following examples give a generic overview as the required steps for integrating a PDSN/AR into the Access Node.1 Registration Request Message.5 AN Database The AN database configuration should be determined by the IP design of the system. PANID/CANID and ESN and pass Registration Request message per IOS 4. This is accomplished by setting the OSPF priorities correctly on the CAT and PDSN.0. No NVOSE will remove the NVOSE.0 RP/Pi traffic should be routed into the PDSN on the PA (FA1/0) interface from CAT-1. the following example will detail the steps required to configure the AN according to the PDSN configuration given in the previous section. Non-Standard BASE ID should not be used unless required by PDSN/AAA o Allowing NVOSE will cause PCF to also pass PANID/CANID. o Version 1. It is impossible to determine the AN configuration for a distributed network design whereby the PDN equipment is located remotely from the Access Node. and out of the PDSN on the other PA interface (FA2/0) to CAT-2 in order to maximize redundancy and loading on the interfaces.SELSCHEME= ? <PDSN selection scheme> expecting an integer number (from 0 to 16) PRIMARYINDEX= ? <index of PDSN> ?? If ACTIVESTANDBY is used. ITID-OMC2-000106 > edit pktpcf-<cbsc#>-<pcf#> pdsn add <cluster#>! 5. Non-Standard BASE ID omits sector id and shifts remaining 3 elements pre-pending the ID with an ascii “0”. the following CLI command should be executed for all PCF devices that will operate using the above cluster list. Therefore. which PDSN will be secondary expecting an enumerated value: ALLOW_NVOSE NO_NVOSE NVOSEMODE= ? ALLOW_NVOSE expecting an enumerated value: NO_SECTOR_ID STANDARD BSIDFORMAT= ? STANDARD expecting an enumerated value: NO YES RESERVED1= ? NO expecting an enumerated value: NO YES RESERVED2= ? NO o Standard BASE ID is as defined by 3GPP2. ESN and 3GPP2 Active time in IOS 4.

45 255.2.255. VLAN-1 should be the VLAN carrying traffic into the PDSN from CAT-1.61 255.255. VLAN-2 should be the VLAN carrying traffic out of the PDSN into CAT-2. Also the converse holds that no ports from CAT-2 will be switched into VLAN-1.5.255.13 255.255. If PDSN Controller and/or redundant HA features are part of the network design.2 Configure the VLAN interfaces Configure CAT-1 VLANs.250. no ports from CAT-1 should be switched into VLAN-2.240 no ip redirects ip ospf message-digest-key 1 md5 CISCO ip ospf cost 3 ip ospf hello-interval 30 ntp broadcast ! !VLAN 302 will be the redundant outgoing route to the PDSN/HA !Note: no interfaces on CAT-1 will be switched into VLAN302 interface Vlan302 description RP/Pi/MIP from PDSN/HA ip address 5. !VLAN 300 will be AR/NMS VLAN !Note: All PDSN/HA fa0/0 interfaces will be switched into CAT-1 VLAN 300 interface Vlan300 description AR/NMS VLAN CAT1 ip address 5.0 Motorola – Cisco IOS Network Integration Page 20 of 30 .5.255.o o o There should be three VLANs configured for routing the PDN traffic. the a fourth VLAN will be added and configured as a Bridge (just like the AR/NMS VLAN).240 no ip redirects ntp broadcast ! !VLAN 301 will be the default outgoing route to the PDSN/HA !Note: All PDSN/HA fa1/0 interfaces will be switched into CAT-1 VLAN 301 interface Vlan301 description RP/Pi/MIP to PDSN/HA ip address 5. 5. Although both VLANs need to be configured in each CAT (this enables VLAN trunk routing over the ISL links).2.250.250.255. VLAN-3 should be the AAA/NMS VLAN carrying RADIUS signalling and any cluster messaging for cluster configurations.240 no ip redirects ip ospf message-digest-key 1 md5 CISCO Version 1. Care should be taken when configuring VLAN-1 and VLAN-2.2.1 Add the VLANs Add the VLANs to each CAT for routing PDN traffic MLS -1-1#vlan database MLS -1-1(vlan)#vlan <vlan number> name RP_PI_to_PDSN MLS -1-1(vlan)#vlan <vlan number> name RP_PI_from_PDSN MLS -1-1(vlan)#vlan <vlan number> name AR_NMS_VLAN MLS -1-1(vlan)#vlan <vlan number> name Controller_HA_VLA N MLS -1-1(vlan)#exit 5.

255.0 Motorola – Cisco IOS Network Integration Page 21 of 30 .2.2.255.250.14 255. the netmask is set to 24 bits to ! include the addresses which will be used for the MIP virtual network ! Customers may employ alternate routing techniques to achieve the same goal.13 255.ip ospf cost 4 ip ospf hello-interval 30 ntp broadcast !VLAN 500 will be the Controller/HA VLAN !Note: All Controller/HA fa1/0 interfaces will be switched into CAT-1 VLAN 500 interface Vlan500 description Controller/HA VLAN CAT1 ip address 5. ip address 5.252.46 255.252.255.2.255.240 no ip redirects ntp broadcast ! !VLAN 301 will be the default outgoing route to the PDSN/HA !Note: No PDSN/HA interfaces will be switched into CAT-2 VLAN 301 interface Vlan301 description RP/Pi/MIP to PDSN/HA ip address 5.250.62 255.255.240 no ip redirects ntp broadcast ! Configure the CAT-2 VLANs !VLAN 300 will be AR/NMS VLAN !Note: All PDSN/HA fa0/1 interfaces will be switched into CAT-2 VLAN 300 interface Vlan300 description AR/NMS VLAN CAT2 ip address 5.250.255.255.240 no ip redirects ip ospf message-digest-key 1 md5 CISCO ip ospf cost 4 ip ospf hello-interval 1 ip ospf dead-interval 3 ntp broadcast !VLAN 500 will be the Controller/HA VLAN !Note: All Controller/HA fa2/0 interfaces will be switched into CAT-2 VLAN 500 interface Vlan500 description Controller/HA VLAN CAT1 ! In this example.240 no ip redirects ip ospf message-digest-key 1 md5 CISCO ip ospf cost 3 ip ospf hello-interval 30 ntp broadcast ! !VLAN 302 will be the redundant outgoing route to the PDSN/HA !Note: All fa2/0 interfaces on PDSN/HA will be switched into CAT-2 VLAN 302 interface Vlan302 description RP/Pi/MIP from PDSN/HA ip address 5.0 no ip redirects ntp broadcast Version 1.2.2.255.14 255.255.255.

The following is an example of a single PDSN configured for the above VLAN assignments.0 Motorola – Cisco IOS Network Integration Page 22 of 30 . CAT-1 port assignments ! interface FastEthernet3/3 description AR/NMS from PDSN A fa0/0 no ip address duplex full speed 100 switchport switchport access vlan 300 switchport mode access end ! interface FastEthernet3/23 description RP/Pi to PDSN A fa1/0 no ip address duplex full speed 100 switchport switchport access vlan 301 switchport mode access end CAT-2 port assignments ! interface FastEthernet3/3 description AR/NMS to PDSN A fa0/1 no ip address duplex full speed 100 switchport switchport access vlan 300 switchport mode access end ! interface FastEthernet3/23 description RP/Pi from PDSN A fa2/0 no ip address duplex full speed 100 switchport switchport access vlan 302 switchport mode access Version 1.3 Configure the Layer 2 Switched Ports Each router (PDSN/HA/Controller) will have four ports switched into the appropriate VLAN. The same configuration principle applies to HA/Controllers as well.! 5.5. All ports will be configured in the same fashion.

0. Please note that the wildcard bits will most likely be different based on core IP network design.252. To start the Cisco AR CLI tool (aregcmd).0 0. always ensure that the AN routing tables are able to route to the virtual network addresses configured for MIP users.255 area 200 * For Mobile IP applications. Example of the network statements in the router ospf 100 routing table: router ospf 100 .end 5.2. ! 250 subnet is PDSN address range network 5. All rights reserved. Overall Cisco AR configuration and setup should be reviewed in the Cisco documentation.0. Logging in to localhost [ //localhost ] LicenseKey = <license ###> Radius/ Administrators/ Server 'Radius' is Running. 5.0 Motorola – Cisco IOS Network Integration Page 23 of 30 . Once the AR has successfully started.0 0.255 area 200 ! 252 subnet is the Controller/HA address range network 5. . An example of the connected networks would be the network used for each VLAN defined (PA and BVI) on that particular CAT. the following should be seen: Cisco Access Registrar 3.2.0R0 Configuration Utility Copyright (C) 1995-2002 by Cisco Systems. .5.250. login to the server and change execute the following command: # /opt/CSCOar/bin/aregcmd -s This will initiate the aregcmd interface and give the user access to the AR. its health is 10 out of 10 --> Version 1.0. ! set authentication type for PDN ospf area area 200 authentication message-digest .0.4 Configure the OSPF routing table Enter the connected networks into the CAT OSPF routing table. Inc.6 Local AAA Database Provisioning The following section will discuss specific details on basic checks for ensuring that the PDSN and user exist in the AR database.

2 Verify the User Record The following command shows the user ivvv_tester has been added under the default local user list ISPABCLocalUsers. Notice that the user has no attributes defined. This means the profile should be verified for accuracy.6. Note that each AR may have several different userlists defined depending on whether the user is Mobile IP. VPDN.2. --> cd radius/clients [ //localhost/Radius/Clients ] Entries 1 to 3 from 3 total entries Current filter: <all> ivvv_pdsn1/ ivvv_pdsn2/ localhost/ --> cd ivvv_pdsn1 [ //localhost/Radius/Clients/ivvv_pdsn1 ] Name = ivvv_pdsn1 Description = IPAddress = 5.1 Verify the PDSN Client has been added to the AR Refer to the following example to verify the PDSN client exists in the AR database. but it does reference a base profile.250.5. 5.0 Motorola – Cisco IOS Network Integration Page 24 of 30 . --> cd /Radius/UserLists/ISPABCLocalUsers/ivvv_tester [ //localhost/Radius/UserLists/ISPABCLocalUsers/ivvv_tester ] Name = ivvv_tester Description = Password = <encrypted> AllowNullPassword = FALSE Enabled = TRUE Group~ = BaseProfile~ = mwts_uc1_nopool AuthenticationScript~ = Version 1.5 SharedSecret = cisco Type = NAS Vendor = IncomingScript~ = OutgoingScript~ = UseDNIS = FALSE DeviceName = DevicePassword = The above example shows a default PDSN client (type NAS) has been added and a shared secret exists (cisco).6. Simple IP etc. This shared secret must match the secret defined in the “radius-server host” command on the PDSN.

it can be seen that the user profile is defined as user class 1 (SIP only).6. The user is set to use framed PPP for the connection with an MTU of 1500 bytes and allowed to use VJ TCP/IP header compression as well as MPPC PPP compression if the client allows. The attributes defined for this profile will determine how the PDSN treats the user. Version 1.AuthorizationScript~ = UserDefined1 = Attributes/ CheckItems/ --> cd attributes [ //localhost/Radius/UserLists/ISPABCLocalUsers/ivvv_tester/Attributes ] --> ls 5. which is used as a base profile for user ivvv_tester. --> cd /radius/profiles/mwts_uc1_nopool [ //localhost/Radius/Profiles/mwts_uc1_nopool ] Name = mwts_uc1_nopool Description = Attributes/ --> ls attributes [ Attributes ] cisco-avpair = lcp:cdma-user-class=1 cisco-avpair = "lcp:interface-config=compress mppc" Framed-Compression = "VJ TCP/IP header compression" Framed-MTU = 1500 Framed-Protocol = ppp Framed-Routing = None Service-Type = Framed From the attributes listed above. It is possible to have the AR configured to manage the IP pools and assign a dynamic address as well. the PDSN will assign an IP address to it from an local PPP pool.0 Motorola – Cisco IOS Network Integration Page 25 of 30 . Since there is no IP address defined.3 Verify the User Profile The following example shows the user profile and attributes for mwts_uc1_nopool.

1 HA Configuration Once the network is configured for Simple IP. Current configuration : 2561 bytes ! version 12. The HA must first be configured to provide MIP tunneling services to subscribers in the network.2 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname HA_A ! boot system flash disk0:c7200-h1ik9s-mz.250.122-8. the Simple IP Database provisioning must be complete and fully operational.0 Motorola – Cisco IOS Network Integration Page 26 of 30 .2.bin ! Configure the Home AAA aaa new-model ! ! aaa group server radius MOT server 5. the basic foundation is in place and ready for Mobile IP support.12 auth-port 1645 acct-port 1646 ! aaa authentication login CONSOLE none aaa authentication ppp default local group MOT aaa authorization config-commands aaa authorization ipmobile default group MOT aaa authorization network default group MOT aaa accounting update periodic 60 aaa accounting network default start-stop group MOT aaa session-id common enable password ivvv ! username haA ip subnet-zero no ip gratuitous-arps ip cef ! ! controller ISA 4/1 ! bridge irb ! ! ! ! Define the loopback interface for mobile hosts interface Loopback10 description MIP Virtual Network Loopback Version 1.6 Mobile IP Database Provisioning ?? Note: In order to establish Mobile IP functionality.BY. 6. The following configuration example assumes that HA redundancy will be supported.

255.0 0.255.2.30 ip classless ip route 0.250.0 5.2.19 5.2.252.252.0.0.0 no ip mroute-cache standby 1 ip 5.2.255.1 255.0 Motorola – Cisco IOS Network Integration Page 27 of 30 .2.252.2.13 no ip http server ip pim bidir-enable ! Enable the home agent function ip mobile home-agent ! Define the mobile host network and mobile host security associations Version 1.255.252.no ip address ! ! FA0/0 and FA1/0 will be used for AR/NMS ! BVI 1 will be the virtual bridge interface interface FastEthernet0/0 description Cisco AR/NMS to CAT-1 fa3/1 no ip address duplex full speed 100 bridge-group 1 ! interface FastEthernet0/1 description Cisco AR/NMS to CAT-2 fa3/1 no ip address duplex full speed 100 bridge-group 1 ! ! FA1/0 and FA2/0 will be used for MIP traffic ! BVI 2 will be the virtual bridge interface interface FastEthernet1/0 description MIP to CAT-1 fa3/20 no ip address duplex full bridge-group 2 ! interface FastEthernet2/0 description MIP to CAT-2 fa3/20 no ip address duplex full bridge-group 2 ! interface BVI1 description AR/NMS Bridge ip address 5.1 255.0.0.252.240 no ip mroute-cache ! interface BVI2 description MIP Bridge ip address 5.10 standby 1 priority 100 standby 1 name HA_Group_1 ! ! Enable Mobile IP router mobile ! ip local pool ha_mip 5.

255.2.2 PDSN Mobile-IP Configuration Now that a Home Agent has been configured.254.252. router mobile ! ip mobile foreign-agent care-of CDMA-Ix1 ip mobile secure home -agent 5.2. the PDSN providing MIP services needs to be configured as a Foreign Agent.com address pool local ha_mip virtual-network 5.250.ip mobile host nai @ispxyz.2.0 Motorola – Cisco IOS Network Integration Page 28 of 30 .0 255.10 spi 100 key ascii cisco algorithm md5 mode prefix-suffix cdma pdsn send-agent-adv ! interface virtual-template 1 cdma pdsn mobile-advertisement-burst 3 200 ip mobile foreign-service challenge 200 5 ip mobile foreign-service challenge forward-mfce timeout 10 window 5 ip mobile registration lifetime 36000 Version 1.225 spi 100 key ascii cisco algorithm md5 mode prefix-suffix ip mobile secure foreign-agent 5.252.254.255.2.2.226 spi 100 key ascii cisco algorithm md5 mode prefix-suffix ! ! ! ! ! Configure the home AAA radius function radius-server host 5.12 auth-port 1645 acct-port 1646 key cisco radius-server retransmit 3 radius-server deadtime 5 radius-server vsa send accounting 3gpp2 radius-server vsa send authentication 3gpp2 bridge 1 protocol ieee bridge 1 route ip bridge 2 protocol ieee bridge 2 route ip call rsvp-sync ! ! mgcp profile default ! dial-peer cor custom ! ! ! ! gatekeeper shutdown ! ! line con 0 line aux 0 line vty 0 4 ! ! end 6.0 aaa load-sa ! Define security associations for the valid foreign agents this HA will serve ip mobile secure foreign-agent 5.

During Mobile IP registrations. the HA will send an Access-Request message to the home AAA along with the MIP username for authentication.3 Home AAA Considerations Please refer to section 5. It sho uld be understood that for Mobile IP.6 and follow the examples to verify that the HA client exists in the Home AAA database and that a Mobile IP subscriber/profile exists in the database as well. it will send a MNHA Authentication Extension in the MIP Registration Request Message. This information must also be programmed into the phone by the vendor. The local AAA must be configured either to authenticate the user based on its MSID or to proxy the MSID based authentication over to a remote AAA server for authentication. the PDSN will send an Access-Request Message to the local AAA along with the MSID of the user for authentication. The MNHA authentication is based on an SPI and shared secret much like the PCF to PDSN. The home AAA must authenticate the user and pass the user profile information back to the HA for processing. and the username/password in the DUN on the data client is not used. or the home AAA must provide it based on the subscriber’s profile so that the HA can authenticate the user. it will send a General Authentication Extension containing a CHAP password in the MIP Registration Request Message. the following key actions need to occur. The HA must have either a security association defined for the mobile.ip mobile foreign-serveice reverse-tunnel ! 6. 2. When received. Mobile Node to AAA Authentication: If configured on the mobile. The MIP username and AAA password must be programmed into the mobile by the vendor using QPST or some other equivalent tool. When received. Version 1. 1.0 Motorola – Cisco IOS Network Integration Page 29 of 30 . Mobile Node to HA Authentication: If configured on the mobile. PPP CHAP authentication is not performed.

1 Upgrading PDSN / HA Devices There are several CLI command changes when moving from 1. The configuration updates should be done offline (text editor) so that the existing configuration stays in tact on 1.8 running AR1.0 devices.0 format without any manual intervention. Do not attempt to use the new configuration files on a 1.2 image.2 Upgrading the AR AR version 3.2 image lines with the Cisco PDSN/HA.0 requires Solaris 5. Cisco highly recommends Sun Professional Services as a support mechanism for upgrading the Sun platforms to 5. It is highly recommended that the system engineers update their configuration files according to this document prior to loading the 1.0 to 1.0 device.2 image. In many instances.8 and implementing AR Clustering.0 Motorola – Cisco IOS Network Integration Page 30 of 30 . 7. Version 1. This will allow the AR upgrade procedure to automatically update the AR database to the 3.7 Upgrade Considerations 7. existing AR devices are not running this operating system. It is highly recommended that the system engineers upgrade the AR devices to 5.7 prior to upgrading the AR software. This will avoid any configuration data loss due to CLI command changes. the new configuration should be applied. After loading the 1.8.

.

*68P09301A55−A* 68P09301A55–A .

Technical Information MOTOROLA–CISCO PDN IOS INTEGRATION WHITE PAPER CDMA ENGLISH NOV 2002 68P09301A55–A .

.

68P09301A55–A CDMA ENGLISH WHITE PAPER NOV 2002 MOTOROLA–CISCO PDN IOS INTEGRATION .

.

and binder cover. Inside Cover: 65 lb.Technical Information Products and Services STANDARD MANUAL PRINTING INSTRUCTIONS Filename: Part Number: 68P09301A55–A 301a55–a. SPECIAL INSTRUCTIONS .5x11 21 1st Level Tabs 11x17 Sheets = (Total Pages) / 2 2nd Level Tabs NON–STANDARD SPECIFICATIONS X Tape Bound Corner Stitch Other: Meet with manager to determine the deliverable. TAB and SHEET SIZE/QUANTITY 7X9 8. LEVEL TABS: Body: 70 lb.pdf APC: 625 Title: Motorola–Cisco PDN IOS Integration Volume of Print Vendor: e. LEVEL TABS: 2nd. dia. Index Binder Cover: Standard TED cover – 10 pt.DOC Date 11/18/02 ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ STANDARD SPECIFICATIONS – FOR REFERENCE–DO NOT MODIFY ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ PAPER: 1st.) Shrink Wrap Body Black ink for body. Carolina Single Sided 5 Cuts Clear Mylar Pantone 2706–C Black Ink Single Sided 7 Cuts Clear Mylar White Black Ink FINISHING: 3–Ring Binder Slant–D 3–Hole Punched (5/16–in. Cougar Tabs: 110 lb. inside cover.