Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsdlswCircuitState",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disconnected",
"(",
"1",
")",
",",
"circuitStart",
"(",
"2",
")",
",",
"resolvePending",
"(",
"3",
")",
",",
"circuitPending",
"(",
"4",
")",
",",
"circuitEstablished",
"(",
"5",
")",
",",
"connectPending",
"(",
"6",
")",
",",
"contactPending",
"(",
"7",
")",
",",
"connected",
"(",
"8",
")",
",",
"disconnectPending",
"(",
"9",
")",
",",
"haltPending",
"(",
"10",
")",
",",
"haltPendingNoack",
"(",
"11",
")",
",",
"circuitRestart",
"(",
"12",
")",
",",
"restartPending",
"(",
"13",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The current state of this circuit. The agent, implementation specific, may choose to keep entries for some period of time after circuit disconnect, so the manager can gather the time and cause of disconnection. While all of the specified values may be returned from a GET operation, the only SETable value is `disconnectPending'. When this value is set, DLSw should perform the appropriate action given its previous state (e.g., send HALT_DL if the state was `connected') to bring the circuit down to the `disconnected' state. Both the partner DLSw and local end station(s) should be notified as appropriate. This MIB provides no facility to re-establish a disconnected circuit, because in DLSw this should be an end station-driven function.\"",
"::=",
"{",
"fsdlswCircuitEntry",
"14",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disconnected",
1
],
[
"circuitStart",
2
],
[
"resolvePending",
3
],
[
"circuitPending",
4
],
[
"circuitEstablished",
5
],
[
"connectPending",
6
],
[
"contactPending",
7
],
[
"connected",
8
],
[
"disconnectPending",
9
],
[
"haltPending",
10
],
[
"haltPendingNoack",
11
],
[
"circuitRestart",
12
],
[
"restartPending",
13
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The current state of this circuit. The agent, implementation specific, may choose to keep entries for some period of time after circuit disconnect, so the manager can gather the time and cause of disconnection. While all of the specified values may be returned from a GET operation, the only SETable value is `disconnectPending'. When this value is set, DLSw should perform the appropriate action given its previous state (e.g., send HALT_DL if the state was `connected') to bring the circuit down to the `disconnected' state. Both the partner DLSw and local end station(s) should be notified as appropriate. This MIB provides no facility to re-establish a disconnected circuit, because in DLSw this should be an end station-driven function."
],
null,
null,
null,
null
]
}