Open davidcc73 opened 9 months ago
When running "onos-cli> source /config/routing_tables.txt" all commands inside the file fail with the same warning.
An example: "route-insert device:r1 2001:1:1::1 128 00:00:00:00:00:10" created log =>
onos | 16:46:41.439 WARN [WriteResponseImpl] Unable to INSERT table entry on device:r1: OTHER_ERROR INVALID_ARGUMENT Cannot provide direct action for indirect table 33612857 (:3) [PiTableEntry{tableId=IngressPipeImpl.routing_v6, matchKey={hdr.ipv6.dst_addr=0x20010001000100000000000000000001/128}, tableAction=IngressPipeImpl.set_next_hop(next_hop=0x10), priority=N/A, timeout=PERMANENT}]
By my testing, commenting the lines 89 and 103 solved the problem by turning the access direct instead of indirect.
When running "onos-cli> source /config/routing_tables.txt" all commands inside the file fail with the same warning.
An example: "route-insert device:r1 2001:1:1::1 128 00:00:00:00:00:10" created log =>
onos | 16:46:41.439 WARN [WriteResponseImpl] Unable to INSERT table entry on device:r1: OTHER_ERROR INVALID_ARGUMENT Cannot provide direct action for indirect table 33612857 (:3) [PiTableEntry{tableId=IngressPipeImpl.routing_v6, matchKey={hdr.ipv6.dst_addr=0x20010001000100000000000000000001/128}, tableAction=IngressPipeImpl.set_next_hop(next_hop=0x10), priority=N/A, timeout=PERMANENT}]