we updated the firmware and the problem described by Patrick shifted, we observe a different behaviour with the updated firmware(14.24.1000).
The target is to setup a flow table entry with an additional count action.
We use the following commands:
ALLOCATE_FLOW_COUNTER (0x939)
SET_FLOW_TABLE_ENTRY (0x936)
The SET_FLOW_TABLE_ENTRY command fails (BAD_PARAM syndrome 0x30B3AF, flow counter id is reserved) when using the flow counter id which was returned by ALLOCATE_FLOW_COUNTER.
We tried count+fwd and count+drop combination (same result).
The “log_max_flow_counter” flow table capability is set to 1.
SET_HCA_CAP does not change the log_max_flow_counter.
We can query the value of log_max_flow_counter via QUERY_HCA_CAP.
We have the following questions:
Does the log_max_flow_counter value affect the ability to set flow counters in a flow table entry?
Which command do we have to use in order to increase the log_max_flow_counter?