Step 4: Examine BGP Routes
Purpose
You can examine the BGP path selection process to determine the single, active path when BGP receives multiple routes to the same destination. In this step, we examine the reverse LSP
R6-to-R1, makingR6the ingress router for that LSP.Action
To examine BGP routes and route selection, enter the following JUNOS CLI operational mode command:
user@host>show routedestination-prefixdetailSample Output 1
user@R6>show route 100.100.1.1 detailinet.0: 30 destinations, 46 routes (29 active, 0 holddown, 1 hidden)100.100.1.0/24 (1 entry, 1 announced)*BGP Preference: 170/-101Source: 10.1.13.1Next hop: via so-0/0/3.0, selectedProtocol next hop: 10.1.13.1Indirect next hop: 8671594 304State: <Active Int Ext>Local AS: 65432 Peer AS: 65432Age: 4d 5:15:39 Metric2: 2Task: BGP_65432.10.1.13.1+3048Announcement bits (2): 0-KRT 4-Resolve inet.0AS path: ILocalpref: 100Router ID: 10.0.0.1Sample Output 2
user@R6>show route 100.100.1.1 detailinet.0: 30 destinations, 46 routes (29 active, 0 holddown, 1 hidden)100.100.1.0/24 (1 entry, 1 announced)*BGP Preference: 170/-101Source: 10.0.0.1Next hop: via so-0/0/3.0 weight 1, selectedLabel-switched-path R6-to-R1Label operation: Push 100000Protocol next hop: 10.0.0.1Indirect next hop: 8671330 301State: <Active Int Ext>Local AS: 65432 Peer AS: 65432Age: 24:35 Metric2: 2Task: BGP_65432.10.0.0.1+179Announcement bits (2): 0-KRT 4-Resolve inet.0AS path: ILocalpref: 100Router ID: 10.0.0.1What It Means
Sample Output 1 shows that the BGP next hop (
10.1.13.1) does not equal the LSP destination address (10.0.0.1) in thetostatement at the [edit protocols mpls label-switched-pathlabel-switched-path-name] hierarchy level when the BGP configuration ofR6andR1is incorrect.Sample Output 2, taken after the configurations on R1 and R6 are corrected, shows that the BGP next hop (
10.0.0.1) and the LSP destination address (10.0.0.1) are the same, indicating that BGP can use the LSP to forward BGP traffic.