Netapp sending failed pings to cluster

Daisyahoy — Wed, 04 Jun 2025 10:28:55 GMT

Hi,

Disclaimer: I am not an experienced in Netapp but I can follow helpful advice

While monitoring our syslog, I am seeing this message:

2021-03-26 11:58:39 Local2.Info B1560-38A-R1R3-MGT1-INT 5880379: Mar 26 16:58:38.357 UTC: %SEC-6-IPACCESSLOGDP: list ACL-TRANSIT-MGMT-IN denied icmp 10.2.21.101 -> 169.254.64.107 (0/0), 19 packets

It appears that the Netapp is trying to ping an IP for one of its clusters but it is headed out its management network to attempt this. The Management switch blocks this as that IP is no beyond its ACL boundary.

Version 9.7P2

I'm not sure if there is any issue at all. IT just appears to be some strange anomaly that repeats every 3 minutes.

Here is some output if it helps:

-------------------------------------------------------------

B1560-38A-R1R2-FAS::*> cluster ping-cluster -node B1560-38A-R1R2-FAS-02
Host is B1560-38A-R1R2-FAS-02
Getting addresses from network interface table...
Cluster B1560-38A-R1R2-FAS-01_clus1 169.254.64.107 B1560-38A-R1R2-FAS-01 e0a
Cluster B1560-38A-R1R2-FAS-01_clus2 169.254.74.5 B1560-38A-R1R2-FAS-01 e0b
Cluster B1560-38A-R1R2-FAS-01_clus3 169.254.124.178 B1560-38A-R1R2-FAS-01 e0c
Cluster B1560-38A-R1R2-FAS-01_clus4 169.254.212.103 B1560-38A-R1R2-FAS-01 e0d
Cluster B1560-38A-R1R2-FAS-02_clus1 169.254.56.214 B1560-38A-R1R2-FAS-02 e0a
Cluster B1560-38A-R1R2-FAS-02_clus2 169.254.206.17 B1560-38A-R1R2-FAS-02 e0b
Cluster B1560-38A-R1R2-FAS-02_clus3 169.254.160.224 B1560-38A-R1R2-FAS-02 e0c
Cluster B1560-38A-R1R2-FAS-02_clus4 169.254.233.247 B1560-38A-R1R2-FAS-02 e0d
Local = 169.254.56.214 169.254.206.17 169.254.160.224 169.254.233.247
Remote = 169.254.64.107 169.254.74.5 169.254.124.178 169.254.212.103
Cluster Vserver Id = 4294967293
Ping status:
................
Basic connectivity succeeds on 16 path(s)
Basic connectivity fails on 0 path(s)
................................................................
Detected 9000 byte MTU on 16 path(s):
Local 169.254.160.224 to Remote 169.254.124.178
Local 169.254.160.224 to Remote 169.254.212.103
Local 169.254.160.224 to Remote 169.254.64.107
Local 169.254.160.224 to Remote 169.254.74.5
Local 169.254.206.17 to Remote 169.254.124.178
Local 169.254.206.17 to Remote 169.254.212.103
Local 169.254.206.17 to Remote 169.254.64.107
Local 169.254.206.17 to Remote 169.254.74.5
Local 169.254.233.247 to Remote 169.254.124.178
Local 169.254.233.247 to Remote 169.254.212.103
Local 169.254.233.247 to Remote 169.254.64.107
Local 169.254.233.247 to Remote 169.254.74.5
Local 169.254.56.214 to Remote 169.254.124.178
Local 169.254.56.214 to Remote 169.254.212.103
Local 169.254.56.214 to Remote 169.254.64.107
Local 169.254.56.214 to Remote 169.254.74.5
Larger than PMTU communication succeeds on 16 path(s)
RPC status:
4 paths up, 0 paths down (tcp check)
4 paths up, 0 paths down (udp check)

----------------------------------------------------------

