Ask Your Question

visualne's profile - activity

2015-07-08 10:07:10 -0500 received badge  Taxonomist
2015-05-31 17:41:33 -0500 answered a question issue regarding port mirroring

What version of OVS are you running? I just determined that I am able to span inbound and outbound traffic from ovs version 1.11.0. But when I try to do the same thing from version 2.1.3 I am unable see inbound traffic. The only traffic I see spanned is outbound only.

2015-04-22 07:16:05 -0500 received badge  Enthusiast
2015-04-20 07:26:11 -0500 commented answer UCS blade adding linux bonded sub interface to external bridge problems

I can't see arp traffic going over the bond. But it's never being forwarded to ports in the same vlan on the bridge.

2015-04-20 07:25:16 -0500 commented answer UCS blade adding linux bonded sub interface to external bridge problems

Yes. However, I have had trouble with it. I have created "fake" interfaces in the same bridge that the bond was created in. And then put those interfaces in the corresponding vlans on the trunk. However, I am unable to achieve connectivity to of these "fake" interfaces.

2015-04-20 07:22:04 -0500 received badge  Famous Question (source)
2015-04-16 19:12:00 -0500 received badge  Notable Question (source)
2015-04-15 22:23:44 -0500 received badge  Popular Question (source)
2015-04-15 10:11:40 -0500 asked a question UCS blade adding linux bonded sub interface to external bridge problems

Hello,

I recently have installed a three node non-ha icehouse cluster on a UCS chassis. I am using the openvswitch plugin with a vxlan overlay. The installation went fine. However, I am seeing some strange behavior once the bonded sub interface is added to the external bridge on the network node. Connectivity appears to be intermittent... In other words connectivity to the ip associated to br-ex is intermittent. And of course connectivity to the floating ips is intermittent as well.

Not quite sure why this is.... I have seen mention in this link https://answers.launchpad.net/openstack-cisco/+question/245039 (https://answers.launchpad.net/opensta...) , response number two that the person has seen intermittent problems with adding a traditional linux bond to an external bridge.

The way the the NICs are presented to the network node is via a traditional port-channel on two physical interfaces that is trunking four vlans. To accommodate this setup, I setup a traditional linux bond and then created sub interfaces corresponding to each vlan. ex) bond0.200, bond0.300, bond0.400.

I then added bond0.200 to the external bridge because that is where our floating ips will be hosted. When I do this I am seeing connectivity flakiness inbound to the vms and outbound from the vms.

misc The NIC driver is: 'Ethernet controller: Cisco Systems Inc VIC Ethernet NIC'

Topology - http://pastebin.com/VVaqjfnU

^ -- The above e0 and e1 ports are on the network node that is hosted on a UCS blade.

2014-07-06 13:47:08 -0500 commented question Neutron doesn't update floatingip with multiple L3 agent Icehouse

We still have the problem. I can't give you the logs because we decided to go with another option. I created the floating ip pool with the appropriate neutron command - neutron net-create networkName --router:external=True

2014-07-05 05:19:40 -0500 received badge  Famous Question (source)
2014-07-04 01:59:56 -0500 received badge  Notable Question (source)
2014-07-04 01:59:56 -0500 received badge  Popular Question (source)
2014-07-03 07:38:50 -0500 asked a question Neutron doesn't update floatingip with multiple L3 agent Icehouse

Hello,

I recently created a five node OpenStack cloud using Packstack. I am using the neutrons OVS agent with GRE tunnels. My goal is to setup two floating ip address pools. In order to accomplish this, we followed this documentation here http://docs.openstack.org/admin-guide-cloud/content/adv_cfg_l3_agent_multi_extnet.html (http://docs.openstack.org/admin-guide...) .

The problem: Whenever I associate a floating ip address from the pool associated with this 'new' layer3 agent, the nat rule is not created. I confirmed this by issuing this command in the associated namespace ip netns exec qrouter-NAMESPACEID iptables -L -t nat. The only nat rule I see in place is the generic one associated with vms on the network attached to the router in the namespace. ex) SNAT all -- 192.168.1.0/24 anywhere to:192.168.90.41

Here is my layer3 agent.ini file (The one that is the old one that works) http://paste.openstack.org/show/85402/

Here is my second layer3 agent.ini file (The one that is not handling the nat correctly) http://paste.openstack.org/show/85404/