Very simple, in your example you leave the set_field action (overwrite value) and remove the pop/push actions :)
> On Apr 7, 2016, at 11:57 AM, Sterdnot Shaken <[email protected]> wrote: > > Thanks for your response Luis! > > I wasn't aware I could just overwrite the vlan value instead of pop/pushing > it actually. Could you provide an xml flow example by chance? > > Thanks! > > On Thursday, April 7, 2016, Luis Gomez <[email protected] > <mailto:[email protected]>> wrote: > Just to be clear, this is nothing wrong with ODL, the switch does not support > the order of the actions as specified in your flow. > > > On Apr 7, 2016, at 11:19 AM, Luis Gomez <[email protected] <javascript:;>> > > wrote: > > > > From the ERROR message It seems like the order of the actions is not > > correct. something I do not understand in this flow is why you pop+push a > > vlan instead of just writing the vlan value. > > > >> On Apr 7, 2016, at 9:45 AM, sdavis <[email protected] > >> <javascript:;>> wrote: > >> > >> Greetings! > >> > >> My intention seems like it should be rather simple… > >> > >> I want to match traffic and strip the current 802.1Q vlan tag and replace > >> it with another tag before I send the traffic on it’s merry way to the > >> next switch as such: > >> > >> <?xml version="1.0" encoding="UTF-8" standalone="no"?> > >> <flow xmlns="urn:opendaylight:flow:inventory"> > >> <id>1</id> > >> <priority>50</priority> > >> <instructions> > >> <instruction> > >> <order>0</order> > >> <apply-actions> > >> <action> > >> <order>0</order> > >> <set-field> > >> <ethernet-match> > >> <ethernet-destination> > >> > >> <address>00:24:38:9c:3d:00</address> > >> > >> </ethernet-destination> > >> </ethernet-match> > >> </set-field> > >> </action> > >> <action> > >> <order>1</order> > >> <pop-vlan-action/> > >> </action> > >> <action> > >> <order>2</order> > >> <push-vlan-action> > >> > >> <ethernet-type>33024</ethernet-type> > >> </push-vlan-action> > >> </action> > >> <action> > >> <order>3</order> > >> <set-field> > >> <vlan-match> > >> <vlan-id> > >> > >> <vlan-id>2011</vlan-id> > >> > >> <vlan-id-present>true</vlan-id-present> > >> </vlan-id> > >> </vlan-match> > >> </set-field> > >> </action> > >> <action> > >> <order>4</order> > >> <output-action> > >> > >> <output-node-connector>1</output-node-connector> > >> </output-action> > >> </action> > >> </apply-actions> > >> </instruction> > >> </instructions> > >> <cookie>0</cookie> > >> <idle-timeout>0</idle-timeout> > >> <flags></flags> > >> <hard-timeout>0</hard-timeout> > >> <match> > >> <in-port>openflow:10195343270477824:2</in-port> > >> <ethernet-match> > >> <ethernet-type> > >> <type>2048</type> > >> </ethernet-type> > >> </ethernet-match> > >> <vlan-match> > >> <vlan-id> > >> <vlan-id>2000</vlan-id> > >> <vlan-id-present>true</vlan-id-present> > >> </vlan-id> > >> <vlan-pcp>0</vlan-pcp> > >> </vlan-match> > >> <ipv4-source>10.64.10.11/32 > >> <http://10.64.10.11/32></ipv4-source> > >> <ipv4-destination>10.64.10.12/32 > >> <http://10.64.10.12/32></ipv4-destination> > >> </match> > >> <table_id>0</table_id> > >> </flow> > >> > >> When I try and install that flow via Postman, the OF message I get this > >> message back from our Brocade MLXe router: > >> > >> OpenFlow 1.3 > >> Version: 1.3 (0x04) > >> Type: OFPT_ERROR (1) > >> Length: 76 > >> Transaction ID: 1043352 > >> Type: OFPET_BAD_ACTION (2) > >> Code: OFPBAC_UNSUPPORTED_ORDER (11) > >> Data > >> > >> Is my problem a syntax or order issue, or is it possible I can’t untag and > >> tag in the same flow? > >> > >> Thanks in advance! > >> _______________________________________________ > >> openflowplugin-dev mailing list > >> [email protected] <javascript:;> > >> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > >> <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev> > > > > _______________________________________________ > openflowplugin-dev mailing list > [email protected] <javascript:;> > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
