User Manual
Copyright © 2004 Software Concepts, Inc.
Copyright and License
All Rights Reserved
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.
2004-07-20
| Revision History | ||
|---|---|---|
| Revision 2.01 | 2004-07-20 | mrb |
| restructured and converted to Docbookx v4.2 | ||
| Revision 1.0 | 2003-10-30 | mrb |
| first release | ||
| Revision 0.9 | 2003-9-30 | mrb |
| release | ||
Abstract
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.
Table of Contents
List of Figures
- 1.1. MOB-IP-SIM Conceptual 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
- 3.8. NAT Configuration menu page
- 4.1. Logs page
- 4.2. tcpdump (show packet contents) page
- 4.3. tcpdump (don't show packet contents) page
- 4.4. Agent-Advertiser log page
- 4.5. Foreign agent log page
- 4.6. Access log page
- 4.7. Error log page
- 4.8. HTTP proxy log page
- 4.9. System log page
- 5.1. Mobile IP network simulator page
- D.1. MOB-IP-SIM / E5515C Interconnection diagram
List of Tables
- 1.1. Features Matrix
- E.1. MOB-IP-SIM Configuration
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
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, “MOB-IP-SIM Conceptual Overview” for an conceptual overview of the system.
The previous figure shows the complete Mobile IP network test system. The Agilent E5515C communications test set provides the required cdma2000 radio network emulation and control, containing the radio link, call setup, and Inter-Working Function (IWF) needed for packet data communications. 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) necessary to set up wireless IP connections.
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 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 serial 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 are indicated in Figure 1.2, “MOB-IP-SIM Component Diagram”.
The simulator must be configured to work within the bounds of your local area network. This configuration, covered in Chapter 3, Simulator Configuration, 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.
| 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 |
| PPP: Configurable CHAP or PAP authentication for Simple IP | No | Yes |
Table 1.1. Features Matrix
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™ processor unit (Either MIP-5800 or MIP-5850 )
DE-9 to DE-9 null modem serial cable
Cat-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 with the E6702B cdma2000 lab application option
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. The unit's operating system, user-specific configuration data, and any user-installed content are stored on an internal CompactFlash™ memory card for maximum reliability.
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, E5515C Interconnection, 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 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, Simulator Configuration Worksheet.
The IP address may be set without the MOB-IP-SIM™ Manager by following the procedure in Appendix F, Manual MOB-IP-SIM Configuration .
![[Note]](images/note.png) | Note |
|---|---|
Do not connect anything until so instructed by the MOB-IP-SIM™ Manager software | |
Table of Contents
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
- 3.1.1. Configuration Menu
- 3.1.2. Network Configuration
- 3.1.3. PPP Configuration
- 3.1.4. MIP-5850 PPP Configuration
- 3.1.5. MIP-5800 Mobile IP Configuration
- 3.1.6. MIP-5850 Mobile IP Configuration
- 3.1.7. NAT Configuration
- 3.1.8. E5515C Configuration
- 3.1.9. Mobile Device Configuration
- 3.1.10. Testing the Configuration
This section outlines the set up 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 4, Logging
Once the initial IP address is set, record the provisioning information in sections [A] and [C] of Appendix E, Simulator Configuration Worksheet) 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, “Mobile IP network simulator page”. Access to the simulator documentation, debugging and operation logs, copyright information, and demonstration web content are also available on this page.
Click on the menu link to reach the main configuration menu page shown in Figure 3.2, “Configuration menu page”. 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 and .
Clicking on the 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 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, , or commands.
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.
Click on the link to display the next configuration page, which is the same in the MIP-5800 and the MIP-5850 .
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 a string based name identifier. This 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™ unit and should have been configured correctly by the MOB-IP-SIM™ Manager setup.
- 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.
- Primary DNS server
This is the IP address of a Dynamic Name Server that provides name lookups for your network. This value only applies in the static IP mode since DHCP mode automatically establishes this address. Type ipconfig /all | more at the Windows DOS prompt to determine this address on your network.
- Secondary DNS server
See Primary DNS server.
- Tertiary DNS server
See Primary DNS server.
Click the button to save the current information and then click to go to the next configuration page, which varies depending upon the model.
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 is the only parameter that is involved in a Mobile IP connection. Each parameter setup is described in this section.
- Propose IP address during IPCP
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. This address is used by Simple IP as the PDSN address and by Mobile IP as the source address for sending Agent Advertisements prior to the Mobile IP registration handshake.
- 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 and by Mobile IP as the source address for sending Agent Advertisements prior to the Mobile IP registration handshake.
- 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.
- Propose PPP authentication
Default is ON. Check this option to cause the simulator to propose authentication. Applies only to Simple IP.
- Permit unauthenticated PPP
Default is ON. Check this option to allow the mobile to reject the proposed authentication. The normal setting is ON. Applies only to Simple IP.
- PPP user name
This is the Authentication name that will be used for dial-up networking on a PC. Applies only to Simple IP.
- PPP password
This is the Authentication password (or secret) that will be used for dial-up networking on a PC. Applies only to Simple IP.
The MIP-5850 provides two additional parameters on its PPP configuration form as indicated by the following figure:
- 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 command 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 command is available only in the MIP-5850.
When completed, click to store the parameters. Then click the link to go to the next configuration page, which varies depending upon the model.
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 link.
Transfer the recorded Mobile IP provisioning information from section [A] of Appendix E, Simulator Configuration Worksheet 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.
- 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
The address of the Home Agent Entry 1 is the Primary HA. Entry 2 is the Secondary HA. These should match the values programmed in the wireless device.
- 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 alphanumeric 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.
- 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.
- 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.
The following parameters are visible only on the Mobile IP Configuration page of the MIP-5850 simulator as shown in the following figure.
- 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 rocessing 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 stations compliance with the network assigned lifetime. Note (ref: RFC-3344): A value of zero indicates that the mobile node has been deregistered.
- 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) 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 address of the MOB-IP-SIM™ that normally acts as the FA. Entering a specific non-zero address will override the normal address that is advertised in the FA care-of address field.
- ICMP Router Advertisment 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 Advertisment 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.
- 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 command is available only in the MIP-5850.
- Registration lifetime
Default is 600 sec. This is the longest lifetime that this agent is 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. Previous spec defined this as Van Jacobson bit. 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.
Click and then click the link to go to the next configuration page.
On the NAT configuration form, you may set up network address translations as required to conform to your network or the mobile stations requirements.
Use the Proxy Server information from section [C] of Appendix E, Simulator Configuration Worksheet to set the NAT configuration if needed.
When completed, click and then click the link to return to the Configuration Menu.
Mobile IP typically uses service option 33 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, Simulator Configuration. The E5515C is also assumed to be set up and ready to handle standard SO33 data calls.
Connect the required communications test set, PCs, Hubs, phone, and MOB-IP-SIM™ as diagrammed in Appendix D, E5515C Interconnection.
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, Simulator Configuration Worksheet and set the External PSDN State to ON.
The E5515C should indicate that the link to the MOB-IP-SIM™ is active after entering the external PDSN address.
Exit back to the E5515C call processing menu.
This completes the E5515C set up.
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, Simulator Configuration Worksheet. 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 manufacturers 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.
You are now ready to set up a Mobile IP data call.
Set up the E5515C for SO33 data operation. Always start with the standard SO33 mode rather than the SO33-FSCH mode to simplify the RF channel setup requirements (F-SCH channel power level adjustments are needed if you plan to use the SO33-FSCH 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 phones 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. | |
Table of Contents
This chapter will teach you
How to access message logs.
How to access error logs.
How to access operational logs.
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™ webserver. Click on the link to reach the following menu and then click on the appropriate link to reach the log of interest.
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 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 field and clicking on the button.
To download the log in binary form, click on the link to see the tcpdump as shown in the following figure. Filtering by expression is also possible. The binary format may be read directly by the Ethereal freeware traffic sniffer software.
Click on the 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.
Click on the link on the Log menu to call up the log of messages from the foreign agent as shown in the following figure.
Click on the link on the Log menu to call up the log of all access to the MOB-IP-SIM™ HTTP content server as shown in the following figure.
Click on the 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.
Click on the link on the Log menu to call up the log of the HTTP proxy server activity as shown in the following figure.
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.
The link leads to files suitable for viewing on a mobile device.
The link leads to the menu discussed in Chapter 3, Simulator Configuration.
The link leads to a PDF of the current operations manual.
The link leads to the log files discussed in Chapter 4, Logging.
The link leads to the legal fine print.
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 (instructions) 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 seven 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.htm : 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.htm 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/.
Table of Contents
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 an equals sign, 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 on this page are available to both the MIP-5800 and MIP-5850 simulators
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.
PPP Commands (available only to the MIP-5850 simulator)
-
+ipdhcp=0 []
-
+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, +pppauto, +pppkill, +pppterm, +pppactive, +ppppassive .
-
+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, +pppauto, +pppkill, +pppterm, +pppactive, +ppppassive
-
+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 , +pppauto , +pppkill , +pppterm , +pppactive , +ppppassive
-
+pppkill []
Immediate Disruptive Action
Kill the PPP link (without sending LCP Terminate-Request).
Agent Advertisement Commands
-
+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
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.
-
+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 +miphaaddr , +miphamask , +mipreplycode , +miphaspi , +miphasecret , +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.
-
+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.
-
+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.
-
+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).
-
+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 doesn't 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
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 doesn't look in extensions by itself; you have to point it there.
-
+capstop
Immediate Action
Stop capturing packets. Any packets already captured are preserved.
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:
Operating system image
MOB-IP-SIM™ Manager for Windows
This manual in PDF and XHTML formats
MOB-IP-SIM Tutorial
The previous figure indicates the typical interconnection required for the MOB-IP-SIM™ to be used with the E5515C The diagram assumes the use of the high-speed serial interface card supplied by Software Concepts. Connections depicted by dashed lines indicate temporary or optional interconnection.
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.
| 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] |
Table E.1. 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 Hyperterm 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 ipmask enter at+ipnetmask? A response of+IPNETMASK: 255.255.255.0 OK
indicates that the ipmask 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