Operating System: All
Platform: All

*OVS (Mininet) & other switches (which are not based on OVS) responds differently when tried with arbitrary Mask *

Example :-

Input :-
<ipv4-destination-address-no-mask>7.7.7.0</ipv4-destination-address-no-mask>
<ipv4-destination-arbitrary-bitmask>255.0.241.0</ipv4-destination-arbitrary-bitmask>

Output on OVS (Mininet) :-
mininet> sh ovs-ofctl dump-flows s1 -O OpenFlow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0x0, duration=105.595s, table=0, n_packets=0, n_bytes=0, priority=7,ip,nw_dst=7.0.1.0/255.0.241.0 actions=dec_ttl

Output on Other switches (which are not based on OVS):-
Flow ID: 75 Priority: 7 Status: Active
Rule:
In Port: generic
Ether type: 0x00000800
Destination IP: 7.7.7.0 Subnet IP: 255.0.241.0
Idle Timeout : 0 secs
Hard Timeout : 0 secs

Comments:-
OVS automatically converts the arbitrary bit mask and shows output with 7.0.1.0/255.0.241.0 but where as some switches didn't yet process but gives raw IP 7.7.7.0/255.0.241.0

Request to make it compatible with both OVS & for other switches (which are not developed on OVS)

Plugin can't change any information send to device. The switch should do it fo it self, or the flow sent should be normalized. And the same plugin can't change the information gain from switch when storing to operational DS. Plugin normalizes ipv4arbitrary but only for matching the flows. This was made in the latest code. So even if the switch stores the IP wrong plugin matches the flow.

Any thoughts/updates Sai? Should we close this?

I think this should fix the issue. https://git.opendaylight.org/gerrit/#/c/36471/

I haven't checked recently. We can close it for now.