C2G 52064 Single Port KVM over IP - Manual (Page 76)

Single Port KVM over IP
74 / 88
Warning
If the reset button on the HTML frontend is used to restart the IP-KVM
switch, all logging information is saved permanently and is available
after the IP-KVM switch has been started. If the IP-KVM switch 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-KVM switch 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.
SMTP Logging enabled
With this option, the IP-KVM switch 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 a SMTP server, that has to be reachable from
the IP-KVM switch device and that needs no authentication at all
(:).
SNMP Logging enabled
If this is activated, the IP-KVM switch sends a 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 an own trap class that
consists of several fields with detailed information about the occurred event.
To receive this SNMP traps, any SNMP trap listener may be used.
Here is a example of all gerenated event and its event group.
Device succesfully started device
Board Reset performed by user... device
Firmware upload failed. device
No firmware file uploaded. device
Uploaded firmware file discarded. device
Firmware validation failed. device
Firmware file uploaded by user... device
Firmware updated by user... device
Internal log file cleared by user... device