SecureStack Generated a Trap referencing OID 1.3.6.1.4.1.52.4.2.31.1.0.1

  • 0
  • 1
  • Article
  • Updated 5 years ago
Article ID: 10381 

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

Changes
Configured to send SNMP Traps.

Symptoms
Network Management station received from the SecureStack a trap referencing "OID:.1.3.6.1.4.1.52.4.2.31.1.0.1".
Network Management station received from the SecureStack a trap referencing "OID:.1.3.6.1.4.1.52.4.2.31.1.0.2".

Solution/Workaround
These are the "Stacked Unit Change of State" SNMP Traps, generated when a Stacked unit either joins or leaves the stack.

Release notes state, in the 'Firmware Changes and Enhancements' section:
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.

OID 1.3.6.1.4.1.52.4.2.31.1.0.1 = ctEntStateOperEnabled, which in ctron-entity-state-mib.txt is described as:
An ctEntStateOperEnabled notification signifies that the SNMP entity, acting in an agent role, has detected that the ctEntStateOper object for one of its entities has transitioned into the 'enabled' state.

OID 1.3.6.1.4.1.52.4.2.31.1.0.2 = ctEntStateOperDisabled, which in ctron-entity-state-mib.txt is described as:
An ctEntStateOperDisabled notification signifies that the SNMP entity, acting in an agent role, has detected that the ctEntStateOper object for one of its entities has transitioned into the 'disabled' state.

The information contained in these SNMP Traps is:
  • unit index - Stacked unit index for example 1
  • unit status - Either (Available for join) or (Not Available for leave)
  • unit description - e.g. "Enterasys Networks, Inc. SecureStack B2"
See also: 7224.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.