File command on remote VNX (automated switchover )

yes i tried ssh ..

but have trouble to put this into a script ..

i created keys but had problems to add these key to ssh-agent to log in without password.

the connection is from one controlstation to other. so recovery from some simple scripts are easy after fileos upgrade, but i would not change the controlstation configuration.

Sven

I would suggest ssh

No .. The IP is on both sides the same. the active interface  on local is up .. on remote down.

i do switchover of FS , i do down the local interface , i do switchover vdm , i do bring up remote interface.  then all sessions (NFS) stay online .. transparent failover works fine ..

but bringing the remote interface up requires login to remote system and execute the server_ifconfig ..

the interface on remote VNX should alway be online (it has a different IP of course, but the name of the interface should be identical to that of the source). Is that different in your configuration ?

why do you need to bring the interface online manually ?

mhh  .. i was thinking if i do a switchover to remote vnx the interface is not going "up" automatically , if this is done ..fine .

i never check if the interface is going up after switchover the vdm.

this interface is used for NFS connectivity only, it's not assigned to any CIFS servers ?

Yes this System has NFS only. No Block , No Cifs ..

your remote VNX has the same subnet so you can use the same IP address ? Cool

So i would setup ssh keys (should be plenty of tutorials online) and then run the commands via ssh, ie:

ssh nasadmin@10.230.11.27 "NAS_DB=/nas /nas/bin/server_df server_2"

Yes these two system are in the same subnet. there are just 10km (7mi) away and connected with two 10g lines. these customer has also a stretched esx cluster over these 2 sites.

both systems hat 2 active FS and replication is to the other system .. so we can use all the nice stuff like FAST cache from both systems

the switchover / failover works like a charme but we have to connect to booth systems as described before.

I`m a good guy so was searching a lot "to execute a remote command" before opening this thread. I tried with ssh keys but hat the problem das the controlstation says

"cannot connect to ssh agent"  if i use ssh-add. I would not modifiy the cs configuration to get these working, because after next OS upgrade these changes are gone. 

Yes for NFS you can to a transparent failover by careful config and moving the IP

In newer codes nas_migrate will do this in an automated fashion

Important for NFS is:

- Need configure the same IP on the remote side

its critical to have the right sequence of dow’ing and up’ing the interfaces there to avoid stale file handles or dup IP

In the latest codes there is an option to create an interface in the down state

- Fsid’s need to be same on both sides – replicator will (silently) try to aquire the same fsid when setup up a replication

but if that fsid is already in use on the remote system it will pick the next available one

- The replication needs to be in a state where the last few changes need to be transferred – then we can failover in less than 60s

setting the minimum possible RTO before the failover and making sure it doesn’t have a lot of data to catch up helps

Configuration in the nasadmin homedir shouldnt be overwritten by a code upgrade

ok, so how do you expect to get password-less authentication to work without setting up public keys on target control station ?

I think , the discussion drift away ... failover works fine ..all NFS-Volumes stay online (yes i also run into the fsid "feature"..) but to have bring up the remote interface online from the same vnx i do the switchover was a goodie , what i would have to fix.

it is cool to have a "all-in-one" script.

I tried to create sshkeys, copy them .. add them but at the point to execute the ssh-add command this failed with connect "cannot connect so ssh-agent" why? i have no idea.

i was hoping that there could be a easy way i have just not found , something like using navicli .. to execute commands on remote vnx.

There is no customer exposed functionality to execute commands on another control station.

Ssh setup shouldn’t be too difficult – I have done it a while ago and don’t remember having problems setting it up after a quick google and reading of the man pages.