Black Box LRA005A-R2 - Manual (Page 98)

ASYNC ROUTER AR-P, AR-5, AND SYNC ROUTER USER’S MANUAL
98
2. Issue the dialup status command. Verify that the correct phone number for the other site is
displayed. To determine if the dialer is configured as required, refer to Section 2.9, dialup, in the
Reference Manual, which begins on page 137, for a description of possible dialer modes: demand,
demand backoff, inactive, incoming, once, or keepup.
Determine the connection status: idle, dialing, listening, serving call, or called out. For possible
modem states, also refer to the Modem Control Signals discussion in the Modem Dialing chapter of the
Reference Manual, which begins on page 137.
3. If you don’t hear a busy signal, it may be necessary to check the configuration of the remote Router.
If possible, log in to the remote Router over the Ethernet or on the console and enter the route
command to check the routing table. The routing table on the remote Router should contain an
entry with the Destination field specified as the (sub)network on which the local Router resides.
Verify that the Bits field in the routing table entry matches the number of significant contiguous bits
to be used as a subnet mask for the local site. Make sure that the Interface field in the routing table is
specified as modemX, where X is the appropriate modem designation number. Make sure that the
phone cable is connected to the modem shown in the Interface field of the route entry.
4. If possible, execute the procedures described in Approach 1 above on both the local and remote
Router.
5. To display PPP information, issue the ppp modemX command, where X is the appropriate modem
designation number. Make sure that the first line displayed after this command is:
Network Protocol Phase (open for XX:XX:XX:XX)
This means that the system names and link passwords are correct on both systems. If you see
anything else, make sure that both systems are configured in each other’s name and password (using
the config modify command).
Determine if any PPP packets have been sent on the link. For more information, refer to Section 2.18,
ppp, in the Reference Manual, which begins on page 137.
6. Issue the asystat command to see transmit and receive statistics for the appropriate modem
interface. Refer to Section 2.3, asystat, in the Reference Manual.
7. Issue the tip command to manually use the appropriate modem interface. Refer to Section B.4.1 in
the Reference Manual.
8. If you have taken the steps above and are still unable to determine why the connection is not being
established, call Technical Support.
Approach 3
If in Approach 2 you were able to establish a dialup connection between the local and remote Routers,
but are unable to send data between the local node and the remote node, continue immediately with
the following steps:
1. Make sure that the subnetmask and the (sub)network number on the local node and the local
Router match. Also verify that the subnetmask and the (sub)network number on the remote node
and the remote Router match. Display this information using the ifconfig command.
2. Verify that both the local node and remote node contain appropriate routing information. The local
node must contain a route that is used to determine how to reach the remote node. Similarly, the
remote node must contain a route that is used to determine how to reach the local node. Different
TCP/IP implementations have differing methods for managing routes. Most UNIX machines
implement the route command to add routes and the netstat command to display routes. Check in
the system administration guide for your TCMP implementation to determine how to manage routes.