All MIBs › SNMP-REPEATER-MIB › rptrInfoResetEvent
rptrInfoResetEvent
Module: SNMP-REPEATER-MIB
OID (symbolic): SNMP-REPEATER-MIB::rptrInfoResetEvent
OID (numeric): 1.3.6.1.2.1.22.0.5
Node type: NOTIFICATION-TYPE
Description:
In a system containing multiple managed repeaters, the rptrInfoResetEvent notification conveys information related to the operational status of a repeater. This notification is sent on completion of a repeater reset action. A repeater reset action is defined as a transition to the START state of Fig 9-2 in section 9 of [IEEE 802.3 Std], when triggered by a management command (e.g., an SNMP Set on the rptrInfoReset object).
The agent must throttle the generation of consecutive rptrInfoResetEvent notifications for a single repeater so that there is at least a five-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a notification means sending to all configured recipients.)
The rptrInfoResetEvent is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. However, it is recommended that a repeater agent send the rptrInfoOperStatus object as an optional object with its coldStart and warmStart trap PDUs.
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> '' SNMP-REPEATER-MIB::rptrInfoResetEvent snmptrap -v2c -c public <manager> '' 1.3.6.1.2.1.22.0.5
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]:61739->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (356005163) 41 days, 4:54:11.63 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMP-REPEATER-MIB::rptrInfoResetEvent