Tracing A Packet's Path At The Remote Annex - Bay Networks Baystream 7 Configuration And Troubleshooting Manual

Configuring and Troubleshooting Bay Dial VPN Services
Table 11-2. Remote Annex Troubleshooting Chart
Problem/Symptom
Annex does not receive
updates.
(continued)

Tracing a Packet's Path at the Remote Annex

You can use the
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
Remote Annex Administrator's Guide for UNIX.
11-22
Possible Cause
4. Is the Annex broadcast address set
correctly?
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.
6. If the Annex parameter
N
set to , passive RIP is disabled.
7. If subnet routes are not being
rip_sub_accept
learned, the
parameter is set to
rip_recv_version
8. Is
for the version(s) of RIP running on
your network?
ping -t (traceroute) superuser command at the Remote Annex
BayStream Multiservice Software Version 7.2
(continued)
Action
Verify the configured Annex broadcast
address.
Verify the configured IP subnet
addresses and subnet masks for the
Annex and the SLIP and PPP ports.
routed
is Reset the Annex parameter
Y
.
Reset the
to Y (the default).
N.
set correctly Verify that the interface parameter
rip_recv_version
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.
ping -t
routed
rip_sub_accept
parameter
is set correctly for
command, refer to the
115623B Rev. 00
to