Sorry this is obviously an old thread but obviously still relevant and will ALWAYS be.
Just wanna make a comment here:Adjacency-RIB-IN:
Contains all received routes from each peer.
The Adjacency-RIB-In tables are the pre-policy tables, meaning that the routes in these tables have not been filtered or modified by routing policies.
This is what I expect from documentation as wellhttps://www.juniper.net/documentation/us/en/software/junos/routing-policy/topics/concept/policy-routing-policies-overview.html
However I played with this example:https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/troubleshooting-bgp-sessions.html#id-verify-bgp-peers
Lets simplify it for the sake of this chat:
Assume you have AS12 with routers R1 and R2, and AS34 with routers R3 and R4
- R1 and R2 are iBGP, and also are R3 and R4
- R1 eBGP peers with R3, while R2 eBGP peers with R4
Now assume both R1 and R2 inject 2 (same) subnets into their eBGP peers (nothing between themselves as mentioned)
- AS34 doesn't advertise anything to AS12 yet
So back to the discussion, just to show you guys what I observed:
Lets say R3 has an import filter that tags 100.100.1.0/24 with LP=200) from R1
So then when you run the "show route receive-protocol bgp R1-IP" on R3 you'd notice that ONLY 100.100.1.0/24 has "*"
user@R3> show route receive-protocol bgp R1-IP
inet.0: x destinations, y routes (z active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
*100.100.1.0/24 x.x.x.x AS12 I
100.100.2.0/24 x.x.x.x AS12 I
And interestingly, if you do the same on R4 (against R2), you'd notice that ONLY 220.127.116.11/24 has "*".
So what does that say about RIB-IN guys?
Can someone check? I found that quite interesting really...
Sent: 12-18-2014 22:05
From: Unknown User
Subject: How do you check for BGP advertised and received routes in JUNOS
Yes, the question from teh OP was clearly and completely answered in the accepted solution. Here is some additional information to your query.
Adjacency-RIB-IN: Contains all received routes from each peer. The Adjacency-RIB-In tables are the pre-policy tables, meaning that the routes in these tables have not been filtered or modified by routing policies. An Adjacency-RIB-In table is created on the local router for each established BGP peer. All routes received from the peer are placed in the appropriate memory table. There's one notable exception to this rule: Routes containing an AS Path loop are immediately discarded by the local route
RIB-LOCAL: Contains routes the local router uses to forward traffic. The Local-RIB tables are the post-policy tables. Even though some vendor may implement 3 different routing table, Junipers implementation use the local inet.0 as the BGP Local-RIB
Adjacency-RIB-OUT: Contains all advertised routes sent to each peer and are placed in the appropriate memory table. In other words, a BGP router advertises only routes that it is currently using to forward data traffic. By default, all Local-RIB routes are placed in each Adjacency-RIB-O