Thinklogical Router - Configuring the ASCII Interface - Manual (Page 6)

Log file debugging entries
When debugging is turned on, several different types of messages are written to the system log
file: /var/log/api. (Early systems did not have a separate log file for the API, all log entries were
written to the file: /var/log/messages.)
Listed below are five commands that were sent to a Vx160. Below those commands is a piece of
the log file showing the corresponding log entries. The first line in the log file records the event
that enabled logging.
ci0150o0151
si0150
so0151
do0151
CI0312O0001
Jul 29 15:44:18 vxrouter vxrapi[391]: caught signal SIGUSR1 (10), turn on api debugging
Jul 29 15:44:55 vxrouter vxrapi[460]: command: ci0150o0151 response: R0000OK#ci0150o0151
Jul 29 15:45:14 vxrouter vxrapi[460]: command: si0150 response: R0000OKI0150O0151#si0150
Jul 29 15:45:18 vxrouter vxrapi[460]: command: so0151 response: R0000OKI0150O0151#so0151
Jul 29 15:45:25 vxrouter vxrapi[460]: command: do0151 response: R0000OK#do0151
Jul 29 15:58:32 vxrouter vxrapi[463]: command: CI0312O0001 response: R0000ER0006#Input port
number 312 is out of range
These log entries list the command that was received and the response sent back to the sender.
The log files contain other system related messages and are a valuable aid in troubleshooting.
Please note that these logs are maintained in RAM, and will be erased during a reset or loss of
power to the VxRouter. Linux does offer the means to send these log file entries over the
network to another system. That discussion is outside the scope of this document. Some
information may be found in the document: Router_Interfaces.pdf
A note for telnet users
By default, vxrapi does not send a CR on each line. This is a problem for Windows telnet client
software. The API (v4.0-4 and later) has a command to turn on CR's. This command is XCRON.
If your telnet output from vxrapi is spread out over the screen, then send the XCRON command.
Revision: G