- ONTAP EMS
- ONTAP 9.x
- Clustered Data ONTAP 8.3
- Data ONTAP 8.2 7-Mode
This article contains a list of most SNMP operational and troubleshooting workflows. However, it is not a comprehensive list. This can be used to narrow your search to the more commonly utilized troubleshooting KBs, broken down to a specific category.
Overview: What is SNMP?
The Simple Network Management Protocol (SNMP) is an Internet-standard application-layer protocol for managing devices on IP networks. SNMP can be configured to monitor and manage storage systems and their functions. SNMP is supported by NetApp® storage systems running Data ONTAP® operating in 7-Mode as well as by NetApp® storage systems running clustered Data ONTAP®. SNMP is based on an agent/manager model.
Differences between 7-Mode and clustered Data ONTAP support for SNMP
The Netapp® custom MIB (netapp.mib) file is common for clustered Data ONTAP® and Data ONTAP® operating in 7-Mode, but there is a difference in the level of SNMP support for the two operating modes.
For a table overview of the level of support offered for SNMP MIBs and SNMP traps in Data ONTAP® 8.2.x for both Data ONTAP® operating in 7-Mode and clustered Data ONTAP® plus what is available in 8.3.x and 9.0, see the following Technical report.
TR-Guide: SNMP Support in Data ONTAP®
Note: Certain objects are not supported for both ONTAP modes.
SNMP tools might not function with clustered Data ONTAP
Starting with Data ONTAP 8.3, OnCommand System Manager is a bundled component of Data ONTAP, and its documentation is part of the Data ONTAP documentation set.
Known issue in 9.x: Using System manager to test the trap host configuration fails with
'Data ONTAP API FAILED; not authorized for that command(error :13003)'
BUG 1058259 - snmp-test-trap-trigger fails in ONTAP 9.0 and 9.1
Note:Only the Test trap call from System Manager is affected. The configuration changes will apply in ONTAP.
Frequently asked questions:
What are the differences between a built-in trap and using SNMP objects OID to pull data?
Built-in traps are predefined in Data ONTAP® and are automatically sent to the network management stations on the traphost list if an event occurs. These traps, such as diskFailedShutdown, cpuTooBusy, and volumeNearlyFull, are defined in the custom MIB. Each built-in trap is identified by a unique trap code.
Basically, the NetApp built-in traps will not have an OID that you can use to perform an snmpget or snmpwalk.
How to find EMS events that support SNMP?
To view the EMS events that support SNMP, simply query the EMS catalog and leverage the snmp-support flag.
To view the entire list:
::> event route show -snmp-support true
In the following example, a query is sent for EMS volume events that support SNMP traps.
::> event route show -snmp-support true -messagename *vvol* Freq Time
Message Severity Destinations Threshd Threshd
-------------------------------- -------------- -------------- ------- -------
wafl.vvol.offline INFORMATIONAL - 0 0
wafl.vvol.online INFORMATIONAL - 0 0
wafl.vvol.restrict INFORMATIONAL - 0 0
3 entries were displayed.
Error: command failed: Failed to add or change SNMP destination because all SNMP destinations defined in both the SNMP and event subsystems mustmatch. Use the "system snmp traphost show" or "event destination show-name traphost" commands to see the current list of traphost destinations.
Error: The user "public" is currently configured for sending notifications. Delete all traphosts associated with this user using "traphost delete" command and try again.
command failed: resource in use
The message indicates you have traphosts configured. When traphosts are first configured they are associated with the defualt snmpuser "public" per the default public comminuty string.
1. verify you have traphosts configured
::> system snmp
2. remove any trapshots (record the information in order to add them back if needed)
::> system snmp traphost delete -peer-address
3. remove the Public community string
::>system snmp community delete -community-name public -type ro
4. re add you trapshots
::>system snmp traphost add
Error: ONTAP 9.2 and earlier software can send an SNMP trap to previously configured trap hosts even after removal
- Remove all traphosts which will clear the database and add the current traphost.
::> System snmp traphost delete
- Add current traphosts
::> system snmp traphost add