JUNIPER-SOAM-PM-MIB :: jnxSoamLmSessionStartStopAlarm

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-SOAM-PM-MIB › jnxSoamLmSessionStartStopAlarm

jnxSoamLmSessionStartStopAlarm

Module: JUNIPER-SOAM-PM-MIB

OID (symbolic): JUNIPER-SOAM-PM-MIB::jnxSoamLmSessionStartStopAlarm

OID (numeric): 1.3.6.1.4.1.2636.3.78.0.1

Node type: NOTIFICATION-TYPE

Description: An jnxSoamLmSessionStartStopAlarm notification is sent when the state of jnxSoamLmCfgSessionStatus changes.

The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the individual PM session reporting the start/stop by the indices in the OID jnxSoamLmCfgSessionStatus, including dot1agCfmMdIndex, dot1agCfmMaIndex, dot1agCfmMepIdentifier, and jnxSoamLmCfgIndex.

An agent is not to generate more than one jnxSoamLmSessionStartStopAlarm 'notification-event' in a given time interval per LM session as specified by the jnxSoamPmNotificationCfgAlarmInterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations.

If additional operational state changes occur within the jnxSoamPmNotificationCfgAlarmInterval period, then notification generation for these changes are be suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any operational state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away.

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' JUNIPER-SOAM-PM-MIB::jnxSoamLmSessionStartStopAlarm
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.2636.3.78.0.1

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:51654->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (407160262) 47 days, 3:00:02.62
  SNMPv2-MIB::snmpTrapOID.0 = OID: JUNIPER-SOAM-PM-MIB::jnxSoamLmSessionStartStopAlarm

Start monitoring Juniper router/switch, carrier Ethernet demarcation/aggregation device (SOAM performance monitoring) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-SOAM-PM-MIB::jnxSoamLmSessionStartStopAlarm OID value, configure state conditions and alerts, and monitor any Juniper router/switch, carrier Ethernet demarcation/aggregation device (SOAM performance monitoring) from a single console.

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.78jnxSoamPmMibJUNIPER-SOAM-PM-MIB
1.3.6.1.4.1.2636.3.78.0jnxSoamPmNotificationsJUNIPER-SOAM-PM-MIB
1.3.6.1.4.1.2636.3.78.0.1jnxSoamLmSessionStartStopAlarmJUNIPER-SOAM-PM-MIB