JUNIPER-SONET-MIB :: jnxSonetLastAlarmEvent

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-SONET-MIB › jnxSonetLastAlarmEvent

jnxSonetLastAlarmEvent

Module: JUNIPER-SONET-MIB

OID (symbolic): JUNIPER-SONET-MIB::jnxSonetLastAlarmEvent

OID (numeric): 1.3.6.1.4.1.2636.3.20.1.1.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This indicates whether the last alarm event set a new alarm or cleared an existing alarm.

What is jnxSonetLastAlarmEvent?

This enumerated value (none, set, or cleared) indicates whether the most recent SONET alarm event on this interface represented a new alarm being raised or an existing one being cleared. An admin reads it alongside jnxSonetLastAlarmId to know not just which alarm changed, but whether the interface's condition is getting worse or recovering. For example, a value of cleared(3) paired with a specific alarm ID would confirm to the admin that a previously reported SONET fault has now resolved.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.20.1.1.1.5
snmpwalk -v2c -c public <target> JUNIPER-SONET-MIB::jnxSonetLastAlarmEvent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.20.1.1.1.5.1
snmpget -v2c -c public <target> JUNIPER-SONET-MIB::jnxSonetLastAlarmEvent.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> jnxSonetLastAlarmEvent.1

Start monitoring Juniper routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-SONET-MIB::jnxSonetLastAlarmEvent OID value, configure state conditions and alerts, and monitor any Juniper routers from a single console.

How to Use in IPNetwork Monitor

Select a Juniper router as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type jnxSonetLastAlarmEvent into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This indicates whether the last alarm event set a new alarm or cleared an existing alarm. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'cleared', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.3jnxMibsJUNIPER-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.20jnxSonetJUNIPER-SONET-MIB
1.3.6.1.4.1.2636.3.20.1jnxSonetAlarmsJUNIPER-SONET-MIB
1.3.6.1.4.1.2636.3.20.1.1jnxSonetAlarmTableJUNIPER-SONET-MIB
1.3.6.1.4.1.2636.3.20.1.1.1jnxSonetAlarmEntryJUNIPER-SONET-MIB
1.3.6.1.4.1.2636.3.20.1.1.1.5jnxSonetLastAlarmEventJUNIPER-SONET-MIB