Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

MetroCluster Tiebreaker uses wrong IP for SNMP traps

Views:
17
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

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support