Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"remoteProtocolVlanRowStatus",
"OBJECT-TYPE",
"SYNTAX",
"RowStatus",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The status of this conceptual row entry. This object is issued to manage the creation and deletion of conceptual rows. The status column has six defined values: - 'active', which indicates that the conceptual row is available for use by the managed device; - 'notInService', which indicates that the conceptual row exists in the agent, but it is unavailable for use by the managed device (see NOTE below); - 'notReady', which indicates that the conceptual row exists in the agent, but it is missing information necessary in order to be available for use by the managed device; - 'createAndGo', which is supplied by a management station intending to create a new instance of a conceptual row and to have its status automatically set to be active and then to make it available for use by the managed device; - 'createAndWait', which is supplied by a management station intending to create a new instance of a conceptual row (but not to make it available for use by the managed device); and, - 'destroy', which is supplied by a management station intending to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except 'notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: 'notReady', 'notInService' and 'active'. That is, when queried, an existing conceptual row has only three states: it is available for use by the managed device (the status column has value 'active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value 'notInService'); or, it is not available for use by the managed device, and an attempt to make it so would be failed because the agent has insufficient information (the state column has value 'notReady'). For a detailed description of this object, please refer to SNMPv2-TC MIB.\"",
"::=",
"{",
"remoteProtocolVlanEntry",
"5",
"}"
],
"syntax_tree": [
[
"row",
"RowStatus"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The status of this conceptual row entry. This object is issued to manage the creation and deletion of conceptual rows. The status column has six defined values: - 'active', which indicates that the conceptual row is available for use by the managed device; - 'notInService', which indicates that the conceptual row exists in the agent, but it is unavailable for use by the managed device (see NOTE below); - 'notReady', which indicates that the conceptual row exists in the agent, but it is missing information necessary in order to be available for use by the managed device; - 'createAndGo', which is supplied by a management station intending to create a new instance of a conceptual row and to have its status automatically set to be active and then to make it available for use by the managed device; - 'createAndWait', which is supplied by a management station intending to create a new instance of a conceptual row (but not to make it available for use by the managed device); and, - 'destroy', which is supplied by a management station intending to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except 'notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: 'notReady', 'notInService' and 'active'. That is, when queried, an existing conceptual row has only three states: it is available for use by the managed device (the status column has value 'active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value 'notInService'); or, it is not available for use by the managed device, and an attempt to make it so would be failed because the agent has insufficient information (the state column has value 'notReady'). For a detailed description of this object, please refer to SNMPv2-TC MIB."
],
null,
null,
null,
null
]
}