Thanks. the patch works fine.

On Tue, Jun 12, 2018 at 11:38 AM, Iwase Yusuke <iwase.yusu...@gmail.com>
wrote:

> Hi,
>
> Hmmm... the current implementation seems not to suppose to have the locally
> generated routes when configured itself as a Route Reflector. Only
> supposed to
> reflect the received routes.
>
> The attached patch fixes this problem?
>
> Thanks,
> Iwase
>
> On 2018年06月11日 20:36, knet solutions wrote:
>
>> Hi Iwase,
>>
>> When i configure route_reflector,  RYU BGP Speaker couldnt establish the
>> comminication with traditional bird router.
>> My code snippet is as below,
>>
>>         # code snippet
>>
>>          self.bgp_speaker = BGPSpeaker(64511, router_id,
>>                                        ssh_console=True, ssh_port=4999,
>>                                        ssh_host='localhost',
>>                                        
>> best_path_change_handler=self.best_path_change_handler
>> )
>>         self.bgp_speaker.neighbor_add(neighbor1_id, 64511,
>> is_route_reflector_client=True)
>>          self.bgp_speaker.neighbor_add(neighbor2_id, 64511,
>> is_route_reflector_client=True)
>>          self.bgp_speaker.prefix_add(prefix="10.2.1.0/24 <
>> http://10.2.1.0/24>")
>>
>>
>> The error is(observed from wireshark trace),
>> Bird router closes the connection with UPDATE MESSAGE ERROR(3)/ Minor
>> code: Optional attribute Error(9)
>>
>> In the bird log , i see the below error
>>
>> Connection to peer 192.168.2.2 lost, reason: Peer closed connection
>> Resetting retry connect loop: True
>> Peer closed connectio
>>
>>
>>
>> Note :  If i just remove the "is_route_reflector_client=True" flag,
>> neighbor establishment and update happens.
>>
>> Query1:
>> 1. To enable route_reflector in RYU,  Do i need to configuration any
>> other API or parameters?
>>
>> Thanks
>> Suresh
>>
>>
>> On Thu, May 31, 2018 at 11:41 AM, Iwase Yusuke <iwase.yusu...@gmail.com
>> <mailto:iwase.yusu...@gmail.com>> wrote:
>>
>>     Hi,
>>
>>     > All routers are same AS number.
>>
>>     This means Ryu and other routers are connected with the iBGP(internal
>> BGP)
>>     peering, right? On the iBGP, generally the received routes from other
>> iBGP peers
>>     will not be advertised in order to avoid network loops. If you need
>> to advertise
>>     the iBGP routers to other iBGP peers, please configure Ryu as a Route
>> Reflector
>>     (or use different AS number on other routers for external BGP
>> peering).
>>
>>     To configure route reflector, please enable
>> "is_route_reflector_client" option.
>>     http://ryu.readthedocs.io/en/latest/library_bgp_speaker_ref.
>> html#ryu.services.protocols.bgp.bgpspeaker.BGPSpeaker.neighbor_add
>>     <http://ryu.readthedocs.io/en/latest/library_bgp_speaker_ref
>> .html#ryu.services.protocols.bgp.bgpspeaker.BGPSpeaker.neighbor_add>
>>
>>     Thanks,
>>     Iwase
>>     <http://knetsolutions.in/>
>>
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>
>>


-- 

*Regards, *
*Knet solutions.*

https://github.com/knetsolutions/KNet
http://knet-topology-builder.readthedocs.io/
http://knetsolutions.in/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to