Hi
A Juniper router has the ability to use any operational routing table as the multicast RPF
table. The only real requirement is that the selected table contain IP unicast routing information.
However, the JUNOS software has set aside the inet.2 routing table for RPF usage, most administrators use this table in place of inet.0
The inet.2 routing table already exists on the router, so we only need to populate it with routing
knowledge for it to appear in the output.
e.g
The administrators of two AS networks have decided to use the
inet.2 routing table for RPF checks. The first step in this process is copying the local routes
into this table by using a rib-group. Much like a routing policy, the rib-group is given a name
in the configuration and is supplied the tables into which the routes should be placed. The dubai router currently has a rib-group called populate-inet2, which contains an import-rib statement. The rib-group lists both inet.0 and inet.2 as tables where it can place routing information. The configuration currently appears as so:
user@dubai> show configuration routing-options
interface-routes {
rib-group inet populate-inet2;
}
rib-groups {
populate-inet2 {
import-rib [ inet.0 inet.2 ];
}
autonomous-system 65001
user@dubai> show route 10.x.x.x terse table inet.2
(You can also concern with JNCIS study guide page 433 to 437) 🙂
Thanx
Fahad