Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Bridge configured in network node - ip not assigning in VMs

Hi,

We have an issue on installing the openstack. Mainly we are struggling on the network of the openstack installation.

We have 5 servers and installed each service in seperate servers ie., 1st server: Controller, glance, keystone, dashboard 2nd Server: Nova compute 3rd " : Block storage (Cinder) 4th " : Object (Swift) 5th " : Network (neutron)

We are following the havana doc of openstack now. Please any one help us to configure these network part correctly.

We have 3 NIC in the network server, we have tried to configure the network part on this server. Now we have configured a bridge br-eth2 with the interface eth2 ip. Now we can see the eth2 ip on the bridge br-eth2. Here is our current ifconfig in the network node:

br-eth2 Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX
inet addr:31.x.y.z Bcast:31.x.y.31 Mask:255.255.255.224 inet6 addr: fe80::xxxx.xxx.xxx.xxxx/64 Scope:Link

br-int Link encap:Ethernet HWaddr 86:xx:xx:xx:xx inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link

br-tun Link encap:Ethernet HWaddr 76:xx.xx.xx.xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link

eth0 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:31.x.y.z1 Bcast:31.x.y.31 Mask:255.255.255.224

      inet6 addr: fe80::xxx.xxx.xxx.xxx/64 Scope:Link

eth1 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx inet addr:10.x.y.z Bcast:10.x.y.255 Mask:255.255.255.0

eth2 Link encap:Ethernet HWaddr 00:xx.xx.xxx..xxx inet6 addr: xxx.xxx.xxx.xxxx/64 Scope:Link

int-br-eth2 Link encap:Ethernet HWaddr 16:xx.xx.xx.xx
inet6 addr: fe80::xxxx.xxx.xxxx.xxxx/64 Scope:Link

I'm ignore some results in the ifconfig. Achually the same ip of eth2 is now displaying on the br-eth2. Please anyone help us is it the right way to configure the bridge in the neutron node. The ip is of br-eth2 currently pinging for us.

We have configured the ip forwarding via VLAN and GRE too, but failed to get the ips to the VM. Currently we are setup with VLAN

Also when we creating an instance in the openstack dashboard the ip is not correctly assigned to the vm, which showing the state as error. There is no any log retrieving on the openstack dashboard, which showing the error as "unable to get the log of Instance_ID".

Please help us to configure the network neutron node correctly. If you want any additional information, please let us know. We will provide you.

Bridge configured in network node - But ip not assigning allocate in VMs

Hi,

We have an issue on installing the openstack. Mainly we are struggling on the network of the openstack installation.

We have 5 servers and installed each service in seperate servers ie., 1st server: Controller, glance, keystone, dashboard 2nd Server: Nova compute 3rd " : Block storage (Cinder) 4th " : Object (Swift) 5th " : Network (neutron)

We are following the havana doc of openstack now. Please any one help us to configure these network part correctly.

We have 3 NIC in the network server, we have tried to configure the network part on this server. Now we have configured a bridge br-eth2 with the interface eth2 ip. Now we can see the eth2 ip on the bridge br-eth2. Here is our current ifconfig in the network node:

br-eth2 Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX
inet addr:31.x.y.z Bcast:31.x.y.31 Mask:255.255.255.224 inet6 addr: fe80::xxxx.xxx.xxx.xxxx/64 Scope:Link

br-int Link encap:Ethernet HWaddr 86:xx:xx:xx:xx inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link

br-tun Link encap:Ethernet HWaddr 76:xx.xx.xx.xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link

eth0 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:31.x.y.z1 Bcast:31.x.y.31 Mask:255.255.255.224

      inet6 addr: fe80::xxx.xxx.xxx.xxx/64 Scope:Link

eth1 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx inet addr:10.x.y.z Bcast:10.x.y.255 Mask:255.255.255.0

eth2 Link encap:Ethernet HWaddr 00:xx.xx.xxx..xxx inet6 addr: xxx.xxx.xxx.xxxx/64 Scope:Link

int-br-eth2 Link encap:Ethernet HWaddr 16:xx.xx.xx.xx
inet6 addr: fe80::xxxx.xxx.xxxx.xxxx/64 Scope:Link

I'm ignore some results in the ifconfig. Achually the same ip of eth2 is now displaying on the br-eth2. Please anyone help us is it the right way to configure the bridge in the neutron node. The ip is of br-eth2 currently pinging for us.

We have configured the ip forwarding via VLAN and GRE too, but failed to get the ips to the VM. Currently we are setup with VLAN

Also when we creating an instance in the openstack dashboard the ip is not correctly assigned to the vm, which showing the state as error. There is no any log retrieving on the openstack dashboard, which showing the error as "unable to get the log of Instance_ID".

