 |
 |
| Q: |
What tools can I use to get port status and debugging information? |
| |
|
| A: |
There are a number of trace and dump facilities available to help track down serial connection problems.
- NativeCOM trace - you can turn on tracing through the NativeCOM driver control panel to trace the data and system calls going to and from one or more NativeCOM COM ports. See the appropriate NativeCOM manual section.
- Port Status from browser or port_stat from login session - to watch a summary of activity on all the ports, point your browser at the port server and select the "Port Status" display, or you can telnet to the unit and run port_stat (in expert mode). See the appropriate Administrator's Guide section.
- Onboard trace facilities - you can trace a number of things in the onboard code using the "expert" trace facility.
For example, to start tracing activity on port 1: expert> trace_on port 1
To display the captured data: expert> trace_display
To clear the captured data: expert> trace_clear
To turn off tracing: expert> trace_off port 1
- Memory dump facilities - it is possible to get a memory dump from a port server to give detailed information to the Systech customer support to diagnose problems. Contact customer support for details on whether you should get a dump of memory and, if so, what procedures to use.
- Flash memory error records - certain hardware failures and catastrophic software failures are recorded in the "product data area" of flash memory for later analysis. You can display these records with the "expert" command "flash_log" or you can retrieve these records over the network and send them to customer support using the port server utility, rcserrlog utility or the r4000 utility.
|
| |
Answer Last Updated: April 3, 2008 |
|
|
|
|
