Hi Dimitry,

Does it solve a problem you're seeing? If so, I can queue it onto volatile/next.

regards,

Paul

On Tue, 14 Feb 2017, Dmitry Melekhov wrote:


Hello!

There are no replies in users mailing list,
so I decided to ask developers.

Thank you!


-------- Перенаправленное сообщение --------
Тема:   Re: nssa, external routes from bgp, problem
Дата:   Mon, 13 Feb 2017 12:19:02 +0400
От:     Dmitry Melekhov <[email protected]>
Кому:   [email protected]



OK, I found similar bug report
https: //bugzilla.quagga.net/show_bug.cgi?id=493

There is proposed patch there and it is not included into  quagga 1.2.0.

Could you tell me this bug status?
Is patch from there usable?

Thank you!

13.02.2017 11:47, Dmitry Melekhov пишет:
 Hello!


 I run quite old version of quagga -  version 0.99.24.1 , from centos7 ,

 but looks like there are no changes in ospf in newer versions....


 I have following scheme:


 area0 <->quagga<->area2<->cisco-router<->bgp.


 I need to advertise routes from bgp to ospf, so I have:

 redistribute bgp ...

 on cisco,


 but I don't need any routes from my ospf on cisco router,

 although I can have these routes on cisco right now.

 I decided make area2 nssa , so any ospf routes, including external,
 will not be on cisco router.

 It worked OK for several days, but then , at weekend, there was
 connectivity loss on bgp side and

 today I found that there are no routes from bgp in area 0, although
 they are in area 2.

 Unfortunately, I had no time to read manuals and debug, so I just removed

 area 2 nssa .


 I guess that when bgp routes were lost and appeared again, for some
 reason LSA7 was not converted by quagga to LSA5.


 Could you tell me how to solve this problem?


 Thank you!






--
Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
What is now proved was once only imagin'd.
                -- William Blake
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to