Please help us to configure the network neutron node correctly. If you want any additional information, please let us know. We will provide you.

Bridge configured in network node - But ip not allocate in VMs

Hi,

We have an issue on installing the openstack. Mainly we are struggling on the network of the openstack installation.

We have 5 servers and installed each service in seperate servers ie., ie.,
1st server: Controller, glance, keystone, dashboard dashboard
2nd Server: Nova compute compute
3rd " : Block storage (Cinder) (Cinder)
4th " : Object (Swift) (Swift)
5th " : Network (neutron)



We are following the havana doc of openstack now. Please any one help us to configure these network part correctly.

We have 3 NIC in the network server, we have tried to configure the network part on this server. Now we have configured a bridge br-eth2 with the interface eth2 ip. Now we can see the eth2 ip on the bridge br-eth2. Here is our current ifconfig in the network node:



br-eth2 Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX
inet addr:31.x.y.z Bcast:31.x.y.31 Mask:255.255.255.224 Mask:255.255.255.224
inet6 addr: fe80::xxxx.xxx.xxx.xxxx/64 Scope:Link



br-int Link encap:Ethernet HWaddr 86:xx:xx:xx:xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link



br-tun Link encap:Ethernet HWaddr 76:xx.xx.xx.xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link



eth0 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:31.x.y.z1 Bcast:31.x.y.31 Mask:255.255.255.224



inet6 addr: fe80::xxx.xxx.xxx.xxx/64 Scope:Link

Scope:Link
eth1 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:10.x.y.z Bcast:10.x.y.255 Mask:255.255.255.0



eth2 Link encap:Ethernet HWaddr 00:xx.xx.xxx..xxx 00:xx.xx.xxx..xxx
inet6 addr: xxx.xxx.xxx.xxxx/64 Scope:Link



int-br-eth2 Link encap:Ethernet HWaddr 16:xx.xx.xx.xx
inet6 addr: fe80::xxxx.xxx.xxxx.xxxx/64 Scope:Link



I'm ignore some results in the ifconfig. Achually the same ip of eth2 is now displaying on the br-eth2. Please anyone help us is it the right way to configure the bridge in the neutron node. The ip is of br-eth2 currently pinging for us.



We have configured the ip forwarding via VLAN and GRE too, but failed to get the ips to the VM. Currently we are setup with VLAN



Also when we creating an instance in the openstack dashboard the ip is not correctly assigned to the vm, which showing the state as error. There is no any log retrieving on the openstack dashboard, which showing the error as "unable to get the log of Instance_ID".



Please help us to configure the network neutron node correctly. If you want any additional information, please let us know. We will provide you.

Bridge configured in network node - But ip not allocate in VMs

Hi,

We have Im trying to setup an issue on installing the openstack. Mainly we openstack multinode installation for a private cloud setup in centos platform. I'm struggling to setting up the neutron in the server. I've completed the installation of the service in the network node,compute and controller by following the havana doc of openstack.

There are struggling on the network of the openstack installation.

We have 5 servers and installed each service in seperate separate servers ie.,
1st server: Controller, glance, keystone, dashboard
2nd Server: Nova compute
3rd " : Block storage (Cinder)
4th " : Object (Swift)
5th " : Network (neutron)

We are following the havana doc of openstack now. Please any one help us to configure these network part correctly.

We have 3 NIC in the network server, we have tried to configure the network part on this server. Now we have configured a bridge br-eth2 with the interface eth2 ip. ip as the external interface. Now we can see the eth2 ip on the bridge br-eth2. Here is our current ifconfig in the network node:

br-eth2 Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX
Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX
inet addr:31.x.y.z Bcast:31.x.y.31 Mask:255.255.255.224
inet6 addr: fe80::xxxx.xxx.xxx.xxxx/64 Scope:Link Scope:Link
.....
...


br-int Link encap:Ethernet HWaddr 86:xx:xx:xx:xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link

br-tun Link encap:Ethernet HWaddr 76:xx.xx.xx.xx
Link encap:Ethernet HWaddr 86:xx:xx:xx:xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link
....
...

br-tun Link encap:Ethernet HWaddr 76:xx.xx.xx.xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link
....
..

eth0 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:31.x.y.z1 Bcast:31.x.y.31 Mask:255.255.255.224

.....
..

inet6 addr: fe80::xxx.xxx.xxx.xxx/64 Scope:Link
eth1 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:10.x.y.z Bcast:10.x.y.255 Mask:255.255.255.0
......
..

eth2 Link encap:Ethernet Link encap:Ethernet HWaddr 00:xx.xx.xxx..xxx
inet6 addr: xxx.xxx.xxx.xxxx/64 Scope:Link

