Date created: 11/13/20 16:58:07. Last modified: 11/13/20 16:58:07

7210 SAS-X SAP Ingress Counter Mode Bug

SAP ingress "counter-mode"

in-out-profile-count — If the counter mode is specified as "in-out-profile-count", one counter counts the total in-profile packets and octets received on ingress of a SAP and another counts the total out-of-profile packets and octets received on ingress of a SAP. A packet is determined to be in- profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. Dropped counts are not maintained in hardware when this mode is used. It is obtained by subtracting the sum of in-profile count and out-of- profile count from the total SAP ingress received count and displayed. Nokia TAC confirmed mode shouldn't be used - the dropped packet counter can increment when no packets are being dropped, meaning it is completely unreliable and "forward-drop-count" should be used instead!


forward-drop-count — If the counter mode is specified as "forward-drop-count", one counter counts the forwarded packets and octets received on ingress of a SAP and another counts the dropped packets. The forwarded count is the sum of in-profile and out-of-profile packets/octets received on SAP ingress. The dropped count is count of packets/octets dropped by the policer. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. The in- profile count and out-of-profile count is not individually available when operating in this mode. Despite this limitation, the counter is completely accurate and thus preferred!

A:switch1>/configure service epipe 123456 sap 1/1/3:934 statistics ingress counter-mode forward-drop-count