Hi Guys I ran into this one last year doing some early testing on pre-release 8.0.1. Never occurred to me this is a bug that might be experienced in the field - my bad. It has since been reported as bug 485715 http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=485715. Although the bug report lists no workaround, I found that appending a command that takes a few seconds, like ping <something that isn't there> or "sysstat -c 1 3' gave the command you wanted time to complete output before the SSH connection is closed.
From one of my test scripts:
sshcmd $filer -qfl root 'priv set -q diag ; stats show vstorage ; ping 172.16.26.254'
Down side is that ping can take 15 seconds to time out, and there's no option in 7-mode to specify a timeout. Sysstat gives you control down to the second, but you have to scrub the output. Sorry, no sleep (ONTAP or me these days! ;-)
Please open a case with NetApp support and have them add you/your case as call_rec to burt 485715.
Thanks
Peter
-----Original Message----- From: A Darren Dunham [mailto:ddunham@taos.com] Sent: Friday, June 10, 2011 9:06 AM To: toasters@mathworks.com Subject: Re: Truncated SSH ouptut on 8.x?
On Thu, Jun 09, 2011 at 08:56:27PM -0400, tmac wrote:
Of course, f you know the right people...you can get the Ontap API
software.
I am able to query 8 different filers, collect info on about 200
volumes
(volume info, aggr info, qtree info--> which there are 1000's of
qtrees)
in about 3-4 seconds and no SSH involved at all.
perl library, jar file, .NET, c++...lots of different ways to plug into ONTAP
No question. But I still have many items running that are hideously complex and more than 10 years old. I can't convert them in any reasonable time frame.
And all our "by hand" administration is still via SSH, which is where we first noticed this. I was just able to get confirmation from this script that is using SSH as well.
It's very possible that by going around the shell/interpreter, the API transport would not be subject to this problem. I'll have to see if I can get that tested. Even if it's fine, I really need the SSH stuff to work because of the legacy scripts I have.