Section 5

IP Access Configuration & Operation

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.

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 CAT-32 IP. To show the log list, click on Event Log on the Maintenance page.

Since the CAT-32 IP’s system memory is used to save all the information, the maximum number of possible log list entries is restricted to 1000 events. Every entry that exceeds this limit overrides the oldest one.

Note: If the reset button on the HTML front end is used to restart the KVM over IP module all logging information is saved permanently and is available after the module has been started. If the KVM over IP module loses power or a hard reset is performed, all logging data will be lost. To avoid this, use one of the log methods described below.

NFS Logging enabled

Defines an NFS server to write all logging data to a file that is located there. To write logging data from multiple CAT-32 IP units 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 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.

Section 5

IP Access Configuration & Operation

SMTP Logging enabled

With this option, the CAT-32 IP is able to send Emails to an address given by the Email address text field in the Event Log Settings. These mails contain the same description strings as the internal log file and the mail subject is filled with the event group of the occurred log event. In order to use this log destination you have to specify an SMTP server that has to be reachable from the CAT-32 IP and that needs no authentication at all (<serverip>:<port>).

SNMP Logging enabled

If this is activated, the CAT-32 IP sends an SNMP trap to a specified destination IP address every time a log event occurs. If the receiver requires a community string, you can set it in the appropriate text field. Most of the event traps only contain one descriptive string with all information about the log event. Only authentication and host power events have a trap class that consists of several fields with detailed information about the occurred event. To receive these SNMP traps, any SNMP trap listener may be used.

Warning In contrast to the internal log file on the CAT-32 IP, the size of the NFS log file is not limited. Every log event will be appended to the end of the file so it grows continuously, so you may have to delete it or move it from time to time.

60

61