Contents:

- Error Messages
- File Retrieval using FTP
- Display debug data to the configuration port using the Serial Configuration Interface
- Display debug data to the debug port using a Web Browser
- Help Pages
- Diagnostic Error Pages
- Using Indicator LED's for Troubleshooting
- Terminal Emulator Troubleshooting
- Functional Tests

Error Messages

Error and Status messages are stored in memory. If the EtherPAD crashes, Error-messages are stored automatically in a file called DebugReport.txt. Alternatively, the user can select (via the Configuration Interface) to write the currently stored error-messages to the DebugReport.txt file.

File Retrieval using FTP

Use an FTP client to connect to the EtherPAD.
Login as root (the default password is xxx).



FTP login from Command Prompt


If the DebugReport.txt file has not been saved, use the quote site log command.



Quote Site Log


The EtherPAD will confirm successful file creation.
Display the EtherPAD file directory with the dir command to confirm that the DebugReport.txt file was written.



Directory Listing


Transfer the file using the get command.
When the file transfer to your PC is complete, you will see the following.



Transfer of Log File


Log out of your FTP session using the bye or quit command.
The DebugReport.txt file may now be read using a text editor such as Notepad.

Display debug data to the configuration port using the Serial Configuration Interface

Connect to the EtherPAD as described in previous chapters
Select 1. Configuration Interface…
Select B. Debug Options…



Displaying debug data (Serial/Telnet)

Display all Debug Output: Selecting Yes displays all debugging data to the Serial Configuration port. Selecting No resets this output.

Display debug data to the debug port using a Web Browser

Connect to the Web Configuration Interface.
Click on Management.



Home Page



Management Settings

Click Debug Options.



Debug Options page

Enable Debug Output - the EtherPAD will display all further debugging information on the Configuration Serial port.

Save Log to File - save the running log to the file DebugReport.txt on the file system. (The Change button must be pressed before the log is actually saved).

The software subsystems that can be debugged are:
Debug IP - the IP (Internet Protocol) layer of the network stack.

Debug TCP - the TCP (Transmission Control Protocol) layer of the network stack.

Debug PPP - the PPP (Point-to-Point Protocol) stack.

Debug Modbus - debug the Modbus and Modbus/TCP protocols. (Only available if the optional Modbus feature is enabled).

Debug File system - monitor operations performed on the EtherPAD's file system.

The following buttons are displayed:
Display Saved Log - the previously saved log file is displayed.

Display Running Log - the current running debugging log is displayed without being saved to a file.

Note: If the software should fail in such a way that the EtherPAD reboots, the debugging information will automatically be saved in the DebugReport.txt file.

Help Pages

Comprehensive Help is available to the Web Browser by clicking on the Help button as illustrated below.



This button appears on most configuration web pages and displays a relevant Help-page.

Diagnostic Error Pages

Should users try to enter an illegal value or inconsistent configuration, one of a comprehensive list of diagnostic error-pages is displayed (e.g. Invalid IP Address).



Configuration Error

Error Codes
If error logging is enabled, various error messages may be reported via the EtherPAD's configuration serial port. Alternatively, the current error log can be downloaded from the web interface. These message numbers can be critical when attempting to interpret a possible error, and should be included in any correspondence to support personnel at SAN People.

Reporting Errors
Should you have any problems or suspected problems with any SAN People product, please report these via e-mail to techsupport@sanpeople.com or your local help-centre. Please remember to include your EtherPADs' MAC Address and a copy of the EtherPAD configuration file. Any error log files you may have recorded can also be attached. SAN People are dedicated to providing comprehensive customer support.

Using Indicator LED's for Troubleshooting



Indicator LEDs on front panel

Using Indicator LED's for Troubleshooting



Indicator LEDs on front panel

Serial Port Status
RTS	Request to Send: Indicates the EtherPAD has turned on the RTS signal.
CTS	Clear to Send: Indicates the incoming CTS signal is active.
Application Status
RIN	Data received on Debug/Configuration Port.
HBT	Heartbeat: Flashes approximately once per second to indicate the EtherPAD is functioning.
TIN	Data output on Debug/Configuration Port.
Ethernet Status
LNK	Link: Always on when the Ethernet Network link is good.
BSE	Base Ethernet: Indicates the EtherPAD is servicing the Ethernet chipset.

EtherPAD LED status indicators

HBT
OFF - Software not running EtherPAD should be returned to SAN People.

Serial LED's
CTS OFF - serial device not connected or cannot receive data.
RTS OFF - pad cannot accept more data from the serial device.

Network LED's
LNK OFF - no network connected

Config port
If RIN stays off when data is transmitted to the configuration port, or the TIN LED stays off if data is transmitted from the pad, the serial configuration port is faulty.

ALL LED's
ALL LED's OFF - Check power connector, power supply and mains supply

Terminal Emulator Troubleshooting

With some applications, the HyperTerminal software supplied with Microsoft Windows Operating Systems and on the SAN People Configurations and Utilities CD does not work correctly. The reason for this is that when HyperTerminal establishes a TCP connection it assumes that the remote server is communicating using the Telnet protocol. This results in every 0xFF character being escaped (not passed to the application). The Remote device thus assumes this to be a bad packet and the transmission is stopped.

There are two ways to solve this problem. The Redirector software supplied on the SAN People Configuration on the Utilities CD can be used to create a virtual serial port. HyperTerminal transmission will then be correctly achieved via this port. The other is to use another terminal emulator.


ZOC Terminal Emulator and Telnet/Secure Shell (SSH/SSH2) Client

The text below should give the user a good idea of the ZOC terminal emulator and Telnet/SSH client capability.



ZOC Terminal Emulator

The screenshot above shows the ZOC terminal emulation screen configured for SSH communication with Linux emulation. The button bar lets you map arbitrary functions, for example calling a certain host, starting a certain REXX file, etc., onto buttons. You have the option of selecting your own labels. The buttons in the status line show the current input/output device, file transfer protocol, terminal emulation, telephone costing information, modem status (via LEDs), log file, online time, etc. Clicking on these buttons brings up the option dialogs defining these services.

Functional Tests

You can do the following simple tests to prove your EtherPAD configuration as well as your serial and network cable choice.


Pinging
Your EtherPAD is now configured and you should be able to Ping the unit. This is a useful test as it confirms correct Network configuration.

Type ping [EtherPAD IP ADDRESS] from your PC Run or Command prompt, where [EtherPAD IP ADDRESS] is the IP Address the EtherPAD was configured with previously.

The arp -a command can be used to confirm that the ping reply is from the EtherPAD under tests and not from a duplicate IP Address on the network. Compare the MAC Address returned with that printed on the side of the EtherPAD.



Indicator LEDs on front panel