The SafeNet Chrysalis-UTSP MIB
Note: The Chrysalis MIB is the SafeNet MIB for all SafeNet HSM products - the Chrysalis name is retained for historical continuity.
To illustrate accessing data, the command "snmpwalk -v 3 -u admin -l authPriv -a SHA1 -A 12345678 -x AES -X 87654321 myLuna19 private" produced this output:
•CHRYSALIS-UTSP-MIB::hsmOperationRequests.0 = Counter64: 3858380
•CHRYSALIS-UTSP-MIB::hsmOperationErrors.0 = Counter64: 385838
•CHRYSALIS-UTSP-MIB::hsmCriticalEvents.0 = Counter64: 0
•CHRYSALIS-UTSP-MIB::hsmNonCriticalEvents.0 = Counter64: 5
•CHRYSALIS-UTSP-MIB::ntlsOperStatus.0 = INTEGER: up(1)
•CHRYSALIS-UTSP-MIB::ntlsConnectedClients.0 = Gauge32: 0
•CHRYSALIS-UTSP-MIB::ntlsLinks.0 = Gauge32: 0
•CHRYSALIS-UTSP-MIB::ntlsSuccessfulClientConnections.0 = Counter64: 16571615927115620
•CHRYSALIS-UTSP-MIB::ntlsFailedClientConnections.0 = Counter64: 1657161592711562
The various counts are recorded since the last restart.
Item | Description |
---|---|
hsmOperationRequests | The total number of HSM operations that have been requested. |
hsmOperationErrors | The total number of HSM operations that have been requested, that have resulted in errors. |
hsmCriticalEvents | The total number of critical HSM events that have been detected (Tamper, Zeroization, SO creation, or Audit role creation) |
hsmNonCriticalEvents | The total number of NON-critical HSM events that have been detected (any that are not among the critical list, above). |
ntlsOperStatus | The current operational status of the NTL service, where the options are: 1 = up, 2 = not running, and 3 = status cannot be determined. |
ntlsConnectedClients | The current number of connected clients using NTLS. |
ntlsLinks | The current number of links in NTLS - can be multiple per client, depending on processes. |
ntlsSuccessfulClientConnections | The total number of successful client connections. |
ntlsFailedClientConnections | The total number of UNsuccessful client connections. |