New Question

JohnF's profile - activity

2016-09-18 11:41:42 +0200 received badge  Favorite Question (source)
2016-07-15 17:57:09 +0200 received badge  Student (source)
2016-07-05 15:43:29 +0200 received badge  Famous Question (source)
2016-06-28 13:09:01 +0200 received badge  Notable Question (source)
2016-06-27 18:10:35 +0200 commented answer Open vSwitch Extension is not running on any switch

Any updates to this issue?

2016-06-27 18:10:35 +0200 received badge  Commentator
2016-06-23 02:16:25 +0200 received badge  Popular Question (source)
2016-06-22 19:48:45 +0200 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 +0200 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 +0200 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 +0200 commented answer Open vSwitch Extension is not running on any switch

Same issue after restarting the agent

2016-06-22 16:46:10 +0200 asked a question Open vSwitch Extension is not running on any switch
PS C:\Users\Administrator> ovs-vsctl.exe add-br br-port3
ovs-vsctl:  Error detected while setting up 'br-port3'.  See ovs-vswitchd log for details.

From the ovs-vswitchd log:

2016-06-22T13:27:04.187Z|00030|wmi|WARN|Open vSwitch Extension is not running on any switch
2016-06-22T13:27:04.188Z|00031|wmi|WARN|Could not find HRESULT description for: 0.
2016-06-22T13:27:04.188Z|00032|dpif_netlink|ERR|Could not create wmi internal port with name:br-port3
2016-06-22T13:27:04.188Z|00033|bridge|INFO|bridge br-port3: using datapath ID 00009a9ef2a50240
2016-06-22T13:27:04.188Z|00034|connmgr|INFO|br-port3: added service controller "punix:C:\ProgramData\openvswitch\/br-port3.mgmt"

However, I do have the vSwitch configured with it:

PS C:\Users\Administrator> get-VMSwitchExtension -VMSwitchName vSwitch -Name "Open vSwitch Extension"


Id                  : 583CC151-73EC-4A6A-8B47-578297AD7623
Name                : Open vSwitch Extension
Vendor              : Open vSwitch
Version             : 16.46.56.366
ExtensionType       : Forwarding
ParentExtensionId   :
ParentExtensionName :
SwitchId            : 9224fc44-b9eb-49cf-b1f8-e5a6c57893e7
SwitchName          : vSwitch
Enabled             : True
Running             : True
ComputerName        : WIN-HQHVLTQ4OLK
Key                 :
IsDeleted           : False

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 +0200 received badge  Famous Question (source)
2016-02-28 03:11:47 +0200 received badge  Enthusiast
2016-02-26 22:37:05 +0200 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 +0200 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 +0200 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 +0200 received badge  Notable Question (source)
2016-02-25 12:18:01 +0200 received badge  Popular Question (source)
2016-02-25 01:45:05 +0200 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 +0200 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 +0200 received badge  Editor (source)
2016-02-23 22:55:27 +0200 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:

C:\Users\Administrator>ovs-vsctl show
d35452eb-9055-4fa3-b027-272833e0e4bd
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
        Port "external.1"
            Interface "external.1"
        Port "vxlan-0a000223"
            Interface "vxlan-0a000223"
                type: vxlan
                options: {df_default="true", dst_port="8472", in_key=flow, local_ip="10.0.2.22", out
_key=flow, remote_ip="10.0.2.35"}
        Port internal
            Interface internal
    Bridge br-int
        fail_mode: secure
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal

I'm not sure how to continue to debug this...


Here is the OVS config:

Here is the OVS config on the server:

    [DEFAULT]
    bridge_mappings = public:public-vs1
    verbose=true
    debug=false
    control_exchange=neutron
    policy_file=C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\etc\policy.json
    rpc_backend=neutron.openstack.common.rpc.impl_kombu
    rabbit_host=controller
    rabbit_port=5672
    rabbit_userid=openstack
    rabbit_password=kb2rgb66
    logdir=D:\OpenStack\Log\
    logfile=neutron-ovs-agent.log
    [agent]
    tunnel_types = vxlan
    vxlan_udp_port = 8472
    enable_metrics_collection=false
    [SECURITYGROUP]
    enable_security_group=true
    [ovs]
    local_ip = 10.0.2.22
    tunnel_bridge = br-tun
    integration_bridge = br-int
    tenant_network_type = vxlan
    enable_tunneling = true

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

C:\Users\Administrator>ovs-ofctl show br-tun
OFPT_FEATURES_REPLY (xid=0x2): dpid:00007eb58589ab4cn_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 1(external.1): addr:00:00:00:00:00:00
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
 2(internal): addr:00:00:00:00:00:00
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
 3(patch-int): addr:02:9b:32:fb:4b:6a
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 4(vxlan-0a000223): addr:8a:27:a8:42:66:d0
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 5(vxlan-0a000224): addr:7e:29:aa:d4:1d:b6
     config:     0
     state:      0
     speed: 0 Mbps now, 0 Mbps max
 LOCAL(br-tun): addr:00:00:00:00:00:00
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0


C:\Users\Administrator>ovs-vsctl list-ports br-tun
external.1
internal
patch-int
vxlan-0a000223
vxlan-0a000224

C:\Users\Administrator>ovs-vsctl list-ports br-int
patch-tun


C:\Users ...
(more)