TRIP-MIB :: tripConnectionEstablished

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTRIP-MIBtripConnectionEstablished

tripConnectionEstablished

Module: TRIP-MIB

OID (symbolic): TRIP-MIB::tripConnectionEstablished

OID (numeric): 1.3.6.1.2.1.116.0.1

Node type: NOTIFICATION-TYPE

Description: The TRIP Connection Established event is generated when the TRIP finite state machine enters the ESTABLISHED state.

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> '' TRIP-MIB::tripConnectionEstablished
snmptrap -v2c -c public <manager> '' 1.3.6.1.2.1.116.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]:53626->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (304987002) 35 days, 7:11:10.02
  SNMPv2-MIB::snmpTrapOID.0 = OID: TRIP-MIB::tripConnectionEstablished

Start monitoring vendor-neutral, standards-based IETF MIB (RFC 3872), VoIP gateway/softswitch acting as TRIP Location Server (admin/oper status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TRIP-MIB::tripConnectionEstablished OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based IETF MIB (RFC 3872), VoIP gateway/softswitch acting as TRIP Location Server (admin/oper status) 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.116tripMIBTRIP-MIB
1.3.6.1.2.1.116.0tripMIBNotificationsTRIP-MIB
1.3.6.1.2.1.116.0.1tripConnectionEstablishedTRIP-MIB