topic Re: Node Managment failing ping to cluster in ONTAP Discussions

Node Managment failing ping to cluster

Daisyahoy — Wed, 04 Jun 2025 11:03:25 GMT

Hi,

I have a Management Node on my system that is sending pings to a cluster interface that isn't completing the ping and being directed out to the network infrastructure. I only know about it as its showing in that switch's logs sent to the syslog server.

2020-06-26 11:58:39 Local2.Info B1560-38A-R1R3-MGT1-INT 5880379: Jun 26 16:58:38.357 UTC: %SEC-6-IPACCESSLOGDP: list ACL-TRANSIT-MGMT-IN denied icmp 10.2.21.103 -> 169.254.206.17 (0/0), 19 packets

Its as if it cant hit the 169 cluster ip and being directed out with the zero route.

But if I run some basic ping tests and interface checks the system seems to be ok.

****** Sorry for formatting, attached text document**********

B1560-38A-R1R2-FAS::cluster*> 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*> 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::cluster*> up

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
jrtc_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
jrtc_svm_shares
share_1_2003 up/up 10.2.2.9/24 B1560-38A-R1R2-FAS-02
a0b-2003
false
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
Press <space> to page down, <return> for next line, or 'q' to quit...
18 entries were displayed.

B1560-38A-R1R2-FAS::*>
application autobalance cluster event
exit history job lun
man metrocluster network protection-type
qos redo rows run
san security set snaplock
snapmirror statistics statistics-v1 storage
storage-service system top up
volume vserver

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

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.

****** Sorry for formatting, attached text document**********

Im not sure why .17 is the only one it is sending the ping to and why it is directed out to the network if it can ping it with a test.

Any help is appreciated, this doesnt seem to be a huge issue but it is clogging up our logs.

Thanks

Re: Node Managment failing ping to cluster

TMACMD — Sat, 27 Jun 2020 03:17:26 GMT

How about:

Is CDP/LLDP enabled on your nodes?

system node run -node * "options cdpd.enable on ; options lldp.enable on"

Wait 3 full minutes after enabling. Then do

set -priv adv
cluster-switch show
network device-discovery show

Send that output please

Re: Node Managment failing ping to cluster

Daisyahoy — Mon, 29 Jun 2020 12:44:17 GMT

Thanks for your help.

I think I was messing up your commands some how.

txt file attached

B1560-38A-R1R2-FAS::> system node run -node B1560-38A-R1R2-FAS-02 * "options ?
* not found. Type '?' for a list of commands

B1560-38A-R1R2-FAS::> system node run -node B1560-38A-R1R2-FAS-02 * "options cdpd.enable on ; options lldp.enable on"
* not found. Type '?' for a list of commands
You are changing option lldp.enable, which applies to
both members of the HA configuration in takeover mode.
This value must be the same on both HA members to ensure correct
takeover and giveback operation.

B1560-38A-R1R2-FAS::> system node run -node B1560-38A-R1R2-FAS-01 * "options cdpd.enable on ; options lldp.enable on"
* not found. Type '?' for a list of commands
You are changing option lldp.enable, which applies to
both members of the HA configuration in takeover mode.
This value must be the same on both HA members to ensure correct
takeover and giveback operation.

B1560-38A-R1R2-FAS::> system node run -node B1560-38A-R1R2-FAS-02 options cdpd.enable on?
No such option ?

B1560-38A-R1R2-FAS::> system node run -node B1560-38A-R1R2-FAS-02 options cdpd.enable on

B1560-38A-R1R2-FAS::> system node run -node B1560-38A-R1R2-FAS-01 options cdpd.enable on

B1560-38A-R1R2-FAS::> set -priv advanced

Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
Do you want to continue? {y|n}: y

B1560-38A-R1R2-FAS::*> cluster-switch show
show show-all

B1560-38A-R1R2-FAS::*> cluster-switch show
(system cluster-switch show)
This table is currently empty.

