Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Quagga>
  3. Users
Networks are not advertised with Quagga 1.1.0 when using route-map
pstaszewski at itcare
Nov 1, 2016, 10:38 PM
Post #1 of 7 (1467 views)
Permalink
Hi


To reproduce problem:

router bgp 100
bgp router-id 192.168.0.1
network 192.168.0.0/24 route-map NET

neighbor 192.168.0.2 remote-as 64000
neighbor 192.168.0.2 description BGP-01
neighbor 192.168.0.2 shutdown
neighbor 192.168.0.2 next-hop-self
neighbor 192.168.0.2 soft-reconfiguration inbound
neighbor 192.168.0.2 route-map BGP-01-in in
neighbor 192.168.0.2 route-map BGP-01-out out


ip community-list standard NET-out permit 1000:1
ip community-list expanded own-comm permit 1000:.*

route-map NET permit 10
set community 1000:1
set local-preference 1000

route-map BGP-01-in permit 10
set comm-list own-comm delete
set community 1000:102
set local-preference 99
!
route-map BGP-01-out permit 10
match community NET-out
set comm-list own-comm delete

After quagga restart (kill bgpd / zebra - start bgpd / zebra)
No networks are advertised.



Need to do :
vtysh
conf t
router bgp 100
network 192.168.0.0/24 route-map NET

Then network 192.168.0.0/24 is advertised.






--

Attached Files:

Re: Networks are not advertised with Quagga 1.1.0 when using route-map [ In reply to ]
pstaszewski at itcare
Nov 1, 2016, 11:01 PM
Post #2 of 7 (1460 views)
Permalink
Sorry fot this example - there is no shutdown in neigh section for
testing :)

so please delete: neighbor 192.168.0.2 shutdown
When try to reproduce problem.

Thanks
Paweł

W dniu 2016-11-02 o 06:38, Paweł Staszewski pisze:
>
> Hi
>
>
> To reproduce problem:
>
> router bgp 100
> bgp router-id 192.168.0.1
> network 192.168.0.0/24 route-map NET
>
> neighbor 192.168.0.2 remote-as 64000
> neighbor 192.168.0.2 description BGP-01
> neighbor 192.168.0.2 shutdown
> neighbor 192.168.0.2 next-hop-self
> neighbor 192.168.0.2 soft-reconfiguration inbound
> neighbor 192.168.0.2 route-map BGP-01-in in
> neighbor 192.168.0.2 route-map BGP-01-out out
>
>
> ip community-list standard NET-out permit 1000:1
> ip community-list expanded own-comm permit 1000:.*
>
> route-map NET permit 10
> set community 1000:1
> set local-preference 1000
>
> route-map BGP-01-in permit 10
> set comm-list own-comm delete
> set community 1000:102
> set local-preference 99
> !
> route-map BGP-01-out permit 10
> match community NET-out
> set comm-list own-comm delete
>
> After quagga restart (kill bgpd / zebra - start bgpd / zebra)
> No networks are advertised.
>
>
>
> Need to do :
> vtysh
> conf t
> router bgp 100
> network 192.168.0.0/24 route-map NET
>
> Then network 192.168.0.0/24 is advertised.
>
>
>
>
>
>
> --
>
>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users


--
Re: Networks are not advertised with Quagga 1.1.0 when using route-map [ In reply to ]
quagga-users at alexis
Nov 2, 2016, 8:58 AM
Post #3 of 7 (1455 views)
Permalink
On Nov 2, 2016, at 1:38 AM, Paweł Staszewski <pstaszewski@itcare.pl> wrote:
> To reproduce problem:
>
> router bgp 100
> bgp router-id 192.168.0.1
> network 192.168.0.0/24 route-map NET
>
> neighbor 192.168.0.2 remote-as 64000
> neighbor 192.168.0.2 description BGP-01
> neighbor 192.168.0.2 shutdown
> neighbor 192.168.0.2 next-hop-self
> neighbor 192.168.0.2 soft-reconfiguration inbound
> neighbor 192.168.0.2 route-map BGP-01-in in
> neighbor 192.168.0.2 route-map BGP-01-out out
>
>
> ip community-list standard NET-out permit 1000:1
> ip community-list expanded own-comm permit 1000:.*
>
> route-map NET permit 10
> set community 1000:1
> set local-preference 1000
> route-map BGP-01-in permit 10
> set comm-list own-comm delete
> set community 1000:102
> set local-preference 99
> !
> route-map BGP-01-out permit 10
> match community NET-out
> set comm-list own-comm delete
>
> After quagga restart (kill bgpd / zebra - start bgpd / zebra)
> No networks are advertised.

This looks like an ordering problem. What happens if you move the route-map block in the config file so it comes before the "router bgp" declaration?

Did you write this config manually or was it emitted in that order by quagga?

