Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[MX] The 'show route logical-system <> table ?' lists all routing tables in master system but no routing tables in the logical system

0

0

Article ID: KB35614 KB Last Updated: 27 Mar 2020Version: 1.0
Summary:

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 master 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:
  <table>              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 master system without logical-system:
labroot@router> show route table ?
Possible completions:
  <table>              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.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search