B1560-38A-R1R2-FAS::*> network device-discovery show
Node/ Local Discovered
Protocol Port Device (LLDP: ChassisID) Interface Platform
----------- ------ ------------------------- ---------------- ----------------
B1560-38A-R1R2-FAS-02/cdp
e0a B1560-38A-R1R2-FAS-01 e0a FAS8040
e0b B1560-38A-R1R2-FAS-01 e0b FAS8040
e0c B1560-38A-R1R2-FAS-01 e0c FAS8040
e0d B1560-38A-R1R2-FAS-01 e0d FAS8040
B1560-38A-R1R2-FAS-02/lldp
e0a B1560-38A-R1R2-FAS-01 (00:a0:98:65:88:b2)
e0a -
e0b B1560-38A-R1R2-FAS-01 (00:a0:98:65:88:b2)
e0b -
e0c B1560-38A-R1R2-FAS-01 (00:a0:98:65:88:b2)
e0c -
e0d B1560-38A-R1R2-FAS-01 (00:a0:98:65:88:b2)
e0d -
e0e B1560-38A-R1R3-UCSFI-01-FA-B (8c:60:4f:4b:85:a0)
Eth1/25 -
e0i B1560-38A-R1R3-UCSFI-01-FA-B (8c:60:4f:4b:85:a3)
Eth1/28 -
e0k B1560-38A-R1R3-UCSFI-01-FA-B (8c:60:4f:4b:85:a2)
Eth1/27 -
e3b B1560-38A-R1R3-UCSFI-01-FA-B (8c:60:4f:4b:85:a1)
Eth1/26 -
B1560-38A-R1R2-FAS-01/cdp
e0a B1560-38A-R1R2-FAS-02 e0a FAS8040
e0b B1560-38A-R1R2-FAS-02 e0b FAS8040
e0c B1560-38A-R1R2-FAS-02 e0c FAS8040
e0d B1560-38A-R1R2-FAS-02 e0d FAS8040
B1560-38A-R1R2-FAS-01/lldp
e0a B1560-38A-R1R2-FAS-02 (00:a0:98:65:c6:3a)
e0a -
e0b B1560-38A-R1R2-FAS-02 (00:a0:98:65:c6:3a)
e0b -
e0c B1560-38A-R1R2-FAS-02 (00:a0:98:65:c6:3a)
e0c -
e0d B1560-38A-R1R2-FAS-02 (00:a0:98:65:c6:3a)
e0d -
e0e B1560-38A-R1R3-UCSFI-01-FA-A (8c:60:4f:4b:83:20)
Eth1/25 -
e0i B1560-38A-R1R3-UCSFI-01-FA-A (8c:60:4f:4b:83:22)
Eth1/27 -
e0k B1560-38A-R1R3-UCSFI-01-FA-A (8c:60:4f:4b:83:23)
Eth1/28 -
e3b B1560-38A-R1R3-UCSFI-01-FA-A (8c:60:4f:4b:83:21)
Eth1/26 -
24 entries were displayed.

Re: Node Managment failing ping to cluster

TMACMD — Mon, 29 Jun 2020 13:33:48 GMT

Ok. Thanks. Now how about this data:

route show
ifgrp show
system node run -node B1560-38A-R1R2-FAS-02_clus2 ifstat e0b

Re: Node Managment failing ping to cluster

Daisyahoy — Mon, 29 Jun 2020 14:04:45 GMT

B1560-38A-R1R2-FAS::*> route show
Vserver Destination Gateway Metric
------------------- --------------- --------------- ------
B1560-38A-R1R2-FAS
0.0.0.0/0 10.2.21.254 20
XXXX_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.

B1560-38A-R1R2-FAS::*> system node run -node ?
B1560-38A-R1R2-FAS-01
B1560-38A-R1R2-FAS-02

B1560-38A-R1R2-FAS::*> system node run -node B1560-38A-R1R2-FAS-02?
B1560-38A-R1R2-FAS-02

B1560-38A-R1R2-FAS::*> system node run -node B1560-38A-R1R2-FAS-02 ifstat e0b

-- interface e0b (86 days, 16 hours, 27 minutes, 29 seconds) --

Re: Node Managment failing ping to cluster

TMACMD — Mon, 29 Jun 2020 15:03:10 GMT

Ok. really weird (so far).

Are you doing anything like BGP or any non-standard networking with ONTAP?

Looks like a switchless cluster using 4-ports (e0a/e0b/e0c/e0d).

There are two IFGRPs (going directly to UCS Fabric Interconnects)

(This works, but you can get better failover capability using external switches instead of the UCS)

Node 1 connects to FI-A and Node-2 connects to FI-B.

(Also, technically, in this particular config, I think you are still supposed to attach both node to both FIs)

Where did the message originate from? ONTAP?

