User manual

31: Diagnostics
_______________________________________________________________________________________________________
The log contains the events of many modules. To filter a specific module, type
logread | grep module_name, for example, if you want to see the vald events
enter:
logread -f | grep vald
Note: the vald module has a command that enables the logging of the
payload.When enabled, vald will additionally log the payload of all received and
sent packets.
To enable payload logging, enter:
root@VA_router:~# val trace on
val trace enabled
Logread as a ‘-f’ option that output the events as the log grows. It is very useful
when you want to live trace. You may use it this way:
root@VA_router:~# logread –f
or
root@VA_router:~# logread -f
31.14.2 Debugging guidelines
If you are having trouble configuring PAD, use the list below to debug.
Is the router receiving calls? To check the router is receiving calls, look at the log and search
for an event similar to the following:
Nov 28 13:05:40 VA_router user.debug vald: (1): Incoming VC,
TCP accepted, VC id 0, LCN 4095
Is data being received on the
asynchronous serial?
To check data is being received on the asynchronous serial,
enter: tserv show stats.
TERMINAL 4, Dev: /dev/ttySC3
State: CONNECTED
Serial Bytes Rx (2036) Tx (26624) TxErrs (0)
TCP Packets Rx (23) Tx (16) TxErrs (0)
TCP Bytes Rx (26624) Tx (2036)
UDP Datagrams Rx (0) Tx (0) TxErrs (0)
UDP Bytes Rx (0) Tx (0)
DSR Up (0) Down (0)
Uptime 0 hrs 0 mins 22 secs
For more details refer to section 6, ‘Terminal Server’.
Are the vald, padd and tservd
modules running?
To check if the modules are running, follow the instructions
described in the PAD section.
For more details refer to the ‘Terminal Server’ section in this
manual.
_______________________________________________________________________________________________________
© Virtual Access 2015
GW1000 Series User Manual
Issue: 2.4 Page 252 of 255