HP-UX Mobile IPv4 A.03.01 Administrator's Guide

8GTKH[KPICPF6TQWDNGUJQQVKPI
%QOOQP2TQDNGOU
Chapter 8
107
Routing Problems - Deleted Mobile IPv4 Routes
If the Mobile Node is registered but you cannot send packets between the Correspondent
Node and the Mobile Node (users report connection timeouts or host unreachable errors),
the gated daemon on the Home or Foreign Agent may have deleted the Mobile IPv4 route
entries. This problem occurs if you start or re-start the gated daemon after the HP-UX
Mobile IPv4 daemon has started. When the gated daemon starts, it deletes routes that it
does not have configuration information for, such as Mobile IPv4 route entries.
Route optimization will also fail if gated deletes Mobile IPv4 routes on a Correspondent
Node.
Use the following procedure to verify if gated is deleting Mobile IPv4 routes:
1. Verify that other HP-UX Mobile IPv4 components are operating properly. Verify that
the Mobile Node is registered. On the Home Agent, check that the output from the
mipadmin -bindings command shows the Mobile Node and correct Care-of Address.
On the Foreign Agent, check that the output from the mipadmin -visitors
command shows the Mobile Node.
If you are using route optimization, use the mipadmin -roinfo command on the
Correspondent Node to verify that the Correspondent Node has an entry with the
Mobile Node’s current Care-of Address.
2. Use the netstat -rn command to check if the Mobile IPv4 routes have been deleted.
Check for the following Mobile IPv4 routes:
• On the Home Agent: the Home Agent must have a host route with the Mobile
Node’s home address as the destination (11.11.11.4 in the example below), the
Home Agent’s address as the gateway (11.11.11.2 in the example below) and an
HP-UX Mobile IPv4 virtual tunnel interface (v4tu0:n, where n is the tunnel
number) as the interface.
#netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
:
:
11.11.11.4 11.11.11.2 UH 0 v4tu0:1 1480
• On the Foreign Agent: the Foreign Agent must have a host route with the Mobile
Node’s address the destination (11.11.11.4), the Foreign Agent’s address
(12.12.12.2) as the gateway and a LAN interface as the interface:
#netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
:
:
11.11.11.4 12.12.12.2 UG 0 lan1 1480
• On the Correspondent Node, if you are using Route Optimization: the
Correspondent Node must have a host route with the Mobile Node’s address as
the destination and a LAN interface as the gateway. The output would be similar
to the above output on a Foreign Agent.