to send 21.0.0.0/8 to the customer ?
Original Message:
Sent: 04-22-2021 10:19
From: Unknown User
Subject: Advertise-inactive
I did a quick lab with as much info I had on this case. I tested this on 21.0.0.0/8 between provider router R1 ge-0/0/6.999 and customer-B2 ge-0/0/6.999. on provider I am using a rib group to leak routes between tables
set routing-options rib-groups B2-RIB import-rib inet.0set routing-options rib-groups B2-RIB import-rib B2.inet.0set routing-instances B2 protocols bgp group ToB2 type externalset routing-instances B2 protocols bgp group ToB2 family inet unicastset routing-instances B2 protocols bgp group ToB2 neighbor 199.99.99.2 peer-as 101set routing-instances B2 instance-type vrfset routing-instances B2 interface ge-0/0/6.999set routing-instances B2 interface lo0.99set routing-instances B2 route-distinguisher 172.30.5.1:999set routing-instances B2 vrf-target target:54591:999
here the routing table as well as advertising /8 to peer:
****************************************root@R1# run show route 21.0.0.0/8 exact inet.0: 849 destinations, 1441 routes (681 active, 0 holddown, 330 hidden)@ = Routing Use Only, # = Forwarding Use Only+ = Active Route, - = Last Active, * = Both21.0.0.0/8 *[BGP/170] 1d 00:05:26, localpref 200, from 172.30.5.41 AS path: 2831679853 26697 56251 10277 21151 I, validation-state: unverified > to 172.30.0.2 via ae0.0, Push 299776B2.inet.0: 296 destinations, 296 routes (295 active, 0 holddown, 1 hidden)+ = Active Route, - = Last Active, * = Both21.0.0.0/8 *[BGP/170] 23:41:40, localpref 200, from 172.30.5.41 AS path: 2831679853 26697 56251 10277 21151 I, validation-state: unverified > to 172.30.0.2 via ae0.0, Push 299776****************************************root@R1# run show route advertising-protocol bgp 199.99.99.2 21.0.0.0/8 B2.inet.0: 296 destinations, 296 routes (295 active, 0 holddown, 1 hidden) Prefix Nexthop MED Lclpref AS path* 21.0.0.0/8 Self 2831679853 26697 56251 10277 21151 I* 21.32.0.0/13 Self 2831679853 26697 19412 41250 18175 61392 9306 25391 I**ignore the second prefix**
so routes learned are via bgp and leaked to instance B2, therefore it gets advertised to remote customer. here is routing table from customer:
root@customer-B2> show route 21.0.0.0/8 exact inet.0: 221 destinations, 221 routes (221 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both21.0.0.0/8 *[BGP/170] 00:03:38, localpref 100 AS path: 54591 2831679853 26697 56251 10277 21151 I, validation-state: unverified > to 199.99.99.1 via ge-0/0/6.999
lets add a similar static route in provider router instance B2, mimicing your 0/0 static route:
set routing-instances B2 routing-options static route 21.0.0.0/8 next-table inet.0
routing table indicates the latest change:
root@R1# run show route 21.0.0.0/8 exact inet.0: 849 destinations, 1441 routes (681 active, 0 holddown, 330 hidden)@ = Routing Use Only, # = Forwarding Use Only+ = Active Route, - = Last Active, * = Both21.0.0.0/8 *[BGP/170] 1d 00:07:20, localpref 200, from 172.30.5.41 AS path: 2831679853 26697 56251 10277 21151 I, validation-state: unverified > to 172.30.0.2 via ae0.0, Push 299776B2.inet.0: 296 destinations, 297 routes (295 active, 0 holddown, 1 hidden)+ = Active Route, - = Last Active, * = Both21.0.0.0/8 *[Static/5] 00:00:07 to table inet.0 [BGP/170] 23:43:34, localpref 200, from 172.30.5.41 AS path: 2831679853 26697 56251 10277 21151 I, validation-state: unverified > to 172.30.0.2 via ae0.0, Push 299776
even though the route is still present, the active /8 route is static which BGP wont advertise by default:
root@R1# run show route advertising-protocol bgp 199.99.99.2 21.0.0.0/8 B2.inet.0: 296 destinations, 297 routes (295 active, 0 holddown, 1 hidden) Prefix Nexthop MED Lclpref AS path* 21.32.0.0/13 Self 2831679853 26697 19412 41250 18175 61392 9306 25391 I**we only see the second prefix that was there before - missing /8**
and here is customers routing table for reference.
root@customer-B2> show route 21.0.0.0/8 exact root@customer-B2> show route 21.0.0.0/8 inet.0: 220 destinations, 220 routes (220 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both21.32.0.0/13 *[BGP/170] 00:02:33, localpref 100 AS path: 54591 2831679853 26697 19412 41250 18175 61392 9306 25391 I, validation-state: unverified > to 199.99.99.1 via ge-0/0/6.999
hope this clarifies the issue for you.
Original Message:
Sent: 04-22-2021 09:27
From: Unknown User
Subject: Advertise-inactive
Hi,
can you please share your rib-group config?
> show configuration routing-options
Based on the routes I see above it looks like the originating table is still inet.0, would be great if you could also share routing table with detail knob.
> show route 0.0.0.0/0 exact detail> show route advertising-protocol bgp 192.168.35.5
I still believe default route is not getting advertised as BGP sees this as a non-bgp route and thus it wont advertise it by default.
to be sure, and so I can clear my own doubts, I can certainly test it out if you can share the topology and your config files?
Original Message:
Sent: 04-21-2021 11:49
From: Unknown User
Subject: Advertise-inactive
set routing-instances B2 protocols bgp group ToB2 family inet unicast rib-group B2ToInet
this line sends B2 bgp routes to inet.0.
In the B2 routing-instance, I have a static route configured to make the reachability within the organization, and a generate default route from bgp based the ISP availablibity. I did not redistribute the static route, as I thought the default route will be advertised with advertise-inactive, but it did not.
I like to know what I have missed.
thanks a lot !!
Original Message:
Sent: 04-21-2021 10:10
From: Unknown User
Subject: Advertise-inactive
hi gongyayu,
it depends on how you have rib-groups and other parts of the lab configured I guess but a quick look tells me yeah it shouldnt be advertised. looks like rib-group B2ToInet is importing routes from inet.0 to B2.inet.0 (isnt it technically InetToB2)? what is the static route used for then? are you testing advertise-inactive functionality? the way I understand that statement is it advertises the inactive paths that might have became inactive due to any reason, lets say due to IGP cost. I see 0/0 is using at least 2 nh ips, 192.168.23.2/ 192.168.13.1 so both are "active" routes and 0/0 should be advertised even without the advertise-inactive statement, this is bgp default behavior to advertise bgp learned routes to ebgp peers. However you have a static route in B2 instance pointing to inet.0, since source protocol is static I believe it wont be advertised by default and requires a policy to do so. Im still not clear on the static route. if its not needed, one way to test this is to simply remove the static route in B2 instance. as a result your active route should be sourced from protocol bgp, and therefore should be advertised.
obviously I dont have the lab in front of me so please be gentle....Im interested to learn your results as well. let me know how it goes if you dont mind.
Original Message:
Sent: 04-20-2021 19:16
From: Unknown User
Subject: Advertise-inactive
I have the following, is the default route supposed to be advertised to the eBGP peer ?
root@vMX3# run show route 0.0.0.0/0 exact inet.0: 37 destinations, 58 routes (37 active, 0 holddown, 2 hidden)+ = Active Route, - = Last Active, * = Both0.0.0.0/0 *[BGP/170] 3d 18:14:21, localpref 150, from 192.168.0.2 AS path: I, validation-state: unverified > to 192.168.23.2 via ge-0/0/1.0, Push 0 [BGP/170] 3d 22:55:13, localpref 100, from 192.168.0.1 AS path: I, validation-state: unverified > to 192.168.13.1 via ge-0/0/0.0, Push 0B2.inet.0: 28 destinations, 41 routes (27 active, 0 holddown, 2 hidden)+ = Active Route, - = Last Active, * = Both0.0.0.0/0 *[Static/5] 3d 17:35:25 to table inet.0 [BGP/170] 3d 17:31:11, localpref 150, from 192.168.0.2 AS path: I, validation-state: unverified > to 192.168.23.2 via ge-0/0/1.0, Push 0 [BGP/170] 3d 17:31:11, localpref 100, from 192.168.0.1 AS path: I, validation-state: unverified > to 192.168.13.1 via ge-0/0/0.0, Push 0[edit]root@vMX3# show routing-instances | display set set routing-instances B2 instance-type vrfset routing-instances B2 interface ge-0/0/6.0set routing-instances B2 route-distinguisher 192.168.0.3:3set routing-instances B2 vrf-target target:65000:1set routing-instances B2 routing-options static route 0.0.0.0/0 next-table inet.0set routing-instances B2 protocols bgp group ToB2 type externalset routing-instances B2 protocols bgp group ToB2 advertise-inactiveset routing-instances B2 protocols bgp group ToB2 family inet unicast rib-group B2ToInetset routing-instances B2 protocols bgp group ToB2 neighbor 192.168.35.5 peer-as 100001set routing-instances B2 protocols bgp group ToB2v6 type externalset routing-instances B2 protocols bgp group ToB2v6 family inet6 unicastset routing-instances B2 protocols bgp group ToB2v6 neighbor 2001:0db8:3000:0035::5 peer-as 100001
thanks for taking a look !!