Monitoring Routing Information
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.
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 terse
show route detail
Table 97 describes the different filters, their functions, and the associated actions.
Table 98 summarizes key output fields in the routing information display.
Table 97: Filtering Route Messages
Specifies the destination address of the route.
Enter the destination address.
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.
Specifies the dynamic routing protocol using which the routing information was received through a particular neighbor.
Enter the routing protocol.
Specifies only the best route available.
Select the view details of the best route.
Specifies the inactive routes.
Select the view details of inactive routes.
Specifies the exact route.
Select the view details of the exact route.
Specifies the hidden routes.
Select the view details of hidden routes.
Applies the specified filter and displays the matching messages.
To apply the filter and display messages, click Search.
Table 98: Summary of Key Routing Information Output Fields
Static Route Addresses
The list of static route addresses.
Protocol from which the route was learned: Static, Direct, Local, or the name of a particular protocol.
The preference is the individual preference value for the route.
The route preference is used as one of the route selection criteria.
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).
How long the route has been active.
Flags for this route.
There are many possible flags.
AS path through which the route was learned. The letters of the AS path indicate the path origin: