https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-61 netvirt <p>2016-08-12 16:20:45,180 | INFO | on-dispatcher-49 | OvsdbConnectionManager | 289 - org.opendaylight.ovsdb.southbound-impl - 1.3.0.SNAPSHOT | Connecting to 127.0.0.1:6641<br/> 2016-08-12 16:20:45,489 | INFO | on-dispatcher-49 | OvsdbConnectionManager | 289 - org.opendaylight.ovsdb.southbound-impl - 1.3.0.SNAPSHOT | OVSDB Connection from /127.0.0.1:6641<br/> 2016-08-12 16:20:45,497 | DEBUG | pool-47-thread-1 | AclNodeListener | 357 - org.opendaylight.netvirt.aclservice-impl - 0.3.0.SNAPSHOT | Added Ingress ACL Table Miss Flows for dpn 158380687717562<br/> 2016-08-12 16:20:45,501 | DEBUG | pool-47-thread-1 | AclNodeListener | 357 - org.opendaylight.netvirt.aclservice-impl - 0.3.0.SNAPSHOT | Added Egress ACL Table Miss Flows for dpn 158380687717562<br/> 2016-08-12 16:20:45,543 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_147577370657608_Tracked_Established17, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,544 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_147577370657608_Tracked_Related17, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,549 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_147577370657608_Tracked_New41, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,549 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_147577370657608_Tracked_Invalid41, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,549 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_147577370657608_Tracked_Established220, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,550 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_147577370657608_Tracked_Related220, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,561 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_147577370657608_Tracked_New252, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,568 | ERROR | entLoopGroup-9-2 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_147577370657608_Tracked_Invalid252, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,615 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_158380687717562_Tracked_Established17, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,624 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_158380687717562_Tracked_Related17, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,631 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_158380687717562_Tracked_New41, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,642 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_158380687717562_Tracked_Invalid41, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,651 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_158380687717562_Tracked_Established220, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,665 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_Trk_158380687717562_Tracked_Related220, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,678 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_158380687717562_Tracked_New252, errors=Device reported error type BADMATCH code BADMASK<br/> 2016-08-12 16:20:45,681 | ERROR | entLoopGroup-9-1 | SalFlowServiceImpl | 305 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | flow add failed for id=Fixed_Conntrk_NewDrop_158380687717562_Tracked_Invalid252, errors=Device reported error type BADMATCH code BADMASK</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-61

aclservice flows fail with BADMATCH code BADMASK

Bug Resolved Won't Do Aswin Suryanarayanan Sam Hague Fri, 12 Aug 2016 20:36:49 +0000 Thu, 3 May 2018 14:37:00 +0000 Tue, 16 Aug 2016 14:55:49 +0000 Boron General 0 0 <p>Errors reported in previous reply when simply connecting to an ovsdb node and creating br-int. This was using the NetvirtIT class.</p> <p>This indicates that OVS does not suppot connection tracking. Ovs &lt; 2.5 does not support connection tracking. <br/> If it happens in OVS2.5 or above, need to check whether the kernel module is installed correctly</p> <p>Aswin, Ok, marking as resolved.</p> <p>Should we look into adding anything to check if stateful and ovs version not good, then don't push flows or log some other helpful hint? I guess the failed flows will clue the user in.</p> Development External issue ID 6404 External issue URL Rank 0|i01ph3: