ONTAP Discussions

ping from ssh not recognized

MIKOFLYZONE
8,016 Views

Hello,

I have a problem that I think was already discussed but I'm unable to find it in older posts.

The ping command works just if I'm direclty connected to netapp, it I executed by passing the command to ssh is not working.

Did you know how to solve this problem? I would like to check the connection on the Disaster Recovery site directly on netapp,

without the need to check the snapmirror status...

Thanks.

See below the example:

BASH-myuser@myserver.rpc.intra /home/myuser# ssh root@fas2

fas2> ping fas4

fas4 is alive

fas2> exit

logout

Connection to fas2 closed.

BASH-myuser@myserver.rpc.intra /home/myuser#

BASH-myuser@myserver.rpc.intra /home/myuser#

BASH-myuser@myserver.rpc.intra /home/myuser# ssh root@fas2 ping fas4

ping not found.  Type '?' for a list of commands

BASH-myuser@myserver.rpc.intra /home/myuser# ssh root@fas2 help

?                   file                nfs                 snap               

acpadmin            flexcache           nfsstat             snaplock           

aggr                fpolicy             nis                 snapmirror         

autosupport         fsecurity           options             snapvault          

backup              ftp                 partner             snmp               

bmc                 halt                passwd              software           

cdpd                help                ping6               source             

cf                  hostname            pktt                sp           

BASH-myuser@myserver.rpc.intra /home/myuser# ssh root@fas2 priv

admin

BASH-myuser@myserver.rpc.intra /home/myuser# ssh root@fas2 sysconfig

        NetApp Release 8.2.1RC2 7-Mode: Sun Feb  9 16:18:31 PST 2014

9 REPLIES 9

senthilj
7,316 Views

Hi Guys, 

 

            We have a NetApp filer whicch is running pretty old ontap version 7.1. I have not been able to ping the storage and cannot login via ssh or telnet. All the shares both cifs nad nfs have lost access to the data. I someohow was able to login to the filer via Serial COM port and did basic test and found the network cards e0a and e0b are up and fine. We have configured vif with both of these interfaces. 

 

Any help to fix the issue is much appreciated.

 

Thanks

Faisal

RPHELANIN
7,298 Views

what is the output of ifconfig -a and rdfile /etc/rc

senthilj
7,289 Views

 

Hi, here is the output

 

 


filer> ifconfig -a
e0a: flags=848043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 02:a0:98:05:55:75 (auto-1000t-fd-up) flowcontrol full
trunked vif1
e0b: flags=848043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 02:a0:98:05:55:75 (auto-1000t-fd-up) flowcontrol full
trunked vif1
lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 9188
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
vif1: flags=848043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.10 netmask 0xfffffc00 broadcast 10.10.10.255
ether 02:a0:98:05:55:75 (Enabled virtual interface)


filer> rdfile /etc/rc
#Auto-generated by setup Mon Nov 2 06:33:36 EST 2015
hostname vcs0886
vif create multi vif1 -b ip e0a e0b
ifconfig vif1 `hostname`-vif1 mediatype auto netmask 255.255.252.0
route add default 10.10.10.1
routed on
options dns.domainname vcs.domain.com
options dns.enable on
options nis.domainname vlg
options nis.enable on

senthilj
7,229 Views

Hi, Did you get a chance to look at the ouput I have provided as requested by you?

 

RPHELANIN
7,223 Views

yes and it looks fine, do you have any vlans on your network?

senthilj
7,218 Views

Yes, we do have VLANs in our network

RPHELANIN
7,212 Views

if those vlans are used by hosts accessing the data then you need to add them to the rc file

 

https://library.netapp.com/ecmdocs/ECMP1196890/html/man1/na_vlan.1.html

 

senthilj
7,197 Views

Okay, I shall do that. First thing I should be able to ping the filer and able to access the filer via putty ssh or telnet which I am unable to. Currently I am able to access only via serial comm port.

JustinFarmiloe
5,911 Views

It's certainly weird behaviour, but it does work if you run "priv set diag" first e.g. ssh myfiler "priv set diag; ping myhost"

Public