Menu Options
Event Log
1
1a
1b
2
Important events like a login failure or a firmware update are logged to a selection of logging destinations (see Figure
1.Event Log Targets
To log events, you may use the internal log list of the RIPM. To show the log list, click on “Event Log” on the “Maintenance” page. Since the RIPM’s system memory is used to save all the information, the maximum number of
Warning: If the reset button on the HTML
is performed, all logging data will be lost. To avoid this, use one of the log methods described below.
1a. Network File System (NFS) Logging Enabled
Define a NFS server to which directories and static links must be exported; all logging data will then be written to a file in that location. To write logging data from multiple RIPM devices to only one NFS share, you must define a file name that is unique for each device. When you change the NFS settings and press the “Apply” button, 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.
Note: In contrast to the internal log file on the RIPM, the size of the NFS log file is not limited. Every log event will be appended to the end of the file so that it grows continuously. You may need to delete it or move away events logged within the file from time to time.
67