Port status is always DOWN

asked 2016-10-11 01:58:01 -0500

Steve Jobs gravatar image

updated 2016-10-11 01:59:30 -0500

Hi,

I'm using 3 node scenario for openstack KILO for my setup. After launching VM, it is not getting IP from DHCP, every time I see in the console-log of VM.

Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
Usage: /sbin/cirros-dhcpc <up|down>
No lease, failing
WARN: /etc/rc3.d/S40-network failed

I checked port-show for the connected port to VM in neutron, it is also DOWN.

root@controller:/home/user# neutron
(neutron) port-list
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                          |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 57c5852f-eeda-43a6-bbbe-413e7ada7956 |      | fa:16:3e:23:b1:18 | {"subnet_id": "7481c98d-8f9c-4639-8fe8-8c4b939b4b31", "ip_address": "199.166.1.3"} |
| c91c2d5a-37c1-484f-95d8-0841f3af294b |      | fa:16:3e:b3:f2:29 | {"subnet_id": "7481c98d-8f9c-4639-8fe8-8c4b939b4b31", "ip_address": "199.166.1.2"} |
| d95e83ff-c72e-422c-8bff-6b5fd18b4eec |      | fa:16:3e:cf:34:6a | {"subnet_id": "7481c98d-8f9c-4639-8fe8-8c4b939b4b31", "ip_address": "199.166.1.1"} |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
(neutron) port-show 57c5852f-eeda-43a6-bbbe-413e7ada7956
+-----------------------+------------------------------------------------------------------------------------+
| Field                 | Value                                                                              |
+-----------------------+------------------------------------------------------------------------------------+
| admin_state_up        | True                                                                               |
| allowed_address_pairs |                                                                                    |
| binding:vnic_type     | normal                                                                             |
| device_id             | 34ac553a-6fa6-43a2-9d83-0db4c33213cd                                               |
| device_owner          | none                                                                               |
| extra_dhcp_opts       |                                                                                    |
| fixed_ips             | {"subnet_id": "7481c98d-8f9c-4639-8fe8-8c4b939b4b31", "ip_address": "199.166.1.3"} |
| id                    | 57c5852f-eeda-43a6-bbbe-413e7ada7956                                               |
| mac_address           | fa:16:3e:23:b1:18                                                                  |
| name                  |                                                                                    |
| network_id            | fdf1c821-4c10-4ac8-832c-58e9ccc9dbbc                                               |
| security_groups       | f41b1c39-221d-445d-875e-b42d690cb10d                                               |
| status                | DOWN                                                                               |
| tenant_id             | 69b9811f8f1e4ff39acb411408a0c637                                                   |
+-----------------------+------------------------------------------------------------------------------------+

This is how I created networks.

neutron net-create ext-net --router:external \
  --provider:physical_network external --provider:network_type flat

neutron subnet-create ext-net 200.1.0.0/24 --name ext-subnet \
  --allocation-pool start=200.1.0.101,end=200.1.0.200 \
  --disable-dhcp --gateway 200.1.0.1

neutron subnet-create demo-net 199.166.1.0/24 \
  --name demo-subnet --dns-nameserver 8.8.4.4 --gateway 199.166.1.1

Output of nova-list

root@controller:/home/user# nova list
+--------------------------------------+----------------+--------+------------+-------------+----------------------+
| ID                                   | Name           | Status | Task State | Power State | Networks             |
+--------------------------------------+----------------+--------+------------+-------------+----------------------+
| 34ac553a-6fa6-43a2-9d83-0db4c33213cd | demo-instance2 | ACTIVE | -          | Running     | demo-net=199.166.1.3 |
+--------------------------------------+----------------+--------+------------+-------------+----------------------+

Any Idea..??

edit retag flag offensive close merge delete

Comments

Have same errors on LABs on VMware based on ESXi hosts. On physical machines dont have problems. Do you have also VMware LAB ?

sztyrlic111 gravatar imagesztyrlic111 ( 2016-10-11 13:58:33 -0500 )edit

Hi sztyrlic111, Thanks for comment. Yes, I'm trying all this on VMs only, not on physical machine.

Steve Jobs gravatar imageSteve Jobs ( 2016-10-12 00:08:34 -0500 )edit
1

I've tryed 3 labs on VMware: Ubuntu 16.04 + Neutron, CentOS7 + Mitaka, Ubuntu 14.04+Mitaka. All with same problem : Sending discover... :/ At least we know its VMware issue. Have no idea whats goin on :/ Promisc mode + mac change + forged transmits - ALL ACCEPT.

sztyrlic111 gravatar imagesztyrlic111 ( 2016-10-12 13:09:29 -0500 )edit

Steve... Could you please setup your LAB on physical machines too ? If you get it work we have to pm on VMware forums....

sztyrlic111 gravatar imagesztyrlic111 ( 2016-10-12 13:12:24 -0500 )edit

@sztyrlic111 Thanks for your comments Some expertise persons are looking and debugging in my setup, if it will not resolved I'll try on physical node and update ASAP

Steve Jobs gravatar imageSteve Jobs ( 2016-10-14 07:11:20 -0500 )edit