B1560-38A-R1R2-FAS::*> cluster ping-cluster -node B1560-38A-R1R2-FAS-01
Host is B1560-38A-R1R2-FAS-01
Getting addresses from network interface table...
Cluster B1560-38A-R1R2-FAS-01_clus1 169.254.64.107 B1560-38A-R1R2-FAS-01 e0a
Cluster B1560-38A-R1R2-FAS-01_clus2 169.254.74.5 B1560-38A-R1R2-FAS-01 e0b
Cluster B1560-38A-R1R2-FAS-01_clus3 169.254.124.178 B1560-38A-R1R2-FAS-01 e0c
Cluster B1560-38A-R1R2-FAS-01_clus4 169.254.212.103 B1560-38A-R1R2-FAS-01 e0d
Cluster B1560-38A-R1R2-FAS-02_clus1 169.254.56.214 B1560-38A-R1R2-FAS-02 e0a
Cluster B1560-38A-R1R2-FAS-02_clus2 169.254.206.17 B1560-38A-R1R2-FAS-02 e0b
Cluster B1560-38A-R1R2-FAS-02_clus3 169.254.160.224 B1560-38A-R1R2-FAS-02 e0c
Cluster B1560-38A-R1R2-FAS-02_clus4 169.254.233.247 B1560-38A-R1R2-FAS-02 e0d
Local = 169.254.64.107 169.254.74.5 169.254.124.178 169.254.212.103
Remote = 169.254.56.214 169.254.206.17 169.254.160.224 169.254.233.247
Cluster Vserver Id = 4294967293
Ping status:
................
Basic connectivity succeeds on 16 path(s)
Basic connectivity fails on 0 path(s)
................................................................
Detected 9000 byte MTU on 16 path(s):
Local 169.254.124.178 to Remote 169.254.160.224
Local 169.254.124.178 to Remote 169.254.206.17
Local 169.254.124.178 to Remote 169.254.233.247
Local 169.254.124.178 to Remote 169.254.56.214
Local 169.254.212.103 to Remote 169.254.160.224
Local 169.254.212.103 to Remote 169.254.206.17
Local 169.254.212.103 to Remote 169.254.233.247
Local 169.254.212.103 to Remote 169.254.56.214
Local 169.254.64.107 to Remote 169.254.160.224
Local 169.254.64.107 to Remote 169.254.206.17
Local 169.254.64.107 to Remote 169.254.233.247
Local 169.254.64.107 to Remote 169.254.56.214
Local 169.254.74.5 to Remote 169.254.160.224
Local 169.254.74.5 to Remote 169.254.206.17
Local 169.254.74.5 to Remote 169.254.233.247
Local 169.254.74.5 to Remote 169.254.56.214
Larger than PMTU communication succeeds on 16 path(s)
RPC status:
4 paths up, 0 paths down (tcp check)
4 paths up, 0 paths down (udp check)

-------------------------------------

B1560-38A-R1R2-FAS::*> network interface show
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
B1560-38A-R1R2-FAS
B1560-38A-R1R2-FAS-01_mgmt1
up/up 10.2.21.101/24 B1560-38A-R1R2-FAS-01
e0M true
B1560-38A-R1R2-FAS-02_mgmt1
up/up 10.2.21.103/24 B1560-38A-R1R2-FAS-02
e0M true
cluster_mgmt up/up 10.2.21.100/24 B1560-38A-R1R2-FAS-01
e0M true
Cluster
B1560-38A-R1R2-FAS-01_clus1
up/up 169.254.64.107/16 B1560-38A-R1R2-FAS-01
e0a true
B1560-38A-R1R2-FAS-01_clus2
up/up 169.254.74.5/16 B1560-38A-R1R2-FAS-01
e0b true
B1560-38A-R1R2-FAS-01_clus3
up/up 169.254.124.178/16 B1560-38A-R1R2-FAS-01
e0c true
B1560-38A-R1R2-FAS-01_clus4
up/up 169.254.212.103/16 B1560-38A-R1R2-FAS-01
e0d true
B1560-38A-R1R2-FAS-02_clus1
up/up 169.254.56.214/16 B1560-38A-R1R2-FAS-02
e0a true
B1560-38A-R1R2-FAS-02_clus2
up/up 169.254.206.17/16 B1560-38A-R1R2-FAS-02
e0b true
B1560-38A-R1R2-FAS-02_clus3
up/up 169.254.160.224/16 B1560-38A-R1R2-FAS-02
e0c true
B1560-38A-R1R2-FAS-02_clus4
up/up 169.254.233.247/16 B1560-38A-R1R2-FAS-02
e0d true
ABCD_svm_iscsi
iscsi_1 up/up 10.2.3.1/25 B1560-38A-R1R2-FAS-01
a0a true
iscsi_2 up/up 10.2.4.1/25 B1560-38A-R1R2-FAS-02
a0a true
ABCD_svm_shares
share_1_2003 up/up 10.2.2.9/24 B1560-38A-R1R2-FAS-01
a0b-2003
true
shares_1_2003
up/up 10.2.2.7/24 B1560-38A-R1R2-FAS-01
a0b-2003
true
shares_2_2003
up/up 10.2.2.8/24 B1560-38A-R1R2-FAS-02
a0b-2003
true
shares_3_2004
up/up 10.2.16.2/22 B1560-38A-R1R2-FAS-01
a0b-2004
true
shares_4_2004
up/up 10.2.16.3/22 B1560-38A-R1R2-FAS-02
a0b-2004
true
18 entries were displayed.

-----------------------------------------------

B1560-38A-R1R2-FAS::*> network port show