int-br-eth2 Link encap:Ethernet HWaddr 16:xx.xx.xx.xx
HWaddr 16:xx.xx.xx.xx
inet6 addr: fe80::xxxx.xxx.xxxx.xxxx/64 Scope:Link

I'm ignore My doubt is that according to the docs it says when you port a bridge to a device, then the device ip will not ping. Is that true? First time when i did i too faced this issue.
Then i
some results in the ifconfig. Achually the same how managed the bridge ip of eth2 is to ping and get it displayed under the bridge device. Is this should be done like this way ?

Please could advise me whether i'm going wrong!!! :(

After this I installed the openvswitch plugin and enabled the GRE Tunneling as the network type. Then followed the step: creating base neutron network and configured a external network, internal network and integrated this two networks with a router too.

Is that all to do,
now displaying on the br-eth2. Please anyone help us is it the right way to configure the bridge in the neutron node. The ip is of br-eth2 currently pinging for us.

We have configured the ip forwarding via VLAN and GRE too, but failed to get the ips to the VM. Currently we are setup with VLAN

Also when we creating
ready to launch an instance in the openstack dashboard the ?

I tried one instance to launch but unfortunately it will not get an
ip and the launch fails. :( In the subnet created we can see floating ip's created but the status is not correctly assigned to the vm, which showing the state as error. There is no any log retrieving on the openstack dashboard, which showing the error as "unable to get the log of Instance_ID".

down.

I hope you have a got an idea about the issue im facing.
Please help us to configure the network neutron node correctly. If you want any additional information, please let us know. We will provide you.kindly go through advice me whether I'm missing anything in between. Or if i'm doing something wrong!!!

Please assist!!

Awaiting your kind assistance.

Bridge configured in network node - But ip not allocate in VMs

Hi,

Im trying to setup an openstack multinode installation for a private cloud setup in centos platform. I'm struggling to setting up the neutron in the server. I've completed the installation of the service in the network node,compute and controller by following the havana doc of openstack.

There are 5 servers and installed each service in separate servers ie.,
1st server: Controller, glance, keystone, dashboard
2nd Server: Nova compute
3rd " : Block storage (Cinder)
4th " : Object (Swift)
5th " : Network (neutron)

We have 3 NIC in the network server, we have tried to configure the network part on this server. Now we have configured a bridge br-eth2 with the interface eth2 ip as the external interface. Now we can see the eth2 ip on the bridge br-eth2. Here is our current ifconfig in the network node:

br-eth2 Link encap:Ethernet HWaddr 00:XX:XX:XX:XX:XX
inet addr:31.x.y.z Bcast:31.x.y.31 Mask:255.255.255.224
inet6 addr: fe80::xxxx.xxx.xxx.xxxx/64 Scope:Link
.....
...

br-int Link encap:Ethernet HWaddr 86:xx:xx:xx:xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link
....
...

br-tun Link encap:Ethernet HWaddr 76:xx.xx.xx.xx
inet6 addr: fe80:xxxx.xxxx.xxxx.xxxx/64 Scope:Link
....
..

eth0 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:31.x.y.z1 Bcast:31.x.y.31 Mask:255.255.255.224
.....
..

inet6 addr: fe80::xxx.xxx.xxx.xxx/64 Scope:Link
eth1 Link encap:Ethernet HWaddr 00:xx.xx.xx.xx.xx
inet addr:10.x.y.z Bcast:10.x.y.255 Mask:255.255.255.0
......
..

eth2 Link encap:Ethernet HWaddr 00:xx.xx.xxx..xxx
inet6 addr: xxx.xxx.xxx.xxxx/64 Scope:Link

int-br-eth2 Link encap:Ethernet HWaddr 16:xx.xx.xx.xx
inet6 addr: fe80::xxxx.xxx.xxxx.xxxx/64 Scope:Link

My doubt is that according to the docs it says when you port a bridge to a device, then the device ip will not ping. Is that true? First time when i did i too faced this issue.
Then i some how managed the bridge ip to ping and get it displayed under the bridge device. Is this should be done like this way ?

Please could advise me whether i'm going wrong!!! :(

After this I installed the openvswitch plugin and enabled the GRE Tunneling as the network type. Then followed the step: creating base neutron network and configured a external network, internal network and integrated this two networks with a router too.

Is that all to do, now is it ready to launch an instance ?

I tried one instance to launch but unfortunately it will not get an ip and the launch fails. :( In the subnet created we can see floating ip's created but the status is down.

I hope you have a got an idea about the issue im facing. Please kindly go through advice me whether I'm missing anything in between. Or if i'm doing something wrong!!!

Please assist!!

Awaiting your kind assistance.