Raloy IP Functions for KVM - Manual (Page 33)

30
3-4.7 Event Log
Important events like a login failure or a firmware update are logged to a selection of logging destinations.
Each of those events belongs to an event group, which can be activated separately.
The common way to log events is to use the internal log list of the IP module. To show the log list, click on
“Event Log” on the “Maintenance” page. In the Event Log Settings you can choose how many log entries
are shown on each page. Furthermore, you can clear the log file here.
List logging enabled
The common way to log events is to use the internal log list of the IP module . To show the log list, click
on “Event Log” on the “Maintenance” page.
Since the IP module’s system memory is used to save all the information, the maximum number of
possible log list entries is restricted to 1.000 events. Every entry that exceeds this limit overrides the
oldest one, automatically.
Warning
If the reset button on the HTML frontend is used to restart the IP module, all
logging information is saved permanently and is available after the IP module
has been started. If the IP module loses power or a hard reset is performed, all
logging data will be lost. To avoid this, use one of the following log methods.
NFS Logging Enabled
Define a NFS server, where a directory or a static link have to be exported, to write all logging data to a
file that is located there. To write logging data from more than one IP module devices to only one NFS
share, you have to define a file name that is unique for each device. When you change the NFS settings
and press the button “Apply” , the NFS share will be mounted immediately. That means, the NFS share
and the NFS server must be filled with valid sources or you will get an error message.