Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Viewing Routing Table Details

    The Routing Table window enables you view the routing table information for the selected virtual routing instance. For L3VPN services, you can determine which LSPs or tunnels are being used by looking at the routing tables.

    To view extensive information about the active entries in the routing tables for a device associated with a particular service:

    1. From the View selector, select Service View. The functionalities that you can configure in this view are displayed.

    2. Click the Monitor mode icon in the Service View of the Connectivity Services Director banner. The workspaces that are applicable to this mode are displayed.

    3. From the Service View pane, select the L3VPN service for which you want to view interface statistics. The service statistical details are displayed in the middle pane.

    4. From the task pane, which is displayed on the rightmost pane, select Tasks > Routing Table. The Routing Table window is displayed. The left pane of the window displays the names of the devices that are associated with the particular service.

    5. From the Device Name pane, select the device for which you want to view the routing table information. The following information is displayed in the right pane of the window in a tabular grid.

      Table 1: Routing Table Window Field Descriptions

      Name

      Description

      Service Name

      Name of the service for which routing table statistics are displayed.

      Number of Destinations

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

      Number of Routes

      Total number of routes in the routing table.

      Active Routes

      Number of routes that are active.

      Hidden Routes

      Number of routes that are not used because of routing policy.

      Hold-down Routes

      Number of routes that are in the hold-down state before being declared inactive.

      Destination Prefix

      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.

      State

      State of the route.

      Protocol

      Name of the protocol from which the route was learned. For example, OSPF, RSVP, and Static.

      Protocol Preference

      Preferred protocol for this routing instance. Junos OS uses this preference to choose which routes become active in the routing table.

      Age

      Displays how long since the route was learned.

      BGP Metric

      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.

      BGP Local Preference

      A metric used by BGP sessions to indicate the degree of preference for an external route. The route with the highest local preference value is preferred.

      AS Path

      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.

      • Recorded—The AS path is recorded by the sample process (sampled).

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

      When AS path numbers are included in the route, the format is as follows:

      • [ ]—Brackets enclose the local AS number associated with the AS path if more than one AS number is configured on the routing device, or if AS path prepending is configured.

      • { }—Braces enclose AS sets, which are groups of AS numbers in which the order does not matter. A set commonly results from route aggregation. The numbers in each AS set are displayed in ascending order.

      • ( )—Parentheses enclose a confederation.

      • ( [ ] )—Parentheses and brackets enclose a confederation set.

      Next Hop Type

      Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.

      If the destination is Discard, traffic is dropped.

      Local Interface

      The local interface used to reach the next hop.

      Next Hop

      Next-hop address of the interface.

      MPLS Label

      MPLS label and operation occurring at the next hop. The operation can be pop (where a label is removed from the top of the stack), push (where another label is added to the label stack), or swap (where a label is replaced by another label).

    6. Click Close after you complete viewing the details. You are returned to the main or home page in Monitor Mode of Service View, which is the Service Summary tab.

    Modified: 2017-07-20