Description

Default route is added in routing table after a reboot.

 

After a reboot on the SRX device on version 21.4R3-S3.4, we see there is a new default route entry created on the routing table on the main links:

 

0.0.0.0/0      *[Static/1] 6d 11:11:46, metric2 0

           > to 212.81.126.105 via reth4.26

           [Static/20] 28w0d 07:16:33

           > to 212.81.126.105 via reth4.26

[Static/1] 03:25:44, metric2 0

           > to 62.23.232.249 via reth4.526

           [Static/25] 03:25:44

           > to 62.23.232.249 via reth4.526

 

These are a carbon copy of the already manually configured default routes of the device.

Symptoms

  • SRX has a reboot and generates these default entries.
  • No logs show the entry creations.
  • IPv4 or IPv6 default entries.
  • Traffic still works as usual.

Solution

This is an existing PR. The PR Number is: 1715907

 

After the device reboots with lpm (longest prefix match) profile configured, the default route entry is getting created on ipv4 and ipv6 (pfe hw lpm) due to gRIBI routing instance and same route is removed after the interface flap.

Product-Group=evo

 

The multi-topology table gribi.inet6.0 is always created when the rib service is being instantiated. Since this is a dynamic table, if we do a configuration commit and the rpd infra module sees that the table is not being used, the dynamic table will be reclaimed (deleted) by the infra module. To prevent the rpd infra module from reclaiming the table, create a dummy route entry in gribi.inet6.0.

 

Workaround: Flap the interface associated with the default entry that was created. This will delete the default entry the moment the interface is flapped.

 

Solution: Upgrade the device to the following versions:

evo:22.4R2-S1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1

Modification History

2024-01-24 : Article Created