› Forums › Network Management › ZeroShell › Asymmetric links lead to whole network freeze!!
- This topic is empty.
-
AuthorPosts
-
February 23, 2017 at 2:51 pm #44740
Montikore
ParticipantHi all,
I just noticed a very strange behavior with zeroshell : my network is mostly on gigabit links, but i have a few links at 100Mb. If i launch a file copy on a computer on the 100Mb link, the files being on the gigabit link side, then the whole network is broken (except for the copy which is working…) and zeroshell doesn’t answer anymore on the web interface…
So i finally understood why sometimes the whole network is broken…. but what the fuck??!!!
February 23, 2017 at 4:29 pm #54351DrmCa
ParticipantWhat is your topology?
February 23, 2017 at 4:49 pm #54352Montikore
Participantone central zeroshell, 4 subnetworks each on a dedicated gigabit ethernet card
with a 100Mb link, the copy is at 10Mb/s and the whole network is down…
with a Giga link, the copy is at 40Mb/s and everything is smoothAnd this is always the same!
February 24, 2017 at 4:13 pm #54353DrmCa
ParticipantAnd what is your ZS hardware, including mobo, CPU, RAM, NICs?
So you have a box with 4 GB NICs running ZS. What are you referring to as ‘100mb/s link’?
February 27, 2017 at 10:28 am #54354Montikore
Participanti don’t know about the mobo, but i have the feeling this is a software issue. Anyway here are the details :
proc :Intel Core2 Quad
RAM : 3Gb
NICs : D-Link System Inc DGE-528TWhen i speak about 100Mb link, i just mean the computer is behind a 100Mb switch.
For now the only solution (without replacing all switches) i see is to install the x64 kernel (i’m currently running the 32bit version) to have a try when it will be possible…
February 28, 2017 at 3:24 pm #54355DrmCa
ParticipantI would look into replacing the Dlink NICs with Intel based NICs first. You can get the Intel NICs off the Ebay very cheap.
April 25, 2017 at 9:05 am #54356Montikore
Participantjust in case somebody else faces the same issue : after installing the x64 core, the issue is resolved.
So there is a bug in the x32 version… perhaps running the x32 version on a x64 computer is not well supported…
April 25, 2017 at 3:37 pm #54357DrmCa
ParticipantSame version 64bit core as 32bit was?
Wow, this is lame then. 32 and 64 should be only different in binary format after compilation as the instruction sets are the same except for memory addressing. Thanks for sharing! -
AuthorPosts
- You must be logged in to reply to this topic.