A flow installed with VLAN ID (say 100) shows up in the operational database with a different ID

If a flow is installed with VLAN ID (say 100) it show up in the operational database with a different ID (something like #UF$TABLE*0-7).

On further queries by Ram, Anil provided the answer and an Ram's advice, I am opening this bug

Please see the details below

______________________________________________________________________

From: Anil Vishnoi vishnoianil@gmail.com
Sent: Saturday, November 22, 2014 10:55 AM
To: Gowrishankar, Ramkumar
Cc: openflowplugin-dev@lists.opendaylight.org
Subject: Re: [openflowplugin-dev] difference in flow id in config and operational datastore

Hi Ramkumar,

Statistics manager use this specific format ID [UF$TABLE*0-7 -- Unidentified Flow from Table -0 , and its 7th unidentified flow] to augment the flow statistics in operational data store, when it doesn't found respective matching flow in the config data store. Sometime even if you have respective flow in the config data store, it still augment flow statistics using the special id and the reason is as follows.

In openflow specs, flow structure don't have an ID associated with flow, so when statistics manager fetches flow from switch, it actually compare statistics flow against the config flows by comparing each element of the flow( For the first time, we do have few optimization here ). These custom comparator's some time fails, when switch installed the same flow in different form than what user added to the configuration data store. For example, if you use source-ip=10.11.12.13 and mask=16 and send it to switch, switch actually will install the flow with source-ip=10.11.00.00 and mask=16. And now when statistics manager fetches the flow stats from switch, its gets 10.11.00.00 and the custom comparator fails here because its not matching with the flow that user added to configuration data store ( with ip = 10.11.12.13) and eventually it end up using this specific id to augment the statistics. Although this bug example is already fix, but there are few other corner cases which we come to know as and when user reports.

Can you please open a bug to bugzilla, so that we can track it and fix it.

Thanks
Anil