Too many routes were configured under the backup-router hierarchy on the cluster secondary node, which caused SSH access failure.

Too many backup routes cause the node1 forwarding table fails to generate some routing entries.

For example, node1 cannot generate 172.16.3.18/32 in the forwarding table. When SSH node1's fxp0 from 172.16.3.18/32, SSH session times out and SSH cannot be established.

  node1 {

    system {

      backup-router 192.168.1.254 destination [ 10.1.1.1/32 10.1.1.2/32 10.1.1.3/32 10.1.1.4/32 10.1.1.5/32 10.1.1.6/32 10.1.1.7/32 10.1.1.8/32 10.1.1.9/32 10.1.1.10/32 10.1.1.11/32 10.1.1.12/32 10.1.1.13/32 10.1.1.14/32 10.1.1.15/32 10.1.1.16/32 10.1.1.17/32 10.1.1.18/32 172.16.1.1/32 172.16.1.2/32 172.16.1.3/32 172.16.1.4/32 172.16.1.5/32 172.16.1.6/32 172.16.1.7/32 172.16.1.8/32 172.16.1.9/32 172.16.1.10/32 172.16.1.11/32 172.16.1.12/32 172.16.1.13/32 172.16.1.14/32 172.16.1.15/32 172.16.1.16/32 172.16.1.17/32 172.16.1.18/32 172.16.2.1/32 172.16.2.2/32 172.16.2.3/32 172.16.2.4/32 172.16.2.5/32 172.16.2.6/32 172.16.2.7/32 172.16.2.8/32 172.16.2.9/32 172.16.2.10/32 172.16.2.11/32 172.16.2.12/32 172.16.2.13/32 172.16.2.14/32 172.16.2.15/32 172.16.2.16/32 172.16.2.17/32 172.16.2.18/32 172.16.3.1/32 172.16.3.2/32 172.16.3.3/32 172.16.3.4/32 172.16.3.5/32 172.16.3.6/32 172.16.3.7/32 172.16.3.8/32 172.16.3.9/32 172.16.3.10/32 172.16.3.11/32 172.16.3.12/32 172.16.3.13/32 172.16.3.14/32 172.16.3.15/32 172.16.3.16/32 172.16.3.17/32 172.16.3.18/32 ];

Simplify backup route entries, merge routing entries for the same subnet.

 node1 {

  system {

   backup-router 192.168.1.254 destination [ 10.1.1.0/24 172.16.1.0/24 172.16.2.0/24 172.16.3.0/24];