Skip to main content
NetApp Knowledge Base

Why is an impending drive failure event not reported through SNMP Trap in SANtricity

  1. Last updated
  2. Save as PDF
Views:
19
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

Applies to

NetApp E-Series

Answer

  • An impending drive failure event (IMPENDING_DRIVE_FAILURE_RISK_LOW) is not a supported SNMP Trap notification event in SANtricity.　
  • By design, SANtricity does not generate an SNMP Trap for this event type because the event is logged as informational and does not require immediate attention.
Example event details from the Major Event Log (MEL):
Date/Time: 7/14/26, 2:13:37 PM
Sequence number: 16183
Event type: 101F
Event category: Internal
Priority: Informational
Event needs attention: false
Event send alert: false
Event visibility: true
Description: Summary of impending drive failure detected by controller
Event specific codes: 0/0/0
Component type: Drive
Component location: Shelf 99, Bay 22
Logged by: Controller in bay B

Additional Information

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.