Netapp Rsh Error Permission Denied
Contents |
I cannot be held responsible if you take down your production systems! Tuesday, 8 February 2011 Configuring Netapp filer for rsh connections So you need to connect to your Netapp filer via rsh. Maybe for example you wish to coordinate the snapshot on a volume with some other specific events in a script, as I did to perform consistent Oracle database backups. So how do you set it up for this? First we need to check that the Netapp settings allow rsh, it is allowed https://kb.netapp.com/support/s/article/how-to-configure-and-enable-remote-shell-rsh-access-on-a-storage-system by default but it is worth us checking. Login to the filer via telnet and checks the rsh.enable parameter: Netapp_filer> options rsh.enable rsh.enable on If it is set to off, we will need to turn it on with: Netapp_filer> options rsh.enable=on Now we need to allow our host to connect via rsh. We will also define it for a specific user as we http://iamthelinuxsysadmin.blogspot.com/2011/02/configuring-netapp-filer-for-rsh.html don't want to.make the system too insecure by letting everyone run system commands on the filer! First we need read/write access to the root filesystem on the Netapp, so we need to share the /vol/vol0 volume with read/write permissions through the nfs section of the GUI - I am not going to document that step here as it is a common task when setting up nfs shares. I will however remind you to hit the "export all" button once you have set it up, otherwise you will be left scratching your head as to why you cannot mount the filesystem as expected! Now navigate to the /etc directory of this filesystem, and make a backup of the hosts and hosts.equiv files: Linux> cd /vol0/etc Linux> cp hosts hosts_080211 Linux> cp hosts.equiv hosts.equiv_080211 We know need to add our host to the hosts file, I.e. add the line: 1.2.3.4 our_host Then we need to add the hostname and account name to the hosts.equiv file. Here we are using the Oracle account so the line we will add is: our_host oracle Once this is complete, we should be a
telnet in) for CLI access get root mount of /vol/vol0/etc in a unix machint do to direct config on files. NOW = NetApp Support Site NetApp man pages ("mirror" by uyema.net) http://www.oocities.org/tho01/netapp.html RAID-DP IMHO Admin Notes Notes about NetApp export, NFS and Windows CIFS ACL permission issues. Best practices is for most (if not all) export points of NFS server is to implement root_squash. root http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/rsh-failed-after-changing-the-default-route-on-the-nim-server-4936410 on the nfs client is translated to user 'nobody' and would effectively have the lowest access permission. This is done to reduce accidents of user wiping out the whole NFS server content permission denied from their desktops. Sometime NetApp NFS exports are actually on top of filesystem using windows NT ACL, their file permission may show up as 777, but when it comes to accessing the file, it will require authentication from the Windows server (PDC/BDC or AD). Any user login name that does not have a match in windows user DB will have permission denied problems. Most unix client netapp rsh error with automount can access nfs server thru /net. However, admin should discourage the heavy reliance on /net. It is good for occassional use. /home/SHARE_NAME or other mount points should be provided, such as /corp-eng and /corp-it. This is because mount path will be more controllable, and also avoid older AIX bug of accessing /net when accessing NFS mounted volumes, access them as user instead of root, which get most priviledges squashed away. If the FS is accessible by Windows and Unix, it is best to make share name simple and keep them consistent. Some admin like to create matching \\net-app-svr1\share1 /net-app-svr1/share1 \\net-app-svr2\share2 /net-app-svr2/share2 I would recommend that in the unix side, that /net-app-svr1 be unified into a single automount map called like /project . This would mean all share names need to be uniq across all servers, but it help keep transparency that allows for server migration w/o affecting user's work behaviour. Old Filer to New Filer Migration problems: If copy files from Unix FS to Windows-style FS, there are likely going to be pitfalls. NDMP would copy the files, and permissions and date would be preserved, but ownership of the files may n
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX VoIP_News Inside-ERP I_am_the_dragon Inside-CRM maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Craig Borysowich Dennis Stevenson mircea_luca Richard DukeGanote iudithm Clinton Jones bracke Nikki Klein AbhaiTripathi Iqbalyk jakarman Adrian_Grigoriu knowscognosdoi COMPANIES GeoTrust Juniper Networks Silver Peak Sophos View All Topics View All Members View All Companies Toolbox for IT Topics UNIX Groups Ask a New Question IBM AIX The IBM AIX group is your premier resource for objective technical discussion and peer-to-peer support on IBM AIX. Home | Invite Peers | More UNIX Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. RSH Failed after Changing the Default Route on the NIM Server jtrauzzi asked Sep 17, 2012 | Replies (7) Hi, We are rsh to communicate to our systems from our NIM server. I had to change the default route to the second network gateway and now RSH fails with "rshd: 0826-813 Permission is denied" Does any