Ask Your Question
0

neutron gre segmentation id unique?

asked 2014-10-16 05:58:14 -0500

foexle gravatar image

updated 2014-10-16 07:32:35 -0500

larsks gravatar image

Hi guys,

I had a strange problem with my network.

  • Icehouse
  • Ubuntu 12.04
  • Neutron => ml2 gre

I created with an unprivileged user a network in tenant a, I switch the tenant and created a network in tenant b. I created a router in tenant a and add tenant a network. I switch to admin user and attach tenant b network to router of tenant a.

All is working if both networks have a different segmentation_id and that's the default case.

I had now a situation with two networks and the same segmentation_id .... how is that possible ? If i try to create with :

neutron net-create --tenant-id 74b33a6afdc24f8191f51a91d0f11565 --provider:network_type=gre --provider:segmentation_id=2 test2-net

409-{u'NeutronError': {u'message': u'Unable to create the network. The tunnel ID 2 is in use.', u'type': u'TunnelIdInUse', u'detail': u''}}

How can that be possible that i have networks with the same segmentation_id ? In addition i had added the interface to router and both networks was broken on the whole stack.

Questions:

  1. How can that be possible OpenStack catch the same segmentation_id if i create a new network ? ?

    neutron=# select * from ml2_network_segments ;

                      id                  |              network_id              | network_type | physical_network | segmentation_id 
    --------------------------------------+--------------------------------------+--------------+------------------+-----------------
     1f8bb020-31a1-4877-aa6c-936d4159fddd | a61a3964-42ed-4a5c-9a6a-b44d9270edab | gre   |   |  1
     f8757fbf-eabe-4603-91d5-be962b76b2f1 | 3966d105-f9b0-4c3d-8e4e-142355d67ca5 | gre  |   |   2
     0d523075-8cb1-41be-8da7-fe25b5c6eb2f | d41a58f4-116c-427f-a734-00a6f8ca4336 | gre  |    |   3
     587c1aea-0d6e-4c94-8a6e-22479285bcc9 | 8356d0a3-5eee-45be-b2de-574a6279f187 | gre  |   |   5
     2374cd77-1d0f-44b0-ab8d-943de552d34e | f00f560e-4a58-4d02-b8db-562d6332caf6 | gre  |   |   6
     617ca47d-1b1f-41d7-a0c8-19014895a2f8 | 07240086-6011-46c6-a3c3-51edffecc5c6 | gre  |   |   7
     985fb99e-1c2d-44c4-80b7-ec9e85428f71 | 20adf831-b14e-481d-9460-11db5ba8fae7 | gre |   |   8
     d25cb3cc-6cd5-4eed-b027-1b49af3425b0 | 889d29ff-ed4b-4059-bc53-a80e072031ac | gre |   |   10
     47901dee-6814-490e-b009-099a5d55685d | a81baf40-a4fe-417f-a403-da80a1f270b4 | gre |   |   11
     a0d8e330-e4ba-4acb-aff8-ab55ea2e1971 | 7e6bb686-bb16-42ed-848e-d437f3d0cd98 | gre |   |   12
     1a0aed55-4fec-4988-81b1-9b5b7c0563ed | 69ff0594-d6ad-4937-8978-dadc9c20ebaf | gre |   |   13
     571d8df6-633a-45e3-8947-0efbe64909d9 | 7b0d8a73-9031-4dab-9627-ee68cc0d2f76 | gre |   |   17
     5e052704-a57e-4156-a146-439db9a23d78 | 4f617bae-cd9a-462a-b9e0-09ea656099c8 | gre |   |   18
     e3359b38-2d83-4fa0-b14e-5a7a274de191 | 3cd7b1eb-4fee-4538-acaa-2dfd3e9fe47f | gre |   |   21
     e225748a-3241-4300-825d-4e6bc9827210 | 4c505be7-0175-4b2a-943c-1950e18d8cf8 | gre |   |   1
     153041a1-3a56-4ccb-9987-c535542819f9 | 4dfac120-c17c-4735-9858-57c432b3b929 | gre  |   |   3
     3110e32a-6343-4272-8bed-8c0ae7dec79e | 3e9104a6-59c1-4754-8bf9-27a76a381fc0 | gre  |   |   4
    
  2. Why will breaks my internal network connection of these networks ? If both have the same segmentation_id all ports with this id should have access on both networks but all was broken.

Thanks and Cheers Heiko

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-10-17 09:15:29 -0500

foexle gravatar image

All right

i found the problem why Neutron takes the wrong segment id's:

neutron=# select * from ml2_gre_allocations where allocated='t';
 gre_id | allocated 
--------+-----------
      3 | t
      4 | t
      1 | t
(4 rows)

All other segement id's are "free" .... i think that was a problem by the upgrade from Havana to IceHouse and switch to ml2.

Cheers Heiko

edit flag offensive delete link more

Comments

I have the same problem. How have you solved? Should i delete networks with the same segmentation id and then recreate?

Marco Marino gravatar imageMarco Marino ( 2015-04-30 10:24:00 -0500 )edit

Hi marco,

yes :)

Cheers Heiko

foexle gravatar imagefoexle ( 2015-06-26 06:20:21 -0500 )edit

Before recreating the network, did you manually fix the update, setting allocated to 't' to the already used gre_ids ?

sgaravat gravatar imagesgaravat ( 2015-12-22 04:49:41 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2014-10-16 05:58:14 -0500

Seen: 1,015 times

Last updated: Oct 17 '14