Routing
Monitoring Route Information
Purpose
View information about the routes in a routing table, including destination, protocol, state, and parameter information.
Action
Select Monitor>Routing>Route Information in the J-Web user interface, or enter the following CLI commands:
show route terse
show route detail
When you use an HTTPS connection in the Microsoft Internet Explorer browser to save a report from this page in the J-Web interface, the error message "Internet Explorer was not able to open the Internet site" is displayed. This problem occurs because the Cache-Control: no cache HTTP header is added on the server side and Internet Explorer does not allow you to download the encrypted file with the Cache-Control: no cache HTTP header set in the response from the server.
As a workaround, refer to Microsoft Knowledge Base article 323308, which is available at this URL: http://support.microsoft.com/kb/323308. Also, you can alternatively use HTTP in the Internet Explorer browser or use HTTPS in the Mozilla Firefox browser to save a file from this page.
Table 78 describes the different filters, their functions, and the associated actions.
Table 79 summarizes key output fields in the routing information display.
Table 78: Filtering Route Messages
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. |
Reset | Resets selected options to default | To reset the filter, click Reset. |
Table 79: Summary of Key Routing Information Output Fields
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:
| – |
Monitoring RIP Routing Information
Purpose
View RIP routing information, including a summary of RIP neighbors and statistics.
Action
Select Monitor>Routing>RIP Information in the J-Web user interface, or enter the following CLI commands:
show rip statistics
show rip neighbors
Table 80 summarizes key output fields in the RIP routing display in the J-Web user interface.
Table 80: Summary of Key RIP Routing Output Fields
Field | Values | Additional Information |
|---|---|---|
| RIP Statistics | ||
Protocol Name | The RIP protocol name. | – |
Port number | The port on which RIP is enabled. | – |
Hold down time | The interval during which routes are neither advertised nor updated. | – |
Global routes learned | Number of RIP routes learned on the logical interface. | – |
Global routes held down | Number of RIP routes that are not advertised or updated during the hold-down interval. | – |
Global request dropped | Number of requests dropped. | – |
Global responses dropped | Number of responses dropped. | – |
| RIP Neighbors | ||
Details | Tab used to view the details of the interface on which RIP is enabled. | – |
Neighbor | Name of the RIP neighbor. | This value is the name of the interface on which RIP is enabled. Click the name to see the details for this neighbor. |
State | State of the RIP connection: Up or Dn (Down). | – |
Source Address | Local source address. | This value is the configured address of the interface on which RIP is enabled. |
Destination Address | Destination address. | This value is the configured address of the immediate RIP adjacency. |
Send Mode | The mode of sending RIP messages. | – |
Receive Mode | The mode in which messages are received. | – |
In Metric | Value of the incoming metric configured for the RIP neighbor. | – |
Monitoring OSPF Routing Information
Purpose
View OSPF routing information, including a summary of OSPF neighbors, interfaces, and statistics.
Action
Select Monitor>Routing>OSPF Information in the J-Web user interface, or enter the following CLI commands:
show ospf neighbors
show ospf interfaces
show ospf statistics
Table 81 summarizes key output fields in the OSPF routing display in the J-Web user interface.
Table 81: Summary of Key OSPF Routing Output Fields
Field | Values | Additional Information |
|---|---|---|
| OSPF Interfaces | ||
Details | Tab used to view the details of the selected OSPF. | – |
Interface | Name of the interface running OSPF. | – |
State | State of the interface: BDR, Down, DR, DRother, Loop, PtToPt, or Waiting. | The Down state, indicating that the interface is not functioning, and PtToPt state, indicating that a point-to-point connection has been established, are the most common states. |
Area | Number of the area that the interface is in. | – |
DR ID | ID of the area's designated device. | – |
BDR ID | ID of the area's backup designated device. | – |
Neighbors | Number of neighbors on this interface. | – |
| OSPF Statistics | ||
| Packets tab | ||
Sent | Displays the total number of packets sent. | – |
Received | Displays the total number of packets received. | – |
| Details tab | ||
Flood Queue Depth | Number of entries in the extended queue. | – |
Total Retransmits | Number of retransmission entries enqueued. | – |
Total Database Summaries | Total number of database description packets. | – |
| OSPF Neighbors | ||
Address | Address of the neighbor. | – |
Interface | Interface through which the neighbor is reachable. | – |
State | State of the neighbor: Attempt, Down, Exchange, ExStart, Full, Init, Loading, or 2way. | Generally, only the Down state, indicating a failed OSPF adjacency, and the Full state, indicating a functional adjacency, are maintained for more than a few seconds. The other states are transitional states that a neighbor is in only briefly while an OSPF adjacency is being established. |
ID | ID of the neighbor. | – |
Priority | Priority of the neighbor to become the designated router. | – |
Activity Time | The activity time. | – |
Area | Area that the neighbor is in. | – |
Options | Option bits received in the hello packets from the neighbor. | – |
DR Address | Address of the designated router. | – |
BDR Address | Address of the backup designated router. | – |
Uptime | Length of time since the neighbor came up. | – |
Adjacency | Length of time since the adjacency with the neighbor was established. | – |
Monitoring BGP Routing Information
Purpose
Monitor BGP routing information on the routing device, including a summary of BGP routing and neighbor information.
Action
Select Monitor>Routing>BGP Information in the J-Web user interface, or enter the following CLI commands:
show bgp summary
show bgp neighbor
Table 82 summarizes key output fields in the BGP routing display in the J-Web user interface.
Table 82: Summary of Key BGP Routing Output Fields
Field | Values | Additional Information |
|---|---|---|
| BGP Peer Summary | ||
Total Groups | Number of BGP groups. | – |
Total Peers | Number of BGP peers. | – |
Down Peers | Number of unavailable BGP peers. | – |
Unconfigured Peers | Address of each BGP peer. | – |
| RIB Summary tab | ||
RIB Name | Name of the RIB group. | – |
Total Prefixes | Total number of prefixes from the peer, both active and inactive, that are in the routing table. | – |
Active Prefixes | Number of prefixes received from the EBGP peers that are active in the routing table. | – |
Suppressed Prefixes | Number of routes received from EBGP peers currently inactive because of damping or other reasons. | – |
History Prefixes | History of the routes received or suppressed. | – |
Dumped Prefixes | Number of routes currently inactive because of damping or other reasons. These routes do not appear in the forwarding table and are not exported by routing protocols. | – |
Pending Prefixes | Number of pending routes. | – |
State | Status of the graceful restart process for this routing table: BGP restart is complete, BGP restart in progress, VPN restart in progress, or VPN restart is complete. | – |
| BGP Neighbors | ||
Details | Click this button to view the selected BGP neighbor details. | – |
Peer Address | Address of the BGP neighbor. | – |
Autonomous System | AS number of the peer. | – |
Peer State | Current state of the BGP session:
| Generally, the most common states are Active, which indicates a problem establishing the BGP connection, and Established, which indicates a successful session setup. The other states are transition states, and BGP sessions normally do not stay in those states for extended periods of time. |
Elapsed Time | Elapsed time since the peering session was last reset. | – |
Description | Description of the BGP session. | – |