[j-nsp] router reflector clients and non-clients

[Alexander Marhold]

If you set the cluster-id for a group all configured neighbors are
RR-clients
So in your example all 4 neighbors including D and E are clients.

However the RR concept is quite flexible, a RR itself can be a client of
another RR ( hierarchically or at peer level)
Which means  A can be the RR of D and the same time D can be the RR of A

Regards
Alexander Marhold

-----Ursprüngliche Nachricht-----
Von: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] Im Auftrag von
Victor Sudakov
Gesendet: Mittwoch, 30. Mai 2018 07:59
An: juniper-nsp at puck.nether.net
Betreff: [j-nsp] router reflector clients and non-clients

Dear Colleagues,

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.

Please help?

Quoting from the document:

user at A# show protocols
bgp {
	group internal-peers {
		type internal;
		local-address 192.168.6.5;
		export send-ospf;
		cluster 192.168.6.5;
		neighbor 192.163.6.4; # client, router B
		neighbor 192.168.40.4; # client, router C
		neighbor 192.168.0.1; # non-client, router D
		neighbor 192.168.5.5; # non-client, router E
		}
}

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
AS43859
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp