Details
-
Improvement
-
Status: Resolved
-
Resolution: Done
-
None
-
None
-
None
-
Operating System: Windows
Platform: PC
Description
We configure this:
PUT http://127.0.0.1:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/2/flow/139
<flow xmlns="urn:opendaylight:flow:inventory">
<priority>2</priority>
<flow-name>Foo</flow-name>
<match>
<ethernet-match>
<ethernet-type>
<type>2048</type>
</ethernet-type>
</ethernet-match>
<ipv4-destination>10.0.10.1/32</ipv4-destination>
</match>
<id>139</id>
<table_id>2</table_id>
<instructions>
<instruction>
<order>0</order>
<apply-actions>
<action>
<order>0</order>
<dec-nw-ttl/>
</action>
</apply-actions>
</instruction>
</instructions>
</flow>
In the operational we do not see the flow:
GET http://127.0.0.1:8080/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/2
{
"flow-node-inventory:table": [
{
"opendaylight-flow-statistics:aggregate-flow-statistics":
,
"flow-node-inventory:id": 2,
"opendaylight-flow-table-statistics:flow-table-statistics":
}
]
}
However in the switch, we see a flow with actions=drop:
odluser@odl-system-test:~/integration\> sudo ovs-ofctl -O OpenFlow10 dump-flows s1
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=7.633s, table=0, n_packets=0, n_bytes=0, idle_timeout=300, hard_timeout=600, idle_age=7, priority=2,ip,nw_dst=10.0.10.1 actions=drop