Description

This is a minor CLI output issue, however, it may cause confusion if there are same name routing-instances that exist in both systems. Sometimes it may lead to incorrect configuration of the system.

Symptoms

When executing the command with a question mark:  ​'show route logical-system <> table ?' , the output lists all routing tables in the primary system, but not the routing tables in the logical system.

Example:

It expects only list inet.0 and ine6.0 tables which exist in logical-system test. However, the output lists all routing tables in themaster system: 

labroot@router> show route logical-system test table ?
Possible completions:
Name of routing table bgp.l2vpn.0 bgp.rtarget.0 inet.0 inet.3 inet6.0 inet6.3 mpls.0 testvpn.l2vpn.0

When specifying the table name, the error pops up since it does not belong to logical-system test.

This is an expected behavior: 
labroot@router> show route logical-system test table testvpn.l2vpn.0
error: No routing tables matching specification.

This is the expected behavior; list route tables related to primary system without logical-system: 
labroot@router> show route table ?
Possible completions:
Name of routing table bgp.l2vpn.0 bgp.rtarget.0 inet.0 inet.3 inet6.0 inet6.3 mpls.0 testvpn.l2vpn.0

 

Solution

This issue is expected to be fixed in JUNOS 20.2R1 and later. There is currently no workaround available. Please be careful to execute the command and avoid confusion when you have configured multiple logical-systems in the router.