Upgrade to a version that contains fix for xos0054714. Check section "Resolved Issues" in Release Notes of latest patch of recommended EXOS release. (What Is The Recommended SW Release For My Platform?
, Where to get release notes?
The OID to gather the counter output via SNMP is 220.127.116.11.4.1.1918.104.22.168.1 with the following explanation:
|extremeAclStatsVlanIfIndex (22.214.171.124.4.1.19126.96.36.199.1.1.1)||The IfIndex of the VLAN in which this policy/rule is applied|
|extremeAclStatsPortIfIndex (188.8.131.52.4.1.19184.108.40.206.1.1.2)||The IfIndex of the port in which this policy/rule is applied|
|The ingress/egress direction to which this policy/rule is applied (0 for ingress and 1 for Egress)|
|Name of the counter for which the stats is requested|
|The total number of packets that matches this rule|
|The total number of bytes that matches this rule|
The OIDs 1-4 that are index variables, and they are not accessible.
The user can only view the values of the counters of the respective indices.
OID 5 represents packet count, and 6 represents byte count.
Here an example:
.220.127.116.11.4.1.1918.104.22.168.22.214.171.124.655126.96.36.199.188.8.131.52 = Counter64: 0
.184.108.40.206.4.1.19220.127.116.11.18.104.22.168 à This represents the vlan instance to which the rule is applied. (Here, this rule is not applied to a vlan)
.22.214.171.124.4.1.19126.96.36.199.188.8.131.52.65543 -> The port instance (This rule is applied to a port)
.184.108.40.206.4.1.19220.127.116.11.18.104.22.168.65543.0 -> The direction in which the acl is applied (0 indicates ingress, and 1 indicates egress). (Rule is applied in ingress direction)
.22.214.171.124.4.1.19126.96.36.199.188.8.131.52.65543.0.5 -> Number of characters in the counter name.
.184.108.40.206.4.1.19220.127.116.11.18.104.22.168.65522.214.171.124.126.96.36.199 --> ASCII value of counter name (Here it is "cnt40")