If an MPLS LSP (label-switched path) has a primary path and one or more secondary paths, when one of its secondary path is up or down, the LSP will be flushed even when its primary path is always up.

The age timer of an LSP restarts from 00:00:00 when its secondary path is up or down. All routes (such as L3VPN) that traverse through this LSP will be flushed too, and their age timer of these routes will restart from 00:00:00.

For example, LSP “toR2” is up about 30 minutes and uses the primary path, which traverses through interface ge-1/3/6.0:

Then shutdown interface ge-1/0/8 to let the secondary path down:

After several seconds, this LSP route will be flushed and its up time will restart from 00:00:00.

The same thing happens when the secondary path of this LSP is up again.

When an LSP has a primary path and one or more secondary paths, its corresponding route in table inet.3 will have matched nexthops. When one of its secondary path is up or down, the nexthops of the route in table inet.3 will be updated. Therefore, the age timer of this LSP will restart from 00:00:00.

This is a cosmetic issue. There is no traffic impact.

The age timer of LSP restarting from 00:00:00 does not mean this route is deleted or added again. This can be confirmed with the command, rtsockmon since there's no route delete or add happening when one of its secondary path is up or down.