The value identifies the present state of the PPP
link.
The closed(1) state indicates that the link is down and
there is no attempt being made to open it and all connection
requests from peers are rejected.
In listen(2) state, the link
is down and there is no attempt being made to open it, however,
all the connection requests from peers are accepted.
The state
request-sent(3) indicates that an active attempt is being made
to open the link. In this state, a Configure-request packet has
been sent and no Configure-Ack has yet been received.
In the
state ack-received(4), a Configure-request packet has been sent
and Configure-Ack packet has been received.
The state ack-sent(5)
indicates that a Congigure-request and Configure-Ack packets
have been sent and Configure-Ack has not yet been received.
The opened(6) state implies that a connection has been made and
data may be sent.
The state term-sent(7) indicates that an
attempt is being made to close the connection and that a
Terminate-request packet has been sent and a Terminate-Ack
packet has not yet been received.
Parsed from file ibmiroc.mib.txt
Company: None
Module: IBMIROC-MIB
The value identifies the present state of the PPP
link.
The closed(1) state indicates that the link is down and
there is no attempt being made to open it and all connection
requests from peers are rejected.
In listen(2) state, the link
is down and there is no attempt being made to open it, however,
all the connection requests from peers are accepted.
The state
request-sent(3) indicates that an active attempt is being made
to open the link. In this state, a Configure-request packet has
been sent and no Configure-Ack has yet been received.
In the
state ack-received(4), a Configure-request packet has been sent
and Configure-Ack packet has been received.
The state ack-sent(5)
indicates that a Congigure-request and Configure-Ack packets
have been sent and Configure-Ack has not yet been received.
The opened(6) state implies that a connection has been made and
data may be sent.
The state term-sent(7) indicates that an
attempt is being made to close the connection and that a
Terminate-request packet has been sent and a Terminate-Ack
packet has not yet been received.
Parsed from file IBMIROC-MIB.mib
Module: IBMIROC-MIB
Vendor: IBM
Module: IBMIROC-MIB
[Automatically extracted from oidview.com]
pppLCProtoState OBJECT-TYPE SYNTAX INTEGER { closed (1), listen (2), requestSent (3), ackReceived (4), ackSent (5), opened (6), termSent (7) } ACCESS read-only STATUS mandatory DESCRIPTION "The value identifies the present state of the PPP link. The closed(1) state indicates that the link is down and there is no attempt being made to open it and all connection requests from peers are rejected. In listen(2) state, the link is down and there is no attempt being made to open it, however, all the connection requests from peers are accepted. The state request-sent(3) indicates that an active attempt is being made to open the link. In this state, a Configure-request packet has been sent and no Configure-Ack has yet been received. In the state ack-received(4), a Configure-request packet has been sent and Configure-Ack packet has been received. The state ack-sent(5) indicates that a Congigure-request and Configure-Ack packets have been sent and Configure-Ack has not yet been received. The opened(6) state implies that a connection has been made and data may be sent. The state term-sent(7) indicates that an attempt is being made to close the connection and that a Terminate-request packet has been sent and a Terminate-Ack packet has not yet been received. " ::= { pppLCProtoEntry 2 }
pppLCProtoState OBJECT-TYPE SYNTAX INTEGER { closed (1), listen (2), requestSent (3), ackReceived (4), ackSent (5), opened (6), termSent (7) } ACCESS read-only STATUS mandatory DESCRIPTION "The value identifies the present state of the PPP link. The closed(1) state indicates that the link is down and there is no attempt being made to open it and all connection requests from peers are rejected. In listen(2) state, the link is down and there is no attempt being made to open it, however, all the connection requests from peers are accepted. The state request-sent(3) indicates that an active attempt is being made to open the link. In this state, a Configure-request packet has been sent and no Configure-Ack has yet been received. In the state ack-received(4), a Configure-request packet has been sent and Configure-Ack packet has been received. The state ack-sent(5) indicates that a Congigure-request and Configure-Ack packets have been sent and Configure-Ack has not yet been received. The opened(6) state implies that a connection has been made and data may be sent. The state term-sent(7) indicates that an attempt is being made to close the connection and that a Terminate-request packet has been sent and a Terminate-Ack packet has not yet been received. " ::= { pppLCProtoEntry 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.6.119.4.2.3.1.1 | pppLCProtoIfIndex | 0 | 0 | A unique identifier for an interface running PPP. This object is the same as the MIB-II ifIndex object. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.3 | pppLCProtoPreviousState | 0 | 0 | The state of the PPP link prior to the state given by pppLCProtoState. These states are the same as those described for the objec… |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.4 | pppLCProtoLastTimeChange | 0 | 0 | The value of sysUpTime when the last PPP link state change occurred. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.5 | pppLCProtoOutPackets | 0 | 0 | Total number of LCP packets transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.6 | pppLCProtoOutOctets | 0 | 0 | Total number of LCP octets transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.7 | pppLCProtoOutCRs | 0 | 0 | Total number of LCP Config-requests transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.8 | pppLCProtoOutCAs | 0 | 0 | Total number of LCP Config-acks transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.9 | pppLCProtoOutCNs | 0 | 0 | Total number of LCP Config-nacks transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.10 | pppLCProtoOutCRejs | 0 | 0 | Total number of LCP Config-rejects transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.11 | pppLCProtoOutTRs | 0 | 0 | Total number of LCP Terminate-requests transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.12 | pppLCProtoOutTAs | 0 | 0 | Total number of LCP Terminate-acks transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.13 | pppLCProtoOutCodeRejs | 0 | 0 | Total number of LCP Code-rejects transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.14 | pppLCProtoOutEchoReqs | 0 | 0 | Total number of LCP Echo-requests transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.15 | pppLCProtoOutEchoReps | 0 | 0 | Total number of LCP Echo-replies transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.16 | pppLCProtoOutDiscReqs | 0 | 0 | Total number of LCP Discard-requests transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.17 | pppLCProtoOutResetReqs | 0 | 0 | Total number of LCP Reset-requests transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.18 | pppLCProtoOutResetAcks | 0 | 0 | Total number of LCP Reset-Acks transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.19 | pppLCProtoOutIdents | 0 | 0 | Total number of LCP Identification packets transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.20 | pppLCProtoOutTimeRemains | 0 | 0 | Total number of LCP Time-Remaining packets transmitted over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.21 | pppLCProtoInRejects | 0 | 0 | Total number of a LCP protocol-reject packets received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.22 | pppLCProtoInPackets | 0 | 0 | Total number of LCP packets received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.23 | pppLCProtoInOctets | 0 | 0 | Total number of LCP octets received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.24 | pppLCProtoInCRs | 0 | 0 | Total number of LCP Config-requests received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.25 | pppLCProtoInCAs | 0 | 0 | Total number of LCP Config-acks received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.26 | pppLCProtoInCNs | 0 | 0 | Total number of LCP Config-nacks received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.27 | pppLCProtoInCRejs | 0 | 0 | Total number of LCP Config-rejects received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.28 | pppLCProtoInTRs | 0 | 0 | Total number of LCP Terminate-requests received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.29 | pppLCProtoInTAs | 0 | 0 | Total number of LCP Terminate-acks received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.30 | pppLCProtoInCodeRejs | 0 | 0 | Total number of LCP Code-rejects received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.31 | pppLCProtoInEchoReqs | 0 | 0 | Total number of LCP Echo-Requests received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.32 | pppLCProtoInEchoReps | 0 | 0 | Total number of LCP Echo-replies received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.33 | pppLCProtoInDiscReqs | 0 | 0 | Total number of LCP Discard-requests received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.34 | pppLCProtoInResetReqs | 0 | 0 | Total number of LCP Reset-requests received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.35 | pppLCProtoInResetAcks | 0 | 0 | Total number of LCP Reset-Acks received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.36 | pppLCProtoInIdents | 0 | 0 | Total number of LCP Identification packets received over the PPP interface. |
| 1.3.6.1.4.1.2.6.119.4.2.3.1.37 | pppLCProtoInTimeRemains | 0 | 0 | Total number of LCP Time-Remaining packets received over the PPP interface. |