Figured it out. Enclosing it for reference:
NSH fields in Action:
<action>
<order>1</order>
<nx-reg-load
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<value>255</value>
<dst>
<nx-nsi-dst
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action"/>
<start>0</start>
<end>7</end>
</dst>
</nx-reg-load>
</action>
<action>
<order>2</order>
<nx-reg-load
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<value>5</value>
<dst>
<nx-nsp-dst
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action"/>
<start>0</start>
<end>31</end>
</dst>
</nx-reg-load>
</action>
<action>
<order>3</order>
<nx-reg-load
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<value>1</value>
<dst>
<nx-nsh-mdtype
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action"/>
<start>0</start>
<end>7</end>
</dst>
</nx-reg-load>
</action>
<action>
<order>4</order>
<nx-reg-load
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<value>3</value>
<dst>
<nx-tun-gpe-np
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action"/>
<start>0</start>
<end>7</end>
</dst>
</nx-reg-load>
</action>
<action>
<order>5</order>
<nx-reg-load
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<value>20015998341138</value>
<dst>
<nx-encap-eth-dst
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action"/>
<start>0</start>
<end>47</end>
</dst>
</nx-reg-load>
</action>
<action>
<order>6</order>
<nx-reg-load
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<value>20015998341139</value>
<dst>
<nx-encap-eth-src
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action"/>
<start>0</start>
<end>47</end>
</dst>
</nx-reg-load>
</action>
NSH fields as match:
<extension-list
xmlns="urn:opendaylight:openflowplugin:extension:general">
<extension-key
xmlns:x="urn:opendaylight:openflowplugin:extension:nicira:match">x:nxm-nx-nsp-key</extension-key>
<extension>
<nxm-nx-nsp
xmlns="urn:opendaylight:openflowplugin:extension:nicira:match">
<value>5</value>
</nxm-nx-nsp>
</extension>
</extension-list>
<extension-list
xmlns="urn:opendaylight:openflowplugin:extension:general">
<extension-key
xmlns:x="urn:opendaylight:openflowplugin:extension:nicira:match">x:nxm-nx-nsi-key</extension-key>
<extension>
<nxm-nx-nsi
xmlns="urn:opendaylight:openflowplugin:extension:nicira:match">
<nsi>255</nsi>
</nxm-nx-nsi>
</extension>
</extension-list>
On Wed, Aug 3, 2016 at 11:52 PM, Ramesh Devarajan <[email protected]> wrote:
> How is the NSH fields sent in the flow mod XML/JSON ?
>
> I managed to get it for the push_nsh as follows:
> <apply-actions>
> <action>
> <order>0</order>
> <nx-push-nsh xmlns="urn:opendaylight:openflowplugin:extension:
> nicira:action">
> </nx-push-nsh>
> </action>
> ...
>
> But how do i encode the other fields such as NSI, NSP etc.
> I would like a flow addition from ODL to look something similar to this
> flow add command.
> ovs-ofctl add-flow br-sfc "table=0, in_port=LOCAL actions=push_nsh,
> load:0xff->NXM_NX_NSI[], load:0x1f->NXM_NX_NSP[],
> load:0x4->NXM_NX_TUN_GPE_NP[], load:0x1->NXM_NX_NSH_MDTYPE[], output:1"
>
> Could somebody point me to a sample JSON/XML ?
>
> Thanks,
> Ramesh
>
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
