2010-08-22 02:21 AM
I have recently found that I cannot use my Windows 7 or 2008 R2 systems to connect to my filer via PerfMon to monitor stats like Volumes. When I try on my 2003 server it works ok. Does anyone else have this problem?
2010-08-23 01:15 AM
OK, it is within Sales Engineering Community (for NetApp & Partner SEs) & that's probably why you can't access this.
But I think you should be able to see Daniel's blog:
2010-08-23 01:52 AM
So I installed Utilities and SDK for Subsystem for UNIX-based Applications in Microsoft Windows 7 and Windows Server 2008 R2 on my Windows 7 PC. I needed to add the following directory to my %PATH%, C:\Windows\SUA\bin, since it contains all of the *NIX utils such as awk, grep, and . . . RSH. So now, when I open a command prompt, I can use RSH. So now, for example, I can do this:
rsh -l username:password filer version
On the other hand, when I try to now run perfstat I always get the message "RSH to filer myfiler fails! Quitting." I wonder if the app is looking for something other than just the rsh executable. Has anyone at NetApp ever tried this before?
Thanks for the link to the community site page I am able to see. I already knew about using plink in the past, and pretty much did the same, whereby I added plink to my path. Plink though gives me the same problems as above though, since I cannot run PerfMon or perstat with Plink. It just cuts short the installation of the Unix utils and adds a more secure layer of SSH connectivity.
2010-12-10 08:46 AM
hi - did you find a solution yet?
since neither rsh nor ssh is used by w2008-perfmon i wonder why everybody suggests installing unix-tools... i did, rsh is working fine - but perfmon not.
I took some wireshark-traces, perfmon uses smb/rpc.
i disabled smb v2.0 on my w2008-server - no success
i enabled smb v2 on my filer - no success
using w2003 perfmon discovers all entities to monitor - immediatly...
2010-12-13 04:29 AM
You've probably checked this already...
After receiving "RSH to filer myfiler fails! Quitting." error message once, I checked /etc/hosts.equiv and found that only "Admin" was allowed to establish connection from that particular server's IP address. So, I added the account that I was using to log on at the time and was instantly granted access.