All MIBs › LBHUB-BOOM-MIB › resResilienceSwitch
resResilienceSwitch
Module: LBHUB-BOOM-MIB
OID (symbolic): LBHUB-BOOM-MIB::resResilienceSwitch
OID (numeric): 1.3.6.1.4.1.43.0.43
Node type: NOTIFICATION-TYPE
Description:
This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated. Generation of this trap is summarised in the following table: ------------------------------------------------------------------------------ State | Event Main Backup |Main Fail |Main OK |StandBy Fail |Standby OK ------------------------------------------------------------------------------ Active OK | switch | ----- | state | ----- Active Fail | state | ----- | ----- | state OK Active | state | ----- | switch | ----- Fail Active | ----- | state | state | ----- Fail Fail | ----- | switch | ----- | state ----------------------------------------------------------------------------- In this table '-----' indicates no trap is sent. 'switch' indicates the resResilienceSwitch trap is sent and 'state' indicates resStateChange is sent. NOTE: The agent in the MSH does not suppress any traps that caused the state change. For example if the active link is lost then both a 'loss-of-link' trap AND a resilienceSwitch trap are generated.
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-BOOM-MIB::resResilienceSwitch snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.43.0.43
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]:64759->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (18331895) 2 days, 2:55:18.95 SNMPv2-MIB::snmpTrapOID.0 = OID: LBHUB-BOOM-MIB::resResilienceSwitch