Here we directly set protocols bgp advertise-inactive (and in routing-instances too with an apply-group adding various stuff, like always-compare-med, router-id, and so on). Never seen any good reason to stay with the junos default about this point...
> On 15 jul. 2017 at 14:32, Roger Wiklund <roger.wikl...@gmail.com> wrote : > > Indeed you are right Saku. > > set routing-instances VR2 protocols bgp group TO-VR1-AND-VR2 neighbor > 10.0.0.1 peer-as 100 > set routing-instances VR2 protocols bgp group TO-VR1-AND-VR2 neighbor > 20.0.0.2 advertise-inactive > set routing-instances VR2 protocols bgp group TO-VR1-AND-VR2 neighbor > 20.0.0.2 peer-as 300 > > Session reset when I added advertise-inactive to the neighbor. > > Before: > Group Type: External Local AS: 200 > Name: TO-VR1-AND-VR2 Index: 4 Flags: <> > Holdtime: 0 > Total peers: 2 Established: 2 > 10.0.0.1+179 > 20.0.0.2+179 > VR2.inet.0: 0/1/1/0 > > After: > Group Type: External Local AS: 200 > Name: TO-VR1-AND-VR2 Index: 4 Flags: <> > Holdtime: 0 > Total peers: 1 Established: 1 > 10.0.0.1+179 > VR2.inet.0: 0/1/1/0 > > Group Type: External Local AS: 200 > Name: TO-VR1-AND-VR2 Index: 1 Flags: <> > Options: <AdvertiseInactive> > Holdtime: 0 > Total peers: 1 Established: 1 > 20.0.0.2+179 > VR2.inet.0: 0/0/0/0 > > So a workaround would be to put it in a separate group then... _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp