
Introduction
1-21
If the ping command yields the response “Target does not respond,” the station
you issued the ping from believes it knows how to get to the end node, but never
received a reply to its echo request. In this case, start pinging each node in the path
between the source and destination until you find the problem interface.
Refer to Using Technician Interface Software or Managing Routers and BNX
Platforms for detailed instructions on issuing a
ping command.
Using Packet Capture
The Technician Interface Packet Capture tool allows you to filter, send, capture,
and view packets in hexadecimal format. You can save the data in a Network
General Sniffer format file, transfer the file to a network analyzer, and use the
analyzer to parse the data. We recommend that you use Packet Capture to capture
data generated at remote routers, save it in Network General Sniffer format files,
and use TFTP (Trivial File Transfer Protocol) or FTP (File Transfer Protocol) to
transfer the files to a site where you can open the files with a network analyzer.
Appendix B provides detailed instructions on how to use Packet Capture.
Using Inbound Telnet to Access the Technician Interface
Versions 7.60 and higher allow you to use Telnet to establish a Technician
Interface session with a router.
To make Telnet a configurable option in the Protocols menu, create and enable
TCP (Transmission Control Protocol) and Telnet Server as follows:
1. From the Configuration Manager window, select Protocols➔Global
Protocols➔TCP➔Create TCP.
2. Select Protocols➔Global Protocols➔Telnet Server➔Create Telnet Server.
The Telnet Configuration window appears.
3. Change the settings to the ones you want, or use the default settings, and
click OK.
Note: We strongly recommend that you learn how to establish an inbound
Telnet session with the router in order to troubleshoot problems from a remote
site.
Komentáře k této Příručce