show aggregate route

Name of the routing table (for example, inet.0).

Number of destinations for which there are routes in the routing table.

Number of routes in the routing table and total number of routes in the following states:

• active (routes that are active).

• holddown (routes that are in the pending state as a protocol still has its interest bit set on it). The route is in the holddown state even though it is marked as 'delete' because the protocol still has interest in the route, meaning that the interest bit is set. The route will be deleted after all protocols withdraw their advertisement of the route and remove their interest bits. A persistent holddown state often means that the interested protocol is not releasing its interest bit properly.

Route destination (for example:10.0.0.1/24). Sometimes the route information is presented in another format, such as:

• MPLS-label (for example, 80001).

• interface-name (for example, ge-1/0/2).

• neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only. For example, 10.1.1.195:NoCtrlWord:1:1:Local/96):

  • neighbor-address—Address of the neighbor.

  • control-word-status—Whether the use of the control word has been negotiated for this virtual circuit: NoCtrlWord or CtrlWord.

  • encapsulation type—Type of encapsulation, represented by a number: (1) Frame Relay DLCI, (2) ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet, (6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport.

  • vc-id—Virtual circuit identifier.

  • source—Source of the advertisement: Local or Remote.

Protocol from which the route was learned and the preference value for the route.

• +—A plus sign indicates the active route, which is the route installed from the routing table into the forwarding table.

• - —A hyphen indicates the last active route.

• *—An asterisk indicates that the route is both the active and the last active route. An asterisk before a to line indicates the best subpath to the route.

In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value.

How long the route been known (for example, 2w4d 13:11:14, or 2 weeks, 4 days, 13 hours, 11 minutes, and 14 seconds).

Cost value of the indicated route. For routes within an AS, the cost is determined by the IGP and the individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined by a preference value.

Local preference value included in the route.

Interface from which the route was received.

AS path through which the route was learned. The letters at the end of the AS path indicate the path origin, providing an indication of the state of the route at the point at which the AS path originated:

• I—IGP.

• E—EGP.

• ?—Incomplete; typically, the AS path was aggregated.