tmnxTlsFailureReason
TIMETRA-TLS-MIB ·
.1.3.6.1.4.1.6527.3.1.2.107.10.11
Object
scalar Enumeration
The value of the object tmnxTlsFailureReason indicates the reason
for the TLS connection failure:
lackOfResources - Out of memory condition encountered during creation
of the TLS connection,
profileNotOperational - server or client TLS profile used by the TLS connec-
tion is not operational - might be administratively
down, have not got any operational cert profile or
trust anchor,
invalidCertificate - certificate received during the TLS handshake from
a peer can not be verified. Exact reason can be found
in tmnxAppPkiCertVerificationFailed notification,
handshakeFailure - TLS handshake failed because there was no common
cipher, TLS version mismatch or peer rejected our
certificate,
badPacket - An unexpected or corrupted packet was received,
renegotiationFailure - A failure occurred during a renegotiation. The reason
may be one of the reasons mentioned for
handshakeFailure or profileNotOperational.
Context
- MIB
- TIMETRA-TLS-MIB
- OID
.1.3.6.1.4.1.6527.3.1.2.107.10.11- Type
- scalar
- Access
- notifyonly
- Status
- current
- Parent
- tmnxTlsNotifyObjects
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-TLS-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-TLS-MIB::tmnxTlsFailureReason.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-TLS-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-TLS-MIB::tmnxTlsFailureReason'
Syntax
Enumeration
Values & Constraints
Enumerated Values
0 | lackOfResources |
1 | profileNotOperational |
2 | invalidCertificate |
3 | handshakeFailure |
4 | badPacket |
5 | renegotiationFailure |
Conformance
Member of