All MIBs › LBHUB-FMS-MIB › deprRptrResetEvent
deprRptrResetEvent
Module: LBHUB-FMS-MIB
OID (symbolic): LBHUB-FMS-MIB::deprRptrResetEvent
OID (numeric): 1.3.6.1.4.1.43.0.3
Node type: NOTIFICATION-TYPE
Description:
The deprRptrReset trap conveys information related to the operational state 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 [11], when triggered by a management command (e.g., an SNMP Set on the deprRptrReset object). The agent must throttle the generation of consecutive deprRptrReset traps so that there is at least a five-second gap between them. The deprRptrReset 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 deprRptrHealth variables as optional variables with its coldStart and warmStart trap PDUs. The deprRptrOperStatus variable must be included in the varbind list sent with this trap. The agent may optionally include the deprRptrHealthText variable 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> '' LBHUB-FMS-MIB::deprRptrResetEvent snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.43.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]:61172->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (510931700) 59 days, 3:15:17.00 SNMPv2-MIB::snmpTrapOID.0 = OID: LBHUB-FMS-MIB::deprRptrResetEvent
SNMPv3 example:
snmptrap -v3 -l authPriv -u snmpv3user -a SHA -A "AuthPass1" -x AES -X "PrivPass1" <manager> '' LBHUB-FMS-MIB::deprRptrResetEvent