Scripted SSH access to MSA1510i stopped working -- looking for alternatives

[Mark H. Wood]

I have a couple of nice little Expect scripts that used to save our ADU and tech_support reports weekly in case of disaster.  Somehow a recent update of putty/plink broke this but I can't see how.  "plink -ssh -2 -T -l $user -pw $passWord $host" gets us:

FATAL ERROR: Server refused to start a shell/command
send: spawn id exp4 not open
    while executing
"send "show tech_support\r""

while "plink -ssh -2 -t -l $user -pw $passWord $host" yields:

Server refused to allocate pty
FATAL ERROR: Disconnected: Received unsolicited SSH_MSG_CHANNEL_SUCCESS
send: spawn id exp3 not open
    while executing
"send "show tech_support\r""

So it dislikes both requesting and not requesting a PTY.  ???

I managed to work out the URL to get a tech_support report, but I'd like the ADU report too.  Then I could give up on plink altogether and get what I need with wget.

Ideas?  Is there a table of report URLs somewhere that I haven't found yet?

I'd also like to find some way other than SSH to command a reboot from a script.  Ideas?  I need to reboot the thing from a cron job, to clean up accumulated weirdness that eventually leads to controller failure.  (We've had just about every part swapped out and nothing fixed it, so we work around it.)

BTW I'm doing all this from Linux so I need to use tools that I can get for that environment.