Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


You can define the services level failover domain and to configure the SRX nodes to work in the high availability mode using the services-redundancy-group parameter.



Services redundancy group identifier


Specify a signal route required for mastership enforcement to be used along with the route exist policy. You can configure the required route (active-signal route) to be used with if-route-exists condition and HA module will add this route to the routing table on moving to active role which will activate the policy to start advertising higher preference.


In spite of the split brain prevention mechanism, theoretically the nodes can still get in to a ACTIVE-ACTIVE state when the interchassis link is down and there are network issues on the probe router at the same time because of which it replies to probe requests from both the SRX nodes. In this case once the situation improves and the interchassis link is up, the node with lower local id backs off and takes the backup role. This behavior can be overridden by the optional activeness-priority configuration.

  • Range: 1 through 254


Specify the probe destination IP address for activeness determination.


Specify the backup signal route for the backup to advertise a medium priority. When the HA link is down or the current active relinquishes mastership after any failure, the active signal route is removed and the backup will overwrite the default routing preference towards the old active node with the medium priority.


Specify the designated floating IP address for the services redundancy group.


Specify to configure the BFD and IP monitoring.


Allows you to choose a specific peer when multiple HA peers are configured globally to the service redundancy group.


Enable packet forward engine to forward packets on backup node for the corresponding service redundancy group.


Configure one or multiple Interfaces which are required to be shut down to isolate the node in case of internal failures.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level


Release Information

Statement introduced in Junos OS Release 20.4R1.