In many vendor's implementations, ACLs / Filters are not using one single table of a fixed format (column width and row count), instead there are multiple tables with various internal data structures and these tables may not be of fixed format.
Would it make more sense to report acl-memory-utilization percentage metric instead of those 4 currently defined?
And leave to the vendor how acl-memory-utilization is computed over various internal metrics.
This issue is stale because it has been open 180 days with no activity. If you wish to keep this issue active, please remove the stale label or add a comment, otherwise will be closed in 14 days.
Hello OC Team!
This is a vendor question / suggestion (from Juniper Networks).
There are 4 attributes defined in this model https://github.com/openconfig/public/blob/master/release/models/platform/openconfig-platform-pipeline-counters.yang
acl-memory-total-entries acl-memory-used-entries acl-memory-total-bytes acl-memory-used-bytes
In many vendor's implementations, ACLs / Filters are not using one single table of a fixed format (column width and row count), instead there are multiple tables with various internal data structures and these tables may not be of fixed format.
Would it make more sense to report acl-memory-utilization percentage metric instead of those 4 currently defined?
And leave to the vendor how acl-memory-utilization is computed over various internal metrics.
Thanks, Dmitry.