Ask Your Question

anemic's profile - activity

2014-07-18 06:37:26 -0500 received badge  Famous Question (source)
2014-02-17 01:36:34 -0500 received badge  Nice Answer (source)
2014-02-11 08:30:14 -0500 received badge  Notable Question (source)
2014-01-31 10:52:18 -0500 received badge  Teacher (source)
2014-01-30 01:45:45 -0500 received badge  Enthusiast
2014-01-28 09:50:33 -0500 commented question Instance does not receive DHCP address

can you post ovs-vsctl show, ovs-ofctl dump-flows br-tun and ifconfig at least?

2014-01-28 02:14:58 -0500 received badge  Supporter (source)
2014-01-27 17:46:36 -0500 answered a question No network communication on a 3 node Havana setup

Do not put your physical interface eth3 into br-int if you're using gre tunnels. This causes the dhcp packets to flow to ethernet via the bridge without gre.

Also it pays off to tcpdump the raw interface(eth3) to see the gre tunneling in effect and use -e to see the mac addresses.

The packet flow should be like this: compute: br-int, packets tagged with vlan1 signifying the tenant network compute: br-tun where gre encapsulation occurs compute: eth3, this is a normal network interface without any bridging! packets should be gre tunneled here wire network: eth3, gre-tunneled, again no bridging here network: br-tun, removes encapsulation and attaches vlan tag 1 (for broadcast packets it might route it to several vlans if present) network: br-int, vlan1

You can check ovs-ofctl dump-flows br-tun to see the rules for gre<->vlan switching

2014-01-27 17:19:42 -0500 answered a question How do you mount an additional disk for cinder?

I think you definitely need cinder-volume to use storage. There could be something wrong with the devstack configuration. Check what you have in the VOLUME_GROUP/VOLUME_BACKING_FILE/VOLUME_BACKING_DEVICE options. If you already have some space configured you need to remove it first as stack.sh does not grow it. My suggestion is to unmount the drive and use it using VOLUME_BACKING_DEVICE=/dev/sd... assuming you want to dedicate the whole drive to cinder. If you want to use multiple disks for storage, look for "CINDER_MULTI_LVM_BACKEND = True" option.

2014-01-27 16:45:51 -0500 commented question invalid choice: 'network-create'

what does nova --version give you? Mine gives 2.15.0. Make sure that you pull python-nova-client from the havana repo and not from ubuntu as it will be too old?

2014-01-27 16:40:59 -0500 answered a question Why network traffic gets out of control as instance is launched

Finally solved it. Somehow from the installation documentation I got the idea to add a port from br-int to internal network just like br-ex is.

So the solution was to remove the port and deconfigure ip from br-int and now it seems to work.

The key to solving this was that the internal vlan communication of the hosts was leaked to the physical network as it should be tunneled with GRE. After scanning through the openflow rules (not recommended reading for anyone) I finally figured out how the networking shoud work. The GRE tunnels are configured with remote_ip=<destination> which will send them with correct interface and need not be connected via openvswich to physical interface.

2014-01-27 13:21:41 -0500 received badge  Popular Question (source)
2014-01-22 05:35:37 -0500 asked a question Why network traffic gets out of control as instance is launched

I have followed the standard ubuntu 12.04 installation instructions with GRE networking. I have one controller node and 4 compute nodes. Two network interfaces/node (one public, one private) as per instructions. When I start an instance the network just goes crazy (I'm using 10.0.99. as private net and 10.0.20. as tenant net):

13:58:46.846449 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846453 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846458 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846465 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846471 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846476 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846482 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846489 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846494 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42
13:58:46.846500 IP 10.0.99.5 > 10.0.99.30: GREv0, key=0x4, length 64: ARP, Reply 10.0.20.11 is-at fa:16:3e:e6:b9:b3 (oui Unknown), length 42

It just generates gigabytes of traffic in seconds! The traffic can be ARP or DHCP requests or just pings and somehow the traffic multiplies so that there is a constant flow of packets.

After restarting all services if I get lucky the first instance is working fine without problems but as soon as I create second instance (that gets a different node) the problems begin. When terminating the second instance the traffic will soon stop but then the first instance is not accessible anymore.

I have double checked all the configuration ... (more)

2014-01-22 05:06:21 -0500 answered a question dhcp issue

try to tcpdump your raw interface to see the traffic. Sometimes the GRE tunnel just goes one-way, the DHCP request goes in the GRE tunnel but the reply is sent without GRE.

But I can't help how to fix that permanently, for me restarting neutron-server,neutron-plugin-openvswitch-agent and openvswitch-switch usually works.