Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
The FAS2040s we are using appear to allow only one simultaneous SSH session to a head.
We have a problem in that we have a 'lost' SSH session on one of our 2040s - the SSH client program has crashed, yet the filer appears to think it is still up, since we can't log another ssh session in.
I've tried using the Filer View web interface Filer->Use Command Line, but that appears similarly afflicted.
Whilst I'm sure I could resolve this by rebooting the filer, is there a more graceful solution to clean up this ssh session?
I can mount to /vol/vol0 - is there anything I can do to the file system to kill the existing SSH session details?
Also, is there a configuration option to allow more than one concurrent SSH access?
Thanks for the replies so far. I've managed to restore ssh access. The previous ssh session was running a script over the weekend. I believe the script was still running on the filer despite the ssh session crashing (or the ssh client session timing out), since after accessing the filer via the serial connection (and seeing no prompt), I pressed control-C, at which point the filer prompt reappeared. Having now killed this running process and exiting the serial connection session, I am able to ssh into the filer again