2016-09-18 11:41:42 +0300 | received badge | ● Favorite Question (source) |
2016-07-15 17:57:09 +0300 | received badge | ● Student (source) |
2016-07-05 15:43:29 +0300 | received badge | ● Famous Question (source) |
2016-06-28 13:09:01 +0300 | received badge | ● Notable Question (source) |
2016-06-27 18:10:35 +0300 | commented answer | Open vSwitch Extension is not running on any switch Any updates to this issue? |
2016-06-27 18:10:35 +0300 | received badge | ● Commentator |
2016-06-23 02:16:25 +0300 | received badge | ● Popular Question (source) |
2016-06-22 19:48:45 +0300 | commented answer | Open vSwitch Extension is not running on any switch Still no luck: 2016-06-22T16:47:38.029Z|00086|wmi|WARN|Open vSwitch Extension is not running on any switch |
2016-06-22 18:04:15 +0300 | commented answer | Open vSwitch Extension is not running on any switch + CategoryInfo : InvalidArgument: (:) [Set-Content], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetContentCommand |
2016-06-22 18:04:04 +0300 | commented answer | Open vSwitch Extension is not running on any switch Set-Content : A positional parameter cannot be found that accepts argument 'start/strcustom/6066F867-7CA1-4418-85FD-36E3F9C0600C/VmmsWmiEventProvider'. At line:1 char:1 + sc triggerinfo ovs-vswitchd start/strcustom/6066F867-7CA1-4418-85FD-36E3F9C0600C ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
2016-06-22 17:06:36 +0300 | commented answer | Open vSwitch Extension is not running on any switch Same issue after restarting the agent |
2016-06-22 16:46:10 +0300 | asked a question | Open vSwitch Extension is not running on any switch From the ovs-vswitchd log: However, I do have the vSwitch configured with it: So what am I doing incorrectly? I'm following the blog post from https://cloudbase.it/open-vswitch-2-5... |
2016-03-04 15:15:54 +0300 | received badge | ● Famous Question (source) |
2016-02-28 03:11:47 +0300 | received badge | ● Enthusiast |
2016-02-26 22:37:05 +0300 | commented answer | external IP address unavailable after openvswitch starts I'm really at a loss here. icmp traffic is blocked to the target IP, arp traffics seems blocked, dhcp requests across the xvlan tunnel do not work. I do not know where else to troubleshoot. Any help would be appreciated. |
2016-02-26 00:32:20 +0300 | commented answer | external IP address unavailable after openvswitch starts There are three NICs in use. One is for 'public/internet" access. This is not used for openstack. The second is the openstack management interface also not used by OVS. The third and the one in question here for OVS is the interface to be used for vxlan bridging... |
2016-02-25 17:26:32 +0300 | commented answer | external IP address unavailable after openvswitch starts I did do as suggested. The IP address was then available but no traffic was routed over the vxlan tunnels. I have reverted to the original configuration |
2016-02-25 15:14:28 +0300 | received badge | ● Notable Question (source) |
2016-02-25 12:18:01 +0300 | received badge | ● Popular Question (source) |
2016-02-25 01:45:05 +0300 | commented question | external IP address unavailable after openvswitch starts If I add a flow in table 0 at priority 1 or two with an action of NORMAL I am again able to ping the other endpoints. However, that prevents the packet from reaching table 10 which should be the VXLAN learning flow (or at least that is my understanding) I'm not sure what I am missing... |
2016-02-24 22:02:19 +0300 | commented answer | external IP address unavailable after openvswitch starts the external interface may be a misnomer as it is the interface used for the vxlan tunnels. The public interface with internet access is a separate adapter. I added the flow and other OVS information at the end of the original post. What I seem to be seeing is packets being dropped by the flows |
2016-02-24 18:33:38 +0300 | received badge | ● Editor (source) |
2016-02-23 22:55:27 +0300 | asked a question | external IP address unavailable after openvswitch starts I seem to be having an issue with getting openvswitch configured properly. I am able to setup the OVS bridges br-tun and br-int with no issue and I can ping both the local IP (10.0.2.22) and the other vxlan endpoint (10.0.2.35) with no issue. However once I start the agent the IPs stop responding. The only way I can recover is to stop the agent and remove/readd br-tun. When I start the agent the vxlan tunnel is created does not seem to work. The other end is a Centos 7.2 Liberty setup and I have successfully run another Centos 7.2 compute node using OVS and vxlan... Here is the ovs-vsctl show: Other OVS information; The only flow getting packets is fropping them: cookie=0xa4424c7dd109bf50, duration=58.055s, table=0, npackets=51, nbytes=3821, idle_age=0, priority=0 actions=drop
|