TRIP-MIB :: tripPeerInUpdates

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTRIP-MIBtripPeerInUpdates

tripPeerInUpdates

Module: TRIP-MIB

OID (symbolic): TRIP-MIB::tripPeerInUpdates

OID (numeric): 1.3.6.1.2.1.116.1.5.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of TRIP update messages received from this remote peer since the last restart of this location server.

What is tripPeerInUpdates?

This is a running counter of TRIP update messages received from this remote peer since this location server last restarted. Admins compare it against tripPeerOutUpdates to see whether route exchange with this peer is flowing in both directions.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.116.1.5.1.1
snmpwalk -v2c -c public <target> TRIP-MIB::tripPeerInUpdates

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.116.1.5.1.1.1
snmpget -v2c -c public <target> TRIP-MIB::tripPeerInUpdates.1

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::tripPeerInUpdates 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.

How to Use in IPNetwork Monitor

Select a device implementing TRIP-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tripPeerInUpdates into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of TRIP update messages received from this remote peer since the last restart of this location server. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

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.1tripMIBObjectsTRIP-MIB
1.3.6.1.2.1.116.1.5tripPeerStatisticsTableTRIP-MIB
1.3.6.1.2.1.116.1.5.1tripPeerStatisticsEntryTRIP-MIB
1.3.6.1.2.1.116.1.5.1.1tripPeerInUpdatesTRIP-MIB