(1) Networker Server (Start Stop Services Command)?

  WIN       net start | stop nsrd

  UL         /etc/init.d/networker start | stop    (the script starts all necessary dependencies)

(2) Storage Node (Start Stop Services command)?

   same as client

(3) NMC console (Start Stop Services command)?

  WIN       net start | stop gstd

  UL         /etc/init.d/gstd start | stop

(4) Networker Client (Start Stop Services command)?

  WIN       net start | stop nsrd

  UL         /etc/init.d/networker start | stop    (the script starts all necessary dependencies)

Hi Bingo,

isn't the NetWorker client also running on the NMC console? In that case it's more precise to say for

(3) NMC console (Start Stop Services command)?

  WIN       net start | stop gstd

               net start | stop nsrd

  UL         /etc/init.d/gstd start | stop

               /etc/init.d/networker start | stop

You asked how to start NMC

There are dependencies/specific orders which NW &NMC has to follow. Please verify the process ids.

So if you start the NW server (nsrd) or the NMC server (gstd), it would automatically start the client daemon (nsrexecd) first. Of course, you can start the client daemon individually first.

However, if you stop the servers (nsrd / gstd) this will not automatically stop the client as well.

Please note this goes out the window with 18.2   the following do not exist there.

/etc/init.d/gstd

/etc/init.d/networker   

Anyone have new update?  

The legacy commands are still valid for Linux servers controlled by sysvinit.

For all other Linux system (controlled by systemd), use 'sysctl start | stop '.

There is no way to control the storage node daemon - it will be started/stopped as needed.

Well, this does not happen all the time but I did see this happen a couple of times in my test environment. I am no LINUX expert so dont know how to fix this or as to what went wrong. You can still use the following commands on NetWorker to start, stop or check status. 

service networker status/stop/start