PTOPO-MIB :: ptopoConfigMaxHoldTime

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PTOPO-MIB › ptopoConfigMaxHoldTime

ptopoConfigMaxHoldTime

Module: PTOPO-MIB

OID (symbolic): PTOPO-MIB::ptopoConfigMaxHoldTime

OID (numeric): 1.3.6.1.2.1.79.1.3.2

Node type: OBJECT-TYPE

Type: Integer32

Access: read-write

Description: This object specifies the desired time interval for which an agent will maintain dynamic ptopoConnEntries. After the specified number of seconds since the last time an entry was verified, in the absence of new verification (e.g., receipt of a topology protocol message), the agent shall remove the entry. Note that entries may not always be removed immediately, but may possibly be removed at periodic garbage collection intervals. This object only affects dynamic ptopoConnEntries, i.e. for which ptopoConnIsStatic equals 'false(2)'. Static entries are not aged out. Note that dynamic ptopoConnEntries may also be removed by the agent due to the expired timeliness of learned topology information (e.g., timeliness interval for a remote port expires). The actual age-out interval for a given entry is defined by the following formula: age-out-time = min(ptopoConfigMaxHoldTime, ) where is determined by the discovery algorithm, and may be different for each entry.

What is ptopoConfigMaxHoldTime?

This read-write Integer32 (1..2147483647 seconds), defaulting to 300, specifies, per its source description, how long the agent will keep a dynamic (non-static) topology connection entry without re-verification before removing it, computed per-entry as the minimum of this value and any entry-specific hold-time set by the discovery algorithm itself. Admins raise or lower this to control how quickly stale neighbor information disappears from the topology table versus how tolerant the table is of a temporarily quiet or unresponsive discovery protocol. For example, lowering this from the 300-second default to 120 would cause dynamic entries to age out faster if a neighboring device stops sending topology protocol updates.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.79.1.3.2
snmpwalk -v2c -c public <target> PTOPO-MIB::ptopoConfigMaxHoldTime

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.79.1.3.2.1
snmpget -v2c -c public <target> PTOPO-MIB::ptopoConfigMaxHoldTime.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.79.1.3.2.1 i <value>

Start monitoring vendor-neutral, standards-based MIB (physical topology discovery) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PTOPO-MIB::ptopoConfigMaxHoldTime OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB (physical topology discovery) 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.79ptopoMIBPTOPO-MIB
1.3.6.1.2.1.79.1ptopoMIBObjectsPTOPO-MIB
1.3.6.1.2.1.79.1.3ptopoConfigPTOPO-MIB
1.3.6.1.2.1.79.1.3.2ptopoConfigMaxHoldTimePTOPO-MIB