Mismatch between Operational Datastore and the actual Flow Entry

While VTN Testing, We have identified that for some actions the flow entries are installed correctly on the OpenFlow switch. But, the operational datastore does not reflect the correct action for the flow entry. It has been noted for a few actions specifically

a. action: set vlan pcp

Flow Entry on Switch
cookie=0x7f5600000000007b, duration=0.193s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=13,ip,in_port=1,dl_vlan=200,dl_src=6e:30:ce:63:16:4b,dl_dst=26:a1:54:78:73:70,nw_src=10.0.0.1,nw_dst=10.0.0.5 actions=set_field:6->vlan_pcp,output:3

Operational DS contents for the switch

• Added as attachment txt file

Similar problems seen when using flow entries for setting vlan id, set-dl-
src-action, set-dl-dst, set-nw-src, set-nw-tos, set-tp-src, set-tp-dst.

• Please see other attachment where entries are collected from every switch as well as the operational DS contens.

b. POST /restconf/operations/sal-flow:add-flow
Body:

{
"input": {
"node": "/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id=\"openflow:1\"]",
"table_id": 0,
"priority": 10,
"idle-timeout": 0,
"hard-timeout": 0,
"match": {
"ip-match":

{ "ip-protocol": 6 }

,
"ethernet-match": {
"ethernet-type":

{ "type": 2048 }

}
}
"instructions": {
"instruction": [
{
"order": 0,
"apply-actions": {
"action": [
{
"set-vlan-id-action":

{ "vlan-id": 10 }

,
"order": 0
},
{
"order": 1,
"set-vlan-pcp-action":

{ "vlan-pcp": 5 }

},
{
"order": 2,
"set-dl-src-action":

{ "address": "00:aa:bb:cc:dd:ee" }

},
{
"set-dl-dst-action":

{ "address": "00:11:22:33:44:55" }

,
"order": 3
},
{
"set-nw-src-action":

{ "ipv4-address": "10.20.30.40/32" }

,
"order": 4
},
{
"order": 5,
"set-nw-dst-action":

{ "ipv4-address": "192.168.1.2/32" }

},
{
"order": 6,
"set-nw-tos-action":

{ "tos": 252 }

},
{
"order": 7,
"set-tp-src-action":

{ "ip-protocol": 6, "port": 32000 }

},
{
"order": 8,
"set-tp-dst-action":

{ "port": 333, "ip-protocol": 6 }

}
]
}
}
]
}
}
}

The flow is installed correctly.

• • • s1 ------------------------------------------------------------------------
      NXST_FLOW reply (xid=0x4):
      cookie=0x0, duration=54.583s, table=0, n_packets=0, n_bytes=0, idle_age=54, \ priority=10,tcp \ actions=mod_vlan_vid:10,mod_vlan_pcp:5,\
      mod_dl_src:00:aa:bb:cc:dd:ee,mod_dl_dst:00:11:22:33:44:55,\
      mod_nw_src:10.20.30.40,mod_nw_dst:192.168.1.2,\
      mod_nw_tos:252,mod_tp_src:32000,mod_tp_dst:333

However, action information for the flow entry in operational DS is wrong due to the bug.

• set-nw-dst-action doesn't have the value of MAC address.
• Other action information doesn't exist in the operational DS.

GET /restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/0
Result:

{
"flow-node-inventory:table": [
{
"id": 0,
"flow": [
{
"id": "#UF$TABLE*0-5",
"priority": 10,
"table_id": 0,
"opendaylight-flow-statistics:flow-statistics": {
"duration":

{ "second": 244, "nanosecond": 397000000 }

,
"byte-count": 0,
"packet-count": 0
},
"idle-timeout": 0,
"match": {
"ip-match":

{ "ip-protocol": 6 }

,
"ethernet-match": {
"ethernet-type":

{ "type": 2048 }

}
},
"hard-timeout": 0,
"cookie": 0,
"instructions": {
"instruction": [
{
"order": 0,
"apply-actions": {
"action": [
{
"order": 0,
"set-nw-dst-action": {}
}
]
}
}
]
}
}
],
"opendaylight-flow-table-statistics:flow-table-statistics":

{ "active-flows": 0, "packets-looked-up": 10464, "packets-matched": 10464 }

}
]
}