Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sslResponseStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"noAttempt",
"(",
"1",
")",
",",
"queued",
"(",
"2",
")",
",",
"pending",
"(",
"3",
")",
",",
"responded",
"(",
"4",
")",
",",
"noResponse",
"(",
"5",
")",
"}",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\" <Definition> This object provides status about the interchange between the SSM and SSL for sslCommand and sslResponse. noAttempt: the SSM has made no attempt or the sslNumber is zero or the sslCommandFrequency is disabled queued: an SSLCommand is valid but waiting for transmission based on sslCommandFrequency pending: an SSLCommand has been transmitted but a response has not been received responded1: the value in sslResponse is for the command in sslCommand responded2: the value in sslResponse is for a command other than the one in sslCommand noResponse: there has been no response from sslNumber When sslNumber > 0 and < 63, all responses from sslNumber shall be placed in sslResponse without regard to sslCommandFrequency. When the TMC writes to sslCommand, the SSM sets this status to 'queued.' When the SSM transmits the content of sslCommand it sets this status to 'pending.' If a response is received the SSM sets this status to 'responded1.' If no response is received, the SSM sets this status to 'noResponse.' <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.8.1.9\"",
"DEFVAL",
"{",
"noAttempt",
"}",
"::=",
"{",
"sslMsgRoutedEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"noAttempt",
1
],
[
"queued",
2
],
[
"pending",
3
],
[
"responded",
4
],
[
"noResponse",
5
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This object provides status about the interchange between the SSM and SSL for sslCommand and sslResponse. noAttempt: the SSM has made no attempt or the sslNumber is zero or the sslCommandFrequency is disabled queued: an SSLCommand is valid but waiting for transmission based on sslCommandFrequency pending: an SSLCommand has been transmitted but a response has not been received responded1: the value in sslResponse is for the command in sslCommand responded2: the value in sslResponse is for a command other than the one in sslCommand noResponse: there has been no response from sslNumber When sslNumber > 0 and < 63, all responses from sslNumber shall be placed in sslResponse without regard to sslCommandFrequency. When the TMC writes to sslCommand, the SSM sets this status to 'queued.' When the SSM transmits the content of sslCommand it sets this status to 'pending.' If a response is received the SSM sets this status to 'responded1.' If no response is received, the SSM sets this status to 'noResponse.' <Object Identifier> 1.3.6.1.4.1.1206.4.2.10.8.1.9"
],
null,
null,
null,
[
"DEFVAL",
"noAttempt"
]
]
}