Subscribe

Systemshell - cant ssh to filer after systemshell session left open

Hi,

 

I am unable to ssh to a filer after accidentally leaving the systemshell logged in.

 

Ontap version is 8.1.4P6

 

Unlocked diaguser:

 

priv set advanced

useradmin diaguser unlock

useradmin diaguser password

******

systemshell

diag

******

 

and then hit ctrl-D rather than typing 'exit' first.

 

I am unable to access the filer via SSH or telnet since.

 

I was hoping that the session would time out but I've left it overnight and no joy Smiley Sad

 

P.S Yes I know I should'nt be playing with the system shell :P

 

Any ideas without reboot/takeover?

Re: Systemshell - cant ssh to filer after systemshell session left open

 

Danny -

 

Some lessons we have to learn the hard way - don't do that !

 

: )

 

Use the console connection ... ?

Or the SP ?

 


I hope this response has been helpful to you.

At your service,

Eugene E. Kashpureff, Sr.
Independent NetApp Consultant http://www.linkedin.com/in/eugenekashpureff
Senior NetApp Instructor, IT Learning Solutions http://sg.itls.asia/netapp
(P.S. I appreciate 'kudos' on any helpful posts.)

Re: Systemshell - cant ssh to filer after systemshell session left open

Managed to get in, phew.

 

Had to get access to the systemshell prompt non-interactively:

 

ssh user@filer "priv set advanced; systemshell"

 

Log in using user "diag"

 

then ps -ef to identify the hung session

 

kill -9 to terminate it

 

Smiley Happy