Adding flows with go-to-table and output port via RESTCONF

asked 2016-03-22 05:51:54 -0800

nodachi gravatar image

updated 2016-03-22 05:52:20 -0800

Hello,

I'm trying to add a single flow with "go to table" and "output" action. I was able to directly enter this flow in OVS and the command was executed successfuly. I want to know if this is possible to do via REST? I've tried adding a flow below but I get a following error:

<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>protocol</error-type> <error-tag>malformed-message</error-tag> <error-message>Error parsing input: Unknown child node: (urn:opendaylight:flow:inventory?revision=2013-08-19)apply-actions, does not belong to: ChoiceCaseNodeImpl[qname=(urn:opendaylight:flow:inventory?revision=2013-08-19)go-to-table-case] as a direct child. Direct child nodes: [(urn:opendaylight:flow:inventory?revision=2013-08-19)go-to-table], augmented child nodes: []</error-message> </error> </errors>

My REST body:

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<flow xmlns="urn:opendaylight:flow:inventory">
      <instructions>
        <instruction>
            <order>0</order>
            <go-to-table>
                <table_id>1</table_id>
            </go-to-table>
            <apply-actions>
                <action>
                    <order>1</order>
                    <output-action>
                        <max-length>60</max-length>
                        <output-node-connector>3</output-node-connector>
                    </output-action>
                </action>
            </apply-actions>
        </instruction>
    </instructions>
    <table_id>0</table_id>
    <id>250</id>
    <match>
        <ethernet-match>
            <ethernet-type>
                <type>2048</type>
            </ethernet-type>
        </ethernet-match>
        <in-port>2</in-port>
    </match>   
    <hard-timeout>0</hard-timeout>
    <cookie>10</cookie>
    <idle-timeout>0</idle-timeout>
    <flow-name>flow-instruction-go-to-tablee</flow-name>
    <priority>400</priority>
</flow>
edit retag flag offensive close merge delete