2020-06-26 11:58:39 Local2.Info B1560-38A-R1R3-MGT1-INT 5880379: Jun 26 16:58:38.357 UTC: %SEC-6-IPACCESSLOGDP: list ACL-TRANSIT-MGMT-IN denied icmp 10.2.21.103 -> 169.254.206.17 (0/0), 19 packets

Any idea which file (if from ONTAP, which I think it is)

Did you make *any* modifications to the ONTAP firewall policies?

the Cluster network is in a different IPspace from everything else so I am trying to figure how the ICMP crossed boundaries?

Lastly, which ONTAP version?

Re: Node Managment failing ping to cluster

Daisyahoy — Mon, 29 Jun 2020 15:47:39 GMT

So we took over a project after it was built and tested. So the reasoning behind many things, I'm unsure of.

Also a headsup, I have a cisco networking background but Netapp is pretty new to me.

Lastly, which ONTAP version?

9.7P2

Where did the message originate from? ONTAP?

This message is on our syslog server. The message was sent by a managment switch. The switch blocks this traffic and logs it as the 169.x.x.x traffic is not in the allowed ip space on that switch. Its also strange to me that it knows how to get to its destination but still sends it out to a Management switch.

*Attaching a snippet png of a network diagram for this particular area*

*Just updated that snippet after discovering we aren't so redundant*

Did you make *any* modifications to the ONTAP firewall policies?

I personally haven't. I can check for something if you like.

Are you doing anything like BGP or any non-standard networking with ONTAP?

I don't believe so. Internally i believe its standard ip routing. External to ontap the rest of the network uses OSPF.

Node 1 connects to FI-A and Node-2 connects to FI-B.

(Also, technically, in this particular config, I think you are still supposed to attach both node to both FIs)

that

I was confused at what you meant but now I see that each Node shows 4 links to one FI. The UCS shows these configured as 2x Access and 2x Trunk for each. That may be a project for later lol.

Re: Node Managment failing ping to cluster

TMACMD — Mon, 29 Jun 2020 16:01:21 GMT

I would keep an eye on it for a little while. Maybe even open a case.

Right now, I have no idea (yet) how that communication path can be established.

If you find an answer, please let us know.

Re: Node Managment failing ping to cluster

Daisyahoy — Mon, 29 Jun 2020 17:50:08 GMT

Ok, thanks for your help sir.

Re: Node Managment failing ping to cluster

maffo — Mon, 29 Jun 2020 20:43:48 GMT

ONTAP should never ping from management interfaces to cluster network interfaces, 169.254.x.x network cannot be routed.

Has this cluster ever been converted between switchless/switched?

Also if you have opened a case feel free to pm me the case number so I can try having a look.

Re: Node Managment failing ping to cluster

GidonMarcus — Mon, 29 Jun 2020 20:57:04 GMT

Hi,

can you print us the routing table? is the issue still happens?

network route active-entry show

Also - i don't currently have a simulator in hand to check if it works, but can you try get these

netstat -rn and route -s commands from the node level (node run * "priv set diag;netstat -rn;route -s") ?

Re: Node Managment failing ping to cluster

Daisyahoy — Thu, 08 Oct 2020 15:12:46 GMT

Sir,

Extreme apologies for taking so long to reply. In all honesty I didn't even know I had more replies to this thread.

Anywho,

Here is the output for the command you mentioned.

Vserver: B1560-38A-R1R2-FAS
Node: B1560-38A-R1R2-FAS-01
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
10.2.21.0/24 link#2 e0M 60
10.2.21.0/24 link#2 e0M 60
10.2.21.100 link#2 lo0 1
10.2.21.101 link#2 lo0 1
127.0.0.1 link#7 "" 1
127.0.0.1 link#7 lo0 1
127.0.10.1 link#7 lo0 1
127.0.20.1 link#7 lo0 1
default 10.2.21.254 e0M 65 UGS
default 10.2.21.254 e0M 65 UGS

Vserver: B1560-38A-R1R2-FAS
Node: B1560-38A-R1R2-FAS-01
Subnet Group: ::/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
::1 link#7 lo0 1

Vserver: B1560-38A-R1R2-FAS
Node: B1560-38A-R1R2-FAS-02
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
10.2.21.0/24 link#2 e0M 60
10.2.21.103 link#2 lo0 1
127.0.0.1 link#7 "" 1
127.0.0.1 link#7 lo0 1
127.0.10.1 link#7 lo0 1
127.0.20.1 link#7 lo0 1
default 10.2.21.254 e0M 65 UGS

