There is option to stop the receiver from the interface, then via ssh you can shut it down.
The actual stop will wait for all pending operation on the receiver level to complete which will ensure there is no corruption.
Actually are you doing this for some kind of maintenance?
Annual site shutdown for electrical safety checks.
So, when the 'Stop' operation is complete, I ssh onto the box and use the Linux 'shutdown' command?
Should I shut down the secondary first?
Yep that's all correct
In case the services don't come up automatically after you turn on the devices just type via ssh : NitroStart
Thank you very much for your help, alexander_h.
So, just to add alexander_h ..... we have gone back and forth internally a while back on this topic.
Here is what we do:
- Establish ssh sessions on both receivers in the HA pair
- secondary: NitroStop
- wait for the prompt
- prime: NitroStop
- wait for prompt
- secondary: init 0
- prime: init 0
When it comes to powering back up..... power up the Primary wait 30+ seconds then power up the Secondary. If you don't care if the secondary might beat the primary starting up and take the lead role, just power them up at the same time.
I would also recommend that you log in after the receivers are back up and run ha_status to make sure all is good. We still have HA receiver pairs show OK in the ESM but looking at ha_status output we see both are in secondary mode = bad.
Just wanted to note, the best way to perform NitroStop/NitroStart is to append "--nod" to the end which tells the script to only return a prompt when the stop is finished. To verify the status of the Stop/Start perform a "NitroStarted" which will report the status.
From personal experience we have had nothing but headaches with HA receiver pairs. I'm going to separate all the pairs and run them individually.
just my 2 cents