CoreXL messes with kernel tables

On a corexl gateway, the kernel table will be replicated multiple times.

This appears to mess with the counter value of each kernel table. We have seen this to skew astronomically high. This should not be problem as long as the limit reflects the duplicated values. However, the table limit does not account for duplication and therefore, Indeni flags the device as having overutilized kernel tables.

What would be the right way to calculate kernel table limit utilization?

Can you give some example, together with the command that retreives the value? Does it always happen?

would you be able to assist with this issue? What kernel tables are allowed to go beyond their limit?

I’m going to close this as we found a way to solve the problem on our IND scripts!

Do share! What’s the solution?