Hi Ben, Currently we are implementing OXS as an independent infrastructure. While sending OXS Flow Stat Request, we are facing the below issue. We have dumped and verified the packet is in proper format only, but we are not receiving the Reply.
2016-12-21T06:46:56Z|00016|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt: sent (Success): OFPST_OXS_FLOW request (OF1.5) (xid=0x2): 2016-12-21T06:46:56Z|00017|poll_loop|DBG|wakeup due to 0-ms timeout 2016-12-21T06:47:55Z|00018|poll_loop|DBG|wakeup due to [POLLIN] on fd 4 (<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155 2016-12-21T06:47:55Z|00019|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt: received: OFPT_ECHO_REQUEST (OF1.5) (xid=0x0): 0 bytes of payload 2016-12-21T06:47:55Z|00020|ofctl|DBG|received reply with xid 00000000 != expected 02000000 2016-12-21T06:48:55Z|00021|poll_loop|DBG|wakeup due to [POLLIN][POLLHUP] on fd 4 (<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155 ovs-ofctl: OpenFlow packet receive failed (End of file) Thanks and Regards Satya Valli -----Ben Pfaff <[email protected]> wrote: ----- ======================= To: Satyavalli Rama <[email protected]> From: Ben Pfaff <[email protected]> Date: 12/16/2016 10:23PM Cc: [email protected] Subject: Re: [ovs-dev] reg: OpenVswitch Fields Implementation ======================= On Fri, Dec 16, 2016 at 03:33:11PM +0530, Satyavalli Rama wrote: > We are working on Openflow 15 EXT-334 i.e OpenFlow Extensible Flow Entry > Statistics, as per OpenvSwitch fields implementation in the meta-flow.h, > the key-value pairs for "OXS fields" to be added/declared separately or do > we need to follow the existing NXM/OXM key-value pairs. > > Please clarify us, and please refer us some guidelines that we need to > follow for implementing this Openvswitch fields. I don't think that OXS defines fields at all, so I'd expect their implementation to be independent of existing infrastructure. =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
