LAN interface keeps going down every so often and comes back up on its own
Experiencing a strange issue here. LAN interface keeps going down and coming back up on its own. It seems to happen every 20 - 40 minutes or so and is down for about 3 - 10 minutes and comes back up on its own. VPN's stay up, WAN stay up, OPT1 stays up.
Little background, brand new box, supermicro hardware. We are using 2.2.5 pfsense. We have tried reloading with same issue.
If I go into my system logs this is what we see when the LAN port comes back up:
Dec 14 14:07:13 check_reload_status: Syncing firewall
Dec 14 14:07:43 check_reload_status: Linkup starting igb1
Dec 14 14:07:43 kernel: igb1: Watchdog timeout – resetting
Dec 14 14:07:43 kernel: igb1: Queue(810107728) tdh = 718230942, hw tdt = -38012042
Dec 14 14:07:43 kernel: igb1: TX(810107728) desc avail = 29555,Next TX to Clean = 12408
Dec 14 14:07:43 kernel: igb1: link state changed to DOWN
Dec 14 14:07:44 php-fpm: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.0.253 )
Dec 14 14:07:48 kernel: igb1: link state changed to UP
Dec 14 14:07:48 check_reload_status: Linkup starting igb1
Dec 14 14:07:49 php-fpm: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.0.253 )
Dec 14 14:07:49 check_reload_status: rc.newwanip starting igb1
Dec 14 14:07:50 php-fpm: /rc.newwanip: rc.newwanip: Info: starting on igb1.
Dec 14 14:07:50 php-fpm: /rc.newwanip: rc.newwanip: on (IP address: 192.168.0.253) (interface: LAN[lan]) (real interface: igb1).
Dec 14 14:07:50 check_reload_status: Reloading filter
Does anyone have any ideas of what is going on???????? Please help this is a router in a large production environment.
An Update … I just wanted to list the hardware we are using in case this would help.
SYS-E200-9B (Model Number)
X11SBA-LN4F (Motherboard Part Number)
Intel I220AT (Ethernet Chipset Used)
disclaimer: this is just speculation based on some googling
is tso offloading enabled? if yes => try todisable it.
These commands may be placed into a shellcmd tag to execute at boot time to make the change persistent. (install shellcmd package)
this appears similar for em-driver (no clue if its related).