Network Bizzard
in [Debian]
|
Prev: mashup "apt-cache search <SearchTerm>"
Next: Linux PDA cell phones - Linux on Android compatible cell phones? ; jor Debian
From: Camaleón on 29 Jun 2010 11:50 On Tue, 29 Jun 2010 07:40:09 -0700, Phillipus Gunawan wrote: > Today I found a network problem which being fixed but I can not explain > why/how. So if someone can enlightening me, would be much appreciated (...) If both networks are working fine when they act separately, then the problem may reside in the network setup (duplicated/conflicting IP addresses, bad cabling or switch connections, routing problems...) so the problem arises when you join both networks. I assume both swicthes are unmanageable layer 2, 16-port gigabit standard switches and all ports MID/MDIX capable so nor "up-link" ports nor crossover cable is needed. The more details you provide (cabling management details?, are there pacth panels in use or just direct plug to the swtich...?) the better. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/pan.2010.06.29.15.43.12(a)gmail.com
From: Stan Hoeppner on 29 Jun 2010 13:30 Camaleón put forth on 6/29/2010 10:43 AM: > On Tue, 29 Jun 2010 07:40:09 -0700, Phillipus Gunawan wrote: > >> Today I found a network problem which being fixed but I can not explain >> why/how. So if someone can enlightening me, would be much appreciated > > (...) > > If both networks are working fine when they act separately, then the > problem may reside in the network setup (duplicated/conflicting IP > addresses, bad cabling or switch connections, routing problems...) so the > problem arises when you join both networks. > > I assume both swicthes are unmanageable layer 2, 16-port gigabit standard > switches and all ports MID/MDIX capable so nor "up-link" ports nor > crossover cable is needed. > > The more details you provide (cabling management details?, are there > pacth panels in use or just direct plug to the swtich...?) the better. Having 2 physical links between ethernet switches requires link aggregation, port bonding, whatever the switch vendor calls it. All switches with such capability fall into the "managed switch" product category. If these are managed switches, read the documentation and find out if they support link aggregation. If they are not managed switches, then make sure there is only one uplink cable between the switches. If you would provide us with the brand and model of the switches we could probably tell you pretty quickly if they support link aggregation or not. -- Stan -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C2A2C12.9000000(a)hardwarefreak.com
From: Phillipus Gunawan on 29 Jun 2010 20:50 Thank for you replies, Once those 3 PCs on level 5 turn on, after a few minutes, level 4 and 5 loose connections The PCs starting to throws errors IP duplications As I mentioned, DHCP server is on Netgear FVS318v3 I should mentioned earlier, the cabling are straight to the switches are Netgear -> G1, one Cat5e cable G1 -> G2, two Cat5e connected each other <Stan> >If you would provide us with the brand and model of the switches we could >probably tell you pretty quickly if they support link aggregation or not. Switches model: TP-SG1016 from TPLink (http://www.tp-link.com.au/products/productDetails.asp?class=&content=spe&pmodel=TL%2DSG1016) <Camaleón> >I assume both swicthes are unmanageable layer 2, 16-port gigabit standard >switches and all ports MID/MDIX capable so nor "up-link" ports nor >crossover cable is needed. >The more details you provide (cabling management details?, are there >pacth panels in use or just direct plug to the swtich...?) the better. Both switches are supports Auto-MDI/MDIX function The cabling between G1 and G2 are direct cable/direct plug to the switch -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/297415.97130.qm(a)web65707.mail.ac4.yahoo.com
From: Andrei Popescu on 30 Jun 2010 04:00 On Ma, 29 iun 10, 17:41:27, Phillipus Gunawan wrote: > > Switches model: TP-SG1016 from TPLink (http://www.tp-link.com.au/products/productDetails.asp?class=&content=spe&pmodel=TL%2DSG1016) There is no mention there about link-aggregation or bonding (or whatever). To me this means it's not supposed to work with two cable. Disconnect one, but leave it in place, in case you ever have troubles with the other. And don't blame it on the cabling guys either. Consider someday you might upgrade your switches to models supporting bonding and you will be able to increase the throughput by using the additional wire. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: Camaleón on 30 Jun 2010 04:30
On Tue, 29 Jun 2010 17:41:27 -0700, Phillipus Gunawan wrote: > Thank for you replies, > > Once those 3 PCs on level 5 turn on, after a few minutes, level 4 and 5 > loose connections The PCs starting to throws errors IP duplications As I > mentioned, DHCP server is on Netgear FVS318v3 > > I should mentioned earlier, the cabling are straight to the switches are > Netgear -> G1, one Cat5e cable > G1 -> G2, two Cat5e connected each other ¿"Two" cables? Why that? Redundancy/failover? :-? It should be just "one", as Andrei suggests. If after unplugging one of the cables linking the switches you are still facing problems, replace the switches. Your setup is very common and should have no problems at all if the installation went through standards-compliant (cabling length limits, connectors crimping...). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/pan.2010.06.30.08.28.15(a)gmail.com |