04-13-2017 09:26 AM
Hi, here at the office we have a cluster with two SRX240H (node0, node1) v. 12.1X44-D60.2, by mistake one of the nodes (node1) was powered off and some changes where made and committed to the active node0.
Is it possible to just power on the node1, that is powered off, and make a config syncronization from the active node0?
Thank you for your help!
Solved! Go to Solution.
04-13-2017 11:22 PM
yes, you can power on the other node and then do a dummy commit on the other node which is the primary node and was processing the traffic, this way both the nodes will have the same configuration.
Remember not to do any commits on the node which just got rebooted.
However before doing any commits do check the cluster status, the control and the Fab links should be up on both the nodes.
04-17-2017 05:57 AM
Thank you! worked ok. Just another short question, now the two nodes are ok but in redundancy group 2 the primary/secondary nodes are with different status... node0 is the secondary one. Should I leave this and it's ok or do I need to change it manually ?
admin@fw1> show chassis cluster status
Cluster ID: 1 Node Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 1
node0 100 primary no no
node1 1 secondary no no
Redundancy group: 1 , Failover count: 1
node0 100 primary yes no
node1 1 secondary yes no
Redundancy group: 2 , Failover count: 2
node0 1 secondary yes no
node1 100 primary yes no
04-17-2017 06:21 AM
You can leave it as such. The status you are seeing is because you have configured the RG2 with higher priority for the node 1 and lesser priority for the node 0 and hence the devise with higher priority is prefered over the lower priority.
It is absolutely normal with the output that you are seeing.
"Please mark my response as solution accepted if it helped resolve your issue"