sth...@nethelp.no wrote: > > I'm reading > > https://www.juniper.net/documentation/en_US/junos/topics/topic-map/bgp-route-reflectors.html > > and it is completely mind-boggling. > > > > The example configuration of the Router Reflector (RR) places all neighbors > > (both clients and non-clients) into one group "internal-peers." How is this > > supposed to work? How do I tell the RR that routers B and C are clients, and > > routers E and D are non-clients? > > > > In Cisco, you set the "router-reflector-client" statement for each > > peer (or peer-group) who is a RR-client, explicitly. I don't see > > anything of the kind in the example from the Juniper site. > > Indeed, having separate groups for clients (cluster x.x.x.x) and > non-clients (no cluster configured) is the normal way of configuring > this.
Sorry, this cannot be the normal way. If a router receives an update from a non-client with its own cluster-id (e.g. from another RR in the same cluster) it should *drop* this update. Having no cluster configured is totally wrong, especially if there are redundant RRs with iBGP sessions between them. > The example configuration from juniper.net looks wrong. Disbelieve :-) I would rather believe in my own folly. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
