[openstack-dev] [neutron][SFC]
Alioune
balioune3 at gmail.com
Tue Jun 21 13:05:08 UTC 2016
Hi all,
I 'm still trying to integrate sfc project with devstack using [1] but the
L2 agent is unable to chech status of br-int (see error bellow).
I think that the error is not due to OpenFlow version negociation since I
can execute the command "sudo ovs-ofctl dump-flows br-int -O OpenFlow13
table=23"
Someone knows how to solve this error ?
Regards,
Here are some information about my environement:
uname -r
3.16.0-30-generic
sudo ovs-vsctl --version
ovs-vsctl (Open vSwitch) 2.4.1
Compiled Jun 20 2016 14:56:46
DB Schema 7.12.1
sudo ovs-vsctl show
83a36bf9-e7fd-40cc-bd6e-fefb3119ff0c
Bridge br-int
Port br-int
Interface br-int
type: internal
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.4.1"
sudo ovs-ofctl dump-flows br-int -O OpenFlow13 table=23
OFPST_FLOW reply (OF1.3) (xid=0x2):
ERROR:
opt/stack/neutron/neutron/agent/linux/utils.py:101
2016-06-21 14:49:26.470 ERROR neutron.agent.linux.utils
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None]
Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23']
Exit code: 1
Stdin:
Stdout:
Stderr: ovs-ofctl: br-int is not a bridge or a socket
2016-06-21 14:49:26.485 ERROR
networking_sfc.services.sfc.common.ovs_ext_lib
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None]
Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23']
Exit code: 1
Stdin:
Stdout:
Stderr: ovs-ofctl: br-int is not a bridge or a socket
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Traceback (most recent call
last):
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib File
"/opt/stack/networking-sfc/networking_sfc/services/sfc/common/ovs_ext_lib.py",
line 125, in run_ofctl
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib
process_input=process_input)
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib File
"/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib raise RuntimeError(m)
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib RuntimeError:
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Command: ['ovs-ofctl', '-O
openflow13', 'dump-flows', 'br-int', 'table=23']
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Exit code: 1
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stdin:
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stdout:
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stderr: ovs-ofctl: br-int is
not a bridge or a socket
2016-06-21 14:49:26.485 TRACE networking_sfc.services.sfc.common.ovs_ext_lib
2016-06-21 14:49:26.485 TRACE networking_sfc.services.sfc.common.ovs_ext_lib
2016-06-21 14:49:26.492 ERROR
networking_sfc.services.sfc.common.ovs_ext_lib
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None] Unable to execute
['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23'].
2016-06-21 14:49:26.495 WARNING
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None] OVS is dead.
OVSNeutronAgent will keep running and checking OVS status periodically.
2016-06-21 14:49:26.498 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None] Agent rpc_loop -
iteration:1983 completed. Processed ports statistics: {'regular':
{'updated': 0, 'added': 0, 'removed': 0}}. Elapsed:0.050 from (pid=7331)
loop_count_and_wait
/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1680
[1] https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining
On 15 June 2016 at 16:22, Mohan Kumar <nmohankumar1011 at gmail.com> wrote:
> could you ping in IRC channel handle #openstack-neutron name : mohankumar
>
> On Wed, Jun 15, 2016 at 7:50 PM, Alioune <balioune3 at gmail.com> wrote:
>
>> Mohan,
>> Is it possible to configure the neutron-plugin-ovs-agent to use
>> OpenFlow13 ?
>>
>> Please could you tell me versions of your openstack environment ?
>>
>> Regards,
>>
>> On 15 June 2016 at 12:58, Alioune <balioune3 at gmail.com> wrote:
>>
>>> Sorry for not being clear,
>>> I juste have the same architecture like in your ONOS demo but I'm only
>>> using neutron without any SDN controller in backend.
>>>
>>> On Wednesday, 15 June 2016, Mohan Kumar <nmohankumar1011 at gmail.com>
>>> wrote:
>>>
>>>> Alioune ,
>>>>
>>>> I suspect this could be OVS cleanup issue , you have to delete ovs
>>>> bridge interfaces and manager before installing ONOS feature: , I
>>>> recommend you to follow below link to set ONOS ML2 support.
>>>>
>>>> http://artifacts.opnfv.org/onosfw/brahmaputra/Brahmaputra_userguide/onosfw-userguide.html
>>>> ( ONOSFW Environment Setup) .
>>>>
>>>> Also please check our recent demo video https://www.youtube.com/watch?v=AnVkt3SSblE
>>>>
>>>>
>>>> Thanks.,
>>>> Mohankumar.N
>>>>
>>>>
>>>> On Wed, Jun 15, 2016 at 2:47 PM, Alioune <balioune3 at gmail.com> wrote:
>>>>
>>>>> Hi Mohan,
>>>>>
>>>>> I'm still trying to set my first SFC with neutron without success.
>>>>>
>>>>> just to give you a breaf description of my platform:
>>>>>
>>>>> #uname -r
>>>>> 4.4.0-21-generic
>>>>>
>>>>> #ovs-vsctl --version
>>>>> ovs-vsctl (Open vSwitch) 2.5.0
>>>>> Compiled Mar 10 2016 14:16:49
>>>>> DB Schema 7.12.1
>>>>>
>>>>> I'm using openstack mitaka and I cloned sfc master branch
>>>>>
>>>>> I would like to implement the architecture you presented in your
>>>>> youtube [Creation of SFC in ONOS] but in my case the sourceVM is the
>>>>> address of dhcp namespace.
>>>>> I watched the presentation of your PTL on Openstack summit, it seems
>>>>> that SFC shoud create an entry flow with priority=65000 in br-int but this
>>>>> entry does not exist in my br-int
>>>>> and when I forcce openflow13 output "sudo ovs-ofctl dump-flows br-int
>>>>> -O openFlow13"
>>>>> I got the error:
>>>>> 2016-06-15T09:13:43Z|00001|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
>>>>> version negotiation failed (we support version 0x04, peer supports version
>>>>> 0x01)
>>>>> ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
>>>>>
>>>>> Please could I know what's wrong in my config ?
>>>>> Regards,
>>>>>
>>>>> Here are the scripts I used:
>>>>> Ports creation (the network net1 is created before)
>>>>> #!/bin/bash
>>>>> neutron port-create --name p1 net1 --no-security-groups
>>>>> neutron port-create --name p2 net1 --no-security-groups
>>>>> neutron port-create --name p3 net1 --no-security-groups
>>>>> neutron port-create --name p4 net1 --no-security-groups
>>>>>
>>>>> Attach VMs to ports
>>>>> #!/bin/bash
>>>>> image=cirros-0.3.3-x86_64
>>>>> flavor=m1.tiny
>>>>> network=net1
>>>>>
>>>>> nova boot --flavor $flavor --image $image --nic port-id=$(neutron
>>>>> port-list | grep -w p1 | awk '{print $2}') --nic port-id=$(neutron
>>>>> port-list | grep -w p2 | awk '{print $2}') vmvx1 --key-name admin_key
>>>>> nova boot --flavor $flavor --image $image --nic port-id=$(neutron
>>>>> port-list | grep -w p3 | awk '{print $2}') --nic port-id=$(neutron
>>>>> port-list | grep -w p4 | awk '{print $2}') vmvx2 --key-name admin_key
>>>>> # video server (destination VM)
>>>>> nova boot --flavor $flavor --image $image --nic net-id=$(neutron
>>>>> net-list | grep net1| head -1|awk ' {print $2} ') video --key-name
>>>>> admin_key
>>>>>
>>>>> Create classifier (55.55.55.2 is the address of tenant dhcp server
>>>>> and 55.7 the video server)
>>>>> neutron flow-classifier-create \
>>>>> --source-ip-prefix 55.55.55.2/32 \
>>>>> --destination-ip-prefix 55.55.55.7/32 \
>>>>> FC1
>>>>>
>>>>> neutron port-pair-create --ingress=p1 --egress=p2 PP1
>>>>> neutron port-pair-create --ingress=p3 --egress=p4 PP2
>>>>>
>>>>> neutron port-pair-group-create --port-pair PP1 PG1
>>>>> neutron port-pair-group-create --port-pair PP2 PG2
>>>>>
>>>>> neutron port-chain-create --port-pair-group PG1 --port-pair-group PG2
>>>>> --flow-classifier FC1 PC1
>>>>>
>>>>> On 13 June 2016 at 11:22, Mohan Kumar <nmohankumar1011 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Alioune,
>>>>>>
>>>>>> If you configured chain , the packet to destination VM will go
>>>>>> though all the SF VMs, say if you execute " ping destiantion-vm-ip" the
>>>>>> tcpdump in SF vms should display the packet counter.
>>>>>>
>>>>>> Sometimes port_security, security_group will block the packets to
>>>>>> enter tab interface if the destination ip not its vm ip . So make sure you
>>>>>> disabled "security_group" and "port_security" and check the same
>>>>>>
>>>>>> neutron port-update p1 --no-security-groups
>>>>>>
>>>>>> neutron port-update p1 --port-security-enabled=False
>>>>>>
>>>>>> p1 ==> neutron-port
>>>>>>
>>>>>> Thanks.,
>>>>>> Mohankumar.N
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jun 13, 2016 at 1:57 PM, Alioune <balioune3 at gmail.com> wrote:
>>>>>>
>>>>>>> Hi Mohan,
>>>>>>>
>>>>>>> could you tell me how did verify that the SFC is correctly working ?
>>>>>>>
>>>>>>> I ran "tcpdump" on SFs' Tap interfaces and tried a connection but
>>>>>>> there was no packet going through these interfaces.
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> On Monday, 13 June 2016, Mohan Kumar <nmohankumar1011 at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Alioune / nazhu,
>>>>>>>>
>>>>>>>> Logical-source-port is not mandatory in API , you can create
>>>>>>>> Flow_classifier without logical-source-port , This restriction is moved to
>>>>>>>> OVS driver . Please refer review link
>>>>>>>> https://review.openstack.org/#/c/313801/5
>>>>>>>>
>>>>>>>> If your back end driver is OVS , you need to specify the
>>>>>>>> logical-source-port is much needed as per design to avoid the return packet
>>>>>>>> to reclassified .
>>>>>>>>
>>>>>>>> Thanks.,
>>>>>>>> Mohankumar.N
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jun 13, 2016 at 7:49 AM, Na Zhu <nazhu at cn.ibm.com> wrote:
>>>>>>>>
>>>>>>>>> I find this issue also, I filed a bug about it
>>>>>>>>> https://bugs.launchpad.net/networking-sfc/+bug/1586721
>>>>>>>>> I think logical-source-port can be optional.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Juno Zhu
>>>>>>>>> IBM China Development Labs (CDL) Cloud IaaS Lab
>>>>>>>>> Email: nazhu at cn.ibm.com
>>>>>>>>> 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong
>>>>>>>>> New District, Shanghai, China (201203)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> From: Alioune <balioune3 at gmail.com>
>>>>>>>>> To: "OpenStack Development Mailing List (not for usage
>>>>>>>>> questions)" <openstack-dev at lists.openstack.org>
>>>>>>>>> Date: 2016/06/10 22:28
>>>>>>>>> Subject: Re: [openstack-dev] [neutron][SFC]
>>>>>>>>> ------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Mohan,
>>>>>>>>> Even if I clone the master branch of networking-sfc project,I get
>>>>>>>>> the following errir when creating flow-classifier, therefore I do precise
>>>>>>>>> the logical-source-port.
>>>>>>>>>
>>>>>>>>> 2016-06-10 05:34:05.693 10799 ERROR neutron.api.v2.resource
>>>>>>>>> DBError: (pymysql.err.IntegrityError) (1048, u"Column 'logical_source_port'
>>>>>>>>> cannot be null")
>>>>>>>>>
>>>>>>>>> I'm trying the example in [1]
>>>>>>>>>
>>>>>>>>> Here is a "ovs-ofctl dump-flows" on br-int ofter creating
>>>>>>>>> port-chain, I expected to see vxlan or gre tunnel encapsulation entries as
>>>>>>>>> explained in [1], may I know why there is no tunnel entry in br-int ?
>>>>>>>>>
>>>>>>>>> sudo ovs-ofctl dump-flows br-int
>>>>>>>>> NXST_FLOW reply (xid=0x4):
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2840.983s, table=0,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2840,
>>>>>>>>> priority=10,icmp6,in_port=16,icmp_type=136 actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2837.039s, table=0,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2837,
>>>>>>>>> priority=10,icmp6,in_port=17,icmp_type=136 actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2831.688s, table=0,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2831,
>>>>>>>>> priority=10,icmp6,in_port=19,icmp_type=136 actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2831.038s, table=0,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2831,
>>>>>>>>> priority=10,icmp6,in_port=18,icmp_type=136 actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2801.555s, table=0,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2801,
>>>>>>>>> priority=10,icmp6,in_port=20,icmp_type=136 actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2840.605s, table=0,
>>>>>>>>> n_packets=8, n_bytes=336, idle_age=2591, priority=10,arp,in_port=16
>>>>>>>>> actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2836.759s, table=0,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2836, priority=10,arp,in_port=17
>>>>>>>>> actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2831.485s, table=0,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2831, priority=10,arp,in_port=19
>>>>>>>>> actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2830.816s, table=0,
>>>>>>>>> n_packets=21, n_bytes=882, idle_age=1605, priority=10,arp,in_port=18
>>>>>>>>> actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2801.309s, table=0,
>>>>>>>>> n_packets=10, n_bytes=420, idle_age=545, priority=10,arp,in_port=20
>>>>>>>>> actions=resubmit(,24)
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=15755.073s, table=0,
>>>>>>>>> n_packets=3241, n_bytes=366555, idle_age=545, priority=0 actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=15754.687s, table=23,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=15754, priority=0 actions=drop
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2841.201s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2841,
>>>>>>>>> priority=2,icmp6,in_port=16,icmp_type=136,nd_target=fe80::f816:3eff:fe2d:c29d
>>>>>>>>> actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2837.177s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2837,
>>>>>>>>> priority=2,icmp6,in_port=17,icmp_type=136,nd_target=fe80::f816:3eff:fee0:f8ca
>>>>>>>>> actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2831.794s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2831,
>>>>>>>>> priority=2,icmp6,in_port=19,icmp_type=136,nd_target=fe80::f816:3eff:fe86:a668
>>>>>>>>> actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2831.150s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2831,
>>>>>>>>> priority=2,icmp6,in_port=18,icmp_type=136,nd_target=fe80::f816:3eff:feb4:965f
>>>>>>>>> actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2801.675s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2801,
>>>>>>>>> priority=2,icmp6,in_port=20,icmp_type=136,nd_target=fe80::f816:3eff:fe5a:3097
>>>>>>>>> actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2840.794s, table=24,
>>>>>>>>> n_packets=8, n_bytes=336, idle_age=2591,
>>>>>>>>> priority=2,arp,in_port=16,arp_spa=55.55.55.3 actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2836.901s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2836,
>>>>>>>>> priority=2,arp,in_port=17,arp_spa=55.55.55.4 actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2831.587s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=2831,
>>>>>>>>> priority=2,arp,in_port=19,arp_spa=55.55.55.6 actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2830.933s, table=24,
>>>>>>>>> n_packets=21, n_bytes=882, idle_age=1605,
>>>>>>>>> priority=2,arp,in_port=18,arp_spa=55.55.55.5 actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=2801.431s, table=24,
>>>>>>>>> n_packets=10, n_bytes=420, idle_age=545,
>>>>>>>>> priority=2,arp,in_port=20,arp_spa=55.55.55.8 actions=NORMAL
>>>>>>>>> cookie=0x90444f3c8fabcbe0, duration=15754.273s, table=24,
>>>>>>>>> n_packets=0, n_bytes=0, idle_age=15754, priority=0 actions=drop
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> is there a link that explains how pipelines are created by SFC in
>>>>>>>>> br-int to compare with my flows entries ?
>>>>>>>>>
>>>>>>>>> Does the flow-classifier referer to floating IPs or tenant network
>>>>>>>>> IPs to do the classification ?
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> *http://docs.openstack.org/developer/networking-sfc/system_design%20and_workflow.html*
>>>>>>>>> <http://docs.openstack.org/developer/networking-sfc/system_design%20and_workflow.html>
>>>>>>>>>
>>>>>>>>> On 9 June 2016 at 18:59, Henry Fourie <*louis.fourie at huawei.com*>
>>>>>>>>> wrote:
>>>>>>>>> Alioune,
>>>>>>>>>
>>>>>>>>> The logical-source-port refers to a Neutron port of the VM that
>>>>>>>>>
>>>>>>>>> originates the traffic that is to be processed by the port-chain.
>>>>>>>>>
>>>>>>>>> - Louis
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *From:* Alioune [mailto:*balioune3 at gmail.com*]
>>>>>>>>> *Sent:* Thursday, June 09, 2016 6:50 AM
>>>>>>>>> *To:* Mohan Kumar
>>>>>>>>> *Cc:* OpenStack Development Mailing List (not for usage questions)
>>>>>>>>> *Subject:* Re: [openstack-dev] [neutron][SFC]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks Mohan,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> After setting service_plugins and adding sfc tables to neutrondb,
>>>>>>>>> I can create port-pair, port-pair-group but classifier creation still claim
>>>>>>>>> a logical-source-port parameter.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> neutron flow-classifier-create --ethertype IPv4
>>>>>>>>> --source-ip-prefix *55.55.55.2/32* <http://55.55.55.2/32> --destination-ip-prefix
>>>>>>>>> *55.55.55.9/32* <http://55.55.55.9/32> --protocol tcp
>>>>>>>>> --source-port 22:22 --destination-port 1:65000 FC1
>>>>>>>>>
>>>>>>>>> ERROR:
>>>>>>>>>
>>>>>>>>> neutron flow-classifier-create: error: argument
>>>>>>>>> --logical-source-port is required
>>>>>>>>>
>>>>>>>>> Try 'neutron help flow-classifier-create' for more information.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please someone can explain what does --logical-source-port
>>>>>>>>> correspond to ?
>>>>>>>>>
>>>>>>>>> Does the classifier require port-create like SF ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 9 June 2016 at 09:21, Mohan Kumar <*nmohankumar1011 at gmail.com*>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> *Alioune,*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *networking-sfc resources not installed / not reachable , *If installation
>>>>>>>>> is okay, Possibly you may missed service_plugins entry in *neutron.conf
>>>>>>>>> *( in case of manual networking-sfc installation)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> it should be ,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *service_plugins =
>>>>>>>>> neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin,networking_sfc.services.sfc.plugin.SfcPlugin*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *and restart q-svc services in screen -x *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *Thanks.,*
>>>>>>>>>
>>>>>>>>> *Mohankumar.N *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jun 9, 2016 at 12:58 AM, Alioune <*balioune3 at gmail.com*>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I've switched from devstack to a normal deployment of
>>>>>>>>> openstack/mitaka and neutron-l2 agent is working fine with sfc. I can boot
>>>>>>>>> instances, create ports.
>>>>>>>>>
>>>>>>>>> However I can not create neither flow-classifier nor port-pair ...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix
>>>>>>>>> *22.1.20.1/32* <http://22.1.20.1/32>--destination-ip-prefix
>>>>>>>>> *172.4.5.6/32* <http://172.4.5.6/32>--protocol tcp --source-port
>>>>>>>>> 23:23 --destination-port 100:100 FC1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> returns: neutron flow-classifier-create: error: argument
>>>>>>>>> --logical-source-port is required
>>>>>>>>>
>>>>>>>>> Try 'neutron help flow-classifier-create' for more information.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> neutron port-pair-create --ingress=p1 --egress=p2 PP1
>>>>>>>>>
>>>>>>>>> 404 Not Found
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The resource could not be found.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Neutron server returns request_ids:
>>>>>>>>> ['req-1bfd0983-4a61-4b32-90b3-252004d90e65']
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> neutron --version
>>>>>>>>>
>>>>>>>>> 4.1.1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> p1,p2,p3,p4 have already been created, I can ping instances
>>>>>>>>> attached to these ports.
>>>>>>>>>
>>>>>>>>> Since I've not installed networking-sfc, are there additional
>>>>>>>>> config to set in neutron config files ?
>>>>>>>>>
>>>>>>>>> Or is it due to neutron-client version ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 8 June 2016 at 20:31, Mohan Kumar <*nmohankumar1011 at gmail.com*>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> neutron agent not able to fetch details from ovsdb . Could you
>>>>>>>>> check below options 1.restart ovsdb-server and execute ovs_vsctl list-br
>>>>>>>>> 2. execute ovs- vsctl list-br manually and try to check error.
>>>>>>>>>
>>>>>>>>> 3. Could be ovs cleanup issue , please check the output of sudo
>>>>>>>>> service openvswitch restart and /etc/init.d/openvswich** restart , both
>>>>>>>>> should be same
>>>>>>>>>
>>>>>>>>> Thanks.,
>>>>>>>>> Mohankumar.N
>>>>>>>>>
>>>>>>>>> On Jun 7, 2016 6:04 PM, "Alioune" <*balioune3 at gmail.com*> wrote:
>>>>>>>>>
>>>>>>>>> Hi Mohan/Cathy
>>>>>>>>>
>>>>>>>>> I've installed now ovs 2.4.0 and followed
>>>>>>>>> *https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining*
>>>>>>>>> <https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining> but
>>>>>>>>> I got this error :
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> + neutron-ovs-cleanup
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.465 22147 INFO neutron.common.config [-]
>>>>>>>>> Logging enabled!
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.468 22147 INFO neutron.common.config [-]
>>>>>>>>> /usr/local/bin/neutron-ovs-cleanup version 7.1.1.dev4
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> [-] Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline',
>>>>>>>>> '--format=json', '--', 'list-br'].
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> File "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 63, in
>>>>>>>>> run_vsctl
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> log_fail_as_error=False).rstrip()
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in
>>>>>>>>> execute
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> raise RuntimeError(m)
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> RuntimeError:
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline',
>>>>>>>>> '--format=json', '--', 'list-br']
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>> Exit code: 1
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 CRITICAL neutron [-] RuntimeError:
>>>>>>>>>
>>>>>>>>> Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline',
>>>>>>>>> '--format=json', '--', 'list-br']
>>>>>>>>>
>>>>>>>>> Exit code: 1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron Traceback (most recent
>>>>>>>>> call last):
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/usr/local/bin/neutron-ovs-cleanup", line 10, in <module>
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron sys.exit(main())
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/cmd/ovs_cleanup.py", line 89, in main
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron ovs_bridges =
>>>>>>>>> set(ovs.get_bridges())
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/common/ovs_lib.py", line 132, in
>>>>>>>>> get_bridges
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron return
>>>>>>>>> self.ovsdb.list_br().execute(check_error=True)
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 83, in execute
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron txn.add(self)
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/ovsdb/api.py", line 70, in __exit__
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron self.result =
>>>>>>>>> self.commit()
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 50, in commit
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron res =
>>>>>>>>> self.run_vsctl(args)
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 70, in
>>>>>>>>> run_vsctl
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron ctxt.reraise =
>>>>>>>>> False
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204,
>>>>>>>>> in __exit__
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron
>>>>>>>>> six.reraise(self.type_, self.value, self.tb)
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 63, in
>>>>>>>>> run_vsctl
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron
>>>>>>>>> log_fail_as_error=False).rstrip()
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron raise
>>>>>>>>> RuntimeError(m)
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron RuntimeError:
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron Command: ['sudo',
>>>>>>>>> 'ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', 'list-br']
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron Exit code: 1
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron
>>>>>>>>>
>>>>>>>>> 2016-06-07 11:25:36.512 22147 ERROR neutron
>>>>>>>>>
>>>>>>>>> + exit_trap
>>>>>>>>>
>>>>>>>>> + local r=1
>>>>>>>>>
>>>>>>>>> ++ jobs -p
>>>>>>>>>
>>>>>>>>> + jobs=
>>>>>>>>>
>>>>>>>>> + [[ -n '' ]]
>>>>>>>>>
>>>>>>>>> + kill_spinner
>>>>>>>>>
>>>>>>>>> + '[' '!' -z '' ']'
>>>>>>>>>
>>>>>>>>> + [[ 1 -ne 0 ]]
>>>>>>>>>
>>>>>>>>> + echo 'Error on exit'
>>>>>>>>>
>>>>>>>>> Error on exit
>>>>>>>>>
>>>>>>>>> + generate-subunit 1465296797 1939 fail
>>>>>>>>>
>>>>>>>>> + [[ -z /opt/stack/logs ]]
>>>>>>>>>
>>>>>>>>> + /home/alioune/devstack/tools/worlddump.py -d /opt/stack/logs
>>>>>>>>>
>>>>>>>>> World dumping... see
>>>>>>>>> /opt/stack/logs/worlddump-2016-06-07-112537.txt for details
>>>>>>>>>
>>>>>>>>> + exit 1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7 June 2016 at 12:08, Mohan Kumar <*nmohankumar1011 at gmail.com*>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi *shihanzhang / *Alioune* ,*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *your kernel (check with uname -r ) should support OVS version ,
>>>>>>>>> below table compare kern*el versions and corresponding Open
>>>>>>>>> vSwitch release support
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> | Open vSwitch | Linux kernel
>>>>>>>>> |:------------:|:-------------:
>>>>>>>>> | 1.4.x | 2.6.18 to 3.2
>>>>>>>>> | 1.5.x | 2.6.18 to 3.2
>>>>>>>>> | 1.6.x | 2.6.18 to 3.2
>>>>>>>>> | 1.7.x | 2.6.18 to 3.3
>>>>>>>>> | 1.8.x | 2.6.18 to 3.4
>>>>>>>>> | 1.9.x | 2.6.18 to 3.8
>>>>>>>>> | 1.10.x | 2.6.18 to 3.8
>>>>>>>>> | 1.11.x | 2.6.18 to 3.8
>>>>>>>>> | 2.0.x | 2.6.32 to 3.10
>>>>>>>>> | 2.1.x | 2.6.32 to 3.11
>>>>>>>>> | 2.3.x | 2.6.32 to 3.14
>>>>>>>>> | 2.4.x | 2.6.32 to 4.0
>>>>>>>>> | 2.5.x | 2.6.32 to 4.3
>>>>>>>>> *http://openvswitch.org/support/dist-docs/FAQ.md.txt*
>>>>>>>>> <http://openvswitch.org/support/dist-docs/FAQ.md.txt>(
>>>>>>>>> ### Q: What Linux kernel versions does each Open vSwitch release
>>>>>>>>> work with?)
>>>>>>>>> I installed SFC with OVS 2.4.0 and 2.5.0 and not seen any issue
>>>>>>>>> Please check SFC wiki for installation guidelines :
>>>>>>>>> *https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining*
>>>>>>>>> <https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining>
>>>>>>>>>
>>>>>>>>> Thanks.,
>>>>>>>>> Mohankumar.N
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jun 7, 2016 at 1:46 PM, shihanzhang <
>>>>>>>>> *ayshihanzhang at 126.com*> wrote:
>>>>>>>>>
>>>>>>>>> Hi Alioune and Cathy,
>>>>>>>>>
>>>>>>>>> For devstack on ubuntu14.04, the default ovs version
>>>>>>>>> is 2.0.2, so there was the error as Alioune said.
>>>>>>>>>
>>>>>>>>> Do we need to install speical ovs version in networking-sfc
>>>>>>>>> devstack plugin.sh?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 在 2016-06-07 07:48:26，"Cathy Zhang" <*Cathy.H.Zhang at huawei.com*>
>>>>>>>>> 写道：
>>>>>>>>>
>>>>>>>>> Hi Alioune,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Which OVS version are you using?
>>>>>>>>>
>>>>>>>>> Try openvswitch version 2.4.0 and restart the openvswitch-server
>>>>>>>>> before installing the devstack.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Cathy
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *From:* Alioune [mailto:*balioune3 at gmail.com*]
>>>>>>>>> *Sent:* Friday, June 03, 2016 9:07 AM
>>>>>>>>> *To:* *openstack-dev at lists.openstack.org*
>>>>>>>>> *Cc:* Cathy Zhang
>>>>>>>>> *Subject:* [openstack-dev][neutron][SFC]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Probleme with OpenStack SFC
>>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> I've installed Openstack SFC with devstack and all module are
>>>>>>>>> corretly running except the neutron L2-agent
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> After a "screen -rd", it seems that there is a conflict between
>>>>>>>>> l2-agent and SFC (see trace bellow).
>>>>>>>>>
>>>>>>>>> I solved the issue with "sudo ovs-vsctl set bridge br
>>>>>>>>> protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13" on all openvswitch
>>>>>>>>> bridge (br-int, br-ex, br-tun and br-mgmt0).
>>>>>>>>>
>>>>>>>>> I would like to know:
>>>>>>>>>
>>>>>>>>> - If someone knows why this error arrises ?
>>>>>>>>>
>>>>>>>>> - is there another way to solve it ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:56.323 WARNING
>>>>>>>>> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] OVS is dead.
>>>>>>>>> OVSNeutronAgent will keep running and checking OVS status periodically.
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:56.330 DEBUG
>>>>>>>>> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Agent rpc_loop -
>>>>>>>>> iteration:4722 completed. Processed ports statistics: {'regular':
>>>>>>>>> {'updated': 0, 'added': 0, 'removed': 0}}. Elapsed:0.086 from (pid=12775)
>>>>>>>>> loop_count_and_wait
>>>>>>>>> /opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1680
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.256 DEBUG
>>>>>>>>> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Agent rpc_loop -
>>>>>>>>> iteration:4723 started from (pid=12775) rpc_loop
>>>>>>>>> /opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1732
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.258 DEBUG neutron.agent.linux.utils
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Running command
>>>>>>>>> (rootwrap daemon): ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int',
>>>>>>>>> 'table=23'] from (pid=12775) execute_rootwrap_daemon
>>>>>>>>> /opt/stack/neutron/neutron/agent/linux/utils.py:101
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.311 ERROR neutron.agent.linux.utils
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None]
>>>>>>>>>
>>>>>>>>> Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int',
>>>>>>>>> 'table=23']
>>>>>>>>>
>>>>>>>>> Exit code: 1
>>>>>>>>>
>>>>>>>>> Stdin:
>>>>>>>>>
>>>>>>>>> Stdout:
>>>>>>>>>
>>>>>>>>> Stderr:
>>>>>>>>> 2016-06-03T12:51:58Z|00001|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
>>>>>>>>> version negotiation failed (we support version 0x04, peer supports version
>>>>>>>>> 0x01)
>>>>>>>>>
>>>>>>>>> ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 ERROR
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None]
>>>>>>>>>
>>>>>>>>> Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int',
>>>>>>>>> 'table=23']
>>>>>>>>>
>>>>>>>>> Exit code: 1
>>>>>>>>>
>>>>>>>>> Stdin:
>>>>>>>>>
>>>>>>>>> Stdout:
>>>>>>>>>
>>>>>>>>> Stderr:
>>>>>>>>> 2016-06-03T12:51:58Z|00001|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
>>>>>>>>> version negotiation failed (we support version 0x04, peer supports version
>>>>>>>>> 0x01)
>>>>>>>>>
>>>>>>>>> ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib Traceback (most recent call
>>>>>>>>> last):
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib File
>>>>>>>>> "/opt/stack/networking-sfc/networking_sfc/services/sfc/common/ovs_ext_lib.py",
>>>>>>>>> line 125, in run_ofctl
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib
>>>>>>>>> process_input=process_input)
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib File
>>>>>>>>> "/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib raise RuntimeError(m)
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib RuntimeError:
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib Command: ['ovs-ofctl', '-O
>>>>>>>>> openflow13', 'dump-flows', 'br-int', 'table=23']
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib Exit code: 1
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib Stdin:
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib Stdout:
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib Stderr:
>>>>>>>>> 2016-06-03T12:51:58Z|00001|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
>>>>>>>>> version negotiation failed (we support version 0x04, peer supports version
>>>>>>>>> 0x01)
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib ovs-ofctl: br-int: failed to
>>>>>>>>> connect to socket (Broken pipe)
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.323 TRACE
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.335 ERROR
>>>>>>>>> networking_sfc.services.sfc.common.ovs_ext_lib
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Unable to execute
>>>>>>>>> ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23'].
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.337 WARNING
>>>>>>>>> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] OVS is dead.
>>>>>>>>> OVSNeutronAgent will keep running and checking OVS status periodically.
>>>>>>>>>
>>>>>>>>> 2016-06-03 12:51:58.341 DEBUG
>>>>>>>>> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
>>>>>>>>> [req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Agent rpc_loop -
>>>>>>>>> iteration:4723 completed. Processed ports statistics: {'regular':
>>>>>>>>> {'updated': 0, 'added': 0, 'removed': 0}}. Elapsed:0.085 from (pid=12775)
>>>>>>>>> loop_count_and_wait
>>>>>>>>> /opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1680
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> __________________________________________________________________________
>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>> Unsubscribe:
>>>>>>>>> *OpenStack-dev-request at lists.openstack.org?subject:unsubscribe*
>>>>>>>>> <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>>>>>>>>> *http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev*
>>>>>>>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> __________________________________________________________________________
>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>> Unsubscribe:
>>>>>>>>> *OpenStack-dev-request at lists.openstack.org?subject:unsubscribe*
>>>>>>>>> <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>>>>>>>>> *http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev*
>>>>>>>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> __________________________________________________________________________
>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>> Unsubscribe:
>>>>>>>>> *OpenStack-dev-request at lists.openstack.org?subject:unsubscribe*
>>>>>>>>> <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>>>>>>>>> *http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev*
>>>>>>>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> __________________________________________________________________________
>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>> Unsubscribe:
>>>>>>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> __________________________________________________________________________
>>>>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>>>> Unsubscribe:
>>>>>>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160621/43bbd709/attachment.html>
More information about the OpenStack-dev
mailing list