---
oid: "1.3.6.1.4.1.6486.801.1.2.1.52.1.1.9.1.1.3"
short-description: "alaDot3OamPortL1PingStatus OBJECT-TYPE"
last-modified: "2021-11-08"
parent-oid: "1.3.6.1.4.1.6486.801.1.2.1.52.1.1.9.1.1"
---

## OID: `1.3.6.1.4.1.6486.801.1.2.1.52.1.1.9.1.1.3`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 6486 alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Software(2) softwareIND1Entities(1) softentIND1Dot3Oam(52) alcatelIND1Dot3OamMIB(1) alcatelIND1Dot3OamMIBObjects(1) alaDot3OamPortLoopbackControl(9) alaDot3OamLoopbackTable(1) alaDot3OamLoopbackEntry(1) alaDot3OamPortL1PingStatus(3)}
```

### Description

```asn1
alaDot3OamPortL1PingStatus OBJECT-TYPE
SYNTAX INTEGER {default(0), start(1), running(2), operationSuccessful(3), operationUnsuccessful(4)}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used to start the L1 ping operation. Operator
can set only start(1) value and setting of start(1) value is not valid
if object value is start(1) or running(2).
Whenever efm gets enabled on any port, this object has default(0) value.
Default(0) value implies that loopback session has not been started even
for a single time. Running(2) is corresponding to the state, when L1 ping
is going on, operationSuccessful(3) is corresponding to the state, when L1
ping operation is done successfully. operationUnsuccessful(4) is corresponding
to state when operation gets failed due to some reason."
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.
