Step 5: Verify Received BGP Routes

Purpose

Display the routing information received on router R6, the ingress router for the reverse LSP R6-to-R1.

Action

To verify that a particular BGP route is received on the egress router, enter the following JUNOS CLI operational mode command:

user@host> show route receive protocol bgp neighbor-address

Sample Output 1

user@R6> show route receive-protocol bgp 10.0.0.1       

inet.0: 30 destinations, 46 routes (29 active, 0 holddown, 1 hidden)

    <<< missing route

inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

__juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 
hidden)

Sample Output 2

user@R6> show route receive-protocol bgp 10.0.0.1 

inet.0: 30 destinations, 46 routes (29 active, 0 holddown, 1 hidden)

  Prefix                  Nexthop              MED     Lclpref    AS path

* 100.100.1.0/24          10.0.0.1                     100        I

inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

__juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 
hidden)

What It Means

Sample Output 1 shows that ingress router R6 (reverse LSP R6-to-R1) does not receive any BGP routes into the inet.0 routing table when the BGP configurations of R1 and R6 are incorrect.

Sample Output 2 shows a BGP route installed in the inet.0 routing table after the BGP configurations on R1 and R6 are corrected using Take Appropriate Action.