Routing

like the title

Hi,

 

Copying from first table to second  is a wrong concept.  

Actually, the first table (vpn-a.inet.0)  is the "Primary" table and the rest of the table/tables are secondary. 

Primary table is the one to which the routes will be installed if we don't have the rib-groups configured.

 

rib-group configurations for static / direct routes might not need the Primary table configured first.  

But, for OSPF , ISIS etc, you have to mention the Primary table first, otherwise it will give you an error when you commit.      

R1# commit check
[edit  protocols isis]
  'rib-group'
    rib-group test: Primary routing table should be inet.0
error: configuration check-out failed

 

 

 

Also, if you want to import routes selectively to secondary tables , you can configure  "import-policy" with rib-group.  

This import policy will be applied to the secondary tables , but not to the primary table.   ( I couldn't find this fact in any Juniper documents. This is based on my several testing)        

 

 

[edit  routing-options]
rib-groups {
      test {
          import-rib [ inet.0 VPN-1.inet.0 ];
          import-policy VPN1-import;
      }
  }
 
 

 

You can find simillar information in this topic

http://forums.juniper.net/t5/Routing/import-rib-VS-export-rib-in-RIB-group-Configuration/td-p/94202/highlight/true/page/2

 

Regards,

Moses N

thx in advance

Yes. That's correct.

rib-groups { a-to-b { import-rib [vpn-a.inet.0 vpn-b.inet.0]; }

 

 

set routing-options interface-routes rib-group a-to-b

 

if rib group a-to-b is a collection of vpn-a.inet.0 and vpn-b.inet.0,what is the meaning of this "set routing-options interface-routes rib-group a-to-b"

it seems I can understand now set routing-options interface-routes rib-group a-to-b this interface-routes is a little special than others we must have inet.0 on it ,otherwise it can't get this direct route from and because it is a direct route,the primary table can be not inet.0 ,but inet.0 should be in the list

Hi

It depend on where you apply the rib-groups.

 

If you are configuring under 

 

<routing-options interface-routes>    <== Main routing instance

Primary table must be inet.0 and all interface routes will be installed in primary and secondary tables.

 

<routing-instances vpn-a routing-options interface-routes>    <== VPN  routing instance

Primary table must be vpn-a.inet.0 and all vpn-a interface routes ( interfaces configured under vpna-a instance)  will be installed in primary(vpn-a.inet.0)  and secondary tables.

 

Simillarly, if you apply rib-groups under,

< protocol bgp group abc family inet unicast>   <== Main routing instance BGP and family inet

Primary table must be inet.0 and all BGP inet routes will be installed in primary and secondary tables.

 

<routing-instances vpn-a  protocol bgp group abc family inet unicast>   <== VPN routing instance BGP and family inet

Primary table must be vpn-a.inet.0 and all BGP inet routes inside the vpn-a  will be installed in primary and secondary tables.

 

Regards,

Moses N

At the risk of jumping into a 'solved' thread 🙂

 

rib-groups support import and export policies (e.g. set routing-options rib-groups a-to-b import-policy rib_import_from_a_to_b) if you want to have a bit more control over the 'leaked' prefixes.

 

Cheers,

you are also appreciated