ATM-FORUM-M4-MIB :: atmfM4IfLopAlarm

MIB Reference — IPNetwork Monitor

All MIBsATM-FORUM-M4-MIBatmfM4IfLopAlarm

atmfM4IfLopAlarm

Module: ATM-FORUM-M4-MIB

OID (symbolic): ATM-FORUM-M4-MIB::atmfM4IfLopAlarm

OID (numeric): 1.3.6.1.4.1.353.100.2.4

Node type: NOTIFICATION-TYPE

Description:

Indicates that an LOP (Loss of Pointer) condition has occurred on the physical path TP associated with the specified interface.

What is atmfM4IfLopAlarm?

This notification alerts network operators when a Loss of Pointer (LOP) alarm condition is detected on an ATM interface, indicating a synchronization problem with the physical transmission path. LOP is a critical signal degradation fault in ATM networks that requires immediate attention. Operators use this alarm to detect and troubleshoot physical layer problems affecting ATM circuit integrity.

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> '' ATM-FORUM-M4-MIB::atmfM4IfLopAlarm
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.353.100.2.4

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]:64777->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (67223817) 7 days, 18:43:58.17
  SNMPv2-MIB::snmpTrapOID.0 = OID: ATM-FORUM-M4-MIB::atmfM4IfLopAlarm

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.353atmForumATM-FORUM-SNMP-M4-MIB
1.3.6.1.4.1.353.100atmfM4MIBATM-FORUM-M4-MIB
1.3.6.1.4.1.353.100.2atmfM4MIBTrapsATM-FORUM-M4-MIB
1.3.6.1.4.1.353.100.2.4atmfM4IfLopAlarmATM-FORUM-M4-MIB