Ask the Community
Groups
Prevent Intel 82574 NICs from going offline - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Prevent Intel 82574 NICs from going offline</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>Prevent Intel 82574 NICs from going offline</p> <h3 data-id="description">Description</h3> <p>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. </p> <p>Below are typical symptoms when this occurs.</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> # 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</pre> <p> </p> <h3 data-id="cause">Cause</h3> <p>The Intel 82574 NICs are vulnerable to certain ASPM faults with the Linux e1000e 2.1.4 or greater driver. </p> <h3 data-id="resolution">Resolution</h3> <p>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. </p> <p><br>If you are experiencing this problem with the symptoms above, it can be resolved as follows: </p> <p>1) Download the nic82574.sh script</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> wget <a href="/home/leaving?allowTrusted=1&target=ftp%3A%2F%2Fftp.unitrends.com%2Fsupport%2Fscripts%2Fnic82574.sh">ftp://ftp.unitrends.com/support/scripts/nic82574.sh</a></pre> <p>2) Run the script to patch the NIC EEPROM and set a kernel parameter to avoid the problem. </p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> sh nic32574.sh</pre> <p>3) Reboot</p> <p> </p> <h3 data-id="third-party-sources">Third-Party Sources</h3> <pre class="code codeBlock" spellcheck="false" tabindex="0"> </pre> <pre class="code codeBlock" spellcheck="false" tabindex="0"> <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fe1000%2Ffiles%2Fe1000e%2520stable%2Feeprom_fix_82574_or_82583%2F">http://sourceforge.net/projects/e1000/files/e1000e%20stable/eeprom_fix_82574_or_82583/</a> where Intel says it can be fixed with an EEPROM bit change via a Linux shellscript.</pre> <pre class="code codeBlock" spellcheck="false" tabindex="0"> </pre> <pre class="code codeBlock" spellcheck="false" tabindex="0"> <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D632650">https://bugzilla.redhat.com/show_bug.cgi?id=632650</a> reports an important change in e1000e 2.1.4 and later around ASPM. The user resolution was to set</pre> <pre class="code codeBlock" spellcheck="false" tabindex="0"> ’pcie_aspm=off’ in the kernel params.</pre> <p> </p> </article> </main>