Skip to main content
NetApp Knowledge Base

Why does 'volume full' not trigger SNMP traps event?

  1. Last updated
  2. Save as PDF
Views:
379
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • SNMP Traps

Answer

  • EMS shows monitor.volume.full as volume uses or reserves 98% of space.
[Hostname: wafl_spcd_main: monitor.volume.full:debug]: Volume vol1@vserver:92ba4446-f4ac-11e9-872e-00a098f9bb53 is full (using or reserving 98% of space and 28% of inodes).
 
Refer TR-4220. ONTAP has an SNMP trap event monitor.volume.full to the trap host. The following EMS message is generated:
monitor.volume.full 
  • However, if the volume used space is consistently more than 98%, the same monitor.volume.full cannot be generated, so ONTAP cannot have the same SNMP trap event monitor.volume.full to the trap host.
  • As the volume used space decreases to less than 98%, then increases to 98%, EMS shows monitor.volume.full. As the volume is using or reserving 98% of space again, the ONTAP has an SNMP trap event monitor.volume.full to the trap host again.

Additional Information

Related KB: FAQ: Overview of Event Management System for ONTAP 9
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.