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.
Parsed from file DLSW-MIB.mib
Module: DLSW-MIB
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.
dlswCircuitState 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)
}
ACCESS read-write
STATUS mandatory
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."
View at oid-info.com
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.
Parsed from file rfc2024-Data-Link-Switches.mib.txt
Company: None
Module: DLSW-MIB
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.
dlswCircuitState 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-write 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." ::= { dlswCircuitEntry 17 }
dlswCircuitState 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) } ACCESS read-write STATUS mandatory 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." ::= { dlswCircuitEntry 17 }
Automatically extracted from Cisco SNMP v1 MIBs
dlswCircuitState 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-write 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." ::= { dlswCircuitEntry 17 }
dlswCircuitState 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-write 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." ::= { dlswCircuitEntry 17 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.46.1.5.2.1.1 | dlswCircuitS1Mac | 0 | 0 | The MAC Address of End Station 1 (S1) used for this circuit. |
| 1.3.6.1.2.1.46.1.5.2.1.2 | dlswCircuitS1Sap | 0 | 0 | The SAP at End Station 1 (S1) used for this circuit. |
| 1.3.6.1.2.1.46.1.5.2.1.3 | dlswCircuitS1IfIndex | 0 | 0 | The ifEntry index of the local interface through which S1 can be reached. |
| 1.3.6.1.2.1.46.1.5.2.1.4 | dlswCircuitS1DlcType | 0 | 0 | The DLC protocol in use between the DLSw node and S1. |
| 1.3.6.1.2.1.46.1.5.2.1.5 | dlswCircuitS1RouteInfo | 0 | 0 | If source-route bridging is in use between the DLSw node and S1, this is the routing information field describing the path betwee… |
| 1.3.6.1.2.1.46.1.5.2.1.6 | dlswCircuitS1CircuitId | 0 | 0 | The Circuit ID assigned by this DLSw node to this circuit. The first four octets are the DLC port Id, and the second four octets … |
| 1.3.6.1.2.1.46.1.5.2.1.7 | dlswCircuitS1Dlc | 0 | 0 | Points to a conceptual row of the underlying DLC MIB, which could either be the standard MIBs (e.g., the SDLC), or an enterprise-… |
| 1.3.6.1.2.1.46.1.5.2.1.8 | dlswCircuitS2Mac | 0 | 0 | The MAC Address of End Station 2 (S2) used for this circuit. |
| 1.3.6.1.2.1.46.1.5.2.1.9 | dlswCircuitS2Sap | 0 | 0 | The SAP at End Station 2 (S2) used for this circuit. |
| 1.3.6.1.2.1.46.1.5.2.1.10 | dlswCircuitS2Location | 0 | 0 | The location of End Station 2 (S2). If the location of End Station 2 is local, the interface information will be available in the… |
| 1.3.6.1.2.1.46.1.5.2.1.11 | dlswCircuitS2TDomain | 0 | 0 | If the location of End Station 2 is remote, this value is the transport domain of the transport protocol the circuit is running ov… |
| 1.3.6.1.2.1.46.1.5.2.1.12 | dlswCircuitS2TAddress | 0 | 0 | If the location of End Station 2 is remote, this object contains the address of the partner DLSw, else it will be an OCTET STRING… |
| 1.3.6.1.2.1.46.1.5.2.1.13 | dlswCircuitS2CircuitId | 0 | 0 | The Circuit ID assigned to this circuit by the partner DLSw node. The first four octets are the DLC port Id, and the second four… |
| 1.3.6.1.2.1.46.1.5.2.1.14 | dlswCircuitOrigin | 0 | 0 | This object specifies which of the two end stations initiated the establishment of this circuit. |
| 1.3.6.1.2.1.46.1.5.2.1.15 | dlswCircuitEntryTime | 0 | 0 | The amount of time (in hundredths of a second) since this circuit table conceptual row was created. |
| 1.3.6.1.2.1.46.1.5.2.1.16 | dlswCircuitStateTime | 0 | 0 | The amount of time (in hundredths of a second) since this circuit entered the current state. |
| 1.3.6.1.2.1.46.1.5.2.1.18 | dlswCircuitPriority | 0 | 0 | The transmission priority of this circuit as understood by this DLSw node. This value is determined by the two DLSw nodes at cir… |
| 1.3.6.1.2.1.46.1.5.2.1.19 | dlswCircuitFCSendGrantedUnits | 0 | 0 | The number of paced SSP messages that this DLSw is currently authorized to send on this circuit before it must stop and wait for … |
| 1.3.6.1.2.1.46.1.5.2.1.20 | dlswCircuitFCSendCurrentWndw | 0 | 0 | The current window size that this DLSw is using in its role as a data sender. This is the value by which this DLSw would increas… |
| 1.3.6.1.2.1.46.1.5.2.1.21 | dlswCircuitFCRecvGrantedUnits | 0 | 0 | The current number of paced SSP messages that this DLSw has authorized the partner DLSw to send on this circuit before the partne… |
| 1.3.6.1.2.1.46.1.5.2.1.22 | dlswCircuitFCRecvCurrentWndw | 0 | 0 | The current window size that this DLSw is using in its role as a data receiver. This is the number of additional paced SSP messa… |
| 1.3.6.1.2.1.46.1.5.2.1.23 | dlswCircuitFCLargestRecvGranted | 0 | 0 | The largest receive window size granted by this DLSw during the current activation of this circuit. This is not the largest numb… |
| 1.3.6.1.2.1.46.1.5.2.1.24 | dlswCircuitFCLargestSendGranted | 0 | 0 | The largest send (with respect to this DLSw) window size granted by the partner DLSw during the current activation of this circui… |
| 1.3.6.1.2.1.46.1.5.2.1.25 | dlswCircuitFCHalveWndwSents | 0 | 0 | The number of Halve Window operations this DLSw has sent on this circuit, in its role as a data receiver. The value zero should b… |
| 1.3.6.1.2.1.46.1.5.2.1.26 | dlswCircuitFCResetOpSents | 0 | 0 | The number of Reset Window operations this DLSw has sent on this circuit, in its role as a data receiver. The value zero should b… |
| 1.3.6.1.2.1.46.1.5.2.1.27 | dlswCircuitFCHalveWndwRcvds | 0 | 0 | The number of Halve Window operations this DLSw has received on this circuit, in its role as a data sender. The value zero should… |
| 1.3.6.1.2.1.46.1.5.2.1.28 | dlswCircuitFCResetOpRcvds | 0 | 0 | The number of Reset Window operations this DLSw has received on this circuit, in its role as a data sender. The value zero should… |
| 1.3.6.1.2.1.46.1.5.2.1.29 | dlswCircuitDiscReasonLocal | 0 | 0 | The reason why this circuit was last disconnected, as seen by this DLSw node. This object is present only if the agent keeps circ… |
| 1.3.6.1.2.1.46.1.5.2.1.30 | dlswCircuitDiscReasonRemote | 0 | 0 | The generic reason code why this circuit was last disconnected, as reported by the DLSw partner in a HALT_DL or HALT_DL_NOACK. I… |
| 1.3.6.1.2.1.46.1.5.2.1.31 | dlswCircuitDiscReasonRemoteData | 0 | 0 | Implementation-specific data reported by the DLSw partner in a HALT_DL or HALT_DL_NOACK, to help specify how and why this circuit… |