It is helpful to monitor the RxErrors and TxErrors on ports on Extreme Networks switches to get a heads up on any issues before they begin to impact service. The Extreme Networks MIB can be downloaded from the Extreme Networks support portal to assist you in finding the relevant SNMP OIDs, the below is an example of the NagiosXI check_snmp query needed to retrieve the TxErrors and RxErrors for a particular port, and apply thresholds which if breached will indicate warning or critical state.
/usr/local/nagios/libexec/check_snmp -H switchname.domain.com -C public -o .18.104.22.168.22.214.171.124.1.20.1049 -o .126.96.36.199.188.8.131.52.1.14.1049 -l "TxErrors" -l "RxErrors" -w 5,5 -c 10,10
This provides an output such as:
[root@wtgc-nagios-01 libexec]# /usr/local/nagios/libexec/check_snmp -H switchname.domain.com -C public -o .184.108.40.206.220.127.116.11.1.20.1049 -o .18.104.22.168.22.214.171.124.1.14.1049 -l "txErrors" -l "rxErrors" -w 1,1 -c 10,10 SNMP OK - txErrors 0 rxErrors 0 | txErrors=0c;1;10; rxErrors=0c;1;10;
In this example the SNMP query checks port 49 for RxErrors or TxErrors if these counters exceed 5 then this service check shows a warning, if it exceeds 10 then it shows critical. Although in normal operation you shouldn’t have any RxErrors or TxErrors the odd one isn’t anything much to worry about, however if a port starts showing more than 10 then it would point to a fibre, port, transceiver issue that would need attention.