Mobile IP Simulator for the Agilent E5515C

Software Concepts, Inc

This is the user manual for the MIP-5800 and MIP-5850 Mobile IP Simulator. The document is specific to the Agilent E5515C RF test set and explains the installation and operation of the Mobile IP Simulator in that environment. The user is expected to have a familiarity with the Agilent E5515C and Mobile IP technology in general.

Copyright and License

This product includes open source software developed by the Apache Software Foundation, the NetBSD Foundation, Inc., the OpenSSL Project, the University of California, Berkeley, and other contributors. Complete copyright information and acknowledgments are embedded in the product at http://IP address of MOB-IP-SIM/copyright .

Many product designations are claimed as trademarks or service marks. Where such designations appear in this manual, they are represented by capitals or initial capitals.

All copyrights are held by their respective owners unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark nor should the naming of particular products or brands be seen as endorsements.

Software Concepts, Inc. assumes no responsibility for errors or omissions in this publication, or for any damage resulting from any information contained herein.

Software Concepts, Inc. guarantees the Mobile IP Simulator to be free from defects in material and workmanship for one year from purchase. Tampering, misuse, or modification shall void this agreement, as does damage caused by external overloads such as lightning or power source surges, or any acts of nature. In the event of failure we will at our discretion repair or replace the failed material upon prepaid return to the factory.

