_______________________________________________________________________________________________________
_______________________________________________________________________________________________________
© Virtual Access 2018
GW2020 Series User Manual
Issue: 2.1
Page 357 of 423
35.5.4
ISAD diagnostics
35.5.4.1
Checking process
To check to see if ISAD is running, enter pgrep –fl isad:
root@VA_router:~# pgrep -fl isad
5303 /usr/sbin/isad -b 60 -s 10 -c 200 -u /var/state /var/const_state
35.5.4.2
Checking bin statistics
To check if stats are being collected, enter cat /var/state/monitor:
root@VA_router:~# cat /var/state/monitor
monitor.bin_0=isad
monitor.bin_0.end_ts=85020
monitor.bin_0.start_ts=84960
monitor.bin_1=isad
monitor.bin_1.end_ts=85080
monitor.bin_1.start_ts=85020
monitor.bin_2=isad
monitor.bin_2.end_ts=85140
monitor.bin_2.start_ts=85080
35.5.5
ISAD operation
The bin statistics stored on the router must be periodically pushed statistics to Monitor.
This is normally done centrally when statistics are enabled on Monitor. Monitor contacts
each router and auto-generates a script that will automatically schedule the upload of
the bin statistics.
However, if Monitor cannot access the router WAN IP, you must do this manually on
each router using a UDS script. An example is shown below where the bins are uploaded
every hour to a Monitor server IP 89.101.154.154 using TFTP.
package uds
config script 'isb_upload_scr'
option enabled '1'
option exec_type 'periodic'
option period '1h'
list text '/usr/sbin/isb_upload.lua 89.101.154.154:69'