All MIBs › PTOPO-MIB › ptopoConfigTrapInterval
ptopoConfigTrapInterval
Module: PTOPO-MIB
OID (symbolic): PTOPO-MIB::ptopoConfigTrapInterval
OID (numeric): 1.3.6.1.2.1.79.1.3.1
Node type: OBJECT-TYPE
Type: Integer32
Access: read-write
Description: This object controls the transmission of PTOPO notifications.
If this object has a value of zero, then no ptopoConfigChange notifications will be transmitted by the agent.
If this object has a non-zero value, then the agent must not generate more than one ptopoConfigChange trap-event in the indicated period, where a 'trap-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional configuration changes occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of ptopoLastChangeTime to detect any missed ptopoConfigChange trap-events, e.g. due to throttling or transmission loss.
If notification transmission is enabled, the suggested default throttling period is 60 seconds, but transmission should be disabled by default.
If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a re-initialization of the management system.
What is ptopoConfigTrapInterval?
This read-write Integer32 (0 or 5..3600 seconds), defaulting to 0 (disabled), controls, per its source description, how often the agent may send a ptopoConfigChange notification: zero disables the trap entirely, while a nonzero value throttles the agent to at most one such trap per that interval even if multiple topology changes occur, with a suggested default throttling period of 60 seconds once enabled. Admins enable this and set a reasonable interval to get proactive notification of topology changes without flooding the NMS with a trap for every single link change during, say, a busy discovery period. For example, setting this to 60 would ensure the agent sends at most one topology-change trap per minute, relying on ptopoLastChangeTime to catch any changes suppressed by the throttling.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.79.1.3.1 snmpwalk -v2c -c public <target> PTOPO-MIB::ptopoConfigTrapInterval
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.79.1.3.1.1 snmpget -v2c -c public <target> PTOPO-MIB::ptopoConfigTrapInterval.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.79.1.3.1.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> ptopoConfigTrapInterval.1
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::ptopoConfigTrapInterval 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | APERTUS-NPG-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.79 | ptopoMIB | PTOPO-MIB |
| 1.3.6.1.2.1.79.1 | ptopoMIBObjects | PTOPO-MIB |
| 1.3.6.1.2.1.79.1.3 | ptopoConfig | PTOPO-MIB |
| 1.3.6.1.2.1.79.1.3.1 | ptopoConfigTrapInterval | PTOPO-MIB |