[j-nsp] Configuration -- rib groups

[Keegan.Holley at sungard.com]

David Taylor <davidtaylor1977 at yahoo.com> 
Sent by: juniper-nsp-bounces at puck.nether.net
02/02/08 04:03 PM

To
Juniper List <juniper-nsp at puck.nether.net>
cc

Subject
[j-nsp] Configuration -- rib groups






Hi,
  can anyone explain what does this following script do .... Seems like we 
are pouring routes from one place to another ? If so why do we need 
this... Why do we use Rib groups ...?
 
  }
routing-options {
    graceful-restart;
    static {
        route 192.168.20.0/24 next-table OM.inet.0;
        route 10.10.0.0/24 next-table OM.inet.0;

Tells the router to consult the OM.inet.0 vrf for a next hop to these two 
networks.


    }
    rib-groups {
        OM_to_inet {
            import-rib [ OM.inet.0 inet.0 ];
            import-policy OM_to_inet;

This is "route-leaking"  any routes that make it through teh OM_to_inet 
policy will be exported into the rib group.  The ribgroup itself is a 
combination of the routes in inet.0 and the routes in the OM vrf.  This 
allows the router to give individual routing tables access to the inet.0 
routing table, this usually provides internet access since the routes in 
the inet.0 table are from upstream providers.  Your usage may be 
different.
        }
    }
 
  routing-instances {
    ZN {
        instance-type vrf;
        interface fe-0/3/1.100;
        interface fe-0/3/1.115;
        interface fe-0/3/0.200;
        route-distinguisher 10.1.26.17:3000;
        vrf-target target:64512:3000;
        vrf-table-label;
        routing-options {
            static {
                route 10.26.0.8/32 next-hop 10.26.0.8;
            }
        }
    }
    OM {
        instance-type vrf;
        interface e1-0/0/5.0;
        interface fe-0/3/1.130;
        interface ae0.315;
        interface lo0.1;
        route-distinguisher 10.1.26.17:3100;
        vrf-import reject-all;
        vrf-export reject-all;
        routing-options {
            interface-routes {
                rib-group inet OM_to_inet;
            }
        }
 
   This creates two routing tables ZN.inet.0 and OM .inet.0 with the 
listed interfaces.

HTH,

Keegan