This article provides an explanation on why the mentioned error is seen on the secondary node in a SRX cluster.

In SRX cluster, you will see the below error message when you run "show route" command on the secondary node in SRX cluster.

"error: the routing subsystem is not running"

This error is seen on the secondary node as the routing daemon is not running on the secondary node. It is running only on the primary node in the SRX cluster.

This is a normal behavior and does not indicate any error condition.

In the below output, we can see that the Node0 displayed the output for the command "show route" however the Node1 returns the error, "error: the routing subsystem is not running. This is a normal behavior and does not indicate any error condition. It states that the routing daemon is primary on another node.

{primary:node0}

root@root-P1> show route

inet.0: 15 destinations, 21 routes (15 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

0.0.0.0/0          *[Static/5] 2d 07:03:49

                    >  to 10.85.172.1 via fxp0.0

                    [Static/5] 1d 05:47:20

                    >  to 10.88.88.1 via reth0.0

10.85.172.0/25     *[Direct/0] 2d 07:03:49

                    >  via fxp0.0

                    [Direct/0] 2d 07:03:49

                    >  via fxp0.0

10.85.172.57/32    *[Local/0] 2d 07:03:49

                       Local via fxp0.0

{secondary:node1}

root@root-P2> show route

error: the routing subsystem is not running

Below are few of the options to check which node is primary and which node has the routing subsytem running

root@root-P1> show chassis cluster status

Monitor Failure codes:
    CS  Cold Sync monitoring        FL  Fabric Connection monitoring
    GR  GRES monitoring             HW  Hardware monitoring
    IF  Interface monitoring        IP  IP monitoring
    LB  Loopback monitoring         MB  Mbuf monitoring
    NH  Nexthop monitoring          NP  NPC monitoring
    SP  SPU monitoring              SM  Schedule monitoring
    CF  Config Sync monitoring      RE  Relinquish monitoring
    IS  IRQ storm

Cluster ID: 8
Node   Priority Status               Preempt Manual   Monitor-failures

Redundancy group: 0 , Failover count: 0
node0  254      primary              no      no       None
node1  1        secondary            no      no       None

Redundancy group: 1 , Failover count: 0
node0  254      primary              no      no       None
node1  1        secondary            no      no       None

root@root-P1> show pfe terse no-forwarding

Slot Type Slot      State     Uptime
 1   RE   Present   Online    19w4d 11:28>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>RE is primary on this node.
     FWDD Present   Online    19w4d 11:32
     FWDD Present   Online    19w4d 12:25

root@root-P2> show pfe terse no-forwarding

Slot Type Slot      State     Uptime
 0   RE   Offline   Init      19w4d 11:29>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>RE is offline on the backuop node.
     FWDD Present   Valid     19w4d 11:34
     FWDD Present   Valid     19w4d 12:27

node0:
--------------------------------------------------------------------------

root@root-P1> show system uptime

node0:
--------------------------------------------------------------------------
Current time: 2024-10-21 16:51:08 UTC
Time Source:  NTP CLOCK
System booted: 2024-06-06 05:16:00 UTC (19w4d 11:35 ago)
Protocols started: 2024-06-06 05:22:56 UTC (19w4d 11:28 ago)>>>>>>>>>>>>>>>>>>>>>>>>>>>Protocols are running on primary node.
Last configured: 2024-09-30 04:53:41 UTC (3w0d 11:57 ago) by space-admin
 4:51PM  up 137 days, 11:35, 2 users, load averages: 0.27, 0.29, 0.33

node1:
--------------------------------------------------------------------------
Current time: 2024-10-21 16:51:08 UTC
Time Source:  NTP CLOCK
System booted: 2024-06-06 04:21:32 UTC (19w4d 12:29 ago)
Last configured: 2024-09-30 04:53:41 UTC (3w0d 11:57 ago) by space-admin
 4:51PM  up 137 days, 12:30, 1 users, load averages: 0.24, 0.22, 0.17

v1