Instance not getting dhcp ip

asked 2017-03-30 09:57:22 -0600

ygk gravatar image

updated 2017-03-31 03:43:10 -0600

Hi All,

I have a newton three node setup on ubuntu platform. Controller, compute and network nodes. The neutron server is on controller node, the dhcp,metadata and openvswitch agents are on network node and another openvswitch agent on compute node.

When I launch an instance, it is not getting dhcp ip . Is it compulsory that the dhcp agent should be on the compute node ? Will it not work if the dhcp agent is on network node separately ?

Please advise.

Compute node configuration
------------- 

COMPUTE NODE CONFIGURATION
----------------------- 



root@compute:/# ifconfig
br-vlan   Link encap:Ethernet  HWaddr 00:0c:29:b8:5c:b1
          inet addr:192.168.40.142  Bcast:192.168.40.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:feb8:5cb1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18278 errors:0 dropped:31 overruns:0 frame:0
          TX packets:34952 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:1108044 (1.1 MB)  TX bytes:14319967 (14.3 MB)

ens33     Link encap:Ethernet  HWaddr 00:0c:29:b8:5c:b1
          inet6 addr: fe80::20c:29ff:feb8:5cb1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:67368 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42864 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16384667 (16.3 MB)  TX bytes:15827530 (15.8 MB)

ens38     Link encap:Ethernet  HWaddr 00:0c:29:b8:5c:bb
          inet addr:10.0.0.139  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:feb8:5cbb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:45437 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44673 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:24774163 (24.7 MB)  TX bytes:27231810 (27.2 MB)

ens39     Link encap:Ethernet  HWaddr 00:0c:29:b8:5c:c5
          inet addr:192.168.227.150  Bcast:192.168.227.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:feb8:5cc5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:57445 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8360 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:79782409 (79.7 MB)  TX bytes:521119 (521.1 KB)

ens40     Link encap:Ethernet  HWaddr 00:0c:29:b8:5c:cf
          inet addr:192.168.112.133  Bcast:192.168.112.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:feb8:5ccf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:337 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:41898 (41.8 KB)  TX bytes:11448 (11.4 KB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask ...
(more)
edit retag flag offensive close merge delete

Comments

The packets are not reaching the br-vlan interface from the br-int bridge inside compute node

ygk gravatar imageygk ( 2017-03-31 04:25:28 -0600 )edit

So how is the connection between the two ens33 interfaces? Did you confirm that it will transport vlan-tagged packets properly?

j-harbott gravatar imagej-harbott ( 2017-03-31 05:20:35 -0600 )edit

Yes, by default it is allowing all tagged vlans. I have installed the setup on vmware workstation.

ygk gravatar imageygk ( 2017-03-31 06:30:00 -0600 )edit