Echelon i.LON 600 LonWorks/IP Server - Manual (Page 67)

Section 2: Advanced Topics
Event Types
The event log records different types of event messages. Every event includes a date/time
stamp and a message.
The following sections list the event types and include a description of the message.
Fatal exception reboot; intvec#<vector>;pc:<address>
A fatal exception has occurred. The event will be followed by a stack trace of the task
that took the exception. The device will reboot after a fatal exception.
Remotely initiated reboot request received
The Configuration Server sent a remote boot request.
**********System started************
The system started after a reboot. Tracking this event is useful in the case where the
system reboots for reasons other than those logged as events. For example, this event
could be due to a power cycle or certain program faults.
******Boot failed/interrupted******
The bootrom failed to load the system image and entered the bootrom console. The
bootrom will also log events to the event log.
Console command: command line
A modifying console command was issued through the Console Application. Console
commands that affect the state of the machine are tracked as events. For security reasons,
the following commands do not log their parameters:
ftpuser
,
ftppassword
, and
authkey
.
<urgent trace>
i.LON 600 User’s Guide 59