Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

Because flow were in both operational and config datastores I did not check openvswitch logs till today :)

There was a line rejecting my flow because of wrong subnetmask:

2017-01-07T09:03:41.970Z|101072|nx_match|WARN|Rejecting NXM/OXM entry 0:32768:11:1:8 with 1-bits in value for bits wildcarded by the mask.

Changed ip addresses in criterias from x.x.x.1/8 to x.x.x.1/32, and flow worked. Kinda weird because in network world the first way is to correct.

Because flow flows were in both operational and config datastores I did not check openvswitch logs till today :)

There was a line rejecting my flow because of wrong subnetmask:

2017-01-07T09:03:41.970Z|101072|nx_match|WARN|Rejecting NXM/OXM entry 0:32768:11:1:8 with 1-bits in value for bits wildcarded by the mask.

Changed ip addresses in criterias from x.x.x.1/8 to x.x.x.1/32, and flow worked. Kinda weird because in network world the first way is to correct.

Because flows were in both operational and config datastores I did not check openvswitch logs till today :)

There was a line rejecting my flow because of wrong subnetmask:

2017-01-07T09:03:41.970Z|101072|nx_match|WARN|Rejecting NXM/OXM entry 0:32768:11:1:8 with 1-bits in value for bits wildcarded by the mask.

Changed ip addresses in criterias from x.x.x.1/8 to x.x.x.1/32, and flow worked. Kinda weird because in network world the first way is to correct.the correct one.