Skip to main content
NetApp Stage KB

Issue in SNMP alert monitoring on AIQUM due to difference in OID value received from aiqum MiB

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
OM
Last Updated:

 

 

Applies to

Issue

  • Issue in SNMP alert monitoring in AIQUM 9.9x and above
  • AIQUM sends an extra .1.0 /.1 before the eventID in the OIDs of the alerts

eg:

  • for the alert ocumevtvolumeoffline with event ID 14702, AIQUM sends traps with OID .1.3.6.1.4.1.789.5.1.1.0.14702 
  • some MiB pursers are pursing the OID as .1.3.6.1.4.1.789.5.1.0.14702
  • Some MiB pursers are pursing the OID as .1.3.6.1.4.1.789.5.1.14702
  • The behaviour is same for other AIQUM alerts with separate event IDs

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.