Fwd: about the bgp route reflector problem?

[曾小小]

---------- Forwarded message ----------
From: 曾小小 <flyinsky2018 at gmail.com>
Date: 2017-11-03 9:36 GMT+08:00
Subject: Re: about the bgp route reflector problem?
To: Matthew Walster <matthew at walster.org>


Sorry for the description of some problems.

Thank you for your answer, thank you very much！！😊

I want to know the route (ebgp) of R3, after entering route reflector (R1),
the route obtained on R2 (for example, 120.26.0.0/18, 122.72.90.78/32 route
entry) did not add BGP.originator_id and BGP. cluster_list routing
attributes?

Did you mean that route reflectors do not add route attributes
(BGP.originator_id and BGP. Cluster_list) to routes originating from ebgp?

2017-11-03 1:47 GMT+08:00 Matthew Walster <matthew at walster.org>:

> Maybe I'm missing something here, but in the examples you show,
> 120.26.0.0/18 and 122.72.90.78/32 have not been reflected? Route
> Reflection deals with iBGP only -- eBGP to iBGP does not need a route
> reflector. Only the attributes learned on the iBGP session from R4 will be
> reflected (and have the originator and cluster attributes set) to R1.
>
> Does that make sense?
>
> Matthew Walster
>
> On 2 November 2017 at 11:30, 曾小小 <flyinsky2018 at gmail.com> wrote:
>
>> about the bgp route reflector problem?
>> Why does the reflector client receive EBGP routing entries without
>> attributes??
>>
>>
>> my topology is shown below:
>>
>>         R3 (as 100)
>> |
>>                  |   （ebgp）
>> |
>> |
>>                  |            ( ibgp)
>>         R1 (RR)--------------------R4 (client) (as 200)
>> |
>>                  |
>>                  |
>> |   ( ibgp )
>>                  |
>> |
>>     R2 （client）(as 200)
>> My configuration is as follows：
>>
>> ===The R1 (RR) configuration is as follows:
>>
>> #ebgp parts
>>
>> protocol bgp bgp_pa_r3 {
>>         description "ebgp-pa-r3";
>>         multihop 10;
>>         table tab_pa_adsl;
>>         igp table tab_ospf_10;
>>         local as 200;
>>         neighbor 192.168.1.1 as 100;
>>         source address 192.168.1.2;
>>         import all;
>>         export all;
>>         next hop self;
>>         default bgp_local_pref 5;
>> }
>>
>> #rr parts
>> template bgp rr_client {
>>         description "ibgp-rr1";
>>         local 192.168.2.1 as 200;
>>         multihop;
>>         rr client;
>>         rr cluster id 1.1.1.1;
>>         }
>>
>> protocol bgp bgp_pa_r2 from rr_client {
>>         debug all;
>>         enable route refresh on;
>>         table tab_rr_1;
>>         igp table tab_ospf_10;
>>         neighbor 192.168.2.2 as 200;
>>         export all;
>>         import all;
>>         }
>>
>> protocol bgp bgp_pa_r4 from rr_client {
>>         table tab_rr_1;
>>         igp table tab_ospf_10;
>>         neighbor 192.168.2.4 as 200;
>>         export all;
>>         import all;
>>        # next hop self;
>>         }
>>
>> ==The R2 client configuration is as follows:
>>
>> protocol bgp bgp_pa_r2 {
>>         router id 192.168.2.2;
>>         debug all;
>> #       debug { states,interfaces,events };
>>         description "ibgp-rr1";
>>         import all;
>>         export all;
>>         local as 200;
>>         neighbor 192.168.2.1 as 200;
>>         source address 192.168.2.2;
>>         next hop self;
>> }
>>
>> ==================
>>
>> Check the route of R2 and find that the route entry received R4 has the
>> BGP.originator_id and BGP.cluster_list attributes,
>>  but the entry received from R1 does not have this attribute. why?
>>
>>  Thank you very much for your help!! thanks!!
>>
>>
>> The route entries viewed by R2 are as follows:
>>
>> bird> show route protocol bgp_pa_r2 all
>> 1007-121.52.236.16/32
>> 1008- Type: BGP unicast univ
>> 1012- BGP.origin: IGP
>>       BGP.as_path:
>>       BGP.next_hop: 192.168.2.4
>>       BGP.local_pref: 100
>>      * BGP.originator_id: 192.168.2.4*
>> *      BGP.cluster_list: 1.1.1.1*
>> 1007-116.211.98.20/32
>> 1008- Type: BGP unicast univ
>> 1012- BGP.origin: IGP
>>       BGP.as_path:
>>       BGP.next_hop: 192.168.2.4
>>       BGP.local_pref: 100
>>    *   BGP.originator_id: 192.168.2.4*
>> *      BGP.cluster_list: 1.1.1.1*
>> 1007-120.26.0.0/18
>> 1008- Type: BGP unicast univ
>> 1012- BGP.origin: IGP
>>       BGP.as_path: 100
>>       BGP.next_hop: 192.168.1.1
>>       BGP.local_pref: 5
>>
>> 1007-122.72.90.78/32
>> 1008- Type: BGP unicast univ
>> 1012- BGP.origin: IGP
>>       BGP.as_path: 100
>>       BGP.next_hop: 192.168.1.1
>>       BGP.local_pref: 5
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20171103/afb2ad2f/attachment.html>