2 Replies Latest reply on Jun 15, 2011 11:27 AM by wademn

    Stuck in Trap

    wademn
    wademn Jun 3, 2011 3:06 PM

      Can someone help me understand why the "Trap Type" text changes periodically? I've been pulling out what's left of my hair (not much) due to changes to the Trap Type text. Why do I care? We have many rules configured for traps with the condition set to match the Trap Type. Whenever changes occur, the rule is no longer valid and unfortunatley I don't know it until something bad happens.

      We've been burned by this quite a bit over the past couple years. The most recent example of such an event occurred today. We have a rule configured to match Trap Type = 'NETWORK-APPLIANCE-MIB:volumeFull'. However, Orion now displays the trap as Trap Type = 'NETAPP-MIB:volumeFull'.

      If you look in the MIB database, both the NETWORK-APPLIANCE-MIB and the NETAPP-MIB are associated to the NetApp OID's. I'd love it if someone could explain to me when and why these changes happen. Is there a better way to configure trap rules to mitigate this type of risk? If I can't rely on the Trap Type remaining constant, how am I supposed to create a good rule? Are these changes published somewhere so we are made aware?

        • Re: Stuck in Trap
          bshopp
          bshopp Employee Jun 14, 2011 7:14 PM (in response to wademn)

          Have you downloaded and applied a newer version or updated MIB DB recently?

            • Re: Stuck in Trap
              wademn
              wademn Jun 15, 2011 11:27 AM (in response to bshopp)

              Yes, I believe this happens when the application is patched/upgraded. However, as far as I know, these changes to the MIB DB are not documented or communicated in any way. Short of testing every DB rule that I have (150+), how am I supposed to know if an upgrade will break any of my trap rules?