---
oid: "1.3.6.1.4.1.562.36.2.1.72.3.13.1.5"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 562 msCarrier(36) mscPassport(2) mscComponents(1) mscFrAtm(72) mscFrAtmLmi(3) mscFrAtmLmiStatsTable(13) mscFrAtmLmiStatsEntry(1) mscFrAtmLmiNetworkSideEventHistory(5)}"
description: "mscFrAtmLmiNetworkSideEventHistory OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2017-12-20"
---

## OID : `1.3.6.1.4.1.562.36.2.1.72.3.13.1.5`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 562 msCarrier(36) mscPassport(2) mscComponents(1) mscFrAtm(72) mscFrAtmLmi(3) mscFrAtmLmiStatsTable(13) mscFrAtmLmiStatsEntry(1) mscFrAtmLmiNetworkSideEventHistory(5)}
```

### Description

```asn1
mscFrAtmLmiNetworkSideEventHistory OBJECT-TYPE
SYNTAX AsciiString (SIZE (1..10))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This attribute displays the Local Management Interface network
side procedure event history in order of occurrence. An event is
represented by a single symbol. A '+' symbol indicates a good
event. An 'X' symbol indicates a protocol error event. The leftmost
event is the most recent to occur. The provisioned eventCount (nN3/
N393) dictates the maximum number of events displayed. A good
event is triggered by receipt of a valid status enquiry message. An
error event is one of three possibilities, either a nT2/T392 timer
expiry, receipt of a status enquiry message with bad sequence
numbers, or when lmiProcedures is provisioned to vendorForum
and we receive more than nN4 status enquiry messages within the
provisioned messageCountTimer (nT3)."
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

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