topic Re: FAS node is reachable but not able to ping gateway in ONTAP Hardware

FAS node is reachable but not able to ping gateway

sed_streaming — Wed, 04 Jun 2025 16:09:24 GMT

Hi all,

we have a FA2520 with ONTAP 9.1RC2.

The port e0M on node 2 is reachable and answers to ping.

However if from a shell we type

ping -node node02 -destination 192.168.100.1 (gateway address)

the node can't reach it. It can't ping any host.

other node has no issue.

Re: FAS node is reachable but not able to ping gateway

Naveenpusuluru — Wed, 25 Jan 2017 15:21:23 GMT

Hi @sed_streaming

Can you please ping me the below commands outputs.

net int show

route show

node run -node nodename -command ifconfig -a

Re: FAS node is reachable but not able to ping gateway

sed_streaming — Wed, 25 Jan 2017 15:32:49 GMT

Here are commands result.

encoder-storage::> net int show
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
encoder-storage-01_clus1
up/up 169.254.214.203/16 enc01 e0d true
encoder-storage-01_clus2
up/up 169.254.223.169/16 enc01 e0f true
encoder-storage-02_clus1
up/up 169.254.249.116/16 enc02 e0d true
encoder-storage-02_clus2
up/up 169.254.92.76/16 enc02 e0f true
aspera_svm1
aspera_svm1_nfs_lif1
up/up 192.168.213.240/24 enc01 e0c true
aspera_svm1_nfs_lif2
up/up 192.168.213.251/24 enc01 e0e true
encoder-storage
cluster_mgmt up/up 192.168.213.235/24 enc01 e0M true
enc01_mgmt up/up 192.168.213.236/24 enc01 e0M true
enc02_mgmt up/up 192.168.213.237/24 enc02 e0M true
encoder_svm
encoder_svm_cifs_lif1
up/up 192.168.213.221/24 enc02 e0c true
encoder_svm_nfs_lif1
up/up 192.168.213.222/24 enc02 e0e true
11 entries were displayed.

encoder-storage::> route show
Vserver Destination Gateway Metric
------------------- --------------- --------------- ------
aspera_svm1
0.0.0.0/0 192.168.213.1 20
encoder-storage
0.0.0.0/0 192.168.213.1 20
encoder_svm
0.0.0.0/0 192.168.213.1 20
3 entries were displayed.

encoder-storage::> node run -node enc02 -command ifconfig -a
e0a: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:a0:98:8b:52:12 (auto-unknown-down) flowcontrol full
e0b: flags=0x170c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:a0:98:8b:52:13 (auto-unknown-down) flowcontrol full
e0c: flags=0x1f0c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO> mtu 1500
inet 192.168.213.221 netmask 0xffffff00 broadcast 192.168.213.255 noddns DATA
ether 00:a0:98:8b:52:18 (auto-1000t-fd-up) flowcontrol none
e0d: flags=0x1f0c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO,CLUSTER_PORT> mtu 9000
inet 169.254.249.116 netmask 0xffff0000 broadcast 169.254.255.255 noddns CLUSTER
ether 00:a0:98:8b:52:19 (auto-10g_t-fd-up) flowcontrol none
e0e: flags=0x1f0c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO> mtu 1500
inet 192.168.213.222 netmask 0xffffff00 broadcast 192.168.213.255 noddns DATA
ether 00:a0:98:8b:52:1a (auto-1000t-fd-up) flowcontrol none
e0f: flags=0x1f0c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,LRO,CLUSTER_PORT> mtu 9000
inet 169.254.92.76 netmask 0xffff0000 broadcast 169.254.255.255 noddns CLUSTER
ether 00:a0:98:8b:52:1b (auto-10g_t-fd-up) flowcontrol full
e0M: flags=0x1b0c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,MGMT_PORT> mtu 1500
inet 192.168.213.237 netmask 0xffffff00 broadcast 192.168.213.255 noddns NODE MGMT
ether 00:a0:98:8b:52:14 (auto-1000t-fd-up) flowcontrol none
e0P: flags=0x1b0c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,ACP_PORT> mtu 1500 PRIVATE
inet 192.168.1.131 netmask 0xfffffc00 broadcast 192.168.3.255 noddns
ether 00:a0:98:8b:52:15 (auto-1000t-fd-up) flowcontrol full
lo: flags=0x1b08049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 9188
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
losk: flags=0x40a000c9<UP,LOOPBACK,RUNNING> mtu 9188
inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1

Re: FAS node is reachable but not able to ping gateway

Naveenpusuluru — Wed, 25 Jan 2017 15:48:32 GMT

Hi @sed_streaming

Try to add route between those two networks like below and try again.

route add -vserver EDCNETAPPCL01 -destination 192.168.100.1/24 -gateway 192.168.213.1 -metric 20

Re: FAS node is reachable but not able to ping gateway

sed_streaming — Wed, 25 Jan 2017 16:31:17 GMT

Hi Naveenpusuluru,

sorry for the disguide but the gateway is 192.168.213.1 so the node already have it. 192.168.100.1 was a mistype

Re: FAS node is reachable but not able to ping gateway

Naveenpusuluru — Wed, 25 Jan 2017 16:35:55 GMT

Hi @sed_streaming

May i know the reason why you want to ping other ip gateways

Re: FAS node is reachable but not able to ping gateway

sed_streaming — Wed, 25 Jan 2017 16:40:40 GMT

Hi,

maybe I'm not explayned well.

It can't ping any address. So it can retrieve software updates from ftp.

Is like the managemente interface can't communicate with outside world.

Re: FAS node is reachable but not able to ping gateway

Naveenpusuluru — Wed, 25 Jan 2017 18:39:02 GMT

You can't do it. If you want to ping netapp node to outside of network you need to create route for that.

Re: FAS node is reachable but not able to ping gateway

sed_streaming — Thu, 26 Jan 2017 09:24:27 GMT

But I can from node 1. not from node 2.

On system manager I have this error under events tab: csm.sessionFailed: Cluster interconnect session (req=enc01:dblade, rsp=enc01:dblade, uniquifier=110546fba4dbdacf) failed with record state ACTIVE and error CSM_CONNABORTED.

I think is related to the fact that node 2 can't reach node 1.