- play_arrow Overview
- play_arrow Overview
- J-Web User Interface for EX Series Switches Overview
- J-Web Interface—Application Package
- Understanding J-Web User Interface Sessions
- Dashboard for EX Series Switches
- Understanding J-Web Configuration Tools
- Understand Alarm Types and Severity Levels on EX Series Switches
- Using the Commit Options to Commit Configuration Changes (J-Web Procedure)
-
- play_arrow Configuration
- play_arrow Starting J-Web
- play_arrow J-Web Configuration Tools
- play_arrow System Basics Configuration
- Connecting and Configuring an EX Series Switch (J-Web Procedure)
- Configuring Date and Time for the EX Series Switch (J-Web Procedure)
- Configuring System Identity for an EX Series Switch (J-Web Procedure)
- Configuring Management Access for the EX Series Switch (J-Web Procedure)
- Generating SSL Certificates to Be Used for Secure Web Access (EX Series Switch)
- Rebooting or Halting the EX Series Switch (J-Web Procedure)
- play_arrow Class of Service Configuration
- Defining CoS Drop Profiles (J-Web Procedure)
- Defining CoS Classifiers (J-Web Procedure)
- Defining CoS Code-Point Aliases (J-Web Procedure)
- Assigning CoS Components to Interfaces (J-Web Procedure)
- Defining CoS Forwarding Classes (J-Web Procedure)
- Defining CoS Rewrite Rules (J-Web Procedure)
- Defining CoS Schedulers (J-Web Procedure)
- Defining CoS Scheduler Maps (J-Web Procedure)
- play_arrow Security and Management Configuration
- play_arrow Routing Policies and Packet Filtering Configuration
- play_arrow Ethernet Switching Configuration
- play_arrow Interfaces
- play_arrow Configuring Services
- play_arrow Configuring Layer 3 Protocols
- play_arrow Configuring Real-Time Performance Monitoring
- play_arrow Software Installation and Upgrades
- play_arrow Configuration, Files, Users, Licenses, and Product Registration
- Managing Configuration Files Through the Configuration History (J-Web Procedure)
- Setting or Deleting the Rescue Configuration (J-Web Procedure)
- Uploading a Configuration File (J-Web Procedure)
- Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure)
- Managing Users (J-Web Procedure)
- Managing Licenses for the EX Series Switch (J-Web Procedure)
- Registering the EX Series Switch with the J-Web Interface
- Generating Support Information Reports for EX Series Switches Using the J-Web Interface
- play_arrow Virtual Chassis Configuration
-
- play_arrow Administration
- play_arrow Software, Files, Licenses, Logs
- Uploading a Configuration File (J-Web Procedure)
- Managing Configuration Files Through the Configuration History (J-Web Procedure)
- Setting or Deleting the Rescue Configuration (J-Web Procedure)
- Updating J-Web Interface on EX Series Switches (J-Web Procedure)
- Upgrading Junos OS on EX Series Switches (J-Web Procedure)
- Managing Licenses for the EX Series Switch (J-Web Procedure)
- Rebooting or Halting the EX Series Switch (J-Web Procedure)
- Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure)
- Registering the EX Series Switch with the J-Web Interface
- Generating Support Information Reports for EX Series Switches Using the J-Web Interface
-
- play_arrow Troubleshooting
- play_arrow Troubleshooting Task
- play_arrow FAQ
-
Monitoring Routing Information
Purpose
This topic applies only to the J-Web Application package.
Use the monitoring functionality to view the inet.0 routing table on the routing device.
Action
To view the routing tables in the J-Web interface, select Monitor > Routing > Route Information. Apply a filter or a combination of filters to view messages. You can use filters to display relevant events.
To view the routing table in the CLI, enter the following commands in the CLI interface:
show route terseshow route detail
Meaning
Table 1 describes the different filters, their functions, and the associated actions.
Table 2 summarizes key output fields in the routing information display.
Field | Function | Your Action |
|---|---|---|
Destination Address | Specifies the destination address of the route. | Enter the destination address. |
Protocol | Specifies the protocol from which the route was learned. | Enter the protocol name. |
Next hop address | Specifies the network layer address of the directly reachable neighboring system (if applicable) and the interface used to reach it. | Enter the next hop address. |
Receive protocol | Specifies the dynamic routing protocol using which the routing information was received through a particular neighbor. | Enter the routing protocol. |
Best route | Specifies only the best route available. | Select the view details of the best route. |
Inactive routes | Specifies the inactive routes. | Select the view details of inactive routes. |
Exact route | Specifies the exact route. | Select the view details of the exact route. |
Hidden routes | Specifies the hidden routes. | Select the view details of hidden routes. |
Search | Applies the specified filter and displays the matching messages. | To apply the filter and display messages, click Search. |
Field | Values | Additional Information |
|---|---|---|
Static Route Addresses | The list of static route addresses. | |
Protocol | Protocol from which the route was learned: Static, Direct, Local, or the name of a particular protocol. | |
Preference | The preference is the individual preference value for the route. | The route preference is used as one of the route selection criteria. |
Next-Hop | Network layer address of the directly reachable neighboring system (if applicable) and the interface used to reach it. | If a next hop is listed as Discard, all traffic with that destination address is discarded rather than routed. This value generally means that the route is a static route for which the discard attribute has been set. If a next hop is listed as Reject, all traffic with that destination address is rejected. This value generally means that the address is unreachable. For example, if the address is a configured interface address and the interface is unavailable, traffic bound for that address is rejected. If a next hop is listed as Local, the destination is an address on the host (either the loopback address or Ethernet management port 0 address, for example). |
Age | How long the route has been active. | |
State | Flags for this route. | There are many possible flags. |
AS Path | AS path through which the route was learned. The letters of the AS path indicate the path origin:
|
