Hi, I’m new to Linux and SuSe, I don’t really know many thing about SuSe but my office server using SuSe 11.2 and sometimes the wired network suddenly disconnected but the NIC LED & the Switch LED is still on. I’ve tried (service network restart) but it’s not working, it says the NIC is started but if I see from MikroTik and WoL program it shown as disconnected or offline, PuTTY can’t connect too. Usually the only solution that I know is to reboot the PC, but after awhile the problem could occur again. I set everything manually with Yast. Is there a permanent fix to this problem? Thank you.
Are you possibly referring to SUSE Linux Enterprise Server perhaps or openSUSE 11.2 (a discontinued version)? If the former is true then the correct forums can be found here
I think it’s openSUSE 11.2, yes it’s an old version I suppose. I think the company been using it since 2009.
openSUSE 11.2 is EOL
But is this a PCI NIC or onboard
I’d replace the PCI or if onboard try adding a PCI
D-Link basic 10/100
It’s onboard GIGABYTE GA-H81M-DS2, sometime we reinstall the SUSE if that happened. And what’s weird is that sometimes it get worse and the entire network would go down if I connect the NIC, I can’t even login to MikroTik when the NIC of the troubled PC connected, usually I would have the SUSE reinstalled when that happened. Most of the user PC here using the same mainboard, but they all use Windows 7 Ultimate x64 and never had the same NIC problem like the one served as server, only the servers uses SUSE. We have 5 SUSE server and the primary server that has MySQL never had that problem, only the other 4 server that connected to the primary server keep acting weird with their NIC.
It sounds like one server out of many (five Linux, some other windows) has
a bad NIC, since it is the only one having a problem. Replace it, or put
in a new NIC and ignore the onboard NIC. Bad hardware cannot be fixed by
software, and hardware eventually goes bad so even if it worked before it
may have some kind of problem now that cannot be fixed by software.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
The part I made bold in your description is of course a very serious issue, but it can be caused by many things all likely resulting in what is likely a broadcast storm.
Some causes…
- Bad hardware as others have pointed out. Besides a bad NIC, even a bad cable or cable connection can cause a broadcast storm.
- Bad DHCP configuration. Your machine must have a unique MAC address and a unique machine name in your network, info for both are easily gathered and verified. If you know enough to be able to inspect your DHCP logs and leases, this can take seconds to do. If you don’t have that kind of expertise, if your network is not large you can still log into every device and machine in your network to verify. You can also try Googling for a free “network inventory scanner,” install it and hopefully get a full report on everything you have with minimal work.
- You may have to run a packet capture app like Wireshark, if you do so it might take only a few minutes for someone to analyze and tell you immediately what your problem is.
Bottom line is that this is something that ordinarily isn’t too difficult to determine the cause (All things that cause very big problems reliably are easy to fix compared to things that are hardly noticeable and intermittent). But, it may take someone with some expertise to understand what the data is saying… So, maybe it would be worthwhile to find someone to look at this problem. In fact, it’s likely that if Internet access can be provided to the problem machine and some other machine the person could even troubleshoot your network remotely and wouldn’t have to visit your site.
IMO,
TSU
All the openSUSE use static IP MikroTik has nothing to do with their IP, only user PC’s with W7U x64 are using fixed DHCP.
Could it be a wrong settings in Yast or a bad or wrong NIC driver? How to install a new driver? It’s a command line only, so no GUI available.
If the whole network down and nobody can connect to anywhere including to a local computer and the MikroTik I usually try and disconnect the LAN cable of those 4 openSUSE server one by one to determine which one causing it and then reinstall it’s OS.
Perhaps I need to check on the cables and make a new one.
Thank you for the suggestion, I just wonder if the hardware is bad why only those 4 out of 5 that use openSUSE that has that kind of problem, and after OS reinstall the problem would go away for a few days or weeks.
Could it be a wrong settings in Yast or a bad or wrong NIC driver? How to install a new driver? It’s a command line only, so no GUI available.
Not likely. A hardware/cabling issue is far more likely, and needs to be eliminated first. As has already been suggested, you could capture and examine the traffic on the subnet when the problem next occurs.
I’ve seen bad switches cause problem when a machine is plugged into a bad port… Try changing the plugs and see if the problem accrues when a different machine is plugged int the port used by the “bad” machine"
Also seen mice and and other rodents chew cable and cause weird problem
Also are you certain that it is openSUSE and not just SUSE???
This is from when the error occur again
I’ll try changing the cables and ports
I don’t know what you’re trying to convey here. It doesn’t show anything problematic. The ifconfig output only shows that the eth0 interface is present and has an IP address (192.168.57.7) assigned. Can you still ping the gateway (or other LAN addresses) successfully at this time? You need to check cabling and switch ports, and use wireshark to capture traffic as already mentioned.
That’s exactly what I meant, it shows eth0 is present with the correct static IP but it’s offline, can’t ping, and it’s shown as turned off in MikroTik & Wake on LAN program, the PuTTY connection to it also disconnected. Restarting the network service doesn’t fix it, I can only reboot the PC to get it normal again. Sometimes it even cause the whole network to go down. As the picture shown, the problem now occur on 192.168.57.7, sometimes the problem randomly occur between 192.168.57.5-19.268.57.8
So, from the linux machine you can’t ping any address on the network? The most pragmatic thing you can probably do is disconnect the ethernet port and add a supported PCI ethernet card. Use that instead.
I’m sorry for being so dumb, I’ve installed a PCI NIC card but I cannot connect from PuTTY or ping it. So right now I’m using the onboard NIC again so that people can still do their job till I get a solution about it. I’ve set the IP, hostname of the PCI NIC and then reboot but it but it’s still not connecting. Any suggestion on this?
Remember, we’re remote from the machine and not able to be over your shoulder. Information is vital.
- Info about the network hardware present…
/sbin/lspci -nnk |grep '\02' -A2
/usr/sbin/hwinfo --netcard
You can copy/paste this to a text file and transfer via memory stick to a computer with internet connectivity for posting here.
- IP configuration…
ip add
ip route
Thank you very much, here is the result (This is from the other server which has the same problem) :
Volca-02:~ # /sbin/lspci -nnk |grep ‘[02’ -A2
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 0c)
Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:e000]
Kernel driver in use: r8169
04:01.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] [1106:3106] (rev 8b)
Subsystem: D-Link System Inc Device [1186:1405]
Kernel driver in use: via-rhine
Volca-02:~ # /usr/sbin/hwinfo --netcard
23: PCI 200.0: 0200 Ethernet controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8168
Unique ID: rBUF.BmqBU9Z2gDD
Parent ID: hoOk.7kVUIMLDyxB
SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: network
Model: “Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller”
Vendor: pci 0x10ec “Realtek Semiconductor Co., Ltd.”
Device: pci 0x8168 “RTL8111/8168B PCI Express Gigabit Ethernet controller”
SubVendor: pci 0x1458 “Giga-byte Technology”
SubDevice: pci 0xe000 “GA-EP45-DS5 Motherboard”
Revision: 0x0c
Driver: “r8169”
Driver Modules: “r8169”
Device File: eth0
I/O Ports: 0xe000-0xefff (rw)
Memory Range: 0xf7d00000-0xf7d00fff (rw,non-prefetchable)
Memory Range: 0xf0000000-0xf0003fff (rw,prefetchable)
IRQ: 35 (5759946 events)
HW Address: fc:aa:14:89:c1:f2
Link detected: yes
Module Alias: “pci:v000010ECd00008168sv00001458sd0000E000bc02sc00i00”
Driver Info #0:
Driver Status: r8169 is active
Driver Activation Cmd: “modprobe r8169”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #17 (PCI bridge)
25: PCI 401.0: 0200 Ethernet controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_1106_3106
Unique ID: JNkJ.dGmxk6YDo52
Parent ID: svHJ.6TfCthqAB73
SysFS ID: /devices/pci0000:00/0000:00:1c.3/0000:03:00.0/0000:04:01.0
SysFS BusID: 0000:04:01.0
Hardware Class: network
Model: “VIA VT6105/VT6106S [Rhine-III]”
Vendor: pci 0x1106 “VIA Technologies, Inc.”
Device: pci 0x3106 “VT6105/VT6106S [Rhine-III]”
SubVendor: pci 0x1186 “D-Link System Inc”
SubDevice: pci 0x1405
Revision: 0x8b
Driver: “via-rhine”
Driver Modules: “via_rhine”
Device File: eth1
I/O Ports: 0xd000-0xdfff (rw)
Memory Range: 0xf7c00000-0xf7c000ff (rw,non-prefetchable)
IRQ: 16 (24 events)
HW Address: 48:ee:0c:ba:d6:e9
Link detected: no
Module Alias: “pci:v00001106d00003106sv00001186sd00001405bc02sc00i00”
Driver Info #0:
Driver Status: via_rhine is active
Driver Activation Cmd: “modprobe via_rhine”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #24 (PCI bridge)
Volca-02:~ # ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether fc:aa:14:89:c1:f2 brd ff:ff:ff:ff:ff:ff
inet 192.168.57.5/24 brd 192.168.57.255 scope global eth0
inet6 fe80::feaa:14ff:fe89:c1f2/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 48:ee:0c:ba:d6:e9 brd ff:ff:ff:ff:ff:ff
inet 192.168.57.5/24 brd 192.168.57.255 scope global eth1
Volca-02:~ # ip route
192.168.57.0/24 dev eth0 proto kernel scope link src 192.168.57.5
192.168.57.0/24 dev eth1 proto kernel scope link src 192.168.57.5
127.0.0.0/8 dev lo scope link
default via 192.168.57.1 dev eth0
From that information, we can see that eth0 has a link while eth1 is not connected.
You have them both assigned with 192.168.57.5 (this is not a good idea to have duplicate addresses), and there is a default route assigned
Volca-02:~ # ip route
192.168.57.0/24 dev eth0 proto kernel scope link src 192.168.57.5
192.168.57.0/24 dev eth1 proto kernel scope link src 192.168.57.5
127.0.0.0/8 dev lo scope link
default via 192.168.57.1 dev eth0
Can you ping the gateway successfully?
ping 192.168.57.1
Can you ping a well known (google) internet address?
ping 8.8.8.8
Can you ping by name?
ping google.com
I’ll try and post the result when the problem happen again, right now the connection is still ok and I’m using eth0 to connect right now.