← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #55426

[Bug 1615919] [NEW] BGP: DVR fip has next_hop to snat gateway after associate first time

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

ENV:
stable/mitaka

When A DVR floating IP associate to a port, the `floatingip_update_callback` will immediately start a `start_route_advertisements` to notify DR agent that FIP bgp route.
But this bgp route is not right, its next_hop is set to snat gateway IP address.
And then after `periodic_interval` seconds, then the DR agent will resync that DVR fip route with new next_hop to the correct FIP namespace fg-device IP address.

Reproduce:
1. create a DVR router 1, set gateway
2. create a network/subnet, and connected to the DVR router 1
3. create a VM 1
4. bind a floating IP to that VM 1
5. in DR agent LOG, you may see the following infos:

2016-08-23 13:08:26.301 13559 INFO bgpspeaker.api.base [req-829d21e2-98c3-49f3-9ba5-bd626aaf782e - - - - -] API method network.add called with args: {'prefix': u'172.16.10.68/32', 'next_hop': u'172.16.6.154'}
2016-08-23 13:08:26.302 13559 INFO neutron.services.bgp.driver.ryu.driver [req-829d21e2-98c3-49f3-9ba5-bd626aaf782e - - - - -] Route cidr=172.16.10.68/32, nexthop=172.16.6.154 is advertised for BGP Speaker running for local_as=2345.
2016-08-23 13:08:37.131 13559 INFO bgpspeaker.api.base [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] API method network.del called with args: {'prefix': u'172.16.10.68/32'}
2016-08-23 13:08:37.131 13559 INFO neutron.services.bgp.driver.ryu.driver [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] Route cidr=172.16.10.68/32 is withdrawn from BGP Speaker running for local_as=2345.
2016-08-23 13:08:37.132 13559 INFO bgpspeaker.api.base [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] API method network.add called with args: {'prefix': u'172.16.10.68/32', 'next_hop': u'172.16.10.66'}
2016-08-23 13:08:37.132 13559 INFO neutron.services.bgp.driver.ryu.driver [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] Route cidr=172.16.10.68/32, nexthop=172.16.10.66 is advertised for BGP Speaker running for local_as=2345.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-bgp

** Description changed:

  ENV:
  stable/mitaka
  
- 
  When A DVR floating IP associate to a port, the `floatingip_update_callback` will immediately start a `start_route_advertisements` to notify DR agent that FIP bgp route.
  But this bgp route is not right, its next_hop is set to snat gateway IP address.
- And then after `periodic_interval` seconds, then the DR agent will resync that DVR fip route with new next_hop to the correct FIP namespace fip-device IP address.
- 
+ And then after `periodic_interval` seconds, then the DR agent will resync that DVR fip route with new next_hop to the correct FIP namespace fg-device IP address.
  
  Reproduce:
  1. create a DVR router 1, set gateway
  2. create a network/subnet, and connected to the DVR router 1
  3. create a VM 1
  4. bind a floating IP to that VM 1
  5. in DR agent LOG, you may see the following infos:
  
- 
  2016-08-23 13:08:26.301 13559 INFO bgpspeaker.api.base [req-829d21e2-98c3-49f3-9ba5-bd626aaf782e - - - - -] API method network.add called with args: {'prefix': u'172.16.10.68/32', 'next_hop': u'172.16.6.154'}
  2016-08-23 13:08:26.302 13559 INFO neutron.services.bgp.driver.ryu.driver [req-829d21e2-98c3-49f3-9ba5-bd626aaf782e - - - - -] Route cidr=172.16.10.68/32, nexthop=172.16.6.154 is advertised for BGP Speaker running for local_as=2345.
  2016-08-23 13:08:37.131 13559 INFO bgpspeaker.api.base [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] API method network.del called with args: {'prefix': u'172.16.10.68/32'}
  2016-08-23 13:08:37.131 13559 INFO neutron.services.bgp.driver.ryu.driver [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] Route cidr=172.16.10.68/32 is withdrawn from BGP Speaker running for local_as=2345.
  2016-08-23 13:08:37.132 13559 INFO bgpspeaker.api.base [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] API method network.add called with args: {'prefix': u'172.16.10.68/32', 'next_hop': u'172.16.10.66'}
  2016-08-23 13:08:37.132 13559 INFO neutron.services.bgp.driver.ryu.driver [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] Route cidr=172.16.10.68/32, nexthop=172.16.10.66 is advertised for BGP Speaker running for local_as=2345.

** Tags added: l3-bgp

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1615919

Title:
  BGP: DVR fip has next_hop to snat gateway after associate first time

Status in neutron:
  New

Bug description:
  ENV:
  stable/mitaka

  When A DVR floating IP associate to a port, the `floatingip_update_callback` will immediately start a `start_route_advertisements` to notify DR agent that FIP bgp route.
  But this bgp route is not right, its next_hop is set to snat gateway IP address.
  And then after `periodic_interval` seconds, then the DR agent will resync that DVR fip route with new next_hop to the correct FIP namespace fg-device IP address.

  Reproduce:
  1. create a DVR router 1, set gateway
  2. create a network/subnet, and connected to the DVR router 1
  3. create a VM 1
  4. bind a floating IP to that VM 1
  5. in DR agent LOG, you may see the following infos:

  2016-08-23 13:08:26.301 13559 INFO bgpspeaker.api.base [req-829d21e2-98c3-49f3-9ba5-bd626aaf782e - - - - -] API method network.add called with args: {'prefix': u'172.16.10.68/32', 'next_hop': u'172.16.6.154'}
  2016-08-23 13:08:26.302 13559 INFO neutron.services.bgp.driver.ryu.driver [req-829d21e2-98c3-49f3-9ba5-bd626aaf782e - - - - -] Route cidr=172.16.10.68/32, nexthop=172.16.6.154 is advertised for BGP Speaker running for local_as=2345.
  2016-08-23 13:08:37.131 13559 INFO bgpspeaker.api.base [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] API method network.del called with args: {'prefix': u'172.16.10.68/32'}
  2016-08-23 13:08:37.131 13559 INFO neutron.services.bgp.driver.ryu.driver [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] Route cidr=172.16.10.68/32 is withdrawn from BGP Speaker running for local_as=2345.
  2016-08-23 13:08:37.132 13559 INFO bgpspeaker.api.base [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] API method network.add called with args: {'prefix': u'172.16.10.68/32', 'next_hop': u'172.16.10.66'}
  2016-08-23 13:08:37.132 13559 INFO neutron.services.bgp.driver.ryu.driver [req-fa420676-2ddd-4b24-9c36-932c2c8b1bef - - - - -] Route cidr=172.16.10.68/32, nexthop=172.16.10.66 is advertised for BGP Speaker running for local_as=2345.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1615919/+subscriptions

Follow ups

  Thread Previous • Date Previous • • Thread Next