This procedure should be followed in case you want to isolate a node from the cluster for troubleshooting purposes. After troubleshooting, you can then rejoin the node to the cluster.

 Perform the following procedure to isolate the node from the cluster.

1. Disable preempt for RG1+ groups on the cluster.
2.  Deactivate interface-monitoring and IP-monitoring
3. Save the configuration to a file on the working node using the following command:
   • show configuration | save /var/tmp/backupconfig.txt 
4. Take console access.
5. Remove all the revenue ports from the node that need to be isolated.
6. Remove the control link and fabric link from the node that needs to be isolated.
7. Once the control link and fabric link are removed, you will see the status of the other node as "lost" in "show chassis cluster status" command output.

1. If the node has cluster enabled and configuration added already move to step 7, if not continue with step 2. 
2. Enable the chassis cluster again by following the command "set chassis cluster cluster-id <id> node <No.>". NOTE: Cluster-id should same as the already working node.
3. Reboot the node. The node will come online with the cluster being enabled:
4. Load the backup config on node by any one of the methods below  (5 or 6)
5. Using the command "load override terminal or load set terminal" When the configuration is completely loaded, commit the configuration.
6. Enter into configuration mode and load the configuration from the file, which was copied in the /var/tmp directory in Step 1. Use the following command to load the configuration:  "load override /var/tmp/ <filename>  "When the configuration is completely loaded, commit the configuration
7. Halt or Power off the node (For SRX1500 and SRX4k series, 'request system halt' won't work') 
   • request system halt
   • request system power-off
8. Now connect the fabric and control ports (make sure that none of the revenue port cables are connected) and reboot the node.
9. Check the status of the FPC PIC by executing the "show chassis fpc pic-status" command. In the output, all of the FPCs and PICs should be online
10. When node 0 comes online, it should join the cluster as the secondary. You can check the status by executing the "show chassis cluster status" command.
11. In the output, the priority of RG0 should be the configured value, and the priority of the other RG should be 0 if interface monitoring has been configured(not deactivated).
12. Connect the revenue ports back on Node 0.