[j-nsp] VRRP VIP route not accepted as contributing route to AGGREGATE

Alexander Marhold alexander.marhold at gmx.at
Tue Jan 26 12:15:29 EST 2016


Hi Experts !

We want to have an aggregate only announced when the VRRP vip route is active on the local BGP speaker

Show route proto local shows the route

1##.123.456.100/32 *[Local/0] 02:15:41
                      Local via ge-0/0/6.0

As the local router is the vrrp master

ge-0/0/6.0    up             26   master   Active      A  0.677 lcl    1##.123.456.1
                                                                vip    1##.123.456.100

the aggregate config is:
        route 1##.123.456.0/24 {
            policy MATCH-VIP-vrrp-226;
            tag 24;

the policy is 

    policy-statement MATCH-VIP-vrrp-226 {
        term 1 {
            from {
                protocol local;
                route-filter 1##.123.456.100/32 exact;
            }
            then accept;
        }
        term 2 {
            then reject;
        }
    }

But the result is negative

lab at mx-2> show route protocol aggregate hidden

inet.0: 32 destinations, 43 routes (30 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both

1##.123.456.0/24    [Aggregate] 00:19:46, tag 24
                      Reject


When removing the policy I do not see the VIP route as contributing route:

1##.123.456.0/24 (1 entry, 1 announced)
TSI:
KRT in-kernel 1##.123.456.0/24 -> {}
Aggregated into 1##.123.456.0/22
Page 0 idx 1, (group TELIA type External) Type 1 val 0x9556434 (adv_entry)
   Advertised metrics:
     Nexthop: Self
     Communities:
Path 1##.123.226.0 Vector len 4.  Val: 1
        *Aggregate Preference: 130
                Next hop type: Reject
                Address: 0x9292a44
                Next-hop reference count: 14
                State: <Active Int Ext>
                
                Age: 22:49
                Validation State: unverified
                        Tag: 24
                Task: Aggregate
                Announcement bits (4): 0-KRT 4-Aggregate 5-BGP_RT_Background 6-Resolve tree 2
                AS path: I (LocalAgg)
                Flags:                  Depth: 0        Active
                AS path list:
                AS path: I Refcount: 1
                Contributing Routes (1):
                        1##.123.456.0/25 proto Direct


So is this a bug ?
or why it is not possible to use a VRRP VIP route as contributing route when it is shown as protocol local  route in the routing table

Or are local  routes not contributing even though they are active? 

The local route state is : State: <Active NoReadvrt Int>


Or is there another way to do this ?

The HW is a MX SW is 13.3, but the test was done on a vMX with 14.1

Thanks for help 

Alexander



More information about the juniper-nsp mailing list