Anything greater than zero is a problem for ethernet interfaces.
Anything greater than zero would be a problem. If you did set a non-zero value, it should be pretty low, because the errors/sec rate is the number of errors divided by the number of seconds (~300).
adam.
On 2014-09-05 22:25, Darian Jimenez wrote:
Thanks Derek. So it seems like there's definitely a problem on my switches dropping packets.
I set an alert for the IfInErrors_rate & IfOutErrors_rate but while it finds the ports for the devices nothing is triggered. What would be a good # to put in there?
On Fri, Sep 5, 2014 at 5:07 PM, Derek dandenoth@gmail.com wrote:
That "m" by the y axes is the symbol for "milli" for a factor of one thousandth. So you can read a number like 500m as .5 errors per second.
Derek
On Fri, Sep 5, 2014 at 3:44 PM, Darian Jimenez darian929@gmail.com wrote:
I just saw I had a warning on port errors and looked at it.
It is monitoring a Juniper switch interface. From the legend I can't tell what the "m" stand for for the y axis.
would this be resource errors from the switch interface stats?
Errors: 275, Drops: 0, Framing errors: 275, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 11740453
Thanks,
Darian _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1]
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1]
Links:
[1] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium