A common error is cabling or connection issues.  These often will show up as rx or tx errors.  The following should help you get to the bottom of them.



Example errors: 

warning    Total number of received packets with errors (rx_errors) on bond2 has reached warning level of 1.
warning    Total number of received packets with errors (rx_errors) on eth1 has reached warning level of 1.


The error message received indicates that the network interface bond2 and eth1 has encountered one or more errors while receiving packets. When sending packets interfaces can get the same error messages and they will simply be denoted as ".  When an error occurs, the network interface card (NIC) usually drops the packet and logs the error. The warning level of 1 indicates that the number of errors has crossed a threshold, and this could indicate a problem with the network interface or the network connection. 


  1. Check the interface statistics from the log file.  It will be found by searching for "ifconfig" in the log\tests log file.  Check the statistics for the interfaces Look for any errors as normal operation all errors should be "0".  If it is not zero that is likely what triggers this issue.  Note that errors for bonds will just match what the offending bond member is listing for errors so you can focus on an individual interface.
  2. Check the dmesg log.  This is also located in log\tests.  Check the system logs for any errors related to the network interface. The dmesg log will allow you to view the kernel log messages related to the network interface.
  3. Check the network cables and connections. Check the Ethernet cables and the connections at both ends. Replace any faulty cables, and reseat the connections to ensure a secure fit.  When in doubt use another cable.
  4. Check the network switch or router: If the problem persists, check the network switch or router to ensure that it is functioning correctly. Check the logs for any errors or warnings related to the interface that is showing the errors on the NX2 or ZX side.
  5. Ensure you have the latest Scale Logic NX and ZX versions so that your NIC driver and firmware: are up to date. In some cases you can use check the lspci output from the log/tests log to check the network card model and then search for the latest driver and firmware updates from the manufacturer's website.  You can also consult Scale Logic tech support if you suspect the firmware might fix the issue.
  6. Reset the network interface: If all else fails, you can try resetting all the interfaces by bringing the NX2 or ZX down and then back up during downtime or disable and reenable the NIC in the System Settings -> Network menu.


These steps should help you identify the cause of the error and resolve the issue with the network interface.