Bay Networks Bay Dial VPN, Configuration And Troubleshooting Manual

Page: 144 / 186

Configuring and Troubleshooting Bay Dial VPN Services
11-24 BayStream Multiservice Software Version 7.2 115623B Rev. 00
Given the topology in Figure 11-1 , the command
annex#
ping –t 132.254.33.4
displays output such as the following when a traceroute packet passes successfully
to the
ping –t destination and back:
PING hobbes: 56 data bytes
Dir Router Hops Speed (b/s) MTU
>>> 132.254.99.2 1 19200 1024
>>> 132.254.33.3 2 10000000 1500
<<< 132.254.99.3 1 19200 1024
<<< 132.254.66.2 2 10000000 1500
64 bytes from 132.254.33.4: time=10. ms line 7
In the next example, Router 2 is unable to forward the outbound packet, as
indicated by the asterisks (***) under the Dir heading. Note that the hop count
remains at 1, since the packet crossed only one router.
annex#
ping –t 132.254.33.4
PING hobbes: 56 data bytes
Dir Router Hops Speed (b/s) MTU
>>> 132.254.99.2 1 19200 1024
*** 132.254.33.3 1 0 0
Troubleshooting Tunnel Problems
Since the TMS is an extension of the proprietary erpcd, you can use essentially
the same troubleshooting procedures that you would use for other erpcd problems.
In general, tunnel problems fall into the following categories:
• User errors
• Equipment failure
• Configuration errors
• TMS database errors
User errors, such as a domain name that is not valid, result in the user being
denied access to the system. Dial VPN logs the message to the syslog. Appendix B
lists the syslog messages.