Stack Failure traps on the SecureStack products

FAQ_User — Wed, 30 Apr 2014 18:51:00 GMT

Article ID: 7224

Products
SecureStack C3, all firmware
SecureStack C2, firmware 3.02.30 and higher
SecureStack B3, all firmware
SecureStack B2, firmware 3.01.16 and higher
SecureStack A2, firmware 1.03.17 and higher

Solution
With earlier firmware (prior to what is shown above), the SecureStack products support traps of type "

code:

entityconfigtrap

", to report when a stack member has dropped from or joined to the stack. The trap does not distinguish between the two actions.

With later firmware (as shown above), and as stated in release notes in the '

code:

Firmware Changes and Enhancements

' section:

code:

Support has been added for the ctEntStateOperEnabled and ctEntStateOperDisabled traps. These traps announce if a unit has dropped from the stack due to a failure or if a unit has joined to the stack.

Note that for the SecureStack products, Trap/Notify actions by default use the read-write community name, rather than the more typical read-only community name.

See also: 10381.

topic Stack Failure traps on the SecureStack products in FAQs

Stack Failure traps on the SecureStack products