CHECKPOINT-MIB-2 :: snmpOutTraps

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCHECKPOINT-MIB-2snmpOutTraps

snmpOutTraps

Module: CHECKPOINT-MIB-2

OID (symbolic): CHECKPOINT-MIB-2::snmpOutTraps

OID (numeric): 1.3.6.1.2.1.11.29

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.

What is snmpOutTraps?

The total number of SNMP Trap PDUs generated by the SNMP agent on this device. This is the meta-counter that tells an NMS whether the gateway's own trap-generation subsystem is alive at all; if this stays flat for an unusually long period while events like interface flaps or hardware alarms would be expected to have fired traps, it's a sign the trap pipeline itself, not just the individual event sources, may be stuck. Example: snmpOutTraps staying completely flat through a known interface flap event, visible via ifOperStatus history, would indicate the trap-sending mechanism itself failed, not that nothing happened.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.11.29
snmpwalk -v2c -c public <target> CHECKPOINT-MIB-2::snmpOutTraps

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.11.29.1
snmpget -v2c -c public <target> CHECKPOINT-MIB-2::snmpOutTraps.1

Start monitoring Check Point security gateway/firewall appliances with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CHECKPOINT-MIB-2::snmpOutTraps OID value, configure state conditions and alerts, and monitor any Check Point security gateway/firewall appliances from a single console.

OID Breakdown

Upper-level ancestors (6 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.11snmpCHECKPOINT-MIB-2
1.3.6.1.2.1.11.29snmpOutTrapsCHECKPOINT-MIB-2