It sounds like they've started including these in the if[In|Out]Errors counter.

Very stupid, also very Juniper.

Nothing we can do. You'll have to exclude these devices from the port errors alerts.

adam.

------ Original Message ------
From: "Arne Van Theemsche" <arnevt@gmail.com>
To: observium@observium.org
Sent: 2018-04-01 17:41:11
Subject: [Observium] taildrops counted as errors since junos 15.X on EX series

Hi,

we started to upgrade our juniper EX switches to 15.X release and notice a change of behaviour in error reporting at interface level in observium

the problem lays that taildrops (which are activated by default and cannot just be, and isn't even a good practice to disable them) are now reported as errors in observium

  Output errors:
    Carrier transitions: 29, Errors: 0, Drops: 177209, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0

 show interfaces queue xe-0/0/4 
   ....
    Tail-dropped packets :                177209
   ......

prior to 15.X we only received reports/mails if the Errors Value was > 0.
Honestly, we only care about errors, because taildrops will always happen from time to time


I don't know if this is a change in behaviour of juniper snmp counters or that this is a flag in observium we can toggle?

thx
Arne