ok I added on both filers options snapmirror.access host=remotehost1 options snapmiorror.access host=remotehost2 it seems to work. but after the successful resync. the volume was still only in read mode. I had to do a manual mscs failover to the other site node and a failback before the volume shows as writable. why is that? I am not using snapdrive ... View more

ok now i broke the mirror, destination drive is writable. but a reverse resync gives another error. SnapMirror transfer request from lun_19Jun2012_175417_vol_SnapMirror_20Jun2012_074939 to host eq-ntap2 at IP address 10.51.1.11 denied: check options snapmirror.access. ... View more

bnot sure what happened. it seems to be working now. but I am trying to setup a ms cluster across sites so I have snapmirror from source vol to destination vol. when i failover the ms cluster resource from source to destination, the destination drive remains as eadable only and not writable. what do I have to do to make that writable? ... View more

I believe the battery firmware was flashed last night. does it take a while before I can ssh back into it? ... View more

hi where would this be under? ... View more

what i mean is a cluster. I got 2 filers in a cluster. I want to test the failover and failback functionality. how do i do this? ... View more

just to test failover and failback. before I upgrade, how do I go that between 2 active filers? ... View more

perl ha-config-check.cgi -s filer1 filer2 == NetApp HA Configuration Checker v2.0.0 == Checking ssh logins ... Checking ssh logins ... OK Checking Data ONTAP versions... OK Checking licenses... OK Checking HA configuration identity... OK Checking cf status... OK Checking fcp cfmode settings... OK Checking options... OK Checking network configuration... c0a (192.168.1.82) on filer1 does not have a partner on filer2 c0b (192.168.2.57) on filer1 does not have a partner on filer2 e0P (192.168.0.32) on filer1 does not have a partner on filer2 c0a (192.168.1.6) on filer1 does not have a partner on filer2 c0b (192.168.2.44) on filer1 does not have a partner on filer2 e0P (192.168.3.145) on filer1 does not have a partner on filer2 Checking network config in /etc/rc OK No HA configuration issues found. Done. What are the network configuration errors? ... View more

ok i finally got it to work. I guess the copy and paste carried over some weird characters. i was able to scp the file to the filer and it works now. thanks a lot ... View more

you are saying i dont need to use authorized_keys? or just copy the .pub keys over? ... View more

on the filer itself in systemshell. ... View more

Its in there. its the correct path xxx% pwd /mroot/etc/sshd/root/.ssh xxx% ls -la total 12 drwx ... View more

i have no nfs or cifs license. ... View more

yes it is ... View more

directory permission is correct? xxxx% ls -la /root/.ssh lrwxrwxrwx 1 root wheel 19 Mar 16 2011 /root/.ssh -> /var/home/root/.ssh xxxxx% cd /var/home/root xxxxx% ls -la total 8 drwxr-xr-x 3 root wheel 512 May 3 2007 . drwxr-xr-x 5 root wheel 512 May 3 2007 .. drwx ... View more

this path is not right? filer\c$\etc\sshd\root\.ssh\authorized_keys i have no cifs license ... View more

ssh-keygen -t rsa -b 1024 ssh-keygen -t dsa -b 1024 cat id_dsa.pub > authorized_keys cat id_rsa.pub >> authorized_keys ... View more

still not working. strange. options ssh ssh.access * ssh.enable on ssh.idle.timeout 0 ssh.passwd_auth.enable on ssh.port 22 ssh.pubkey_auth.enable on ssh1.enable on ssh2.enable on authorized_keys is under filer\c$\etc\root\.ssh\authorized_keys authorized keys was generated from my mgmt workstation ... View more

ok i created the dir and put in the authorized_keys file under filer\c$\etc\sshd\root but still ssh from my management workstation asking for password ... View more

yes its that directory but I cannot create the root directory ... View more