Skip to main content
NetApp Knowledge Base

One node does not send SNMP traps

Views:
669
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9.8
  • SNMP trap

Issue

  • SNMP traps are not reaching the trap host destination from one of the cluster nodes.
  • Ping is alive from node management LIF to the trap host destination.

Example:

::> network ping -lif node01_mgmt -vserver cluster1 -destination 172.19.XX.XXX
172.19.XX.XXX is alive

  • Events are generated in the controller.

Example:

::> event generate -node node02 -message-name callhome.dsk.fault -values test
::> event generate -node node01 -message-name callhome.dsk.fault -values test


::> event notification history show -destination snmp-traphost
Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
9/20/2021 13:35:58  node01           ERROR         callhome.dsk.fault: Call home for test
9/20/2021 13:35:43  node02           ERROR         callhome.dsk.fault: Call home for test

  • Two separate cluster-management LIFs exist on the problematic node, and they are using two different gateways/network routes. 
Example:

::> network interface show
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
cluster1
            cluster_mgmt2
                       up/up      172.31.XX.XX/24    node01     a0a-3150   true
            cluster_mgmt1
                       up/up      172.17.XXX.XXX/24  node01        e0M     true
            node01_mgmt
                       up/up      172.17.XXX.XXX/24  node01        e0M     true
            node02_mgmt
                       up/up      172.17.XXX.XXX/24  node02        e0M     true

::> net route show
  (network route show)
Server              Destination     Gateway         Metric
------------------- --------------- --------------- ------
cluster1
                    0.0.0.0/0       172.17.XXX.1     20
                    0.0.0.0/0       172.31.XX.1      20

  • Network traceroute shows No route to host from the problematic node to SNMP trap host destination.

Example:

From the problematic node:

::> network traceroute -node node01 -destination 172.19.XX.XXX
traceroute to 172.19.XX.XXX (172.19.XXX.XXX), 64 hops max, 40 byte packets
 1  * * *
 2  *traceroute: sendto: No route to host
 *traceroute: wrote 172.19.XX.XXX 20 chars, ret=-1
traceroute: sendto: No route to host
 *
 3 traceroute: wrote 172.19.XX.XXX 20 chars, ret=-1
traceroute: sendto: No route to host
 *traceroute: wrote 172.19.XX.XXX 20 chars, ret=-1
traceroute: sendto: No route to host
 *traceroute: wrote 172.19.XX.XXX 20 chars, ret=-1
traceroute: sendto: No route to host

From the normal node:

::> network traceroute -node node02 -destination 172.19.XX.XXXtraceroute to 172.19.XX.XXX (172.19.XX.XXX), 64 hops max, 40 byte packets
 1  172.17.XXX.1 (172.17.XXX.1)  0.571 ms  0.446 ms  0.285 ms
 2  172.17.XXX.1 (172.17.XXX.1)  0.718 ms  0.991 ms  0.447 ms
 3  172.19.XX.XXX (172.19.XX.XXX)  0.119 ms  0.163 ms  0.125 ms

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.