SLAPM-MIB :: slapmSubcomponentMonitoredEventNotAchieved

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SLAPM-MIB › slapmSubcomponentMonitoredEventNotAchieved

slapmSubcomponentMonitoredEventNotAchieved

Module: SLAPM-MIB

OID (symbolic): SLAPM-MIB::slapmSubcomponentMonitoredEventNotAchieved

OID (numeric): 1.3.6.1.3.88.0.5

Node type: NOTIFICATION-TYPE

Description: This notification is generated when a monitored value does not achieved a threshold specification. This applies only towards monitoring the individual components of a policy traffic profile. The value of the corresponding slapmPolicyMonitorControl can be examined to determine what is being monitored. The first slapmSubcomponentMonitorStatus value supplies the current

monitor status while the 2nd value supplies the previous status.

Note: The corresponding slapmPolicyMonitorControl BITS setting, enableSubcomponentTraps(4), MUST be selected in order for this notification to potentially be generated.

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> '' SLAPM-MIB::slapmSubcomponentMonitoredEventNotAchieved
snmptrap -v2c -c public <manager> '' 1.3.6.1.3.88.0.5

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]:51374->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (85923502) 9 days, 22:40:35.02
  SNMPv2-MIB::snmpTrapOID.0 = OID: SLAPM-MIB::slapmSubcomponentMonitoredEventNotAchieved

Start monitoring vendor-neutral, standards-based MIB, SLA-aware routers/switches and performance monitoring probes (SLA policy vs. threshold status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SLAPM-MIB::slapmSubcomponentMonitoredEventNotAchieved OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, SLA-aware routers/switches and performance monitoring probes (SLA policy vs. threshold status) from a single console.

OID Breakdown

Upper-level ancestors (5 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.3experimentalAPERTUS-NPG-MIB
Numeric OIDNameModule
1.3.6.1.3.88slapmMIBSLAPM-MIB
1.3.6.1.3.88.0slapmNotificationsSLAPM-MIB
1.3.6.1.3.88.0.5slapmSubcomponentMonitoredEventNotAchievedSLAPM-MIB