Vserver: B1560-38A-R1R2-FAS
Node: B1560-38A-R1R2-FAS-02
Subnet Group: ::/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
::1 link#7 lo0 1

Vserver: Cluster
Node: B1560-38A-R1R2-FAS-01
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
127.0.0.1 link#1 lo0 1
127.0.10.1 link#1 lo0 1
127.0.20.1 link#1 lo0 1
169.254.0.0 link#2 e0a 7
169.254.0.0 link#3 e0b 7
169.254.0.0 link#4 e0c 7
169.254.0.0 link#5 e0d 7
169.254.124.178 link#4 lo0 1
169.254.212.103 link#5 lo0 1
169.254.64.107 link#2 lo0 1
169.254.74.5 link#3 lo0 1

Vserver: Cluster
Node: B1560-38A-R1R2-FAS-02
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
127.0.0.1 link#1 lo0 1
127.0.10.1 link#1 lo0 1
127.0.20.1 link#1 lo0 1
169.254.0.0 link#2 e0a 7
169.254.0.0 link#3 e0b 7
169.254.0.0 link#4 e0c 7
169.254.0.0 link#5 e0d 7
169.254.160.224 link#4 lo0 1
169.254.206.17 link#3 lo0 1
169.254.233.247 link#5 lo0 1
169.254.56.214 link#2 lo0 1

Vserver: ABCD_svm_iscsi
Node: B1560-38A-R1R2-FAS-01
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
10.2.3.0/25 link#1 a0a 7
10.2.3.1 link#1 lo0 1

Vserver: ABCD_svm_iscsi
Node: B1560-38A-R1R2-FAS-01
Subnet Group: ::/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
::1 link#7 lo0 1

Vserver: ABCD_svm_iscsi
Node: B1560-38A-R1R2-FAS-02
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
10.2.4.0/25 link#1 a0a 7
10.2.4.1 link#1 lo0 1
127.0.0.1 link#7 lo0 1
127.0.10.1 link#7 lo0 1
127.0.20.1 link#7 lo0 1

Vserver: ABCD_svm_iscsi
Node: B1560-38A-R1R2-FAS-02
Subnet Group: ::/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
::1 link#7 lo0 1

Vserver: ABCD_svm_shares
Node: B1560-38A-R1R2-FAS-01
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
10.2.16.0/22 link#23 a0b-2004 60
10.2.16.2 link#23 lo0 1
10.2.2.0/24 link#22 a0b-2003 60
10.2.2.0/24 link#22 a0b-2003 60
10.2.2.7 link#22 lo0 1
10.2.2.9 link#22 lo0 1
127.0.0.1 link#7 lo0 1
127.0.10.1 link#7 lo0 1
127.0.20.1 link#7 lo0 1
default 10.2.2.254 a0b-2003 65 UGS
default 10.2.2.254 a0b-2003 65 UGS

Vserver: ABCD_svm_shares
Node: B1560-38A-R1R2-FAS-01
Subnet Group: ::/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
::1 link#7 lo0 1

Vserver: ABCD_svm_shares
Node: B1560-38A-R1R2-FAS-02
Subnet Group: 0.0.0.0/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
10.2.16.3 link#23 lo0 1
10.2.2.0/24 link#22 a0b-2003 60
10.2.2.8 link#22 lo0 1
127.0.0.1 link#7 lo0 1
127.0.10.1 link#7 lo0 1
127.0.20.1 link#7 lo0 1
default 10.2.2.254 a0b-2003 65 UGS

Vserver: ABCD_svm_shares
Node: B1560-38A-R1R2-FAS-02
Subnet Group: ::/0
Destination Gateway Interface Metric Flags
---------------------- ------------------- --------- ------ -----
::1 link#7 lo0 1
74 entries were displayed.

Re: Node Managment failing ping to cluster

Daisyahoy — Thu, 08 Oct 2020 15:16:18 GMT

Sorry, I'm pretty ignorant when it comes to netapp tech.

When you say "from the node level" what exactly do you mean?

Thanks for your help.

Re: Node Managment failing ping to cluster

isc-dario — Tue, 10 Aug 2021 12:04:58 GMT

Is there a solution as we have the same problem with one node only (in a two node switchless cluster)?