The current state of the LEC. Note that busConnect is only a
monitorable state if the BUS is colocated with the LES. In the
event that it is not then the client state should proceed
immediately to operational within this table (though it may not
do so in actuality). Note that there is no relation between the
client's internal state and the state reflected here. The
state here is only the LES's observed state of the LEC.
Parsed from file CISCO-LES-MIB.mib
Module: CISCO-LES-MIB
The current state of the LEC. Note that busConnect is only a
monitorable state if the BUS is colocated with the LES. In the
event that it is not then the client state should proceed
immediately to operational within this table (though it may not
do so in actuality). Note that there is no relation between the
client's internal state and the state reflected here. The
state here is only the LES's observed state of the LEC.
lesClientState OBJECT-TYPE
SYNTAX INTEGER { connected(1),
joinRecv(2),
verify(3),
addLec(4),
busConnect(5),
operational(6),
terminating(7) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" The current state of the LEC. Note that busConnect is only a
monitorable state if the BUS is colocated with the LES. In the
event that it is not then the client state should proceed
immediately to operational within this table (though it may not
do so in actuality). Note that there is no relation between the
clients internal state and the state reflected here. The
state here is only the LESs observed state of the LEC."
View at oid-info.com
The current state of the LEC. Note that busConnect is only a
monitorable state if the BUS is colocated with the LES. In the
event that it is not then the client state should proceed
immediately to operational within this table (though it may not
do so in actuality). Note that there is no relation between the
client's internal state and the state reflected here. The
state here is only the LES's observed state of the LEC.
Parsed from file CISCO-LES-MIB.my.txt
Company: None
Module: CISCO-LES-MIB
The current state of the LEC. Note that busConnect is only a
monitorable state if the BUS is colocated with the LES. In the
event that it is not then the client state should proceed
immediately to operational within this table (though it may not
do so in actuality). Note that there is no relation between the
client's internal state and the state reflected here. The
state here is only the LES's observed state of the LEC.
lesClientState OBJECT-TYPE SYNTAX INTEGER { connected(1), joinRecv(2), verify(3), addLec(4), busConnect(5), operational(6), terminating(7) } ACCESS read-only STATUS mandatory DESCRIPTION " The current state of the LEC. Note that busConnect is only a monitorable state if the BUS is colocated with the LES. In the event that it is not then the client state should proceed immediately to operational within this table (though it may not do so in actuality). Note that there is no relation between the client's internal state and the state reflected here. The state here is only the LES's observed state of the LEC." ::= { lesClientEntry 3 }
lesClientState OBJECT-TYPE SYNTAX INTEGER { connected(1), joinRecv(2), verify(3), addLec(4), busConnect(5), operational(6), terminating(7) } ACCESS read-only STATUS mandatory DESCRIPTION " The current state of the LEC. Note that busConnect is only a monitorable state if the BUS is colocated with the LES. In the event that it is not then the client state should proceed immediately to operational within this table (though it may not do so in actuality). Note that there is no relation between the client's internal state and the state reflected here. The state here is only the LES's observed state of the LEC." ::= { lesClientEntry 3 }
Automatically extracted from Cisco "SNMP v2 MIBs".
lesClientState OBJECT-TYPE SYNTAX INTEGER { connected(1), joinRecv(2), verify(3), addLec(4), busConnect(5), operational(6), terminating(7) } MAX-ACCESS read-only STATUS current DESCRIPTION " The current state of the LEC. Note that busConnect is only a monitorable state if the BUS is colocated with the LES. In the event that it is not then the client state should proceed immediately to operational within this table (though it may not do so in actuality). Note that there is no relation between the client's internal state and the state reflected here. The state here is only the LES's observed state of the LEC." ::= { lesClientEntry 3 }
lesClientState OBJECT-TYPE SYNTAX INTEGER { connected(1), joinRecv(2), verify(3), addLec(4), busConnect(5), operational(6), terminating(7) } MAX-ACCESS read-only STATUS current DESCRIPTION " The current state of the LEC. Note that busConnect is only a monitorable state if the BUS is colocated with the LES. In the event that it is not then the client state should proceed immediately to operational within this table (though it may not do so in actuality). Note that there is no relation between the client's internal state and the state reflected here. The state here is only the LES's observed state of the LEC." ::= { lesClientEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.39.1.2.1.1.1 | lesClientLecid | 0 | 0 | The LECID selected for an LEC by the LES during the JOIN phase. |
| 1.3.6.1.4.1.9.9.39.1.2.1.1.2 | lesClientAtmAddr | 0 | 0 | The primary ATM address associated with the designated LEC. |
| 1.3.6.1.4.1.9.9.39.1.2.1.1.4 | lesClientIfIndex | 0 | 0 | The interface of the bi-directional control direct connection between the LEC and LES. |
| 1.3.6.1.4.1.9.9.39.1.2.1.1.5 | lesClientControlVpi | 0 | 0 | The VPI of the bi-directional control direct connection between the LEC and LES. |
| 1.3.6.1.4.1.9.9.39.1.2.1.1.6 | lesClientControlVci | 0 | 0 | The VCI of the bi-directional control direct connection between the LEC and LES. |
| 1.3.6.1.4.1.9.9.39.1.2.1.1.7 | lesClientStatus | 0 | 0 | The status of the (conceptual) row. Note that this object may only return the active(1) state. The only value which may be writ… |