The ePipe has many built-in diagnostic tools that can help to identify and resolve issues. All of the non-interactive diagnostic tools and reports are available through the web interface by selecting "status" from the toolbar, then "Reports", and then "General". All other tools can be used from either the command line, or through the HTML Command Line Interface.
The ping command is useful to determine connectivity, packet round trip time, DNS name resolution and link quality.
Note: Ping is unavailable from the web interface, and should be used through the command line. A ping command can be aborted by pressing any key whilst ping is running.
To test connectivity between the ePipe and a remote IP address, use the simplest form of ping.
For example:
Local 10>> ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=0.000 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0.000 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=0.000 ms
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 0.000/0.000/0.000/0.000 ms
Some of the errors that may occur when using ping are listed below.
ping: sendto: No route to host
This error indicates that the remote address specified is unreachable from any network to which the ePipe is connected. Double check IP addresses and connected gateways (use the SHOW INTERNET GATEWAYS command to do this).
20 packets transmitted, 0 packets received, 100% packet loss
20 packets transmitted, 4 packets received, 80% packet loss
"0 packets received" indicates that while the packets were transmitted on the correct interface, the remote host is down, a link between the ePipe and the remote host was missing or an intermediate host has incorrect routing information.
If the number of packets received is less than the number of packets sent then the link is not completely reliable.
Check the ePipe routing table. If possible, try "pinging" intermediate hosts between the ePipe and the remote host. If dialed directly to a remote host, check that end for routing or connectivity problems. Also check the phone line for quality if less than 100% packets received.
unknown host: hostname
ping couldn't resolve the name of the host "hostname". Check DNS name resolution settings and make sure the DNS server is available (eg use the command SHOW INTERNET NAME RESOLUTION).
The ePipe maintains counters for both data traffic and network errors. These can be useful in determining any errors on the LAN.
Local 10>> show server counters
EPIPE-4000 Version: V1.0.0 Uptime: 00:47:37 Ethernet: 00-60-1F-99-99-99 Internet: 192.168.51.2 Name: EPIPE_00601F999999
Time Since Zeroed:
00:47:37Port Input Bytes: Port Output Bytes: Overrun Errors: Framing/Parity Errors:
Ethernet counters:Bytes received: Bytes Transmitted: Frames Received: Frames Transmitted: Receive Errors: Transmit Errors: Input Frames Dropped: Collisions: Bad Protocol:
Network Buffer counters:Total Mbufs: Total Clusters: Free Mbufs: Free Clusters: Header Mbufs: Data Mbufs: Waited for Mbufs: Drained Mbufs:
For example, non-zero values for Overrun, Framing or Parity errors indicates problems with the data being recived with the serial ports. The SHOW PORT portnumber COUNTERS can be used for further investigation.
Non-zero counts for the Ethernet counters may indicate faulty cabling, exceptionally busy networks or other network issues such as multiple systems with the same IP address.
The ePipe also keeps track of port activity, including transmit and receive character counts, and errors.
| Local 10>> show port 1 counters | ||||||||
|
Receiver
|
Transmitter
|
Error Counters | ||||||
| Port ==== |
Characters ========== |
Stop/Start ========== |
Characters ========== |
Stop/Start ========== |
Overrun ======= |
Parity ====== |
Framing ======= |
|
|
1
|
80
|
0
|
2618
|
0
|
0
|
0
|
0
|
|
The current status of all of the telnet listeners can be shown using the command:
Totals are calculated by the ePipe for all internet connections:
Local 10>> show internet counters
TCP segments: Transmitted: Bytes Transmitted: Data: Bytes Data: Data Retransmitted: Bytes Data Retransmitted: Received: Bytes Received: Data: Bytes Data: Errors:
IP packets:
Internet Connections:Packets Transmitted: Requested: Packets Received: Accepted: Fragments Received: Established: Fragments Dropped: Closed: Error in Header: Dropped:
ICMP Messages:
UDP Datagrams:Transmitted: Transmitted: Received: Received: Dropped: Dropped: Destination Unreachable: Error in Header:
These counters allow you to diagnose issues at a particular protocol level with th TCP/IP family.
Loopback tests are useful in determining if either the serial or ethernet ports are not functioning properly. The loopback test reports the status of all signals on each tested port, as well as the result of transmitting data from the port. Whatever data is received must be the same as the data that was transmitted.
Note: Care must be taken if there is sensitive equipment attached to some ports of the ePipe! Do not run loopback tests on any port that does not have a loopback cable connected!
Local 10>> show port 1 loopback
Errors:
port <n> the port being tested is looped to another port corrupt the data received didn't match what was sent chopped the data received was shorter than what was sent mangled the data received didn't match and was different length to what was sent
If problems persist, click on "help" on the toolbar, then "Support" for information on support procedures:
Either email or fax your dealer / distributor or ePipe this report. Contact details can be found by clicking on "Contacts" on the Support page.
about ePipe | products | solutions | support | information center | contact us
Copyright © 2002 ePipe Pty. Ltd. All rights reserved.
Getting started guides for:
2344
(1.4M pdf)
ML-IP
Concentrator (1.3M pdf)
2202
(1.4M pdf)
2242
(1.4M pdf)
2148/2188
(350KB pdf)
2181
(1.4M pdf)
ePipe
ServerWare (650K pdf)
User Guides for:
ML-IP
Family
VPN
and Security Family
Utilities for viewing guides:
Get
Acrobat Reader (free)
