[RFE] BGP neutron should allow for 32bit ASN

Bug #1573092 reported by Dr. Jens Harbott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Wishlist
Armando Migliaccio

Bug Description

Currently there is a limit hardcoded in Neutron that will only allow 16bit ASN being used in the configuration of BGP speakers and peers, i.e. a range of [1..65535]. But with https://tools.ietf.org/html/rfc6793 it is possible for BGP implementations to allow 32bit numbers to be used and in fact some RIRs have already run out of 16bit ASNs and are only handing out new ASNs that are above 65536.

So although the ryu-based reference implementation does not support this, there may be other agents e.g. based on ExaBGP that will support 32bit ASNs being used, and it doesn't seem sensible that Neutron should prevent this upfront.

Changed in neutron:
assignee: nobody → Dr. Jens Rosenboom (j-rosenboom-j)
Doug Wiegley (dougwig)
Changed in neutron:
importance: Undecided → Wishlist
status: New → Confirmed
tags: added: rfe
tags: added: l3-bgp
Changed in neutron:
status: Confirmed → Triaged
summary: - neutron and python-neutronclient should allow for 32bit ASN
+ neutron should allow for 32bit ASN
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote : Re: neutron should allow for 32bit ASN

I will defer to the BGP team to determine whether the support for this RFC is critical to the adoption of Neutron's BGP support. It definitely looks like low-hanging fruit and assumed the spin out complete and successful, and someone volunteers for addressing this need, I think it should be allowed.

summary: - neutron should allow for 32bit ASN
+ [RFE] BGP neutron should allow for 32bit ASN
Revision history for this message
Carl Baldwin (carl-baldwin) wrote :

Ryu supports only 16 bit. Should we ask Ryu to support this and require all backends to support it?

Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

According to this http://article.gmane.org/gmane.network.ryu.devel/11267 it is already on the todo list for ryu, but it may take some time to land.

Changed in neutron:
status: Triaged → Confirmed
Changed in neutron:
assignee: Dr. Jens Rosenboom (j-rosenboom-j) → nobody
tags: added: rfe-postponed
removed: rfe
Revision history for this message
Yusuke Iwase (iwase-yusuke0) wrote :

Ryu supports 32bit ASNs from the following commit.
  https://github.com/osrg/ryu/commit/55d955f4841189d2ce683988d67cab3d5836fe5c

And this commit is planned to release from version 4.5 early next month.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-dynamic-routing (master)

Fix proposed to branch: master
Review: https://review.openstack.org/499915

Changed in neutron:
assignee: nobody → Hirofumi Ichihara (ichihara-hirofumi)
status: Confirmed → In Progress
Changed in neutron:
assignee: Hirofumi Ichihara (ichihara-hirofumi) → Gary Kotton (garyk)
Changed in neutron:
assignee: Gary Kotton (garyk) → Hirofumi Ichihara (ichihara-hirofumi)
Changed in neutron:
assignee: Hirofumi Ichihara (ichihara-hirofumi) → Armando Migliaccio (armando-migliaccio)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-dynamic-routing (master)

Reviewed: https://review.openstack.org/499915
Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=972756f603f72a0026713d98a0d485eb0026094a
Submitter: Zuul
Branch: master

commit 972756f603f72a0026713d98a0d485eb0026094a
Author: Hirofumi Ichihara <email address hidden>
Date: Fri Sep 1 15:33:01 2017 +0900

    Support 4-Byte AS Numbers

    Now neutron_dynamic_routing supports 2 byte AS numbers only.
    This patch expands AS numbers constraint so that it supports
    4 byte AS numbers. It expects that operators use asplain
    notation to set AS numbers[1]. That's backward compatible with
    existing 2 byte AS numbers.

    [1]: https://tools.ietf.org/html/rfc5396

    Change-Id: I06ae0c42d983e88e1f38c501d5c85a7956f195ad
    Closes-Bug: #1573092

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-dynamic-routing 12.0.0.0b2

This issue was fixed in the openstack/neutron-dynamic-routing 12.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers