Routing

test

Hi Rob,

As per your config, it is expected behavior. The rib-group config under BGP family will import routes coming from BGP neighbor(s) to the desired rib.

Based on vpnA config, as below, the routes from 192.168.16.6 will be imported to vpnAB rib.

    protocols {
        bgp {
            group vpnA {
                type external;
                family inet {
                    unicast {
                        rib-group vpnA-AB;
                    }
                }
                neighbor 192.168.16.6 {
                    peer-as 6;
                }
            }

Similarly in case of vpnAB, the routes from neighbor 192.168.17.7 would be imported to vpnA and vpnB

vpnAB {
    instance-type vrf;
    interface em1.17;
    route-distinguisher 100:3;
    vrf-import vpnAB-import;
    vrf-export vpnAB-export;
    vrf-table-label;
    protocols {
        bgp {
            group bgp {
                type external;
                family inet {
                    unicast {
                        rib-group vpnAB-A-B;
                    }
                }
                neighbor 192.168.17.7 {
                    peer-as 7;
                }


So strictly speaking the rib-group configs will affect only for the routes which are advertised by the BGP neighbor and not for any routes which are imported.

Regards
Surya

Hi,

In addtion to Surya's post, I just try to clarify the rib-group function.

There are two entities here. One is "Routing Process/Protocols"  and the other one is "Routing Table".

RIB Groups and import/Export polices interacts between these two sets of entities.

If you take rib-group,

import-rib  -- > Installs routes from a routing process to one / many routing tables mentioned in the group.

export-rib  -->  Exports routes from a single  routing table to protocol.

So in your case, routes were installed to vpnA and vpnAB routing tables from BGP.

But you can't expect routes from vpnAB table will be installed to vpnA / vpnB table. ( This is not between protocol and table)

This will happen when only vpnAB BGP installs any routes to vpnAB table.

Regards,

Moses N