Prevent Intel 82574 NICs from going offline - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Prevent Intel 82574 NICs from going offline - Connect IT Community | Kaseya

SUMMARY

Prevent Intel 82574 NICs from going offline

ISSUE

Purpose

Prevent Intel 82574 NICs from going offline

Description

Some Unitrends systems, like R813, have Intel 82574 NICs which are vulnerable to certain ASPM faults which will cause the NIC to stop working and accumulate errors.

Below are typical symptoms when this occurs.

# lspci |grep Eth

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection (rev ff)

# ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 00:25:90:C7:41:AF

          inet addr:192.168.134.51  Bcast:192.168.134.255  Mask:255.255.255.0

          inet6 addr: fe80::225:90ff:fec7:41af/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:215 errors:747324309330 dropped:124554051555 overruns:0 frame:498216206220

          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:26075 (25.4 KiB)  TX bytes:5512 (5.3 KiB)

          Interrupt:17 Memory:fb6e0000-fb700000



# ethtool -i eth0

driver: e1000e

version: 2.3.2-k

firmware-version: 1.9-0

bus-info: 0000:05:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

Cause

The Intel 82574 NICs are vulnerable to certain ASPM faults with the Linux e1000e 2.1.4 or greater driver.

Resolution

If you have unitrends-drivers-2.6.32_279.el6.x86_64-2014011025.x86_64 or later from release 7.4.0, this should already be resolved, unless you have added a NIC card with 82574s after installing it.

If you are experiencing this problem with the symptoms above, it can be resolved as follows:

1) Download the nic82574.sh script

wget ftp://ftp.unitrends.com/support/scripts/nic82574.sh

2) Run the script to patch the NIC EEPROM and set a kernel parameter to avoid the problem.

sh nic32574.sh

3) Reboot

Third-Party Sources

http://sourceforge.net/projects/e1000/files/e1000e%20stable/eeprom_fix_82574_or_82583/ where Intel says it can be fixed with an EEPROM bit change via a Linux shellscript.

https://bugzilla.redhat.com/show_bug.cgi?id=632650  reports an important change in e1000e 2.1.4 and later around ASPM.  The user resolution was to set

’pcie_aspm=off’ in the kernel params.