Stallion Technologiessupport
Product documentation
online documentation
 
Documetation image, 8K

EasyServer Installation Troubleshooting 

EasyConnection

EasyIO

EasyServer II

Troubleshooting Using On-Line Diagnostics 

The EasyServer II has a powerful in-built diagnostics facility which can speed and simplify the business of determining and fixing problems. In the event that problems are encountered, the integrity of the hardware can be checked by performing the tests described in Verifying Proper Functionality. 

View the easyadm Technical Reference [PDF - KB].

Topics:

Using Web Diagnostics.  

Invoke the Server's diagnostics by entering its IP address in a network-connected web-browser, (i.e. http://123.456.789.001). 
When the Setup front page is displayed:

1. Press the `Diags' button. 
2. Select the required diagnostic hyperlink from the Diags screen. These are: 
  • Ping. Use the ping command to verify that network hosts can be reached. This command tests DNS and routing configurations. 
  • Server Counters

    Counters track data traffic and detects errors on networks and serial lines. Use the Counter pages to verify that data is being transmitted, and that no severe errors are occurring. 
    Other useful Counter pages include: 
    - Port Counters 
    - Telnet Listener Status 
    - Internet Counters 
     
  • Loopback Tests. 

    The loopback tests provide a way to test the hardware functionality of your server. Quite often you do not want to test all ports as there may be sensitive equipment attached. In this case you can run the loopback tests on individual ports.
     
  • Support. 

    If you cannot find the problem with your server or its configuration then your should contact your support representative. 
    For further information access the Using the Web-Based Configuration Facility section of the Installation page. 
     

Ping 

Using Web Diagnostics.  
Select the host to be pinged by entering its name in the dialogue box, and pressing <enter>. An example of successful test results, where the host has been contacted and has returned results, are shown below for a host named `cluster' whose IP address is 192.159.80.70 (hosts must first be specified in Setup > Server > DNS): 
  Resolving host "cluster" ... 192.159.80.70 
PING cluster: 72 data bytes ... 
80 bytes from 192.159.80.70: icmp_seq=1. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=2. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=3. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=4. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=5. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=6. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=7. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=8. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=9. time=20. ms 
80 bytes from 192.159.80.70: icmp_seq=10. time=20. ms 
10 packets transmitted, 10 packets received, 0% packet loss. 
round-trip (ms) min/avg/max = 20/20/20 
 

Server Counter 

Using Web Diagnostics.  
The server counter diagnostic displays a variety of information about data traffic, network errors and serial lines. Example output of a successful server counter diagnostic test is shown below: 
es2-servercount.gif (26986 bytes)   
 

Port Counters 

Using Web Diagnostics. Port counters check the functionality of connected ports, and indicated errors where they occur. Sample output is shown below. 

es2-portcount.gif (15607 bytes)

 

Telnet Listener Status 

Using Web Diagnostics.  
The telnet listener status test can be used to determine whether the telnet listener is active. Sample output is shown below:
  es2-listner.gif (6878 bytes)   
 

Internet Counters 

Using Web Diagnostics.  
The internet counters test checks the various aspects of the transmission of TCP segments, IP packets and ICMP messages, as shown below. Sample output from a successful internet counters test is shown below: 

es2-counters.gif (27036 bytes)

 

Loopback Tests 

Using Web Diagnostics.  
Loopback tests check the IRX/ITX, RX/TX, RTS/CTS and DTR/DCD functionality of ports with a loopback connecter attached (part no. CO-LBRJ-UNI). In the sample output below, port 2 has a loopback device connected. The results indicate that this port is functioning correctly. 
If problems persist, use the `Support' option on the `Diags' main screen to: 
es2-loopback.gif (15850 bytes)   
  • Contact the dealer/distributor from whom you received the EasyServer II, or if unavailable, Stallion Technologies. 
  • Generate the diagnostic information which will help Support to identify the problem(s) and determine the solution(s). 
Either e-mail or fax your dealer/distributor or Stallion (e-mail: support@stallion.com or support@stallion.oz.au). If e-mail is unavailable, print diagnostic page from your browser and FAX it to your dealer or one of the Stallion offices listed on the contact page. 
The diagnostic page is a comprehensive listing of your server's current configuration. It also includes the results of a number of diagnostic tests already discussed above. 
 

Conclusion 

If all of the above tests are successful, the EasyServer II is functional. Further troubleshooting to track down a network problem may require the use of the PING and TELNET commands from either the server or another host on the network 
Copyright © 2007 Lantronix. All rights reserved