Cydon, Your RRs should (must?) be fully meshed to meet IBGP requirements. The full mesh requirement is relaxed toward clients. I believe the current best practice is assigning each RR its own cluster ID and having each client router peered with at least two RRs for redundancy. This set up results in the clients receiving two (or more) copies of the same route, something to keep in mind if your clients are carrying full Internet routes.
Depending on the size and configuration of your network a scenario like this might apply: RR1/RR2 are assigned unique cluster IDs and are fully meshed. Client A is peered RR1 and client B is peered with RR2. RR1 and RR2 must be peered with one another (as non-clients) to exchange routes learned from clients A and B. RR1 will reflect the routes from client B to client A. RR2 will reflect the routes from client A to client B. Without the RR/RR peering there is no way to propagate routes between clients A and B. Peering both clients to both RRs that would solve the problem but is not scalable in a large network where there are many RRs and significant # of clients. As always, ymmv. Lee -----Original Message----- From: cisco-nsp [mailto:[email protected]] On Behalf Of Cydon Satyr Sent: Monday, April 07, 2014 1:02 PM To: [email protected] Subject: [c-nsp] Peering between route reflectors Guys, Could you help me clear this out. Basically, if there are multiple route reflectors NOT in the forwarding path of the traffic, is there ANY reason to peer between them? I don't see a reason why they should peer, but I'd like to get this confirmed. Also, if they are NOT in the forwarding path, regardless of whether they are peering between themselves or not, it shouldn't matter if they are all in the same CLUSTER, correct ? I know the questions might look simple to you but I've seen designs where the questions pop out, and I'd like to be sure about this. regards _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
