Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tmnxTlsFailureReason",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"lackOfResources",
"(",
"0",
")",
",",
"profileNotOperational",
"(",
"1",
")",
",",
"invalidCertificate",
"(",
"2",
")",
",",
"handshakeFailure",
"(",
"3",
")",
",",
"badPacket",
"(",
"4",
")",
",",
"renegotiationFailure",
"(",
"5",
")",
"}",
"MAX-ACCESS",
"accessible-for-notify",
"STATUS",
"current",
"DESCRIPTION",
"\"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.\"",
"::=",
"{",
"tmnxTlsNotifyObjects",
"11",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"lackOfResources",
0
],
[
"profileNotOperational",
1
],
[
"invalidCertificate",
2
],
[
"handshakeFailure",
3
],
[
"badPacket",
4
],
[
"renegotiationFailure",
5
]
]
]
],
null,
[
"MaxAccessPart",
"accessible-for-notify"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"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."
],
null,
null,
null,
null
]
}