/a
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: Networks are not advertised with Quagga 1.1.0 when using route-map [ In reply to ]
pstaszewski at itcare
Nov 4, 2016, 2:47 AM
Post #4 of 7 (1452 views)
Permalink
W dniu 2016-11-02 o 16:58, Alexis Rosen pisze:
> On Nov 2, 2016, at 1:38 AM, Paweł Staszewski <pstaszewski@itcare.pl> wrote:
>> To reproduce problem:
>>
>> router bgp 100
>> bgp router-id 192.168.0.1
>> network 192.168.0.0/24 route-map NET
>>
>> neighbor 192.168.0.2 remote-as 64000
>> neighbor 192.168.0.2 description BGP-01
>> neighbor 192.168.0.2 shutdown
>> neighbor 192.168.0.2 next-hop-self
>> neighbor 192.168.0.2 soft-reconfiguration inbound
>> neighbor 192.168.0.2 route-map BGP-01-in in
>> neighbor 192.168.0.2 route-map BGP-01-out out
>>
>>
>> ip community-list standard NET-out permit 1000:1
>> ip community-list expanded own-comm permit 1000:.*
>>
>> route-map NET permit 10
>> set community 1000:1
>> set local-preference 1000
>> route-map BGP-01-in permit 10
>> set comm-list own-comm delete
>> set community 1000:102
>> set local-preference 99
>> !
>> route-map BGP-01-out permit 10
>> match community NET-out
>> set comm-list own-comm delete
>>
>> After quagga restart (kill bgpd / zebra - start bgpd / zebra)
>> No networks are advertised.
> This looks like an ordering problem. What happens if you move the route-map block in the config file so it comes before the "router bgp" declaration?
>
> Did you write this config manually or was it emitted in that order by quagga?
>
> /a

This is output ordered like from "wr term"



--

Attached Files:

Re: Networks are not advertised with Quagga 1.1.0 when using route-map [ In reply to ]
quagga-users at alexis
Nov 4, 2016, 5:12 AM
Post #5 of 7 (1450 views)
Permalink
On Nov 4, 2016, at 5:47 AM, Paweł Staszewski <pstaszewski@itcare.pl> wrote:
> W dniu 2016-11-02 o 16:58, Alexis Rosen pisze:
>> This looks like an ordering problem. What happens if you move the route-map block in the config file so it comes before the "router bgp" declaration?
>>
>> Did you write this config manually or was it emitted in that order by quagga?
>
> This is output ordered like from "wr term"

And that may be the bug. Like I said, an ordering problem. Try changing it as I suggested and see if that fixes it.

/a

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: Networks are not advertised with Quagga 1.1.0 when using route-map [ In reply to ]
rmitev at speditor
Nov 4, 2016, 5:55 AM
Post #6 of 7 (1451 views)
Permalink
Look at this line:
...
neighbor 192.168.0.2 shutdown
...

On Fri, Íîåìâðè 4, 2016 11:47, Pawe? Staszewski wrote:
> W dniu 2016-11-02 o 16:58, Alexis Rosen pisze:
>> On Nov 2, 2016, at 1:38 AM, Pawe? Staszewski <pstaszewski@itcare.pl>
>> wrote:
>>> To reproduce problem:
>>>
>>> router bgp 100
>>> bgp router-id 192.168.0.1
>>> network 192.168.0.0/24 route-map NET
>>>
>>> neighbor 192.168.0.2 remote-as 64000
>>> neighbor 192.168.0.2 description BGP-01
>>> neighbor 192.168.0.2 shutdown
>>> neighbor 192.168.0.2 next-hop-self
>>> neighbor 192.168.0.2 soft-reconfiguration inbound
>>> neighbor 192.168.0.2 route-map BGP-01-in in
>>> neighbor 192.168.0.2 route-map BGP-01-out out
>>>
>>>
>>> ip community-list standard NET-out permit 1000:1
>>> ip community-list expanded own-comm permit 1000:.*
>>>
>>> route-map NET permit 10
>>> set community 1000:1
>>> set local-preference 1000
>>> route-map BGP-01-in permit 10
>>> set comm-list own-comm delete
>>> set community 1000:102
>>> set local-preference 99
>>> !
>>> route-map BGP-01-out permit 10
>>> match community NET-out
>>> set comm-list own-comm delete
>>>
>>> After quagga restart (kill bgpd / zebra - start bgpd / zebra)
>>> No networks are advertised.
>> This looks like an ordering problem. What happens if you move the
>> route-map block in the config file so it comes before the "router bgp"
>> declaration?
>>
>> Did you write this config manually or was it emitted in that order by
>> quagga?
>>
>> /a
>
> This is output ordered like from "wr term"
>
>
>
> --
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users
>



_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: Networks are not advertised with Quagga 1.1.0 when using route-map [ In reply to ]
mwinter at opensourcerouting
Nov 4, 2016, 8:46 PM
Post #7 of 7 (1451 views)
Permalink
I’ve reproduced the issue and I can confirm that this is an ordering
issue.

The route-map of the local network doesn’t exist yet when the network
is
parsed. I assume this might have been a bug introduced with all the BGP
speed
optimization.

I’ll see if I can narrow down the bad commit.

- Martin


On 4 Nov 2016, at 5:12, Alexis Rosen wrote:

> On Nov 4, 2016, at 5:47 AM, Paweł Staszewski <pstaszewski@itcare.pl>
> wrote:
>> W dniu 2016-11-02 o 16:58, Alexis Rosen pisze:
>>> This looks like an ordering problem. What happens if you move the
>>> route-map block in the config file so it comes before the "router
>>> bgp" declaration?
>>>
>>> Did you write this config manually or was it emitted in that order
>>> by quagga?
>>
>> This is output ordered like from "wr term"
>
> And that may be the bug. Like I said, an ordering problem. Try
> changing it as I suggested and see if that fixes it.
>
> /a
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal