SOLVED Link state changed to down - Link state change to up

VolumeTank

Dabbler
Joined
Dec 23, 2018
Messages
38
Ok! Yes I'm new but I just want to make sure that everything is fine. Suddenly my FreeNAS started to show some link state down/up everyday around the same time. I didn't think is something wrong I did some research just to see what was being said about that. Some people point this to a PWS problem, NIC or the Motherboard. Every hardware on FreeNAS is about a month old except the PWS which is about 6-7 years old. I did some test my self based on the little I know before posting this thread and this is what I get:


From the FreeNAS console I was getting this everyday at the same time.
Jan 22 18:51:32 freenas kernel: igb0: link state changed to DOWN
Jan 22 18:51:32 freenas kernel: igb0: link state changed to DOWN
Jan 22 18:51:32 freenas kernel: igb0: link state changed to UP
Jan 22 18:51:32 freenas kernel: igb0: link state changed to UP

From my router I’m getting this every day almost all day long
On the router that's the port were the FreeNAS is connected to.
an 22 19:03:28 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:03:32 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 22 19:03:53 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:03:57 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 22 19:04:03 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:04:06 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 22 19:04:12 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:04:15 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 10 mbps full duplex
Jan 22 19:07:28 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:07:32 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 22 19:08:21 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:08:24 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 22 19:08:33 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:08:36 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 22 19:08:42 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:08:45 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 10 mbps full duplex
Jan 22 19:12:30 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:12:34 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 22 19:12:42 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 22 19:12:45 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex

I ping FreeNAS through the hostname and get this it looks OK to me
PING freenas.local (192.168.50.201): 56 data bytes
64 bytes from 192.168.50.201: icmp_seq=0 ttl=64 time=0.701 ms
64 bytes from 192.168.50.201: icmp_seq=1 ttl=64 time=0.742 ms
64 bytes from 192.168.50.201: icmp_seq=2 ttl=64 time=0.699 ms
64 bytes from 192.168.50.201: icmp_seq=3 ttl=64 time=0.733 ms
64 bytes from 192.168.50.201: icmp_seq=4 ttl=64 time=0.744 ms
64 bytes from 192.168.50.201: icmp_seq=5 ttl=64 time=0.855 ms
64 bytes from 192.168.50.201: icmp_seq=6 ttl=64 time=0.735 ms
64 bytes from 192.168.50.201: icmp_seq=7 ttl=64 time=0.721 ms
64 bytes from 192.168.50.201: icmp_seq=8 ttl=64 time=0.730 ms
64 bytes from 192.168.50.201: icmp_seq=9 ttl=64 time=0.747 ms
64 bytes from 192.168.50.201: icmp_seq=10 ttl=64 time=0.792 ms
64 bytes from 192.168.50.201: icmp_seq=11 ttl=64 time=0.729 ms
64 bytes from 192.168.50.201: icmp_seq=12 ttl=64 time=0.700 ms
64 bytes from 192.168.50.201: icmp_seq=13 ttl=64 time=0.768 ms
64 bytes from 192.168.50.201: icmp_seq=14 ttl=64 time=0.739 ms
64 bytes from 192.168.50.201: icmp_seq=15 ttl=64 time=0.912 ms
64 bytes from 192.168.50.201: icmp_seq=16 ttl=64 time=0.751 ms
^C
--- freenas.local ping statistics ---
17 packets transmitted, 17 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.699/0.753/0.912/0.054 ms
user-iMac:~ user$$

I ping through the IP and get this and also looks ok to me:
PING 192.168.50.201 (192.168.50.201): 56 data bytes
64 bytes from 192.168.50.201: icmp_seq=0 ttl=64 time=0.738 ms
64 bytes from 192.168.50.201: icmp_seq=1 ttl=64 time=0.707 ms
64 bytes from 192.168.50.201: icmp_seq=2 ttl=64 time=0.702 ms
64 bytes from 192.168.50.201: icmp_seq=3 ttl=64 time=0.768 ms
64 bytes from 192.168.50.201: icmp_seq=4 ttl=64 time=0.735 ms
64 bytes from 192.168.50.201: icmp_seq=5 ttl=64 time=0.744 ms
64 bytes from 192.168.50.201: icmp_seq=6 ttl=64 time=0.653 ms
64 bytes from 192.168.50.201: icmp_seq=7 ttl=64 time=0.700 ms
64 bytes from 192.168.50.201: icmp_seq=8 ttl=64 time=0.832 ms
64 bytes from 192.168.50.201: icmp_seq=9 ttl=64 time=0.744 ms
64 bytes from 192.168.50.201: icmp_seq=10 ttl=64 time=1.154 ms
64 bytes from 192.168.50.201: icmp_seq=11 ttl=64 time=0.809 ms
64 bytes from 192.168.50.201: icmp_seq=12 ttl=64 time=0.750 ms
64 bytes from 192.168.50.201: icmp_seq=13 ttl=64 time=0.707 ms
64 bytes from 192.168.50.201: icmp_seq=14 ttl=64 time=0.688 ms
64 bytes from 192.168.50.201: icmp_seq=15 ttl=64 time=0.757 ms
64 bytes from 192.168.50.201: icmp_seq=16 ttl=64 time=0.766 ms
64 bytes from 192.168.50.201: icmp_seq=17 ttl=64 time=0.773 ms
64 bytes from 192.168.50.201: icmp_seq=18 ttl=64 time=0.774 ms
^C
--- 192.168.50.201 ping statistics ---
19 packets transmitted, 19 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.653/0.763/1.154/0.101 ms
user-iMac:~ user$
 
D

dlavigne

Guest
Which FreeNAS version?
Are you using jumbo frames?
Does that occur throughout the day or just that one point during the day?
 

VolumeTank

Dabbler
Joined
Dec 23, 2018
Messages
38
Which FreeNAS version?
Are you using jumbo frames?
Does that occur throughout the day or just that one point during the day?

Version FreeNAS-11.2-RELEASE-U1
No jumbo frame, on the FreNAS it occurs everyday at the same time. On the router it's basically all day long.
And is only that port of the FreNAS I change the FreeNAS to different LAN ports of the router it does the same thing other devices like, XBOX, 1 Window PC, 2 MAC PC and Apple TV they all connected wired and it doesn't happen, that's why I know is something on the FreeNAS. Today it didn't happen on the FreeNASv I turn it off yesterday for about 2 hours but I keep getting the same log on the router from the FreeNAS port...

Jan 23 18:32:51 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 23 18:32:55 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 23 18:33:12 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 23 18:33:15 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 23 18:33:22 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 23 18:33:25 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex
Jan 23 18:33:32 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jan 23 18:33:35 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 10 mbps full duplex

I'm starting to think it has something to do with FreeNAS changing network speed or sleep mode I don't know :)
 

HolyK

Ninja Turtle
Moderator
Joined
May 26, 2011
Messages
653
This seems to be some sort of NIC power save? can you give us ifconfig -a and state which one is the NIC you're using (if you have more than one).
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
You try a new cable?
 

VolumeTank

Dabbler
Joined
Dec 23, 2018
Messages
38

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
I did used different cables but not new ones, some used cables I had on a draw. I will try a brand new instead.
Different cable is fine, just as long as it's a know good cable. Maybe the nic is bad at this point. Since the port on the switch didn't matter much and the cable didn't make a difference. The only thing left is the nic in the machine.
 

VolumeTank

Dabbler
Joined
Dec 23, 2018
Messages
38
Different cable is fine, just as long as it's a know good cable. Maybe the nic is bad at this point. Since the port on the switch didn't matter much and the cable didn't make a difference. The only thing left is the nic in the machine.

At first that was my first thought, but I don't want to spend money on a new NIC yet. I was planning to update from the onboard NIC to 10GB SFP+ instead. Is so crazy how much they want for RJ45 NIC specially 10GB T-Base.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
At first that was my first thought, but I don't want to spend money on a new NIC yet. I was planning to update from the onboard NIC to 10GB SFP+ instead. Is so crazy how much they want for RJ45 NIC specially 10GB T-Base.
I just switched to 10gig but avoided the rj45 stuff. The sfp+ stuff is cheaper, less power hungry and easy solution. A new Intel nic is $30 off eBay, if you just want to troubleshoot more.
 

VolumeTank

Dabbler
Joined
Dec 23, 2018
Messages
38
I just switched to 10gig but avoided the rj45 stuff. The sfp+ stuff is cheaper, less power hungry and easy solution. A new Intel nic is $30 off eBay, if you just want to troubleshoot more.

Yeah definitely the rj45 route is just crazy, I got a list of everything I need in order to switch to 10gig. I think I wili purchased a new nic for the moment on ebay, because once I switch to 10gig I can just take that nic and give it to my sons his on-board noc is a realtek and it sucks. Thanks so much for your help!
 
Top