[j-nsp] Route reflection design consideration

[BRIANT Alain]

Salut Stephane

...

I have never tested this but I think it could work if you have of  
course separated groups for the two clusters (it's not possible  
another way)
If you have a look at the documentation:
"help topic bgp cluster"
...
    To configure a router to be a route reflector, you must do the following:
      * Configure multiple IBGP groups.

      * Configure a cluster identifier (using the cluster statement) for
        groups that are members of the cluster.

      * Configure all the groups with the same IBGP AS number.


It's said here "Configure a cluster statement for Groups" (at pluriel)
Routes are reflected between the different groups configured as they  
are reflected between a group with the cluster statement and another  
group without it (the group to full-mesh the RR).

So I believe it will work like you are waiting

help this makes you more confident.
regards

Alain



Quoting Stéphane Grosjean <Stephane.Grosjean at telindus.fr>:

> Hi folks,
>
>
> I'm scratching my head with some RR configuration, and I'd like your  
>  feeling on it. Is it correct to configure one router to be RR for   
> different clusters? Does it reflects correctly routes from one   
> cluster to another?
>
> Let's have an example: You have on one side a dual RR (router A and   
> B, cluster 1) for some routers, on the other side two other RR   
> (router C and D, cluster 2) for some other routers. As they are all   
> part of the same AS, usually you full mesh the 4 RRs together.
>
> Now, you want to create for some reasons another cluster (cluster 3)  
>  including those 4 RRs (routers A, B, C and D) and some new clients.
>
> Does it work to have on A, B, C and D 2 different clusters   
> configured? Is there any recommendation regarding the peering   
> between those 4 RRs (a full mesh within that new cluster, or a full   
> mesh in another group without cluster definition)? I guess having   
> them in the same cluster could reduce the routes exchange between   
> them (same cluster-list so they drop the routes learned from the   
> cluster). Will (A,B) reflects to cluster 1 the routes learned from   
> cluster 3, and vice-versa?
>
> I guess it works, but I have never seen such a design, nor   
> configuration anywhere...
>
>
> Kind Regards,
>
>
> Stephane.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>



----------------------------------------------------------------

Ce message electronique et tous les fichiers joints qu'il contient  
(ci-apres "le message") sont confidentiels et destines exclusivement a  
l'usage des destinataires indiques ou des personnes dument habilitees  
a les recevoir a leur place.

Si vous recevez ce message par erreur, merci de bien vouloir le  
detruire et d'en avertir l'emetteur.

Toute utilisation de ce message non conforme a sa destination, toute  
diffusion ou toute publication totale ou partielle est interdite sauf  
autorisation expresse de l'emetteur.

Les idees et opinions exprimees dans ce message sont celles de son  
auteur et ne representent pas necessairement celles de CS  
Communication & Systemes ou de ses filiales.

Malgre toutes les dispositions prises par CS Communication & Systemes  
et ses filiales pour minimiser les risques de virus, les fichiers  
joints a ce message peuvent contenir des virus qui pourraient  
endommager votre systeme informatique. Il vous appartient d'effectuer  
vos propres controles anti-virus avant d'ouvrir les fichiers joints.  
CS Communication & Systemes et ses filiales declinent toute  
responsabilite pour toute perte ou dommage resultant de l'utilisation  
de ce message et/ou des fichiers joints.

This e-mail and any file attached hereto (hereinafter 'the e-mail')  
are confidential and intended solely for the use of the adressees  
indicated below or the persons duly entitled to receive them in their  
place.

If you receive this e-mail in error, please delete it and notify the sender.

Any use of this e-mail not in accordance with its purpose, any  
dissemination or disclosure, either whole or partial, is prohibited,  
unless formally approved by the sender.

The ideas or opinions expressed in this e-mail are solely those of its  
author and do not necessarily represent those of CS Communication &  
Systeme or its affiliates.

Despite all the measures taken by CS Communication & Systeme and its  
affiliates in order to minimize the risks of virus, the files attached  
to this e-mail may contain virus which could damage your information  
system. You are responsible for processing your own anti-virus  
checking before opening any file attached hereto. Neither CS  
Communication & Systemes, nor its affiliates, shall be held liable for  
any loss or damage due to the use of this e-mail or any file attached  
hereto.