I am creating Floating IP and it is always generated with its status DOWN. I am associating this IP to an instance on private network. When I am pinging this ip, I am not able to ping. Can someone explain why floating ip is generating with DOWN status and how to make its status UP. Any help will be greatly appreciated.
These are the instructions I used to create floating IP and associate to an instance.Hope this helps
Create external network
neutron net-create ext-net --shared --router:external=True
2 Set the gateway_external_network_id and external_network_bridge in /etc/neutron/l3_agent.ini
gateway_external_network_id = EXTERNAL_NTWK_UUID
external_network_bridge = br-ex
Restart l3 agent
service neutron-l3-agent restart
Create subnet in the external network
neutron subnet-create ext-net --name ext-subnet \ --allocation-pool start=FLOATING_IP_START,end=FLOATING_IP_END \ --disable-dhcp --gateway EXTERNAL_NETWORK_GATEWAY EXTERNAL_NETWORK_CIDR
Set the external network as gateway to the router
neutron router-gateway-set ROUTER_NAME EXTERNAL_NETWORK_NAME
Get a floating IP from the floating IP pool
neutron floatingip-create ext-net
Associate the floating IP to an instance
nova floating-ip-associate INSTANCE_NAME FLOATING_IP
I am having what appears to be the exact same issue, although for me in addition to the floating IP address interface having status DOWN the external router's gateway also always has a DOWN status and I cannot get any external access from my instances. I've installed Juno using the OpenStack Juju charms with neutron networking.
I've followed the network troubleshooting guide ( http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html (http://docs.openstack.org/openstack-o...) ) and find that my instances can ping each other, but not external hosts. The outbound external ping packets do appear on the integration bridge on the network node, so the internal connectivity between compute and network node seems fine, but the problem appears to be with the external router itself.
I'm not sure how to debug this but I suspect it may have something to do with the l3 agent? I have checked and the agent is running and has a smiley face in its status - the only indication of a problem is the interface status being DOWN for all the ports on the external network. Can anyone tell us what process/service/agent is responsible for issuing the "DOWN" status on interface ports?
Please, view : http://textuploader.com/1hey
Section "Create and allocate Floating IP addresses"
$ . keystonerc_boris
$ neutron port-list --device-id acfbd460-d8d7-4eba-962b-de6f2f50db12
+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
| id | name | mac_address | fixed_ips |
+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
| 4ecfe633-dbab-4660-a51c-78ea6dbcc149 | | fa:16:3e:88:05:e0 | {"subnet_id": "04b95f13-cc77-4f9a-8206-7f6ed183461d", "ip_address": "30.0.0.2"} |
+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
where acfbd460-d8d7-4eba-962b-de6f2f50db12 - your instance id
Create a floating IP
$ neutron floatingip-create ext
Created a new floatingip:
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| fixed_ip_address | |
| floating_ip_address | 192.168.122.11 |
| floating_network_id | 12e4de23-34f8-4f9f-ba2b-810c36f3cc40 |
| id | 5976f269-bca2-4c44-8860-7d493909568f |
| port_id | |
| router_id | |
| tenant_id | 2c845a6ad20e45ccb0b045cee27a9661 |
+---------------------+--------------------------------------+
It can be noticed (by running 'keystone tenant-list') , the above
tenant_id corresponds to 'ostenant')
Associate floating IP with the port of the VM
$ neutron floatingip-associate 5976f269-bca2-4c44-8860-7d493909568f 4ecfe633-dbab-4660-a51c-78ea6dbcc149
Associated floatingip 5976f269-bca2-4c44-8860-7d493909568f
Show the floating IP
$ neutron floatingip-show 5976f269-bca2-4c44-8860-7d493909568f
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| fixed_ip_address | 30.0.0.2 |
| floating_ip_address | 192.168.122.11 |
| floating_network_id | 12e4de23-34f8-4f9f-ba2b-810c36f3cc40 |
| id | 5976f269-bca2-4c44-8860-7d493909568f |
| port_id | 4ecfe633-dbab-4660-a51c-78ea6dbcc149 |
| router_id | d72adddf-4c02-4916-ae6d-16bfdaf59d99 |
| tenant_id | 2c845a6ad20e45ccb0b045cee27a9661 |
+---------------------+--------------------------------------+
List the running nova guest
$ nova list
+--------------------------------------+-------------+--------+------------+-------------+------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------------+--------+------------+-------------+------------------------------+
| acfbd460-d8d7-4eba-962b-de6f2f50db12 | cirr-guest2 | ACTIVE | None | Running | int=30.0.0.2, 192.168.122.11 |
+--------------------------------------+-------------+--------+------------+-------------+---------------------
When I am running command to create floating ip using command neutron floatingip-create public
In the output of this command there is row stating the status of the generated floating ip and its status is shown as DOWN. In your case there is no such row in the output of creting floating ip.
Asked: 2015-01-06 12:21:09 -0600
Seen: 5,942 times
Last updated: Jan 08 '15
I am having same issue too, If you have found any solution please post it over here.