The MPLS-OPS Archive

[Javier Antich <javier.antich@telindus.es>]

Hi Noemi, 

    That is the normal behaviour of a route reflector. It processes first
the BGP routes it receives and announces routes to its neighbors. The
difference with using normal iBGP is that it sends routes received from iBGP
peers to other iBGP clients (and some other little things).
    If you were using RR for MPLS-VPNs, routes from different VPNs, or even
from the same VPN but from different vrfs (i.e. different RD) would be sent
to the client, since they would be different routes for the RR.

Saludos.
Javier Antich 

-----Original Message-----
From: noemi.fernandez@amena.es
To: mpls-ops@mplsrc.com
Sent: 29/11/01 13:17
Subject: Route Reflector Conceptual Error




     Hi all,

     a Route Reflector (RR) is supposed to simulate IBGP connections
between the RR clients, so it has to forward the updates received from
clients to the rest of clients. However we have faced up with the
following
situation.

     We have routers A, B, C and D, as clients of a RR . A and B are
announcing to the RR the same network (for instance 1.1.1.0/24) with
different attributes. We supposed that router C and D would received the
two updates from RR. However, we have realized that the RR selelected
the
best path according to its policy routing and only reflected this best
path
to the other RR clients.

     As you could suppose we are interested on C and D receive the two
updates, so that they can apply their own policy routing to select the
best
path.

     Should not the RR forward all the updates that it receives from the
clients to the rest of the clients?
     Any suggestions to overcome this problem?

     Thanks,
     Noemí.




-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml