ipdk icon indicating copy to clipboard operation
ipdk copied to clipboard

Can't run demo because of table add failure

Open stolsma opened this issue 2 years ago • 0 comments

When doing the network demo with VM's by hand (automatic demo fails too btw) the command:

ipdk execute --- ovs-p4ctl add-entry br0 ingress.ipv4_host "hdr.ipv4.dst_addr=1.1.1.1,action=ingress.send(0)"

fails with:

ipdk execute --- ovs-p4ctl add-entry br0 ingress.ipv4_host "hdr.ipv4.dst_addr=1.1.1.1,action=ingress.send(0)"
Loaded /home/sander/develop/ipdk/build/scripts/ipdk_default.env
Loaded /home/sander/.ipdk/ipdk.env
Error: Error(s) during Write:
        * At index 0: NOT_FOUND, ''table->tableEntryAdd( *real_session->bfrt_session_, bf_dev_tgt, *real_table_key->table_key_, *real_table_data->table_data_)' failed with error message: Object not found. Could not add table entry with: table_name: pipe.ingress.ipv4_host, table_id: 43484571, table_type: 0, bfrt_table_key { hdr.ipv4.dst_addr { field_id: 1 key_type: 1 field_size: 32 value: 0x01010101 } }, bfrt_table_data { action_id: 18638031 port { field_id: 1 data_type: 3 field_size: 32 value: 0x00000000 is_active: 1 } }'

And the ping doesn't work (as should be expected because the table wasn't filled)...

Could be a regression introduced by this PR that adds tap port support to p4-ovs or by the update of the used p4c version (#139)

stolsma avatar May 05 '22 14:05 stolsma