From: Cheong Kok Yong (kycheong@xxxxxxxxxxxxxx)
Date: Fri Jun 08 2001 - 03:26:56 GMT-3
when I have 6 routers in one AS, 3 routers (R1,R2 & R3) are in one cluster
with R2 is RR, another 3 routers (R4, R5, R6) with R5 is the RR, as follow:
r1---r2----r3
|
|
|
r4---r5---r6
is it a must that the RR connect with each other like the above diagram in
order to propagate the route from one cluster to another like above ? or
instead r3 can peer with r6 to achieve the full mesh ?
Cheong
-----Original Message-----
From: Ryan LaTorre [mailto:cisco@crl.fdns.net]
Sent: Thursday, June 07, 2001 9:17 PM
To: Groupstudy
Subject: Re: BGP cluster-ID
When using Route Reflectors, there is always a cluster-id associated
with the RR and it's RR clients. If not configured explicitly, the
router ID of the RR is used as the cluster-id. This ensures uniqueness
between one RR cluster and another. If there are multiple RRs in the
same cluster though, the cluster-id should be the same, and therefore
the default RID needs to be overridden. This is the only way RR clients
will know that both RRs are in the same cluster.
So to answer your question succinctly, when you have multiple RR
clusters in an AS, you do not need to configure the cluster-id, because
it will automagically do it for you.
Ryan
> ----- Original Message -----
> From: "Cheong Kok Yong" <kycheong@aeradio.com.sg>
> To: "Ccielab (E-mail)" <ccielab@groupstudy.com>
> Sent: Thursday, June 07, 2001 5:33 AM
> Subject: BGP cluster-ID
>
>
> > Hi,
> >
> > how to implement the cluster-id in BGP, when there is more than one
> Route
> > reflector in a cluster ?
> > but not needed when U have 2 clusters in one AS, each cluster having
> one RR
> > ?
> > or you still need the cluster-id whenever you have more than one RR
in
> an AS
> > even though separate cluster ?
> >
> > Cheong
> > **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:20 GMT-3