This object reports the current status of
the circuit.
An existing instance of this object can only
be set to startClear, startPvcResetting, or
invalid. An instance with the value calling
or open can only be set to startClear and
that action will start clearing the circuit.
An instance with the value PVC can only be
set to startPvcResetting or invalid and that
action resets the PVC or deletes the circuit
respectively. The values startClear or
startPvcResetting will never be returned by
an agent. An attempt to set the status of
an existing instance to a value other than
one of these values will result in an error.
A non-existing instance can be set to PVC to
create a PVC if the implementation supports
dynamic creation of PVCs. Some
implementations may only allow creation and
deletion of PVCs if the interface is down.
Since the instance identifier will supply
the PLE index and the channel number,
setting this object alone supplies
sufficient information to create the
instance. All the DEFVAL clauses for the
other objects of this table are appropriate
for creating a PVC; PLEs creating entries
for placed or accepted calls will use values
appropriate for the call rather than the
value of the DEFVAL clause. Two managers
trying to create the same PVC can determine
from the return code which manager succeeded
and which failed (the failing manager fails
because it can not set a value of PVC for an
existing object).
An entry in the closed or invalid state may
be deleted or reused at the agent's
convence. If the entry is kept in the
closed state, the values of the parameters
associated with the entry must be correct.
Closed implies the values in the circuit
table are correct.
The value of invalid indicates the other
values in the table are invalid. Many
agents may never return a value of invalid
because they dynamically allocate and free
unused table entries. An agent for a
statically configured systems can return
invalid to indicate the entry has not yet
been used so the counters contain no
information.
x25CircuitStatus OBJECT-TYPE
SYNTAX INTEGER { -- state table states
invalid (1),
closed (2), -- (p1)
calling (3), -- (p2,p3,p5)
open (4), -- (p4)
clearing (5), -- (p6,p7)
pvc (6),
pvcResetting (7),
startClear (8), -- Close cmd
startPvcResetting (9), -- Reset cmd
other (10)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object reports the current status of
the circuit.
An existing instance of this object can only
be set to startClear, startPvcResetting, or
invalid. An instance with the value calling
or open can only be set to startClear and
that action will start clearing the circuit.
An instance with the value PVC can only be
set to startPvcResetting or invalid and that
action resets the PVC or deletes the circuit
respectively. The values startClear or
startPvcResetting will never be returned by
an agent. An attempt to set the status of
an existing instance to a value other than
one of these values will result in an error.
A non-existing instance can be set to PVC to
create a PVC if the implementation supports
dynamic creation of PVCs. Some
implementations may only allow creation and
deletion of PVCs if the interface is down.
Since the instance identifier will supply
the PLE index and the channel number,
setting this object alone supplies
sufficient information to create the
instance. All the DEFVAL clauses for the
other objects of this table are appropriate
for creating a PVC; PLEs creating entries
for placed or accepted calls will use values
appropriate for the call rather than the
value of the DEFVAL clause. Two managers
trying to create the same PVC can determine
from the return code which manager succeeded
and which failed (the failing manager fails
because it can not set a value of PVC for an
existing object).
An entry in the closed or invalid state may
be deleted or reused at the agents
convence. If the entry is kept in the
closed state, the values of the parameters
associated with the entry must be correct.
Closed implies the values in the circuit
table are correct.
The value of invalid indicates the other
values in the table are invalid. Many
agents may never return a value of invalid
because they dynamically allocate and free
unused table entries. An agent for a
statically configured systems can return
invalid to indicate the entry has not yet
been used so the counters contain no
information."
REFERENCE "See ISO 8208,
table 33 for (p<n>) state table"
View at oid-info.com
This object reports the current status of
the circuit.
An existing instance of this object can only
be set to startClear, startPvcResetting, or
invalid. An instance with the value calling
or open can only be set to startClear and
that action will start clearing the circuit.
An instance with the value PVC can only be
set to startPvcResetting or invalid and that
action resets the PVC or deletes the circuit
respectively. The values startClear or
startPvcResetting will never be returned by
an agent. An attempt to set the status of
an existing instance to a value other than
one of these values will result in an error.
A non-existing instance can be set to PVC to
create a PVC if the implementation supports
dynamic creation of PVCs. Some
implementations may only allow creation and
deletion of PVCs if the interface is down.
Since the instance identifier will supply
the PLE index and the channel number,
setting this object alone supplies
sufficient information to create the
instance. All the DEFVAL clauses for the
other objects of this table are appropriate
for creating a PVC; PLEs creating entries
for placed or accepted calls will use values
appropriate for the call rather than the
value of the DEFVAL clause. Two managers
trying to create the same PVC can determine
from the return code which manager succeeded
and which failed (the failing manager fails
because it can not set a value of PVC for an
existing object).
An entry in the closed or invalid state may
be deleted or reused at the agent's
convence. If the entry is kept in the
closed state, the values of the parameters
associated with the entry must be correct.
Closed implies the values in the circuit
table are correct.
The value of invalid indicates the other
values in the table are invalid. Many
agents may never return a value of invalid
because they dynamically allocate and free
unused table entries. An agent for a
statically configured systems can return
invalid to indicate the entry has not yet
been used so the counters contain no
information.
Agent variations:
DESCRIPTION
not settable
Parsed from file it-router-12.mib.txt
Company: None
Module: IT-ROUTER-12
This object reports the current status of
the circuit.
An existing instance of this object can only
be set to startClear, startPvcResetting, or
invalid. An instance with the value calling
or open can only be set to startClear and
that action will start clearing the circuit.
An instance with the value PVC can only be
set to startPvcResetting or invalid and that
action resets the PVC or deletes the circuit
respectively. The values startClear or
startPvcResetting will never be returned by
an agent. An attempt to set the status of
an existing instance to a value other than
one of these values will result in an error.
A non-existing instance can be set to PVC to
create a PVC if the implementation supports
dynamic creation of PVCs. Some
implementations may only allow creation and
deletion of PVCs if the interface is down.
Since the instance identifier will supply
the PLE index and the channel number,
setting this object alone supplies
sufficient information to create the
instance. All the DEFVAL clauses for the
other objects of this table are appropriate
for creating a PVC; PLEs creating entries
for placed or accepted calls will use values
appropriate for the call rather than the
value of the DEFVAL clause. Two managers
trying to create the same PVC can determine
from the return code which manager succeeded
and which failed (the failing manager fails
because it can not set a value of PVC for an
existing object).
An entry in the closed or invalid state may
be deleted or reused at the agent's
convence. If the entry is kept in the
closed state, the values of the parameters
associated with the entry must be correct.
Closed implies the values in the circuit
table are correct.
The value of invalid indicates the other
values in the table are invalid. Many
agents may never return a value of invalid
because they dynamically allocate and free
unused table entries. An agent for a
statically configured systems can return
invalid to indicate the entry has not yet
been used so the counters contain no
information.
Parsed from file ITOUCHHUB.mib
Module: ITOUCHHUB
x25CircuitStatus OBJECT-TYPE SYNTAX INTEGER { invalid (1), closed (2), calling (3), open (4), clearing (5), pvc (6), pvcResetting (7), startClear (8), startPvcResetting (9), other (10) } ACCESS read-write STATUS mandatory DESCRIPTION "This object reports the current status of the circuit. An existing instance of this object can only be set to startClear, startPvcResetting, or invalid. An instance with the value calling or open can only be set to startClear and that action will start clearing the circuit. An instance with the value PVC can only be set to startPvcResetting or invalid and that action resets the PVC or deletes the circuit respectively. The values startClear or startPvcResetting will never be returned by an agent. An attempt to set the status of an existing instance to a value other than one of these values will result in an error. A non-existing instance can be set to PVC to create a PVC if the implementation supports dynamic creation of PVCs. Some implementations may only allow creation and deletion of PVCs if the interface is down. Since the instance identifier will supply the PLE index and the channel number, setting this object alone supplies sufficient information to create the instance. All the DEFVAL clauses for the other objects of this table are appropriate for creating a PVC; PLEs creating entries for placed or accepted calls will use values appropriate for the call rather than the value of the DEFVAL clause. Two managers trying to create the same PVC can determine from the return code which manager succeeded and which failed (the failing manager fails because it can not set a value of PVC for an existing object). An entry in the closed or invalid state may be deleted or reused at the agent's convence. If the entry is kept in the closed state, the values of the parameters associated with the entry must be correct. Closed implies the values in the circuit table are correct. The value of invalid indicates the other values in the table are invalid. Many agents may never return a value of invalid because they dynamically allocate and free unused table entries. An agent for a statically configured systems can return invalid to indicate the entry has not yet been used so the counters contain no information." REFERENCE "See ISO 8208, table 33 for (p
) state table" ::= { x25CircuitEntry 3 }
Automatically extracted from RFC1382
x25CircuitStatus OBJECT-TYPE SYNTAX INTEGER { invalid (1), closed (2), calling (3), open (4), clearing (5), pvc (6), pvcResetting (7), startClear (8), startPvcResetting (9), other (10) } ACCESS read-only STATUS mandatory DESCRIPTION "This object reports the current status of the circuit. An existing instance of this object can only be set to startClear, startPvcResetting, or invalid. An instance with the value calling or open can only be set to startClear and that action will start clearing the circuit. An instance with the value PVC can only be set to startPvcResetting or invalid and that action resets the PVC or deletes the circuit respectively. The values startClear or startPvcResetting will never be returned by an agent. An attempt to set the status of an existing instance to a value other than one of these values will result in an error. A non-existing instance can be set to PVC to create a PVC if the implementation supports dynamic creation of PVCs. Some implementations may only allow creation and deletion of PVCs if the interface is down. Since the instance identifier will supply the PLE index and the channel number, setting this object alone supplies sufficient information to create the instance. All the DEFVAL clauses for the other objects of this table are appropriate for creating a PVC; PLEs creating entries for placed or accepted calls will use values appropriate for the call rather than the value of the DEFVAL clause. Two managers trying to create the same PVC can determine from the return code which manager succeeded and which failed (the failing manager fails because it can not set a value of PVC for an existing object). An entry in the closed or invalid state may be deleted or reused at the agent's convence. If the entry is kept in the closed state, the values of the parameters associated with the entry must be correct. Closed implies the values in the circuit table are correct. The value of invalid indicates the other values in the table are invalid. Many agents may never return a value of invalid because they dynamically allocate and free unused table entries. An agent for a statically configured systems can return invalid to indicate the entry has not yet been used so the counters contain no information. Agent variations: DESCRIPTION not settable" REFERENCE "See ISO 8208, table 33 for (p
) state table" ::= { x25CircuitEntry 3 }
x25CircuitStatus OBJECT-TYPE SYNTAX INTEGER { invalid (1), closed (2), calling (3), open (4), clearing (5), pvc (6), pvcResetting (7), startClear (8), startPvcResetting (9), other (10) } ACCESS read-write STATUS mandatory DESCRIPTION "This object reports the current status of the circuit. An existing instance of this object can only be set to startClear, startPvcResetting, or invalid. An instance with the value calling or open can only be set to startClear and that action will start clearing the circuit. An instance with the value PVC can only be set to startPvcResetting or invalid and that action resets the PVC or deletes the circuit respectively. The values startClear or startPvcResetting will never be returned by an agent. An attempt to set the status of an existing instance to a value other than one of these values will result in an error. A non-existing instance can be set to PVC to create a PVC if the implementation supports dynamic creation of PVCs. Some implementations may only allow creation and deletion of PVCs if the interface is down. Since the instance identifier will supply the PLE index and the channel number, setting this object alone supplies sufficient information to create the instance. All the DEFVAL clauses for the other objects of this table are appropriate for creating a PVC; PLEs creating entries for placed or accepted calls will use values appropriate for the call rather than the value of the DEFVAL clause. Two managers trying to create the same PVC can determine from the return code which manager succeeded and which failed (the failing manager fails because it can not set a value of PVC for an existing object). An entry in the closed or invalid state may be deleted or reused at the agent's convence. If the entry is kept in the closed state, the values of the parameters associated with the entry must be correct. Closed implies the values in the circuit table are correct. The value of invalid indicates the other values in the table are invalid. Many agents may never return a value of invalid because they dynamically allocate and free unused table entries. An agent for a statically configured systems can return invalid to indicate the entry has not yet been used so the counters contain no information." REFERENCE "See ISO 8208, table 33 for (p) state table" ::= { x25CircuitEntry 3 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.5.5.1.1 | x25CircuitIndex | 0 | 0 | The ifIndex value for the X.25 Interface. |
| 1.3.6.1.2.1.10.5.5.1.2 | x25CircuitChannel | 0 | 0 | The channel number for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.4 | x25CircuitEstablishTime | 0 | 0 | The value of sysUpTime when the channel was associated with this circuit. For outgoing SVCs, this is the time the first call pac… |
| 1.3.6.1.2.1.10.5.5.1.5 | x25CircuitDirection | 0 | 0 | The direction of the call that established this circuit. |
| 1.3.6.1.2.1.10.5.5.1.6 | x25CircuitInOctets | 0 | 0 | The number of octets of user data delivered to upper layer. |
| 1.3.6.1.2.1.10.5.5.1.7 | x25CircuitInPdus | 0 | 0 | The number of PDUs received for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.8 | x25CircuitInRemotelyInitiatedResets | 0 | 0 | The number of Resets received for this circuit with cause code of DTE initiated. |
| 1.3.6.1.2.1.10.5.5.1.9 | x25CircuitInProviderInitiatedResets | 0 | 0 | The number of Resets received for this circuit with cause code other than DTE initiated. |
| 1.3.6.1.2.1.10.5.5.1.10 | x25CircuitInInterrupts | 0 | 0 | The number of interrupt packets received for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.11 | x25CircuitOutOctets | 0 | 0 | The number of octets of user data sent for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.12 | x25CircuitOutPdus | 0 | 0 | The number of PDUs sent for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.13 | x25CircuitOutInterrupts | 0 | 0 | The number of interrupt packets sent on this circuit. |
| 1.3.6.1.2.1.10.5.5.1.14 | x25CircuitDataRetransmissionTimeouts | 0 | 0 | The number of times the T25 data retransmission timer expired for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.15 | x25CircuitResetTimeouts | 0 | 0 | The number of times the T22 reset timer expired for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.16 | x25CircuitInterruptTimeouts | 0 | 0 | The number of times the T26 Interrupt timer expired for this circuit. |
| 1.3.6.1.2.1.10.5.5.1.17 | x25CircuitCallParamId | 0 | 0 | This identifies the instance of the x25CallParmIndex for the entry in the x25CallParmTable which contains the call parameters in u… |
| 1.3.6.1.2.1.10.5.5.1.18 | x25CircuitCalledDteAddress | 0 | 0 | For incoming calls, this is the called address from the call indication packet. For outgoing calls, this is the called address fro… |
| 1.3.6.1.2.1.10.5.5.1.19 | x25CircuitCallingDteAddress | 0 | 0 | For incoming calls, this is the calling address from the call indication packet. For outgoing calls, this is the calling address f… |
| 1.3.6.1.2.1.10.5.5.1.20 | x25CircuitOriginallyCalledAddress | 0 | 0 | For incoming calls, this is the address in the call Redirection or Call Deflection Notification facility if the call was deflected… |
| 1.3.6.1.2.1.10.5.5.1.21 | x25CircuitDescr | 0 | 0 | A descriptive string associated with this circuit. This provides a place for the agent to supply any descriptive information it k… |