In an SRX chassis cluster, the node that acts as secondary has the routing daemon always down because the primary node is in charge of the routing decisions. Because of this situation, a backup-router statement is required for management of the secondary node. For more information about the backup router functionality, see Configuring a Backup Router .

This article explains why a default route ( 0.0.0.0/0 ) should not be used under backup-router in an SRX chassis cluster and what is the correct way to implement the backup-router statement.

IP connectivity or management access to the secondary node of an SRX chassis cluster is not working properly or is working intermittently. Configuration under [edit system backup-router] is using a default route ( 0.0.0.0/0 ).

[edit system]
backup-router 1.1.1.1 destination 0.0.0.0/0;

Due to a system limitation, the destination address specified under backup-router must not be configured as 0.0.0.0/0 or ::/0 . The mask must be a non-zero value.

When configuring routes under backup-router , use specific prefixes rather than a default route. Note that if required, you can configure more than one prefix under the backup-router hierarchy.

[edit system]
backup-router 1.1.1.1 destination 192.168.10.0/24;