About the Syslog and SNMP Monitoring Guide
Monitoring a SafeNet Luna Network HSM is an operational requirement for mission critical systems. Thales makes monitoring available through two principle facilities: the system log (syslog) and simple network management protocol (SNMP). This document describes the syslog facility and provides details for what various messages mean, the probability of observing them and what action to take if observed. It goes on to describe the SNMP traps supported by SafeNet Luna Network HSM appliances.
This guide contains the following chapters:
The preface includes the following information about this document:
For information regarding the document status and revision history, see Document Information.
How to Use This Document
Thales prepared this document for two primary purposes. Firstly, the information within should provide sufficient guidance for an administrator to review log messages and determine a course of action for significant events. Secondly, the contents of this document should provide sufficient information for a developer to create or configure a service to scan log messages for significant events and automate action based on the message.
Caveat Lector
Thales reserves the right to revise log messages with each new release. Consequently, do not hard code pattern matching strings to parse log files. If you intend to match on specific text, create a solution that enables you to easily configure pattern strings.
Conventions & Style Used in this Document
This section describes the conventions and style for this document. This section is important to you, the reader, so that you understand the format herein.
The following conventions apply throughout the document.
>Use the same date and time in all examples unless the time is relevant to the example (e.g., a cron entry). For this version of the document, the date and time are: 2012 Feb 29 12:05:01.
>Use myLuna for the hostname of the Luna appliance.
>Use 192.168.0.xxx for example IP addresses. These values maintain consistency in the examples and ensures that no customer- or Thales-specific network configuration shows in an example.
>Use [1234] for the process identifier.
>Organize log messages into two distinct groups with the following headings: “Expected Log Messages” and “Unexpected Log Messages.”
>Use a table like this example to identify the facility keyword, software process and log file for each new component to be described:
| Facility Keyword | Software Process | Log File |
|---|---|---|
user
|
root
|
messages
|
>Use prose – not a bullets or tables – to describe log messages. Try to maintain the established introductory pre-amble, “This message indicates…” The document uses this structure so that parts can be extracted and provided electronically (e.g., via email) for customer assistance.
>Use greater-than/less-than signs to delimit variable text in log messages (e.g., <user name>).
