V
V
v_k2011-03-04 01:41:00
linux
v_k, 2011-03-04 01:41:00

error in "eth1: link down" logs

There are about 3 messages in the logs per day. Should I pay attention to this or is it not scary yet?

meme:~# lspci |grep -i eth
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)


meme:~# ethtool eth1
Settings for eth1:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised auto- negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 3
Transceiver: external
Auto-negotiation: off
Supports Wake-on: g
Wake-on: d
Link detected: yes


meme:~# uname -a
Linux webtask 2.6.26-2-686 #1 SMP Thu Sep 16 19:35:51 UTC 2010 i686 GNU/Linux


Auto-negotiation is disabled to force 100Mb/s Full duplex operation.

Answer the question

In order to leave comments, you need to log in

4 answer(s)
E
exIV, 2011-03-04
@exIV

In general, as far as I understand, this simply means a physical loss of communication, which can be caused, for example, by rebooting the switch or router where you have this eth1 connected :)

L
Lev Lybin, 2011-03-04
@lybin

Does the connection fail?

L
lazyk, 2011-03-04
@lazyk

Well, in general, this indicates a loss of communication
3 flaps per day, in general, it’s not scary, but if you want to “heal”, check the switches, patches, replacing the network card)))

O
Odinokij_Kot, 2011-03-07
@Odinokij_Kot

and what kind of network card? Personally, I had this when 3 old hundred-thousand-thousand Ryltec network cards stuck out in the router, it didn’t really bother me, of course, but it was interesting why. After changing them to intel, such messages in the log disappeared =)
In my case, the switches were under my control and definitely did not reboot.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question