All MIBs › LANART-AGENT › rptrResetEvent
rptrResetEvent
Module: LANART-AGENT
OID (symbolic): LANART-AGENT::rptrResetEvent
OID (numeric): 1.3.6.1.2.1.22.0.3
Node type: NOTIFICATION-TYPE
Description:
The rptrResetEvent trap conveys information related to the operational status of the repeater. This trap is sent on completion of a repeater reset action. A repeater reset action is defined as an a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std], when triggered by a management command (e.g., an SNMP Set on the rptrReset object). The agent must throttle the generation of consecutive rptrResetEvent traps so that there is at least a five-second gap between them. The rptrResetEvent trap 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 rptrOperStatus object as an optional object with its coldStart and warmStart trap PDUs. The rptrOperStatus object must be included in the varbind list sent with this trap. The agent may optionally include the rptrHealthText object as well.
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> '' LANART-AGENT::rptrResetEvent snmptrap -v2c -c public <manager> '' 1.3.6.1.2.1.22.0.3
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]:54302->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (105425950) 12 days, 4:50:59.50 SNMPv2-MIB::snmpTrapOID.0 = OID: LANART-AGENT::rptrResetEvent
SNMPv3 example:
snmptrap -v3 -l authPriv -u snmpv3user -a SHA -A "AuthPass1" -x AES -X "PrivPass1" <manager> '' LANART-AGENT::rptrResetEvent