How to access systemshell Node shell Netapp Cluster Mode Step by Step Guide

by Ravi Kumar Ankam · March 2, 2017

Systemshell is used to diagnose low level issues. To Access Node Shell in Netapp Cluster mode we have to enable and reset the password of diag user. Be very careful when your enabling and accessing systemshell of the node In this article we are going to see How to Access Systemshell Node Shell Netapp cluster Mode Step by Step Guide.

Note: If your not aware of Systemshell / Node Shell use it very carefully. Any command in Systemshell execute leads to direct impact on Netapp Head.

Access systemshell Node shell Netapp Cluster Mode

ARKIT-NA::> security login show -vserver ARKIT-NA -user-or-group-name diag

Vserver: ARKIT-NA
 Authentication Acct
User/Group Name Application Method Role Name Locked
---------------- ----------- -------------- ---------------- ------
diag console password admin no

As shown in above command output diag account is not locked. If diag user in locked state use below command to unlock diag user.

ARKIT-NA::> security login unlock -username diag -vserver ARKIT-NA

ARKIT-NA::> security login show -user-or-group-name diag

Vserver: ARKIT-NA
 Authentication Acct
User/Group Name Application Method Role Name Locked
---------------- ----------- -------------- ---------------- ------
diag console password admin no

Set the password to diag user

ARKIT-NA::> security login password -username diag -vserver ARKIT-NA

Enter a new password:
Enter it again:

Now change the privilege mode to diagnostic then login using diag user to systemshell.

ARKIT-NA::> set -privilege diagnostic

Warning: These diagnostic commands are for use by NetApp personnel only.
Do you want to continue? {y|n}: y

ARKIT-NA::*> system node systemshell -node ARKIT-NA02

Data ONTAP/amd64 (ARKIT-NA02) (pts/0)

login: diag
Password:
Last login: Wed Mar 1 22:59:42 from 169.254.100.246


Warning: The system shell provides access to low-level
diagnostic tools that can cause irreparable damage to
the system if not used properly. Use this environment
only when directed to do so by support personnel.

ARKIT-NA02% ps aux |grep ndmpd
root 3055 0.0 0.0 0 32 ?? WL 23Jun15 0:00.31 [ndmpd_dispatch_proc]
root 3056 0.0 0.0 0 32 ?? WL 23Jun15 0:00.32 [ndmpd_dispatch_proc]
root 3057 0.0 0.0 0 32 ?? WL 23Jun15 0:00.31 [ndmpd_dispatch_proc]
root 3058 0.0 0.0 0 32 ?? WL 23Jun15 0:00.31 [ndmpd_dispatch_proc]
root 3059 0.0 0.0 0 32 ?? WL 23Jun15 0:00.32 [ndmpd_dispatch_proc]
root 3386 0.0 0.0 0 16 ?? WL 23Jun15 0:05.67 [ndmpd2br_reply_thre]
root 3387 0.0 0.0 0 16 ?? WL 23Jun15 0:04.30 [ndmpd2br_svc_main]
root 23184 0.0 1.0 174776 42284 ?? Is 3:32AM 0:02.60 /sbin/ndmpd
root 23484 0.0 0.0 0 32 ?? WL 3:36AM 2:58.18 [ndmpd_proc]
root 25308 0.0 0.0 0 32 ?? WL 14Nov16 0:00.20 [ndmpd_proc]
root 51525 0.0 0.0 0 32 ?? WL 4Nov16 0:00.52 [ndmpd_proc]
root 51763 0.0 0.0 0 32 ?? WL 8Nov16 0:00.19 [ndmpd_proc]
diag 77221 0.0 0.0 14668 1328 0 S+ 3:27AM 0:00.00 grep ndmpd

ARKIT-NA02% sudo kill -9 51525
ARKIT-NA02%

Systemshell / Node shell Netapp cluster mode is like complete access to BSD core access

Conclusion

Node shell Netap Cluster Mode / Systemshell is used to collect low level diagnostic details, It’s just like Linux Terminal access with super user privileges. Use with care. In this mode most if the BSD commands will work.