Skip to main content
NetApp Stage KB

MetroCluster Tiebreaker uses wrong IP for SNMP traps

Views:
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

 

Applies to

  • MetroCluster Tiebreaker
  • Host system with multiple Ethernet interfaces

Issue

  • When running  snmp config test Tiebreaker does not use the expected IP to send SNMP traps

Example:

ip addr shows:

1: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:01:23:49:12:34 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global noprefixroute dynamic enp0s3

2: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 12:34:27:f1:23:4d brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.25/24 brd 10.0.2.255 scope global noprefixroute dynamic enp0s8

  • The traphost should receive the message from interface enp0s3 with IP 10.0.2.15
  • The message is being sent via interface enp0s3 however it has IP 10.0.2.25, from enp0s8 
  • This can be visible in the SNMP traphost log or a packet trace

 

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.
5fc492cd-a9e6-4c18-95de-bbbc46667766