CALAMP WIRELESS NETWORKS INC. BDP4-EXCT769 Manual De Usuario
001-2019-500 Rev 0
Paragon4 – UHF, 700 & 800MHz User Manual
80
Note:
Log information will be preserved across system restarts or faults.
The general categories of events that can be found in the system log are:
Asserts: undesirable conditions (faults)
Resets: reasons for various system resets
Others: warnings, recovery from a fault, etc
6.11.7.1.1
Asserts
An Assert log entry will normally display an exit code, a module number, and a line number indicating
where the error occurred. See Figure 74 for an example of an Assert log entry. This information will al-
low CalAmp support team to determine the component and the reason of an error so that a corrective ac-
tion could be recommended.
where the error occurred. See Figure 74 for an example of an Assert log entry. This information will al-
low CalAmp support team to determine the component and the reason of an error so that a corrective ac-
tion could be recommended.
Figure 74 - An Assert type system log entry
Note:
“0x0” exit code signifies normal (non-faulty) system exit.
6.11.7.1.2
Resets
A Paragon4 unit may be reset manually (through the Web interface, a telnet shell, or SNMP control) or
automatically (as a result of the unit’s own monitoring facilities).
automatically (as a result of the unit’s own monitoring facilities).
Below are some examples of Reset log entries:
Reset issued by a shell command:
[5 1970-01-01 01:03:45 3827.924 37 C]
stationReset: board hard reset
stationReset: board hard reset
Reset issued through the WEB Interface:
[10 1970-01-10 21:49:00 856116.827 38 C]
HTTP server reset
[11 1970-01-10 21:49:00 856116.842 38 C]
Exit... 0x0
HTTP server reset
[11 1970-01-10 21:49:00 856116.842 38 C]
Exit... 0x0
Reset issued by an SNMP MIB browser:
[14 2007-09-17 16:25:17 631.641 34 C]
SNMP: board hard reset
SNMP: board hard reset
Module
Number
Line Number
Exit Code