List of Figures
1-1. MOB-IP-SIM Overview
1-2. MOB-IP-SIM Component Diagram
3-1. Mobile IP network simulator page
3-2. Configuration menu page
3-3. Network configuration page
3-4. MIP-5800 PPP configuration page
3-5. MIP-5850 PPP configuration page
3-6. MIP-5800 Mobile IP configuration page
3-7. MIP-5850 Mobile IP configuration page (advertiser)
3-8. MIP-5850 Mobile IP configuration page (home agent)
3-9. NAT Configuration menu page
3-10. HTTP Proxy Configuration menu page
4-1. Call Flow Overview
4-2. Agilent E5515C/E6702B PDSN Connection Setup
4-3. CDMA2000 Registration Flow
4-4. CDMA2000 Origination Flow
4-5. Agilent E5515C/E6702B Generator Information Screen
4-6. PPP Overview
4-7. Typical PPP Control Protocol
4-8. Typical PPP Authentication Protocol
4-9. CDMA2000 Registration Flow
4-10. Mobile IP With DMU
4-11. Normal TCP Connection
5-1. Logs page
5-2. tcpdump (show packet contents) page
5-3. tcpdump (don't show packet contents) page
5-4. Agent-Advertiser log page
5-5. Foreign agent log page
5-6. Access log page
5-7. Error log page
5-8. HTTP proxy log page
5-9. System log page
6-1. Mobile IP network simulator page
D-1. MOB-IP-SIM / E5515C Interconnection diagram
D-2. MOB-IP-SIM / E5515C Interconnection diagram for hybrid mode

User Manual

Preface

This manual is meant to provide the information required to fully utilize the Mobile IP Simulators from Software Concepts. It does not discuss the theory or standards upon which mobile IP depends, but succinctly presents the procedures required to accomplish your job. In short, resort to the manual when you need to perform a specific task.The tasks discussed include:

Unpacking the required equipment
Setting up the test system hardware
Configuring the simulator, RF test set, and Mobile IP device
Understanding the logs written by the MOB-IP-SIM
Modifying the MOB-IP-SIM content and operating system

Chapter 1. Introduction

This chapter will:

Describe what the MOB-IP-SIM can do
Describe how the MOB-IP-SIM does its job

By simulating the Foreign Agent and Home Agent required for a Mobile IP connection, the Mobile IP Simulator (MOB-IP-SIM) provides the tools needed for complete developmental testing of wireless devices using Mobile IP as the high-speed data interconnectivity protocol. The wireless device can access web content supplied by the MOB-IP-SIM for testing specific features or can access the Internet by means of the simulator. Two models are available: The MIP-5800 provides the minimum set of configuration parameters needed to support Mobile IP connectivity under standard network conditions, while the MIP-5850 provides additional configuration parameters to allow network error simulation and system configuration control. The MIP-5850 is designed for Mobile IP protocol development and supports test features required to verify compliance with the IS-835 standard. Refer to Figure 1-1 for an conceptual overview of the system.

Figure 1-1. MOB-IP-SIM Overview

The previous figure shows the complete Mobile IP network test system. The Agilent E5515C communications test set provides the required cdma2000 or 1xEV-DO radio network emulation and control, containing the radio link, call setup, and Inter-Working Function (IWF) needed for packet data communications. A second E5515C may be connected for hybrid cdma2000/1xEV-DO testing of a single mobile station. The MOB-IP-SIM supports only a single mobile station; therefore, this configuration is useful only for hybrid-mode testing. The MOB-IP-SIM provides the additional IP network elements needed to complete the Mobile IP network simulation environment, namely the simulated PDSN, Foreign Agent (FA), and Home Agent (HA).

The combination of the E5515C and the MOB-IP-SIM therefore provides a complete solution for Mobile IP connectivity and testing, allowing you to choose levels of features that range from basic connectivity to semi-automated conformance testing.

The simulator is contained in a small enclosure with serial port and LAN connectors. PPP data running over the LAN interfaces the Mobile IP simulator to a cdma2000 or 1xEV-DO communication test set and supports Mobile IP for a single device. The LAN connection provides a web-based user interface to configure the simulator as well as a text-based command port. Configuration requires setting the MOB-IP-SIM to match your specific LAN connection, setting the PPP links for Simple IP and Mobile IP provisioning and operation, and setting up the NAT router. The user interface also provides access to system and data logs and online documentation.

The relationship of the various components required to set up an end-to-end data call is indicated in Figure 1-2.

Figure 1-2. MOB-IP-SIM Component Diagram

The mobile station makes a data call or session to the Agilent E5515C, which forwards the data to the MOB-IP-SIM's internal PDSN. If the mobile supports hybrid mode, it can maintain a registration on a cdma2000 network and a data session on a 1xEV-DO network simultaneously; to test this behavior, two E5515C sets are required. The PDSN handles the PPP frames and forwards registration and user data messages between the home agent and the radio network. In hybrid mode, this includes keeping track of which radio network the mobile is using.

The home agent processes registration requests, consulting the AAA to decide how to handle them. It also forwards the user data to the IP network. The MIP-5850 supports simulation of three home agents; the MIP-5800 supports only one.

The AAA examines each incoming registration request and decides, based on the authenticator and timestamp, whether to accept or reject it. In addition, the AAA can perform dynamic mobile-IP key update (DMU), which uses public-key cryptography to set up the shared MN-HA, MN-AAA, and CHAP keys securely.

The MOB-IP-SIM includes a router with optional network address translation (NAT). NAT mapping allows the mobile station to share the MOB-IP-SIM's address when contacting external servers, so the MOB-IP-SIM and mobile need only one IP address on your LAN. The drawback to this mode is that servers on the LAN cannot initiate connections to the mobile, as the MOB-IP-SIM would receive the connection attempts. NAT redirection allows you to redirect the mobile's connection requests to the server of your choice. This can be useful when testing mobiles or applications with hard-coded IP addresses.

The MOB-IP-SIM includes an FTP server and an HTTP server, into which you can upload your own content for testing. See Appendix A for details. In addition, the HTTP server is used to configure everything. See Chapter 3.

The HTTP proxy allows mobiles with HTTP mini-browsers (also known as WAP 2) to communicate with HTTP origin servers. It translates GIF images to PNG as required. The proxy can modify the requested URL before sending the request. This allows testing mobiles or applications with hard-coded URLs. The URL rewriting mechanism is described in detail in the Section called HTTP Proxy Configuration in Chapter 3. The proxy can communicate directly with an origin server, or it can use another proxy if required by local network policy.

If you need functionality beyond basic HTTP and FTP service, you can connect the MOB-IP-SIM to external servers, either on your local network or elsewhere on the Internet.

The MOB-IP-SIM provides three types of access to network packets. PPP frames in transit between the mobile station and the PDSN are captured in a file for inspection with any network analyzer that supports tcpdump format. All Ethernet frames between the MOB-IP-SIM and the Ethernet are repeated out a second network port for capture and analysis (see Appendix D. In addition, the MIP-5850 has AT commands to capture and analyze PPP frames.

The MOB-IP-SIM must be configured to work within the bounds of your local area network. This configuration, covered in Chapter 3, sets up access to the external Internet and provides routing connections to other entities that you may plan to use as part of your wireless IP test environment. Setup is accessed through any standard Internet browser connected to the LAN where the simulator is installed. The MIP-Manager, a simulator setup utility, is included on the accompanying CD to assist with the initial installation.

The MIP-5800 simulator provides web-based user access to the basic parameters needed to provision the mobile device for Simple IP and Mobile IP operation.

The MIP-5850 simulator provides dynamic control of many additional test parameters that can be modified prior to a data connection attempt or during the data connection in some cases. The most common setup parameters can be set using the web-based interface, while more complex controls must be changed using "AT" commands sent from a terminal or conformance test script.

The following table indicates the features supported by the two models of the Mobile IP Simulator.

Table 1-1. Features Matrix

Feature	MIP-5800	MIP-5850
Built-in NAT Routing	Yes	Yes
Built-in HTTP Proxy Server	Yes	Yes
Built-in Web Server	Yes	Yes
Built-in FTP Server	Yes	Yes
Status & Activity Logging	Yes	Yes
PPP Logging: (Includes PPP, IP, UDP, Mobile IP layers)	Yes	Yes
Registration Request: Automatic MD5 or HMAC-MD5 with or without SPI authentication	Yes	Yes
Primary HA Simulation	Yes	Yes
Secondary HA Simulation	No	Yes
Agent Advertisement: Configurable delay, # of repeats and delay between repeats	No	Yes
Agent Advertisement: Configurable Lifetime, Pref. Reg. Lifetime, care-of address, & bit options	No	Yes
Registration Response: Configurable Lifetime & Code	No	Yes
"AT" command set to support hand-off control, remote test configuration, and log search	No	Yes
PPP: Configurable CHAP or PAP authentication for Simple IP	No	Yes
DMU	No	Option

Chapter 2. Installation

This chapter will tell you:

How to confirm you that have all the components of the MOB-IP-SIM
What additional components you are required to supply
How to connect the MOB-IP-SIM to your RF test set
How to install the MOB-IP-SIM Manager configuration utility

Carefully unpack your MOB-IP-SIM and inspect for any damage. You should have one each of the following:

Main MOB-IP-SIM unit (Either MIP-5800 or MIP-5850 )
DE-9 to DE-9 null-modem serial cable
Category 5 10BaseT cable for connecting the MOB-IP-SIM to the LAN
External 12VDC power supply
MOB-IP-SIM CD-ROM
This manual

You are expected to provide the following items:

Agilent E5515C RF Test Set(s) with the E6702B cdma2000 lab application software and/or the E6706A 1xEV-DO lab application software
A Windows PC with free serial and Ethernet ports

There is no need to open the MOB-IP-SIM enclosure since all configuration is done using software interfaces.

Since the MOB-IP-SIM is a feature extension product designed to be used with the Agilent E5515C, installation and operation will require reference to the Agilent documentation for those procedures outside the scope of this document.

After reviewing the connection diagram in Appendix D, install the MOB-IP-SIM Manager setup utility found on the accompanying CD-ROM by running setup.exe located in the MobIpSimManager folder.

Open the MOB-IP-SIM Manager from your PC by using the Windows Start menu. When the Options screen appears, click on the LAN Setup button and follow the instructions to configure the LAN parameters. The manager will instruct you to power-on the unit, connect cables, etc. at the appropriate time. When the setup is complete, the MOB-IP-SIM will have been assigned a specific IP address. Record the MOB-IP-SIM IP address in section [B] of Appendix E.

The IP address may be set without the MOB-IP-SIM Manager by following the procedure in Appendix F.

Note: Do not connect anything until so instructed by the MOB-IP-SIM Manager software.

Chapter 3. Configuration

This chapter will teach you:

How to configure the MOB-IP-SIM for use
How to set up your wireless device for testing
How to initiate a Mobile IP connection

Simulator Configuration

This section outlines the setup of the the MIP-5800 and MIP-5850 simulators. As the MIP-5800 has a reduced functionality when compared to the MIP-5850, some pages are available only to users of the MIP-5850, and will be so specified as appropriate. Access to all operational configuration is accomplished by these pages. Some information retrieval will be accomplished by accessing the Log Pages as described in Chapter 5

Configuration Menu

Once the initial IP address is set, record the provisioning information in sections [A] and [C] of Appendix E) for the Mobile IP enabled wireless device that you plan to test. A manufacturer's programming tool is typically required to access this information.

After pointing your web browser to http://mobipsimaddress, where mobipsimaddress is the address recorded in section [B] of the worksheet, you should see the page indicated in Figure 3-1. Access to the simulator documentation, debugging and operation logs, copyright information, and demonstration web content are also available on this page.

Figure 3-1. Mobile IP network simulator page

Click on the Configuration menu link to reach the main configuration menu page shown in Figure 3-2. From here the specific forms used for Network, PPP, Mobile IP, and NAT configuration may be reached. Additionally, the present configuration may be downloaded to the controlling PC, or a previously saved configuration file uploaded to the MOB-IP-SIM. Two commands are also accessed here, namely Restart and Reset AT configuration.

Clicking on the Restart button reboots the MOB-IP-SIM. This action, which is equivalent to a simulator power cycle, will restart the simulator following a operating system upgrade and reset the machine to the web-based configuration state. Clicking on the Reset AT configuration button will return all configuration parameters altered by manual or scripted AT commands to the web-based configuration state. Remember that the web-based configuration sets all parameters aside from realdate, PPP link, and script tcpdump commands and that the web-based configuration values will be reloaded following a MOB-IP-SIM power-cycle, Restart, or Reset AT configuration commands.

Figure 3-2. Configuration menu page

The next steps walk through each configuration form. You should carefully review each form during the initial setup so that you will know where the parameters are stored if you need to modify something later. The other network settings can be configured or reconfigured once the MOB-IP-SIM has a valid IP network address.

Network Configuration

Click on the Network link to display the first configuration page, which is the same in the MIP-5800 and the MIP-5850 .

Figure 3-3. Network configuration page

Configure each network parameter as indicated in the following text. Consult with your I.T. department if you are not familiar with IP address management or if you don't know how your local network is configured.

IP configuration

Select static or dynamic (DHCP assigned) IP addressing for the MOB-IP-SIM unit. This should already be configured correctly if the MOB-IP-SIM Manager has been used for the initial LAN setup. Static mode is recommended for most test environments.

DHCP Operation: If the MOB-IP-SIM has been set to DHCP mode, the IP address, netmask, broadcast address, gateway address, and DNS server parameters will automatically be assigned and displayed in this form.

Hostname

Default = mip. Enter an alphanumeric name for the MOB-IP-SIM. This name is used by some DHCP servers to allow network addressing by name rather than direct IP addressing. This setting is not critical.

IP address

If a static IP configuration is used, then this is the static IP address of the MOB-IP-SIM.

Netmask

If a static IP configuration is used, then this is the subnet mask for the local network. Hosts with IP addresses matching the MOB-IP-SIM's address in these bits are contacted directly; others are contacted through the gateway.

Gateway address

This is the address of a local network router used to reach the Internet. This value only applies to the static IP mode since DHCP mode automatically sets this address. The address must be on the local network and the net mask must be compatible with the simulator net mask and IP address. If you have an isolated network, leave this field blank.

Primary DNS server

This is the IP address of a Domain Name Server that provides name lookups for your network. This value only applies in the static IP mode since DHCP mode automatically obtains this address. Type ipconfig /all | more at the Windows command prompt to determine this address on your network.

Secondary DNS server

Primary DNS server

Tertiary DNS server

Primary DNS server

Click the Save button to save the current information and then click PPP to go to the next configuration page, which varies depending upon the model.

PPP Configuration

The PPP configuration form shown in the following figure configures the test Simple IP data connections. Mobile IP connections also depend on the PPP connection; however, the PPP server address and TCP packet logging are the only parameters that are involved in a Mobile IP connection.

Figure 3-4. MIP-5800 PPP configuration page

Propose IP address during IPCP

When enabled, the MOB-IP-SIM sends an IP-Address option in its initial IPCP Configuration-Request message. Turn this on for Simple IP, off for Mobile IP.

IP address of PPP server

Default is 192.168.14.1. This is an arbitrary address assigned to the simulated PDSN. The default value should work as long as it does not conflict with other existing network addresses. The address is used by Simple IP as the PDSN address.

The mobile may use this address to contact the built-in content servers, even on a Mobile IP call. This feature is useful if the mobile is attached to an Ethernet-connected PC, as the PC can contact this address only through the mobile station so a successful transfer means the airlink is working.

The MOB-IP-SIM uses this address internally to refer to the PPP interface, so it must not conflict with any other address the MOB-IP-SIM will need to use.

IP address to assign mobile

Default is 192.168.14.3. This address will be assigned to the mobile station for a Simple IP connection and is unlimited as long as it does not conflict with other existing network addresses. Applies only to Simple IP.

The MOB-IP-SIM uses this address internally to route packets to the mobile, so it must not conflict with any other address the MOB-IP-SIM will need to use.

Propose PPP authentication

Default is ON. Check this option to cause the simulator to propose PPP authentication during LCP.

Permit unauthenticated PPP

Default is ON. Check this option to allow the MOB-IP-SIM to continue a PPP connection even if the mobile rejects the proposed PPP authentication (but not if the mobile agrees to authenticate and then fails authentication).

Log all TCP packets

When enabled, the MOB-IP-SIM logs all TCP packets instead of only those that have TCP flags set. This can help with debugging but slows down data transfer.

Disable PPP compression

When checked, the MOB-IP-SIM disables all forms of PPP compression (Van Jacobson and CCP).

PPP user name

This is the Authentication name that will be used for dial-up networking on a PC. Generally used only with Simple IP.

PPP password

This is the Authentication password (or secret) that will be used for dial-up networking on a PC. Generally used only with Simple IP. If the secret begins with 0x (first character is a zero), it is interpreted as a hexadecimal string (0x616263 is exactly equivalent to abc). It follows that if your secret starts with 0x, you will need to type something that starts with 0x3078.

MIP-5850 PPP Configuration

The MIP-5850 provides two additional parameters on its PPP configuration form as indicated by the following figure:

Figure 3-5. MIP-5850 PPP configuration page

Primary DNS server to advertise to phone: This is the IP address of a DNS server for the mobile or the attached PC to use. It applies to both Simple IP and Mobile IP. Leave it blank to omit the DNS-Server option from IPCP. This option is available only in the MIP-5850.
Secondary DNS server to advertise to phone: Primary DNS server to advertise to phone
Require PAP authentication: Default is OFF. Check this option to require the Password Authentication Protocol, in which case a username and password will be used to authenticate. Applies only to Simple IP. This option is available only in the MIP-5850 .
Require CHAP authentication: Default is OFF. Check this option to require the Challenge Handshake Authentication Protocol. The username and password will be used to authenticate in this case. Applies only to Simple IP. This option is available only in the MIP-5850.

When completed, click Save to store the parameters. Then click the Mobile IP link to go to the next configuration page, which varies depending upon the model.

MIP-5800 Mobile IP Configuration

The Mobile IP form sets values related to processing Mobile IP messages. The simulator only answers messages originating from the mobile's home address and only routes packets destined for the home address to the PPP link.

Transfer the recorded Mobile IP provisioning information from section [A] of Appendix E to the appropriate parameters on the Mobile IP configuration page. Explanations of each field are provided here. The following parameters are available for both the MIP-5800 and MIP-5850 Mobile IP simulators.

Figure 3-6. MIP-5800 Mobile IP configuration page

Mobile Node home address: Obtain this field from the worksheet, unless the recorded Home Address from the mobile is 0.0.0.0, in which case the mobile station is expecting a dynamic IP address assignment and a valid non-zero Home address should be entered. If the recorded Home Address is non-zero, then the recorded value should be entered into the Mobile Node home address field of the form. The address entered into the configuration form will be assigned to the mobile station in either case.

The Home agent configuration table represents independent Home Agents that are normally configured to act as the mobile stations Primary Home Agent (#1 entry) and Secondary Home Agent (#2 entry). The recorded data from section [A] of the Configuration Worksheet should be used to set the parameters in this table. When the simulator receives a registration request (RRQ) message, it searches the table in ascending order looking for a matching Home Agent IP address. When a match is found, a registration response (RRP) message is generated based on the parameters contained in that table entry. Table entries affect the response in various ways as indicated in the following. The MIP-5800 supports only one Home Agent.

IP Address: Enter the IP address of the mobile's primary Home Agent. If the mobile is configured for dynamic home-agent addressing (0.0.0.0 or 255.255.255.255), enter any valid IP address here and the mobile will use it.
Netmask: Default = 255.255.0.0. This netmask supports dynamic home agent address resolution according to RFC-3344 which states " . . . the mobile node MAY use dynamic agent address resolution to learn the address of its home agent. In this case, the mobile node MUST set the Home Agent field to the subnet-directed broadcast address of the mobile node's home network. Each home agent receiving such a Registration Request with a broadcast destination address MUST reject the mobile node's registration and SHOULD return a rejection Registration Reply indicating its unicast IP address for use by the mobile node in a future registration attempt."
Request verification-Secret: This is the shared secret used for mobile to Home Agent authorization of the RRQ message. A mismatched secret will result in a response code = 131 (authentication failure) in the RRP. This field supports hexadecimal strings the same as the PPP password field.
Request verification-SPI: Range [0 to 65535]. This is the numeric index related to the shared secret used for mobile to Home Agent authentication of the RRQ message. A mismatched SPI will result in a response code = 131 (authentication failure) in the RRP.
Response-Secret: Normally set to match the Request verification-Secret, it can be mismatched to test mobile behavior due to invalid authenticator data in the RRP. A mismatch has no effect on the RRP response code, but the mobile should reject the reply. This field supports hexadecimal strings the same as the PPP password field.
Response-SPI: Range [0 to 65535]. Normally set to match the Request verification-SPI previously documented. Can be mismatched to test the mobile stations behavior due to invalid authenticator data in the RRP. A mismatch has no effect on the RRP response code, but the mobile should reject the reply.

MIP-5850 Mobile IP Configuration

The following parameters are available only on the Mobile IP Configuration page of the MIP-5850 simulator as shown in the following figure.

Figure 3-7. MIP-5850 Mobile IP configuration page (advertiser)

Number of spontaneous Agent Advertisements to send when the PPP link comes up: Default is 1. This is a protocol behavior test parameter designed to disable (value = 0) spontaneous advertisements or to send multiple advertisements to the mobile station when the PPP link is established.
Number of seconds between spontaneous Agent Advertisements: Default is 0.01. This is a protocol behavior test parameter designed to control the rate at which advertisements are sent. This parameter applies only if the number of Agent Advertisements is set to a value greater than 1.

Number of seconds to delay Agent Advertisements: Default is 0.01. This is a protocol behavior test parameter designed to delay the first advertisement after the PPP link comes up. This parameter applies only if the number of Agent Advertisements is set to a value greater than 0.
Care-of address: Default is blank or 0.0.0.0 (not set). The default value allows the Foreign Agent Care-of address in the Agent Advertisement to automatically contain the Ethernet IP address of the MOB-IP-SIM that normally acts as the FA. This default address comes from the Network Configuration page. Entering a specific non-zero address will override the normal address that is advertised in the FA care-of address field.
ICMP Router Advertisement lifetime: Default is 9000 seconds per IS-835B. This field defines the maximum period that the Advertisement is considered valid in the absence of further Advertisements. This value is included to test the mobile's action when the timeout expires.
ICMP Router Advertisement preference: Default is 0. This is a 32-bit number representing the preference level of the Router Address included in the Advertisement. A blank entry is treated as a 0.
Registration lifetime: Default is 600 sec. This is the longest lifetime that this agent claims to be willing to accept in a Registration Request. A value of 0xffff indicates infinity. The mobile station is required to re-register when this time expires. This field has no relation to the Lifetime field within the ICMP Router Advertisement portion of the Agent Advertisement.
Registration required: Default is OFF. ON indicates registration with this foreign agent (or another foreign agent on this link) is required even when using a co-located care-of address.
Busy: Default is OFF. ON indicates the foreign agent will not accept registrations from additional mobile nodes.
Home agent: Default is OFF. ON indicates this agent offers service as a home agent on the link on which this Agent Advertisement message is sent.
Foreign agent: Default is ON. ON indicates this agent offers service as a foreign agent on the link on which this Agent Advertisement message is sent.
Minimal encapsulation: Default is OFF. ON indicates this agent implements receiving tunneled datagrams that use minimal encapsulation.
GRE encapsulation: Default is OFF. ON indicates this agent implements receiving tunneled datagrams that use GRE encapsulation.
Reserved: Default is OFF. The previous revision of the Mobile IP specification (RFC 2002) defined this bit to indicate support for Van Jacobson TCP header compression. ON may be used to check that the mobile station ignores this bit.
Reverse tunneling supported: Default is OFF. ON indicates this Foreign Agent supports reverse tunneling.

Figure 3-8. MIP-5850 Mobile IP configuration page (home agent)

Accept dynamic HA request: If this option is enabled, the MOB-IP-SIM will respond to an otherwise valid Registration-Request to a directed broadcast address by sending a Registration-Accept message. If disabled, the MOB-IP-SIM will respond with a Registration-Reject with code 136 (unknown home agent address).
Request verification-AAA: This is the AAA secret used for mobile to Home Agent authorization of the RRQ message. A mismatched secret will result in a response code = 144 (authentication failure) in the RRP. This field supports hexadecimal strings the same as the PPP password field.
Response-Code: Range [0 to 255]. Default is 0. This is used to control the code field in the RRP message sent by the Home Agent to the mobile station. An entry of 0 allows the simulator to function normally with automatic handling of authentication and time sync operations. Code 131 will be returned if authentication fails and code 133 will be returned if a time sync error is detected. Otherwise, code 0 will be returned indicating a successful registration. Non-zero positive values will override normal processing to force a specific code in the RRP message regardless of other conditions. The special case value of -1 is used to disable this Home Agent and the Registration Response message.
Registration lifetime: Range [0 to 65535 sec]. Default is 65535. The default value allows the simulator to automatically reply with the same value requested in the RRQ message for normal operation. All other values limit the registration lifetime contained in the RRP message response and are used to test the mobile station's compliance with the network-assigned lifetime. Note (ref: RFC-3344 3.4): A value of zero indicates that the mobile node has been deregistered.
DMU PKOID: Range [0 to 255]. Default is 129. This number indicates to the mobile which public key it should use for DMU. The default value corresponds to the DMU keypair supplied with the MOB-IP-SIM. This option is available only on the MIP-5850 with DMU.

Click Save and then click the NAT link to go to the next configuration page.

NAT Configuration

On the NAT configuration form, you may set up network address translations as required to conform to your network's or the mobile station's requirements. A common example is shown where the mobile accesses the internet using an HTTP proxy server at address 68.28.31.1 port 80. This server is not locally accessible, so the NAT is configured to direct these requests to the simulator's local proxy server at 127.0.0.1 port 8080.

Use the Proxy Server information from section [C] of Appendix E to set the NAT configuration if needed.

Figure 3-9. NAT Configuration menu page

Mobile Traffic Handling

The MOB-IP-SIM can handle mobile traffic in two ways: translate all outgoing traffic so it appears to come from the MOB-IP-SIM (NAT mode) or make the mobile's address appear to be on the LAN (route mode). Select which you want here.

In NAT mode, the mobile's address appears only on the PPP link between the mobile and the MOB-IP-SIM, so nothing on the LAN or elsewhere needs to be able to reach this address. The address simply needs to be different from any address that the MOB-IP-SIM or mobile might need to reach for any other purpose. The safest choice for the mobile's address in this mode is some random address from the private address ranges of 10.x.x.x or 192.168.x.x.

In route mode, the MOB-IP-SIM forwards packets intact between the mobile and the LAN. Use this mode if you need to initiate connections from the LAN or internet to the mobile. In this mode, the mobile must have an address from the range used on the LAN. The MOB-IP-SIM will provide proxy ARP for the mobile's address on the LAN.

When the mobile requests

Enter an IP address and TCP or UDP port number that the mobile may attempt to connect to. Both TCP and UDP connections with the specified port number will be redirected. The port number may also be specified as a port range, such as 123-456. This means that port 123 is redirected to the "connect it to" port, 124 to the next port, and so on.

Connect it to

Enter an IP address and port number of the server that you would like the mobile to be connected to instead of the one it requested. The server will see the mobile's address as the source of the request messages, and the mobile will see the address it originally tried to contact as the source of the response messages.

When completed, click Save and then click the HTTP link to go to the next configuration page.

HTTP Proxy Configuration

The built-in HTTP proxy server can use an external proxy server, and it can modify the request URL before passing the request along to the content server. Use the HTTP proxy configuration to configure these features.

Figure 3-10. HTTP Proxy Configuration menu page

External HTTP proxy URL

Some network configurations do not allow the MOB-IP-SIM to connect directly to HTTP servers on the Internet but do provide an HTTP proxy server to allow indirect connections. If you have such a network, obtain the details and put the URL for your proxy server here. For example, if your proxy server is at web-proxy.example.com on port 8888, use http://web-proxy.example.com:8888/ as the URL.

If the MOB-IP-SIM can contact HTTP servers directly, leave this entry blank.

Convert GIF images to PNG

Some mobile devices cannot display GIF images but can display PNGs. Check this box to have the HTTP proxy convert image formats.

Change

When the mobile requests a URL that matches the regular expression in this column, the proxy server changes the part of the URL that matches the regular expression before requesting the page from the origin server.

To

The part of the request URL that matches the regular expression is changed to this entry. This entry is not a regular expression, but the $ and \ characters are special, as described below.

Some mobiles have hard-coded home-page URLs or expect the network to transform the request URL in some way. The HTTP proxy can handle either of these cases by transforming the URL. The left column contains a list of regular expressions that the proxy matches against the requested URL. If one of these regular expressions matches the URL, the proxy replaces the matched text with the corresponding text from the right column.

In a regular expression, letters and digits stand for themselves, but many punctuation marks have special meanings:

Table 3-1. Regular Expression Operators

Operator	Description	Example	Matches	Does not match
`.`	Any one character	`a.b`	`axb`	`axxb`
`()`	Grouping: everything in parentheses is treated as a unit	`a(bc)+d`	`abcbcd`	`abcbd`
`+`	At least one of the previous thing	`a.+c`	`abdefc`	`ac`
`*`	Zero or more of the previous thing	`a.*c`	`ac`	`ad`
`?`	Optionally one of the previous thing	`ab?c`	`ac`	`abbc`
`[]`	Any one character from the set	`[a-dx]+`	`acbdxaa`	`afd`
`[^]`	Any one character not in the set	`[^a-dx]+`	`efgtuv`	`efgatuv`
`\`	Use the next character as a normal character	`\.`	`.`	`x`

To be safe, put a \ before each punctuation mark unless you want to use its special meaning.

In the right column of the form, all characters stand for themselves except \ and $. You can use \1 through \9 to refer to the text matching first nine parenthesized groups from the original URL.

Table 3-2. URL Rewriting Examples

Change	To
`www\.example\.com`	`www\.example\.net`
`abc`	`ghi`
`^http\:\/\/search\.example\.com\/(.+)`	`http://www.google.com/search?q=\1`

Original	Result
`http://www.example.com/abc/def`	`http://www.example.net/ghi/def`
`http://search.example.com/testing`	`http://www.google.com/search?q=testing`

When completed, click Save and then click the Menu link to return to the Configuration Menu.

E5515C Configuration

Mobile IP typically uses cdma2000 Service Option 33 or the 1xEV-DO Default Packet Application for data calls. All the normal data call setup parameters on the E5515C apply to mobile IP and are not covered in this manual. The E5515C configuration and connection required to link it to the MOB-IP-SIM are explained here, but the Mobile IP wireless device setup and MOB-IP-SIM configuration are assumed to been completed as described in Chapter 3. The E5515C is also assumed to be set up and ready to handle standard data calls.

Connect the required communications test set, PCs, hubs, phone, and MOB-IP-SIM as diagrammed in Appendix D.
Make sure power is applied to all devices and that the required power-up operations are complete.
Use the E5515C soft menu to navigate to the Data Channel Parameters menu and set the external PDSN address to the MOB-IP-SIM local address previously recorded in section [B] of Appendix E and set the External PDSN State to ON.
The E5515C should indicate that the link to the MOB-IP-SIM is active. You must perform this step each time you reset or turn on the E5515C, either manually or by recalling a register with the External PDSN State set ON.
For hybrid mode (two E5515C sets), synchronize the system time between the sets. On the E5515C with its TRIG IN port connected, navigate to the Cell Info or Access Network Info menu, then to CDMA System Time/Sync Info. Verify that Ext 8960 IP Addr contains the IP address of the other E5515C, then press the Sync To External Server button.
Exit back to the E5515C call processing menu.

This completes the E5515C setup.

Mobile Device Configuration

If you plan to use a mobile phone's built-in browser, you will need to set the browser's home page to something that can be accessed when the browser is launched. The suggested home page setting is http://mobipsimaddress/mobipdemo.htm where mobipsimaddress is the MOB-IP-SIM address recorded in section [B] of Appendix E. You may also use URL rewriting to have the MOB-IP-SIM supply a home page. This will allow you to access the built-in web server. Any valid local or public web server is also acceptable as the home page, so long as it is designed for small mobile screen displays.

If you plan to use the mobile as a wireless modem from a PC, follow the phone manufacturer's instructions for configuring this connection.

Check to make sure you have completed the following steps before attempting a Mobile IP Call:

The MOB-IP-SIM was set up on the network and its IP address was recorded on the worksheet.
The mobile station provisioning parameters related to Mobile IP were recorded on the Configuration Worksheet.
The MOB-IP-SIM was configured using the data from the Configuration Worksheet.
The E5515C was successfully configured to use the External PDSN mode to establish a LAN connection to the MOB-IP-SIM .
The test phone was configured to use either its built-in browser with a valid home page or to act as a wireless modem for a PC-based web browser.

Testing the Configuration

You are now ready to set up a Mobile IP data call.

Set up the E5515C for SO33 (for cdma2000) or Default Packet Application (for 1xEV-DO) data operation. Always start with the standard SO33 mode rather than the SO33+F-SCH mode to simplify the RF channel setup requirements (F-SCH channel power level adjustments are needed if you plan to use the SO33+F-SCH mode).
Initiate a data call using the PC browser or the phone's built-in browser.
Once the call connects, web access should be possible.
End the call by closing the PC browser connection or exiting the phone's browser.

Things to consider when testing Mobile IP operation:

Mobile IP establishes an IP connection on the first call attempt. The traffic channel may be released by the phone's dormant mode inactivity timer, by closing the dial up connection, by exiting the built-in browser, or by manually releasing the call from the E5515C. In most cases, the IP connection remains active even though the call is released. Phones typically have an icon to show this state where the connection is dormant. You will need to become familiar with the characteristics of the mobile device you are using to verify this state.

Note: The phone may unexpectedly start and end Mobile IP call sessions due to dormant timer expirations and registration lifetime expirations. This behavior is often confusing to first time Mobile IP users.

Chapter 4. Call Flow

This chapter will teach you:

How a normal Mobile IP call works
Several common error conditions and their remedies

Overview

A normal Mobile IP call involves several layered protocols. In order from lowest to highest:

CDMA2000 (itself a collection of layered protocols, but beyond the scope of the MOB-IP-SIM) specifies a radio link.
PPP, the Point-to-Point Protocol, specifies some control protocols to establish an error-controlled link, provide authentication of the mobile station, and negotiate IP parameters. In addition, it specifies how to transmit multiple protocols over a link; the only one the MOB-IP-SIM presently supports is IP version 4.
IP, the Internet Protocol, specifies a best-effort packet-switched network. IP datagrams may be delivered out of order, duplicated, or lost.
Mobile IP specifies a protocol for a mobile to register its location and get its traffic forwarded to it from its home location.
Some transport-layer protocol, such as TCP or UDP, provides demultiplexing and possibly error control to an application-layer protocol. These are beyond the scope of the MOB-IP-SIM as well.

Figure 4-1. Call Flow Overview

E5515C External PDSN Connection

The MOB-IP-SIM communicates with the mobile station through the E5515C; therefore, the E5515C and the MOB-IP-SIM must pass packets. This is coordinated over a TCP control connection on port 53613.

Figure 4-2. Agilent E5515C/E6702B PDSN Connection Setup

If this connection fails, check the following:

E5515C and MOB-IP-SIM both connected to the same ethernet hub.
Netmasks set the same.
Each device has its own address, not used for anything else.
Addresses are on the same subnet (where the netmask has a 1 bit, the addresses should match in the corresponding bit).
Port number set to 53613.
Correct "External PDSN IP Address" set on E5515C.

CDMA2000 Registration

Figure 4-3. CDMA2000 Registration Flow

The mobile must acquire the signal from the E5515C, find it acceptable, and then register on the test system. When the mobile registers on the system, the E5515C will display some of the information from the registration message on the Call Setup Screen. If there is already information on the screen, clear it with the Clear MS & Capability Info button on page 2 of the left menu before powering up the mobile.

If the mobile fails to register, any of the following may be a cause:

E5515C SID/NID (under Cell Info) set to unacceptable values
E5515C not operating on a channel that the mobile scans
Poor physical cable connection between the E5515C and the mobile

CDMA2000 call setup

Figure 4-4. CDMA2000 Origination Flow

The mobile must originate a data call using Service Option 33 (high-speed packet data, IP), and the E5515C must terminate it appropriately. The usual failures at this stage are as follows:

Service Option set to a value other than 33 or 33+F-SCH, or radio configurations set to below 3. Set the Radio Config to (Fwd3,Rvs3) or higher and then set the appropriate FCH Service Option to SO33.
If the cdma2000 call works without forward supplemental channels (F-SCH) but not with, check the forward supplemental channel power setting. It defaults to an incorrect values. See Figure 4-5 for some settings that work for a normal call. Use the Code Channel Parameters button to adjust the power levels.

Figure 4-5. Agilent E5515C/E6702B Generator Information Screen

PPP

Figure 4-6. PPP Overview

PPP negotiation consists of three phases: LCP to set up link options (the most important of which is authentication), the optional authentication phase, and IPCP to configure Internet protocol.

Figure 4-7. Typical PPP Control Protocol

The PPP control protocols LCP and IPCP work the same way. Each end sends a configuration-request message that contains some proposed options for the connection. If all the options in the configuration-request message are acceptable to the other end, the other end sends a configuration-acknowledge message; otherwise, the other end sends either a configuration-nak message that contains an acceptable set of values or a configuration-reject for any options that are completely unacceptable. A configuration protocol is complete when both ends have sent a config-ack.

Figure 4-8. Typical PPP Authentication Protocol

The details of the authentication protocols PAP and CHAP differ, but in general the MOB-IP-SIM sends a challenge message to the mobile and examines the mobile's response. The MOB-IP-SIM then sends a message indicating whether the response was acceptable. The only difference is the contents of the challenge and response packets.

If no frames at all appear in the PPP log (see the Section called tcpdump (show packet contents) in Chapter 5), verify that the E5515C is set to use an external PDSN. If a long string of authentication challenge frames with no replies appears,the mobile probably failed to reject the proposed authentication protocol during LCP. As a workaround, you can disable PPP authentication (see Propose PPP authentication), but the mobile is behaving incorectly and needs correcting.

Mobile IP

Figure 4-9. CDMA2000 Registration Flow

After PPP is connected (and IPCP completed), the PDSN sends an ICMP Router Advertisement message with a Mobility Agent Advertisement extension. This may be solicited or unsolicited, depending on configuration. The mobile then sends a Registration Request message to the foreign agent address in the advertisement. This request includes the address of a home agent or one of the special values 0.0.0.0 or 255.255.255.255. The special values indicate that the mobile has no knowledge of its home agent address and is requesting that the PDSN determine this address (which is in general possible only if the PDSN operator and the HA operator have a prior arrangement). The MOB-IP-SIM simulates the result of sending the mobile's request to a home agent and returns the appropriate response.

In the normal case, the mobile sends a request and receives an acceptance message (code 0). If the mobile's clock is out of sync with the HA's clock, the HA returns code 133 (registration identification mismatch) and the mobile registers using the correct time.

If the mobile attempts to contact a home agent that the MOB-IP-SIM is not set to simulate, or if the HA is set to return no answer, or if the FA is disabled, the mobile will receive no reply. Check the aforementioned things.

If the mobile uses a key other than the one in the MOB-IP-SIM to register, it will receive code 131 (mobile node failed authentication). Ensure that the MN-HA shared secret in the mobile matches the one in the MOB-IP-SIM.

Some mobiles are unable to handle code 136 (unknown home agent address), which is sent as part of HA address discovery. The `Accept dynamic HA request' option causes the simulated HA to send a Registration Accept in this case.

Some mobiles will refuse to accept a registration reply if they believe they are already registered on a network. There will typically be an option under a menu somewhere called `Sign Out' to clear this registration status.

DMU

Figure 4-10. Mobile IP With DMU

Dynamic mobile-IP key update (DMU) allows mobile stations to generate new keys and share them securely with the network. DMU testing is available as a software option on the MIP-5850.

The start of a DMU call looks like the start of a normal mobile IP call. However, instead of returning a registration-accept message, the network returns a DMU key-request message, which is a registration-reply with code 89 and a DMU extension of type 1. The mobile generates a set of keys and produces a DMU key-data message, which is a registration-request with a DMU extension of type 2. The network then decrypts this message and returns either an AAA-authenticator message (type 3) to prove that it could decrypt the key data or a public-key-invalid message (type 4) if the decryption failed. If DMU succeeds, then the mobile registers normally afterward.

Application

After Mobile IP registration succeeds, the mobile will attempt to contact some sort of application server or proxy. The details of your particular application protocol are beyond the scope of this manual. Many applications are based on TCP, so that is used as an example here.

Figure 4-11. Normal TCP Connection

A typical TCP connection starts with a SYN (synchronize) segment from the mobile. The server then replies with a segment with both SYN and ACK (acknowledge) flags set, then each subsequent segment has the ACK flag set. The connection continues until each end sends a FIN (finish) segment and receives an ACK for it. In the example shown, the server starts the connection close; this is typical of protocols such as HTTP.

Either end can signal a connection error by sending a RST (reset) segment. This will typically cause the other end to start some sort of error handling. The error handling depends on when the RST is received.

Irregularities in the connection opening (no reply at all from the server or a RST segment) generaly indicate that the server process is not running on the remote system (perhaps it's the wrong system) or there is a firewall in the way. In addition, some network configuration problems such as incorrect gateway address or netmask can prevent any reply from appearing.

Chapter 5. Logging

This chapter will teach you

How to access message logs.
How to access error logs.
How to access operational logs.

Logs Pages

The Logs menu shown in the following figure provides access to a number of logs detailing the operational history of the MOB-IP-SIM . This page may be accessed from the Mobile IP Test Menu found at the root of the MOB-IP-SIM web server. Click on the Log files link to reach the following menu and then click on the appropriate link to reach the log of interest.

Figure 5-1. Logs page

tcpdump (show packet contents)

The PPP packet log may be accessed in either text or binary form. Check here to determine whether PPP negation succeeded and an IP connection was opened. Click on the text link to call up the embedded tcpdump utility, which will display the network traffic in text format as shown in the following figure. The user may filter the content of the tcpdump window by entering a suitable expression in the Filter expressionfield and clicking on the Filter button.

Figure 5-2. tcpdump (show packet contents) page

tcpdump (don't show packet contents)

To download the log in binary form, click on the binary link. The binary format may be read directly by the free Ethereal network software, which is included on the CD-ROM.

Figure 5-3. tcpdump (don't show packet contents) page

Agent-Advertiser Log

Click on the Agent-Advertiser log link on the Log menu to call up a log of all messages from the process that sends mobility agent advertisements as shown in the following figure.

Figure 5-4. Agent-Advertiser log page

Foreign Agent Log

Click on the Foreign agent log link on the Log menu to call up the log of messages from the foreign agent as shown in the following figure.

Figure 5-5. Foreign agent log page

Access Log

Click on the Access log link on the Log menu to call up the log of all accesses to the MOB-IP-SIM HTTP content server as shown in the following figure.

Figure 5-6. Access log page

Error Log

Click on the Error log link on the Log menu to call up the log of all errors reported by the MOB-IP-SIM content server as shown in the following figure.

Figure 5-7. Error log page

HTTP Proxy Log

Click on the proxy log link on the Log menu to call up the log of the HTTP proxy server activity as shown in the following figure.

Figure 5-8. HTTP proxy log page

System Log

Click on the System log link on the Log menu to call up the log of all system messages as shown in the following figure.

Figure 5-9. System log page

Chapter 6. Online Information

This chapter will teach you:

How to access demonstration content
How to access simulator configuration menus
How to access a PDF of this manual
How to access the simulator log files
How to access copyright information and acknowledgments

Embedded documentation may be accessed via the Mobile IP network simulator page indicated below.

Figure 6-1. Mobile IP network simulator page

The Demo link leads to files suitable for viewing on a mobile device.
The Configuration link leads to the menu discussed in Chapter 3.
The Documentation link leads to a PDF of the current operations manual.
The Logfiles link leads to the log files discussed in Chapter 5.
The Copyright link leads to the legal fine print.

Appendix A. Uploading Procedures

This appendix will teach you

How to access embedded content for testing
How to upload new content
How to update the operating system

The MOB-IP-SIM includes FTP and HTTP content servers to which custom content may be uploaded. The operating system of the MOB-IP-SIM may also, if required, be updated by FTP.

The user has complete read/write access to the embedded FTP server. The user account is accessible with a user name of test and password of ftp. To view the files using a web browser, ftp to the simulator using the format ftp://test:ftp@ipaddress/. The server ships with the following five binary test files:

200k 204800 bytes of random data
200k10 200000 bytes of random data
50k 51200 bytes of random data
50k10 50000 bytes of random data
MD5.txt MD5 checksums of the above four files

You can install more files with any standard FTP client. To update the operating system, FTP the binary file into the root directory of the MOB-IP-SIM, naming it upgrade.bin. After the transfer is complete, click on the Restart button at the bottom of the Configuration menu. The ERROR LED will blink once, then remain on during the the reset process, which will take five to ten minutes following the firmware upload. Normal operation will be possible when the ERROR light has gone off.

The embedded HTTP server reads the following files or directories from the web directory that is also accessible by FTP:

index.html: The front page for the MOB-IP-SIM
mobipdemo.htm : The menu page for the demo files
mobipdemo_files : Directory for the demo files
config: Directory for the built-in configuration forms
copyright: Directory for the terms of use, copyright information, and acknowledgments
logs: MOB-IP-SIM generated logs
docs: Directory for the embedded documentation

Of the above HTML files, only the index.html file is modifiable by the user, though custom HTML pages may be installed to provide content for mobile access testing. To view the files using a web browser, ftp to the simulator using the format ftp://test:ftp@ipaddress/web/.

Appendix B. AT Commands

This appendix will teach you how to use AT commands to

configure the simulator for your test requirements
interrogate the simulator regarding its state
command the simulator to perform an action
query the simulator regarding AT command syntax

AT commands may be used to set the configuration of the MOB-IP-SIM, to query the simulator about its state, to command it to perform an action, or to test for the existence and syntax of a command. While the MIP-5850 is expected to be used by a mobile device software engineer who requires significant control of the PPP and Mobile-IP connection, the MIP-5800 user is expected to be the user applications programmer, who requires only those commands required to establish a normal Mobile IP connection for applications testing. The MIP-5800 command set is therefore smaller than that of the MIP-5850. With either model, the AT commands may be used over either the Ethernet or serial ports.

To configure the MOB-IP-SIM the appropriate command must be followed by one or more arguments. Some action commands may also require arguments. To query the simulator a command is followed by a question mark. To test a command requires following the command with =?. Some commands allow setting a value, or take an action that requires arguments. Use the command name followed by = and a value. Some of these commands return a value.

Action commands are used by themselves or sometimes with arguments:

Test commands are those followed by =?, which all commands support. The response is an indication of the syntax of the commands arguments. If no arguments are used, an empty template is returned.

Templates consist of the following pieces:

Decimal numbers and ranges in parentheses
(0-9) One of the integers 0 through 9 inclusive.
(0, 1-9) One of the integers 0 through 9 inclusive, but number 0 is special.
(0.0-9.9) Real numbers 0.0 through 9.9.
Character strings specified in hexadecimal
A string of printing ASCII characters and blanks
A string of lower case as and blanks
Hexadecimal numbers and ranges
Punctuation

Some commands allow querying the current value of some parameter by adding a ? to the name of the command. The response returns the current value.

In the description following, each command description lists the methods supported (except for the =? test).

After the controller issues a command, the MOB-IP-SIM returns one or more lines of response. Each line is terminated with carriage return and line feed.

Every command returns a basic result code, currently either OK or ERROR, as its last line of response. Some commands return extended response lines, which start with a plus sign followed by the command name, a colon, a blank, and some additional information. This additional information is the return value.

Many of the AT commands affect and read configuration data visible from the web pages, one command per datum. While changes to some of these data, such as the fields in Mobile IP messages take effect immediately, changes to others such as the IP address and PPP settings, do not.

The commands are discussed using the following format:

+command [argument]

Query, Immediate, Disruptive, and/or Action

The command description

The template entry indicates what at+foo=? returns, if anything.

A command is labeled Query if it supports the =? command.

A command is labeled Immediate if it has an immediate effect but does not disrupt operation any more than one would expect from changing that parameter.

A command is labeled Disruptive if it forces changes to take effect other than what one may expect from the name or one-line summary of the command.

A command is labeled Action if it has a no-argument form.

The commands listed under "General Commands" are available on both the MIP-5800 and MIP-5850 simulators. The remaining commands are available only on the MIP-5850.

The serial port operates at 9600 bps, with 8-bit characters, no parity, one stop bit. It has the usual IBM AT-style pinout, so you need a null-modem cable to connect it to a PC. Commands are terminated by a CR character (decimal 13); each response line is terminated by CRLF (decimal 13, 10).

The MOB-IP-SIM also listens on TCP port 53614. On this port, both command lines and response lines end in CRLF, in accordance with the usual Internet conventions. A normal TELNET client starts in a mode compatible with the MOB-IP-SIM command processor.

Command Descriptions

General Commands

+datetime [ (2000-2038),(1-12),(1-31),(0-23),(0-59),(0-59)]

Immediate Query:

Read or set the date and time for use in logs. Arguments are year, month, day, hour, minute, and second in numeric form separated by commas but without spaces.

+mipreset

Immediate Disruptive Action

Reset all the settings caused by other AT commands and make the reset take effect immediately. This command may disrupt PPP and network connectivity.

+version

Query

Return the version number tag (release-1_0 or similar)

+ipaddr [(0-255).(0-255).(0-255).(0-255)]

Query

Set the static IP address to use on the next +ipdhcp=0 command.

+ipdhcp [(0,1)]

Immediate Disruptive Query

This command configures the Ethernet interface to use DHCP or static configuration of its IP address, router address, and net mask. As with all AT commands, the effect of this setting is temporary. For permanent changes, use a web browser once communication has been established.

Setting the value to 1 causes the MOB-IP-SIM to broadcast a DHCP request and obtain a dynamic IP configuration.

Setting the value to 0 causes the MOB-IP-SIM to use the static configuration.

+ipdhcpaddr []

Query

Return the DHCP-assigned IP address.

+ipgw [(0-255).(0-255).(0-255).(0-255)]

Query

Set the default gateway to use on the next +ipdhcp=0 command.

+ipnetmask [(0-255).(0-255).(0-255).(0-255)]

Query

Set the net mask to use on the next +ipdhcp=0 command.

+ipping [(0-255).(0-255).(0-255).(0-255)]

Attempt to send an ICMP ping to the specified host. Returns OK if the ping is answered, ERROR if not.

PPP Commands (available only on the MIP-5850 simulator)

+pppauth [(0,1)]

Query

Set to 1 to propose PPP authentication for the next PPP session (either CHAP or PAP is acceptable). If +pppauth is disabled, the peer is allowed to pass IP without authenticating. The peer may reject the proposal if +pppnonauth is also enabled. See also +pppchap, +ppppap, +pppauto, +pppkill, +pppterm, +pppactive, +ppppassive .

+pppchap [(0,1)]

Query

Set to 1 to insist on the PPP Challenge Handshake Authentication Protocol (CHAP) for the next PPP session. See also +pppchap, +ppppap, +pppkill, +pppterm .

+pppprofilenum [(0-9)]

Query

Sets the simple IP profile affected by +pppuser and +ppppass commands.

+pppuser [(20-7e)]

Query

Set the username for a simple IP login. commands.

+pppuser [(20-7e)]

Query

Set the password for a simple IP login. commands.

+pppnocompress [(0,1)]

Query

Set to 1 to disable all forms of PPP compression (VJ and CCP) for the next PPP session. See also +pppkill, +pppterm .

+pppipmobile [(0-255).(0-255).(0-255).(0-255)]

Query

Set the address to use for the mobile-station end of the PPP link. The simulator uses this address internally even if +pppippropose is off, so it must be set to an address that does not conflict with the network to which the simulator is attached. See also +pppipmobile, +ppprestart, +pppterm

+pppipsim [(0-255).(0-255).(0-255).(0-255)]

Query

Set the address to use for the simulator end of the PPP link. This address is used internally by the simulator even if +pppippropose is off, so it must be set to an address that does not conflict with the network to which the simulator is attached. See also +pppipmobile , +ppprestart , +pppterm

+ppprestart []

Immediate Action

Kill the PPP link (without sending LCP Terminate-Request) and start a new one.

Agent Advertisement Commands (available only on the MIP-5850 simulator)

+advb [(0,1)]

Immediate Query

Set to 1 for the Busy bit in the Mobility Agent Advertisement. Must be set to 0 for normal operation.

+advdelay [(0.00-3600.00)]

Immediate Query

Simulated network delay in seconds for Mobility Agent Advertisement messages. TheMOB-IP-SIM sends the advertisement this many seconds after receipt of a Router Solicitation or the establishment of a PPP link with the mobile station.

+advf [(0,1)]

Immediate Query

Foreign Agent bit in the Mobility Agent Advertisement. Must be set to 1 for normal operation.

+advg [(0,1)]

Immediate Query

GRE encapsulation supported bit in the Mobility Agent Advertisement.

+advh [(0,1)]

Immediate Query

Home Agent bit in the Mobility Agent Advertisement. Must be set to 0 for normal operation.

+advlife [(0-65535)]

Immediate Query

Set the number of seconds the Router Advertisement is valid. See also +advreglife .

+advm [(0,1)]

Immediate Query

Minimal encapsulation supported bit in the Mobility Agent Advertisement.

+advpref [(-32768-32767)]

Immediate Query

Set the preference level to advertise for this router (larger means more preferable).

+advr [(0,1)]

Immediate Query

Registration required bit in the Mobility Agent Advertisement. Set to 1 to require registration.

+advreglife [(0-65534, 65535)]

Immediate

Set the number of seconds to include in the Mobility Agent Advertisement as the maximum registration lifetime.

+advseq [(0-65535)]

Immediate Query

Set the sequence number to use the next Router Advertisement message.

+advt [(0,1)]

Immediate Query

Reverse tunneling supported bit in the Mobility Agent Advertisement.

+advv [(0,1)]

Immediate Query

Reserved (formerly Van Jacobson) bit in the Mobility Agent Advertisement.

+mipcoaddr [(0-255).(0-255).(0-255).(0-255)]

Immediate Query

Set a care-of address to include in the Mobility Agent Advertisement message. The special case 0.0.0.0 means the IP address of the of the MOB-IP-SIM .

+spadvcount [(0-100)]

Immediate Query

Set the number of spontaneous Mobility Agent Advertisements to send when the PPP link is established. The MOB-IP-SIM may send fewer than this many Advertisements if the mobile station sends a Registration Request.

+spadvinterval [(0.00-100)]

Immediate Query

Set the interval in seconds between Mobility Agent Advertisements.

Home Agent Commands (available only on the MIP-5850 simulator)

+miphaaddr [(0-255).(0-255).(0-255).(0-255)]

Immediate Query

Mobile Node home address to expect. Registration Replies will be sent only to mobile nodes requesting either this home address or the zero home address. See also +miphanum

+miphaaddr [(0-255).(0-255).(0-255).(0-255)]

Immediate Query

Mobile Node home address to expect. Registration Replies will be sent only to mobile nodes requesting either this home address or the zero home address. See also +miphanum

+miphamask [(0-255).(0-255).(0-255).(0-255)]

Immediate Query

Network mask of the Home Agent currently under configuration used to simulate directed-broadcast behavior. See +miphanum.

+miphanum [(0, 1-3)]

Immediate Query

Select which Home Agent to configure with the +miphanai, +miphaaddr , +miphamask , +mipreplycode , +miphaspi , +miphasecret , +mipaaasecret, +mipmnspi , +mipmnsecret , and +mipreglife commands.

+miphasecret (20-7e)

Immediate Query

Set the secret (in ASCII) to use when verifying the Mobile-Home Authentication Extension in incoming Registration Requests.

+miphaspi [(0-4294967295)]

Immediate Query

Set the SPI to expect in the Mobile-Home Authentication Extension in incoming Registration Requests.

+mipaaasecret (20-7e)

Immediate Query

Set the secret (in ASCII) to use when verifying the AAA Authentication Extension in incoming Registration Requests.

+mipmnaddr [(0-255).(0-255).(0-255).(0-255)]

Immediate Query

Set the Mobile Node home address to expect. Registration Replies will be sent only to mobile nodes requesting either this home address or the zero home address.

+mipmnsecret [(20-7e)]

Immediate Query

Set the secret (in ASCII) to use when generating the Mobile-Home Authentication Extension in outgoing Registration Replies. Must match +miphasecret .

+mipmnspi [(0-4294967295)]

Immediate Query

Set the SPI to include in the Mobile-Home Authentication Extension in outgoing Registration Replies. Must match +miphaspi for normal operation.

+mipreglife [(0-65534, 65535)]

Immediate Query

The upper bound on the number of seconds to include in the Registration Reply as the registration lifetime. It should be greater than zero; 65535 means unlimited lifetime.

+mipreplycode [(-1, 0, 1-255)]

Immediate Query

Set the registration result code to use when sending the next Registration Reply. -1 means no reply (simulate failure); 0 means success; codes from 64 to 192 indicate failures. See RFC 3344 for more details.

+miprrpdelay [(0.00-3600.00)]

Immediate Query

Set the delay in seconds between getting a Registration Request and sending a Reply.

+mipnai [(20-7e)]

Immediate Query

When set, the NAI in a MIP registration request is checked using this value. A mismatch (or missing NAI) will result in an error response. if the value is left blank, the NAI value in a registration request is not checked.

DMU Commands(available only on the MIP-5850 simulator with DMU option)

+mipdmu [(0,1)]

Immediate Query

If the flag is set, the MOB-IP-SIM will respond to a registration-request message with a DMU key-request message. Upon receiving the DMU key-data message, the MOB-IP-SIM will clear +mipdmu and respond with either the AAA-authenticator or public-key-invalid message, depending on whether a private key is available to decrypt the key-data message.

+mipdmupkoid [(0-255)]

Immediate Query

The PKOID value to use in the DMU key-request message. For normal operation, the mobile must have a public key with this PKOID, and the MOB-IP-SIM must have the matching private key.

Packet Capture Commands (available only on the MIP-5850 simulator)

+capcount

Query

Return the number of packets captured so far. They are numbered 0 to N-1.

+capdump [(2e, 30-39, 5b-5d, 5f, 61-7a)]

List all fields in the specified packet or part thereof in alphabetical order. The argument is a field or PDU identifier. This command is not intended for use from scripts, as the format and sequence of data presented are subject to change.

+capfind [(0-9999), (2e, 30-39, 5b-5d, 5f, 61-7a)]

Locate the first packet with a number greater than or equal to START that contains a field named FIELD and return either the number of the found packet, or ERROR.

+capget [(2e, 30-39, 5b-5d, 5f, 61-7a)]

Return a field (not a PDU), generally in decimal. IP addresses are returned as dotted quads, sections and a few other binary fields are returned as hex strings. The data is a raw version of the higher-layer-protocol data (everything but the preceding fixed-length fields; e.g. ip.icmp.data starts at the octet following ip.icmp.sum).

+captime [(30-39)]

Return the timestamp associated with the specified packet, as seconds since the last +capstart command.

+capident [(2e, 30-39, 5b-5d, 5f, 61-7a)]

Identify the specified packet or part thereof. The argument is a field or PDU identifier. Returns the most specific protocol name for the packet or specified part. The command does not look in extensions by itself; you have to point it there.

+capstart [(20-7e)]

Clear the saved packet buffer and start capturing packets. The argument is a tcpdump filter expression and may be left blank to capture all packets.

+capident [(2e, 30-39, 5b-5d, 5f, 61-7a)]

Immediate

+capstop

Immediate Action

Stop capturing packets. Any packets already captured are preserved.

Appendix C. CD Contents

The Compact Disc that accompanies the MOB-IP-SIM contains a variety of files that may be helpful in the use of your simulator. These files include:

MOB-IP-SIM Manager for Windows
This manual in PDF and XHTML formats
MOB-IP-SIM Tutorial
Ethereal network analyzer software

Appendix D. E5515C Interconnection

Figure D-1. MOB-IP-SIM / E5515C Interconnection diagram

The previous figure shows the typical interconnection required for the MOB-IP-SIM to be used with the E5515C. The MOB-IP-SIM, the E5515C, and a PC are all connected to an Ethernet for normal operation. The Ethernet may be connected to a larger LAN or the public Internet if desired.

During setup, the PC is connected to the serial port in order to configure the MOB-IP-SIM's network parameters; this link may be disconnected for normal operation.

Figure D-2. MOB-IP-SIM / E5515C Interconnection diagram for hybrid mode

The previous figure shows the typical interconnection for hybrid mode. Both E5515C sets are connected to the Ethernet, and one supplies a 10 MHz reference signal and a trigger signal to the other. The remaining connections are the same as for a non-hybrid system.

Appendix E. Simulator Configuration Worksheet

The Mobile IP device to be tested must be provisioned to match the MOB-IP-SIM configuration or vice versa. The following worksheet is included to record those test system parameters required for successful operation.

Table E-1. MOB-IP-SIM Configuration

Mobile Parameter Name	Common Name	Recorded Mobile Station Value	MOB-IP-SIM Parameter Name	Table Section
NAI	Mobile Identifier	____@_____	Not Applicable	[A]
HomAdrs	Home Address	___.___.___.___	Mobile node home address	[A]
PrimHA	Primary Home Agent	___.___.___.___	Home agent IP address # 1	[A]
SecHA	Secondary Home Agent	___.___.___.___	Home agent IP address # 2	[A]
MNHA-SS	Home Agent Secret	____________________	Home agent Request & Response Verification Secret	[A]
MNHA-SPI	Home Agent SPI	____________________	Home agent Request & Response Verification SPI	[A]
MNAAA-SS	AAA secret	____________________	Not Applicable	[A]
MNAAA-SPI	AAA-SPI	____________________	Not Applicable	[A]
Rev Tun	Reverse Link Tunneling	0 or 1	Not Applicable	[A]
MOB-IP-SIM Network Address	Network address of the MOB-IP-SIM	___.___.___.___	Network configuration: Static or DHCP assigned address	[B]
ProxSvr	Proxy Server or Gateway address	___.___.___.___:____	NAT configuration: Redirection: ProxSvr :80 to 127.0.0.1:8080	[C]
Home Page	Home Page URL	____________________	Not Applicable	[D]

Appendix F. Manual MOB-IP-SIM Configuration

The MOB-IP-SIM Manager Windows utility should be used to set up the MOB-IP-SIM on your network in most cases. However, if the software utility is not available, the simulator may be manually configured by using a terminal emulator software application such as HyperTerminal to send AT commands directly to the serial port located on the MOB-IP-SIM back panel. The COM port should be set to 9600 Baud, 8 bits, no parity, and 1 stop bit.

To determine the current DHCP configuration enter at+ipdhcp?
A response of
```
+IPDHCP: 1 OK
```
indicates that DHCP is in use. A zero indicates a static configuration.
Enter at+ipdhcpaddr? In this example, a response of
```
+IPDHCPADDR: 192.168.1.210 OK
```
indicates that the assigned address is 192.168.1.210.
If the configuration is indicated to be static then enter at+ipgw? A response of
```
+IPGW: 192.168.1.1 OK
```
indicates the gateway in this case is 192.168.1.1. To retrieve the netmask enter at+ipnetmask? A response of
```
+IPNETMASK: 255.255.255.0 OK
```
indicates that the netmask is set to 255.255.255.0 in this case.
To reconfigure a static IP address, set only the values that need changing, then enter +ipdhcp=0 even if it was set to 0 already; this makes the new settings take effect.
For DHCP IP address assignment, set +ipdhcp=1 and (optionally, but most likely useful) confirm the new address by entering at+ipdhcpaddr?
```
+IPDHCPADDR: 192.168.1.210 OK
```

Colophon

This manual was produced in the DocBookx version 4.2 format as a single-source document and converted to PDF and HTML formats using OpenJade and pdfjadetex. PDF documents were sent directly to the printer.