I'm not sure if this is the right place for this type of report, but I couldn't find a better one. If I should report it another way, please let me know. I don't have a support plan. There is a bug in all official MikroTik templates because the template reads packet errors on the port via OID 1.3.6.1.2.1.2.2.1.14.<ifIndex>, while MikroTik never reports errors there, instead using OIDs in the 1.3.6.1.4.1.14988.1.1.14.1.1 branch.
e.g.
mtxrInterfaceStatsRxFCSError 1.3.6.1.4.1.14988.1.1.14.1.1.45
mtxrInterfaceStatsRxAlignError 1.3.6.1.4.1.14988.1.1.14.1.1.46
mtxrInterfaceStatsRxCarrierError 1.3.6.1.4.1.14988.1.1.14.1.1.53
etc.
There's no single, collective OID for errors, so you need separate items for each error and separate triggers, or a single trigger that fires for any error.
Of course, I know I can change this locally in my template, but firstly, the same problem exists in almost every MikroTik template, and there are several of them. Secondly, this would only solve the problem for me, and many people may not realize that the official template won't provide information about interface errors.
e.g.
mtxrInterfaceStatsRxFCSError 1.3.6.1.4.1.14988.1.1.14.1.1.45
mtxrInterfaceStatsRxAlignError 1.3.6.1.4.1.14988.1.1.14.1.1.46
mtxrInterfaceStatsRxCarrierError 1.3.6.1.4.1.14988.1.1.14.1.1.53
etc.
There's no single, collective OID for errors, so you need separate items for each error and separate triggers, or a single trigger that fires for any error.
Of course, I know I can change this locally in my template, but firstly, the same problem exists in almost every MikroTik template, and there are several of them. Secondly, this would only solve the problem for me, and many people may not realize that the official template won't provide information about interface errors.
Comment