Thanks! There was in fact a catch-all reject policy higher up in the config hierarchy that I didn’t clue into.
So now I see it with all policies removed, so I should be able to work backwards from here. Thanks again for the clue! > On Mar 7, 2019, at 3:46 PM, Olivier Benghozi <[email protected]> > wrote: > > Really sure of your export policy when removed from the neighbour (that is, > any policy under the protocol or the group) ? > > show bgp neighbor exact-instance foo 10.108.35.254 | match export > > > Any NO-EXPORT community attached on the route? > >> Le 7 mars 2019 à 20:04, Jason Lixfeld <[email protected]> a écrit : >> >> My understanding is that since this is a BGP prefix, it’s default export >> policy is to advertise all active BGP routes to all BGP speakers. But, to >> try and work through whether it was an export policy issue anyway, I >> deactivated the export policy on the session to 10.108.35.254, which was >> ineffective. > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
