Bay Networks Bay Dial VPN, Configuration And Troubleshooting Manual

Page: 142 / 186

Configuring and Troubleshooting Bay Dial VPN Services
11-22 BayStream Multiservice Software Version 7.2 115623B Rev. 00
Tracing a Packet’s Path at the Remote Annex
You can use the
ping -t
(traceroute) superuser command at the Remote Annex
console to trace the path of a packet from the local host to the destination host and
back, displaying information about each router in the path. This option lets you
see whether a packet arrived at and/or returned from its remote destination, and if
not, where it stopped. This option is based on the traceroute facility, described in
RFC 1493. For more information about using the
ping -t command, refer to the
Remote Annex Administrator’s Guide for UNIX.
Annex does not receive
updates.
(continued) 4. Is the Annex broadcast address set
correctly?
Verify the configured Annex broadcast
address.
5. If your network is divided into
subnets, the IP subnet addresses
and subnet masks may not be set
correctly for the Annex and the
SLIP and PPP ports.
Verify the configured IP subnet
addresses and subnet masks for the
Annex and the SLIP and PPP ports.
6. If the Annex parameter
routed
is
set to
N
, passive RIP is disabled.
Reset the Annex parameter
routed
to
Y
.
7. If subnet routes are not being
learned, the
rip_sub_accept
parameter is set to
N.
Reset the
rip_sub_accept
parameter
to Y (the default).
8. Is
rip_recv_version
set correctly
for the version(s) of RIP running on
your network?
Verify that the interface parameter
rip_recv_version
is set correctly for
the version(s) of RIP running on your
network. Refer to the description of
authenticating incoming RIP 2 updates
and requests in the
Remote Annex
Administrator’s Guide for UNIX.
Also verify that the gateway is
configured to recognize and send RIP
version 2 updates.
Table 11-2. Remote Annex Troubleshooting Chart
(continued)
Problem/Symptom Possible Cause Action