Luna SNMP Trap Agent
Luna SNMP Trap Agent or lsta looks for significant events within the SafeNet Luna Network HSM appliance. When it sees a worthy event, lsta formats a trap notification and sends it to the configured user.
|
Facility Keyword |
Software Process |
Log File |
|---|---|---|
|
|
|
|
Expected Log Messages
The following log messages are normal and expected entries in the log files when lsta monitoring is enabled and started.
Agent Starting
2012 Feb 29 12:05:01 myLuna local5 info lsta: Starting Luna SNMP Trap Agent
This message indicates that lsta is starting. The agent does not run by default. Rather, an administrator must configure and start it from the Luna administrative shell.
Creating Named Pipe
2012 Feb 29 12:05:01 myLuna local5 info lsta: Created /home/admin/syslog.pipe as a named pipe
This message indicates that lsta created the necessary named pipe for interprocess communication with the syslog facility. This message results the first time lsta is started on a new SafeNet Luna Network HSM appliance.
Termination
2012 Feb 29 12:05:01 myLuna local5 info lsta: Luna SNMP Trap Agent terminated: Interrupted system call
This message indicates that lsta caught a SIGINT, SIGABRT or SIGTERM signal and terminated.
Unexpected Log Messages
Under normal circumstances, you should not see any of these log messages. If you do so, please contact Thales Group Technical Support to report the message and seek guidance on what to do next.
SNMP Data Logged
2012 Feb 29 12:05:01 myLuna local5 info lsta: fanAttentionNotify for [myLUT:192.168.0.58 / messages / 2012 Feb 29 12:05:00 / ipmievd / 1]
When trace level debugging is enabled, this message records the SNMP trap notification data sent by lsta. Trace level debugging is off in Luna SA so this message is unexpected.
Missing SNMP Parameters
2012 Feb 29 12:05:01 myLuna local5 err lsta: Error opening /usr/local/share/snmp/snmp.conf
This message indicates that the SNMP parameters needed by lsta are missing. A likely root cause is that an administrator has not yet set the parameters via the lunash:>sysconf snmp trap set command.
snmptrap Failed
2012 Feb 29 12:05:01 myLuna local5 err lsta: snmptrap failed: 256
This message indicates that lsta was unable to send a formatted trap notification to the intended user. A possible root cause is an out-of-date SAFENET-APPLIANCE-MIB on the appliance or a parameter defined by the lunash:>sysconf snmp trap set command in error (e.g., invalid IP address).
Interprocess Communication Failures
2012 Feb 29 12:05:01 myLuna local5 err lsta: Pipe file disappeared, stopping lsta 2012 Feb 29 12:05:01 myLuna local5 err lsta: Cannot read from pipe /home/admin/syslog.pipe: 5 2012 Feb 29 12:05:01 myLuna local5 err lsta: Will not overwrite /home/admin/syslog.pipe 2012 Feb 29 12:05:01 myLuna local5 err lsta: Cannot mknod /home/admin/syslog.pipe: 13
These messages indicate failure with the named pipe used for interprocess communication with the syslog facility. The first two messages represent failures during lsta operation; the last two on start up.
Unknown Sub-system
2012 Feb 29 12:05:01 myLuna local5 err lsta: Unknown/unsupported sub-system: xxx
This message indicates a programming error. lsta should have logic for all sub-systems defined in the SAFENET-APPLIANCE-MIB.
Log Record Parsing
2012 Feb 29 12:05:01 myLuna local5 info lsta: Could not parse log record: <log record>
This message indicates that lsta could not properly parse a log record for the fields expected. <log record> is the log message received by lsta from rsyslogd.
Could Not Close Parameters File
2012 Feb 29 12:05:01 myLuna local5 err lsta: Error closing /usr/local/share/snmp/snmp.conf
This message indicates that lsta could not properly close the SNMP parameters file.
Could Not Close Pipe
2012 Feb 29 12:05:01 myLuna local5 err lsta: Error closing /home/admin/syslog.pipe
This message indicates that lsta could not properly close the named pipe used by rsyslog to communicate log records.
chdir Failed
2012 Feb 29 12:05:01 myLuna local5 err lsta: Could not chdir
This message indicates that lsta could not properly change working directories.
umask Failed
2012 Feb 29 12:05:01 myLuna local5 err lsta: Could not umask
This message indicates that lsta could not properly determine the umask file settings.
Could Not Open stdin
2012 Feb 29 12:05:01 myLuna local5 err lsta: Error opening stdin
This message indicates that lsta could not properly open standard input.
Could Not Open stderr
2012 Feb 29 12:05:01 myLuna local5 err lsta: Error opening stderr
This message indicates that lsta could not properly open standard error.
