Hi @hemh !
What about these two OIDs sent as traps:
.1.3.6.1.4.1.25506.2.91.6.0.2
hh3cStackTopologyChange NOTIFICATION-TYPE
-- FROM HH3C-STACK-MIB
OBJECTS { hh3cStackTopology }
DESCRIPTION "The hh3cStackTopologyChange trap indicates that the topology type of
the IRF stack has changed."
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hh3c(25506) hh3cCommon(2) hh3cStack(91) hh3cStackTrap(6) hh3cStackTrapOjbects(0) 2 }
.1.3.6.1.4.1.25506.2.91.6.0.1
hh3cStackPortLinkStatusChange NOTIFICATION-TYPE
-- FROM HH3C-STACK-MIB
OBJECTS { hh3cStackMemberID, hh3cStackPortIndex, hh3cStackPortStatus }
DESCRIPTION "The hh3cStackPortLinkStatusChange trap indicates that the link status
of the stack port has changed."
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hh3c(25506) hh3cCommon(2) hh3cStack(91) hh3cStackTrap(6) hh3cStackTrapOjbects(0) 1 }
Also, there is an OID that you can possibly monitor, but it has to be polled by SNMP GET, it's not sent as trap, so I am not really sure if you can create an alarm in IMC for the value decrease:
.1.3.6.1.4.1.25506.2.91.1.2
hh3cStackMemberNum OBJECT-TYPE
-- FROM HH3C-STACK-MIB
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of members currently in a stack."
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hh3c(25506) hh3cCommon(2) hh3cStack(91) hh3cStackGlobalConfig(1) 2 }