Node: B1560-38A-R1R2-FAS-01
Ignore
Speed(Mbps) Health Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status
--------- ------------ ---------------- ---- ---- ----------- -------- ------
a0a Default iSCSI up 1500 auto/- healthy false
a0b Default - up 1500 auto/- healthy false
a0b-2003 Default VLAN2003 up 1500 auto/- healthy false
a0b-2004 Default VLAN2004 up 1500 auto/- healthy false
e0M Default Default up 1500 auto/1000 healthy false
e0a Cluster Cluster up 9000 auto/10000 healthy false
e0b Cluster Cluster up 9000 auto/10000 healthy false
e0c Cluster Cluster up 9000 auto/10000 healthy false
e0d Cluster Cluster up 9000 auto/10000 healthy false
e0e Default - up 1500 auto/10000 healthy false
e0f Default - down 1500 auto/- - false
e0g Default - down 1500 auto/- - false
e0h Default - down 1500 auto/- - false
e0i Default - up 1500 auto/1000 healthy false
e0j Default - down 1500 auto/- - false
e0k Default - up 1500 auto/1000 healthy false
e0l Default - down 1500 auto/- - false
e3a Default - down 1500 auto/- - false
e3b Default - up 1500 auto/10000 healthy false
e4a Default - down 1500 auto/- - false
e4b Default - down 1500 auto/- - false

Node: B1560-38A-R1R2-FAS-02
Ignore
Speed(Mbps) Health Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status
--------- ------------ ---------------- ---- ---- ----------- -------- ------
a0a Default iSCSI up 1500 auto/- healthy false
a0b Default - up 1500 auto/- healthy false
a0b-2003 Default VLAN2003 up 1500 auto/- healthy false
a0b-2004 Default VLAN2004 up 1500 auto/- healthy false
e0M Default Default up 1500 auto/1000 healthy false
e0a Cluster Cluster up 9000 auto/10000 healthy false
e0b Cluster Cluster up 9000 auto/10000 healthy false
e0c Cluster Cluster up 9000 auto/10000 healthy false
e0d Cluster Cluster up 9000 auto/10000 healthy false
e0e Default - up 1500 auto/10000 healthy false
e0f Default - down 1500 auto/- - false
e0g Default - down 1500 auto/- - false
e0h Default - down 1500 auto/- - false
e0i Default - up 1500 auto/1000 healthy false
e0j Default - down 1500 auto/- - false
e0k Default - up 1500 auto/1000 healthy false
e0l Default - down 1500 auto/- - false
e3a Default - down 1500 auto/- - false
e3b Default - up 1500 auto/10000 healthy false
e4a Default - down 1500 auto/- - false
e4b Default - down 1500 auto/- - false
42 entries were displayed.

-----------------------------------

B1560-38A-R1R2-FAS::*> route show
Vserver Destination Gateway Metric
------------------- --------------- --------------- ------
B1560-38A-R1R2-FAS
0.0.0.0/0 10.2.21.254 20
ABCD_svm_shares
0.0.0.0/0 10.2.2.254 20
2 entries were displayed.

------------------------------------------

B1560-38A-R1R2-FAS::*> ifgrp show
Port Distribution Active
Node IfGrp Function MAC Address Ports Ports
-------- ---------- ------------ ----------------- ------- -------------------
B1560-38A-R1R2-FAS-01
a0a ip 02:a0:98:65:88:b3 partial e0e, e3a, e3b
a0b ip 02:a0:98:65:88:b2 full e0i, e0k
B1560-38A-R1R2-FAS-02
a0a ip 02:a0:98:65:c6:3b partial e0e, e3a, e3b
a0b ip 02:a0:98:65:c6:3a full e0i, e0k
4 entries were displayed.

Re: Netapp sending failed pings to cluster

maffo — Thu, 01 Apr 2021 12:15:37 GMT

This could be the same scenario mentioned in one of our KBs: Management port attempting to ping IPs routing through customer network - NetApp Knowledgebase

Can you try disabling CDP as the KB suggests?

Re: Netapp sending failed pings to cluster

Daisyahoy — Thu, 01 Apr 2021 13:08:09 GMT

Maffo,

Thanks for your response. My account is not a customer account so im unable to see the contents of the page.

Can you tell me the gist of what it says or copy some of it here?

Re: Netapp sending failed pings to cluster

maffo — Thu, 01 Apr 2021 13:15:52 GMT

the command to disable it would be (from CLI):

::> options cdpd.enable off

if you require further information or you see the issue persists after this change, please open a technical case for Support team to look into this.

Re: Netapp sending failed pings to cluster

Daisyahoy — Thu, 01 Apr 2021 14:24:56 GMT

Maffo,

Sorry this doesn't appear to have had any affect.

The syslog message is still appearing.

Thank you for your help.

Re: Netapp sending failed pings to cluster

Mjizzini — Fri, 02 Apr 2021 04:48:00 GMT

If Disabling CDPD didnt Help, There is a second internal workaround for burt 1216522. Please contact Technical support.

1216522 - Unexpected SNMP requests from ONTAP cluster sent to cluster IPspace or neighbor switches on the management network.

Re: Netapp sending failed pings to cluster

Daisyahoy — Tue, 06 Apr 2021 04:38:21 GMT

Hi Mjizzini,

When I click on the link it tell me access is denied.

topic Re: Netapp sending failed pings to cluster in ONTAP Discussions

Netapp sending failed pings to cluster

Re: Netapp sending failed pings to cluster

Re: Netapp sending failed pings to cluster

Re: Netapp sending failed pings to cluster

Re: Netapp sending failed pings to cluster

Re: Netapp sending failed pings to cluster

Re: Netapp sending failed pings to cluster