Ask Your Question
1

Assigning Floating IP fails.

asked 2014-02-05 04:08:17 -0500

Krist gravatar image

updated 2014-02-06 17:20:32 -0500

smaffulli gravatar image

I'm trying to assign a floating IP, which unfortunately failed, with the following error:

External network a03ebfb2-f897-4181-bf14-109f507eecac is not reachable from subnet 881be3de-bd37-4672-aa9f-1ee18c7f0fd4. Therefore, cannot associate Port f3692842-5514-4afc-a906-3fb1245e820c with a Floating IP

The network config on the host the L3 agent runs on is rather complex, and I think that I might not have configured everything the correct way. But I'm not sure what I'm missing. Something probably isn't OK.

Output of a few commands that might be helpfull:

[root@dc1-03 ~]# ip netns exec qdhcp-a03ebfb2-f897-4181-bf14-109f507eecac ip a
32: tapd3e6cb74-4d: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether fa:16:3e:ce:63:ab brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.151/24 brd 10.0.0.255 scope global tapd3e6cb74-4d
    inet6 fe80::f816:3eff:fece:63ab/64 scope link 
       valid_lft forever preferred_lft forever
33: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
[root@dc1-03 ~]# ovs-vsctl show
485f9e34-4319-4a6e-a8df-ec9e40c30df4
    Bridge br-tun
        Port "gre-4"
            Interface "gre-4"
                type: gre
                options: {in_key=flow, local_ip="172.16.2.3", out_key=flow, remote_ip="172.16.2.22"}
        Port "gre-3"
            Interface "gre-3"
                type: gre
                options: {in_key=flow, local_ip="172.16.2.3", out_key=flow, remote_ip="172.16.2.18"}
        Port "gre-2"
            Interface "gre-2"
                type: gre
                options: {in_key=flow, local_ip="172.16.2.3", out_key=flow, remote_ip="172.16.2.6"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-int
        Port "qr-0ab74295-3b"
            tag: 4
            Interface "qr-0ab74295-3b"
                type: internal
        Port "tapd3e6cb74-4d"
            tag: 4
            Interface "tapd3e6cb74-4d"
                type: internal
        Port "qr-f0e8404e-a9"
            tag: 1
            Interface "qr-f0e8404e-a9"
                type: internal
        Port "tap1ac50aa1-e8"
            tag: 3
            Interface "tap1ac50aa1-e8"
                type: internal
        Port "qr-2b7745aa-7a"
            tag: 3
            Interface "qr-2b7745aa-7a"
                type: internal
        Port "qr-7f7a8355-a1"
            tag: 2
            Interface "qr-7f7a8355-a1"
                type: internal
        Port "tap071025ee-98"
            tag: 2
            Interface "tap071025ee-98"
                type: internal
        Port "qr-b6d898ee-99"
            tag: 1
            Interface "qr-b6d898ee-99"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port "tap76d2ea76-c7"
            tag: 1
            Interface "tap76d2ea76-c7"
                type: internal
        Port "qr-7f8fbb47-30"
            tag: 1
            Interface "qr-7f8fbb47-30"
                type: internal
    ovs_version: "1.11.0"


[root@dc1-03 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: p1p1: <BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc mq master bond0 state UNKNOWN qlen 1000
    link/ether b8:ca:3a:9e:44:2e brd ff:ff:ff:ff:ff:ff
3: em1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000
    link/ether b8:ca:3a:9e:44:2e brd ff:ff:ff:ff:ff:ff
4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether f6:93:bb ...
(more)
edit retag flag offensive close merge delete

Comments

Are you using GRE or VLAN? Can you post the output of 'neutron net-show [ID]', 'neutron subnet-show [ID]', and 'neutron router-show [ID]' for the relevant Neutron network devices so we can see what your configuration looks like?

dtaylor gravatar imagedtaylor ( 2014-02-06 20:11:19 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
6

answered 2014-02-10 07:14:12 -0500

Diego Lima gravatar image

It looks like you created a network but didn't create a router to connect it to your external network. In order to assign a floating IP to an instance you need the following:

  1. Properly configured external network
  2. Properly configured internal network
  3. Router that has a gateway set on your external network and a port in your internal network
  4. Instance launched in your internal network (and whose gateway is the above mentioned router)

In your case the external network is probably "a03ebfb2-f897-4181-bf14-109f507eecac" and your internal network is "881be3de-bd37-4672-aa9f-1ee18c7f0fd4".

The whole process of creating an internal network and adding the router is like this:

$ neutron net-create samplenetwork
$ neutron subnet-create samplenetwork 192.168.0.0/24
$ neutron router-create samplerouter
$ neutron router-gateway-set samplerouter externalnet
$ neutron router-interface-add  samplerouter subnetID

On the example above externalnet is your external network and you'd replace subnetID with the ID of the subnet you just created.

After doing that you should launch an instance into that subnet and then associate the floating IP.

edit flag offensive delete link more
0

answered 2017-04-21 08:38:54 -0500

updated 2017-04-21 09:03:16 -0500

Got the same issue:

image description

Make sure you have created a router with gateway on your public network (from which the floating IP is generated) and then add an interface (LAN) from the internal nework from which your instance took its IP.

image description

It should work fine.

image description

If you start by creating the router, wou will not encounter such error. In my opinion a control should be done before closing the assign floatingIP box (like for a forgotten required field)

edit flag offensive delete link more

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

1 follower

Stats

Asked: 2014-02-05 04:08:17 -0500

Seen: 6,764 times

Last updated: Apr 21 '17