Please don't drop the mailing list. You are clearly using OpenFlow 1.0. I don't know much about POX. You should probably ask on a POX mailing list.
On Sat, Feb 21, 2015 at 12:35:26PM +0000, AMER wrote: > Do you think the problem because the pox are still using OF 1.0, if so how to > force it to use the required version. > > Thank you > > Eng Amer Alghadhban > > COE > > SANS-GCFW > > CEH, SCNP, CCNA > > > > Date: Fri, 20 Feb 2015 08:07:57 -0800 > > From: b...@nicira.com > > To: amer7...@hotmail.com > > CC: dev@openvswitch.org; murphy.mccau...@gmail.com > > Subject: Re: [ovs-dev] Error > > > > The error says "Version: 1", so you are still using OpenFlow 1.0. > > > > On Fri, Feb 20, 2015 at 02:06:49PM +0000, AMER wrote: > > > Hello, > > > after upgrading my openvswitch to the latest version still I am facing > > > same error: > > > [00-00-00-00-00-02 183] Error: header:[00-00-00-00-00-02 183] Error: > > > version: 1[00-00-00-00-00-02 183] Error: type: 1 > > > (OFPT_ERROR)[00-00-00-00-00-02 183] Error: length: > > > 76[00-00-00-00-00-02 183] Error: xid: 915[00-00-00-00-00-02 183] > > > Error: type: OFPET_FLOW_MOD_FAILED (3)[00-00-00-00-00-02 183] Error: > > > code: OFPFMFC_BAD_EMERG_TIMEOUT (3)[00-00-00-00-00-02 183] Error: > > > datalen: 64[00-00-00-00-00-02 183] Error: 0000: 01 0e 00 48 00 00 03 93 > > > 00 10 00 1f 00 00 00 00 |...H............|[00-00-00-00-00-02 183] > > > Error: 0010: 00 00 00 00 00 00 00 00 00 00 4e 6f 6e 65 00 00 > > > |..........None..|[00-00-00-00-00-02 183] Error: 0020: 00 00 00 00 00 00 > > > 00 00 00 00 00 00 00 00 00 00 |................|[00-00-00-00-00-02 > > > 183] Error: 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 > > > |................|INFO:openflow.of_01:[00-00-00-00-00-01 184] > > > closedINFO:openflow.of_01:[00-00-00-00-00-02 183] closed^CINFO:core:Going > > > down...INFO:openflow.of_01:[00-00-00-00-00-02 187] > > > disconnectedINFO:openflow.of_01:[00-00-00-00-00-03 186] > > > disconnectedINFO:openflow.of_01:[00-00-00-00-00-04 185] > > > disconnectedINFO:core:Down. > > > I am using POX with nicira installed in mininet pox.py > > > openflow.nicira --convert-packet-in forwarding.l2_nx > > > Thank you > > > > > > > > > Eng Amer Alghadhban > > > > > > COE > > > > > > SANS-GCFW > > > > > > CEH, SCNP, CCNA > > > > > > > > > > Date: Sun, 15 Feb 2015 08:25:43 -0800 > > > > From: b...@nicira.com > > > > To: amer7...@hotmail.com > > > > CC: dev@openvswitch.org > > > > Subject: Re: [ovs-dev] Error > > > > > > > > OpenFlow 1.3 is your best bet; it is well supported by OVS and widely > > > > supported by other switches too. > > > > > > > > On Sun, Feb 15, 2015 at 04:38:40PM +0300, Amer wrote: > > > > > Thank you Ben > > > > > This means I need to upgrade to a new openflow version, > > > > > Which version you suggest. > > > > > > > > > > Best regards, > > > > > Amer > > > > > > > > > > > On ١٣/٠٢/٢٠١٥, at ٧:٣٣ م, Ben Pfaff <b...@nicira.com> wrote: > > > > > > > > > > > >> On Fri, Feb 13, 2015 at 11:27:48AM +0300, Amer wrote: > > > > > >> I am trying to change the size of VLAN tag, I have changed the size > > > > > >> parameters in pox and the size of VLAN-tci in > > > > > >> openveswitch/datapath/vlan.h and vlan.c > > > > > >> > > > > > >> However, I am still receiving the down error, my question is what > > > > > >> parameters should I modify in openveswitch code files to extend the > > > > > >> vlan tag to 64-bit. > > > > > > > > > > > > The error you provided is for OpenFlow 1.0. OpenFlow 1.0 has a > > > > > > fixed-size flow match structure. Any change you make to a flow > > > > > > match, > > > > > > such as to extend the VLAN ID to 64-bit (!), will make the result > > > > > > incompatible with every other OpenFlow 1.0 implementation. > > > > > > > > > > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
