Show the Table of Contents
Administration & Maintenance - SNMP
For Luna HSM 5.x, SafeNet supports Simple Network Management Protocol (SNMP v3) for remote monitoring of conditions on a local HSM that might require administrative attention.
We provide the following MIBs (management information base):
|CHRYSALIS-UTSP-MIB.mib||defines SNMP access to information about the Luna appliance|
|SAFENET-HSM-MIB.mib||defines SNMP access to information about the Luna HSM|
|SAFENET-GLOBAL-MIB.mib||must be found in your system path so that symbols can be resolved|
|SAFENET-APPLIANCE-MIB.mib||reports Software Version of Luna SA appliance (this MIB exists inside the appliance, only)|
Copy all MIBs in <luna client install dir > to the MIB directory on your system.
For Luna SA, the host is the appliance, so all the above MIBs are in the appliance, to support SNMP.
We find that most customers choosing to use SNMP already have an SNMP infrastructure in place. Therefore, we provide a subagent that you can install on your managed workstations, and which can point to your agent via the socket created by the agent. This applies to Luna G5 and Luna PCI-E - for Luna SA, the subagent is already on the appliance.
The Luna SNMP subagent (luna-snmp) is an AgentX SNMP module that extends an existing SNMP agent with support for SafeNet HSM monitoring. It is an optional component of the Luna client installation. The subagent has been tested against net-snmp, but should work with any SNMP agent that supports the AgentX protocol.
After selecting one or more products from the main LunaClient installation menu, you are presented with a list of optional components, including the Luna SNMP subagent. It is not selected by default, but can be installed with any product except the Luna SA client installed in isolation.
After the Luna client is installed, complete the following steps to configure the SNMP subagent:
Normally the agent is started first. However, the subagent periodically attempts to connect to the agent until it is successful. The defaults controlling this behavior are listed below. They can be overridden by changing the appropriate entries in luna-snmp.conf.
|agentXSocket [<transport-specifier>:]<transport-address>[,...]||Defines the address to which the subagent should connect. The default on
UNIX-based systems is the Unix Domain socket "/var/agentx/master".
Another common alternative is tcp:localhost:705.
See the section LISTENING ADDRESSES in the snmpd manual page for more information about the format of addresses (http://www.net-snmp.org/docs/man/snmpd.html).
|The default, for Linux, is "/var/agentx/master".
In the file, you can choose to un-comment "tcp:localhost:705" which is most commonly used with Windows.
|agentXPingInterval <NUM>||Makes the subagent try to reconnect every <NUM> seconds to the master if it ever becomes (or starts) disconnected.||15|
|agentXTimeout <NUM>||Defines the timeout period (NUM seconds) for an AgentX request.||1|
|agentXRetries <NUM>||Defines the number of retries for an AgentX request.||5|
SNMP Operation and Limitations
The SafeNet CHRYSALIS-UTSB MIB
Show the Table of Contents