Connecting Switches to Router

What's wrong with the D-Link?

According to a quick part number search it has a couple of Gigabit ports available to connect it to the rest of the network.

I haven't checked but it'd probably be possible to set up link aggregation and have both ports connected to the HP switch.
 
Dooksy said:
Get rid of the D-Link as posted.
Click to expand...

Why? There isn't a specific need, and whilst it is only 100Mb, a 24-Port PoE switch isn't throwaway money.

IP cameras will not max a 100Mb connection by themselves, so arguably the only bottleneck becomes the connection to the NVR and the Uplink to the HP Switch. Both are easily solvable though, as that switch has 2x 1Gb copper ports, so connect the NVR to one, and use the other as the uplink to the HP Switch.

Edit: amended my "diagram" above
 
Well I would D/C it for a start and do a transfer between the PC and NAS and see how that is then when connecting to the router.

What is the interface set to on the PC? It happens in Windows quite often where it will negotiate at 100Mbit instead of 1Gbit.

It sounds like something is getting saturated, it's a case of finding out what exactly.
 
Just caught up on the replies (long day and night with work) and they made me laugh... especially the BS comment. Out of curiosity, @ov_sjo what smells?

@bledd, the setup was done just over 2 years ago and the D-Link was pretty good for the PoE support I required for the cameras. As @Armageus has mentioned, the cameras will definitely not use more than 100Mbps and the D-Link is connected to the router via a 1Gbit link so this shouldn't be an issue.

The primary Synology NAS (DS1813+) is the NVR running 7 x 3TB drives as SHR2. Since the cameras are on the D-Link and almost everything else is on the HP I thought that that may be causing issues, which is why I started this thread in the first place.

Network diagram:
4KEGZcll.png.jpg

Messy thing:
PdjswHjl.jpg
 
Looking at the above - the fix is to plug the dlink straight into the HP (as already mentioned).

The other question though is why is the Asus bottlenecking with LAN traffic though? In theory it should just be an integrated switch. You aren't running DD-WRT or other custom firmware are you? Or some complex firewall rules going on? Can't see what should max the routers CPU with LAN traffic otherwise.

(But as above - remove the LAN traffic and let the Router just route internet traffic)
 
Why no patch panels :(

Having self made cables turning into ports like that puts strain on the jacks. You should use patch panels and then short molded cat5e patch leads between panel and switch.




Currently the cameras go through the Dlink, Asus and HP.

I would use the HP as the main device, just have a single cable going from the Asus to the HP, then HP to gigabit uplink of the Dlink, nothing else connected to the router.



So from the top would be..

Modem
Asus
HP
-Connect all to HP.
-Connect Dlink to HP.


You could even do a 2GB trunk between the 2x switches.
 
Last edited:
Armageus said:
Looking at the above - the fix is to plug the dlink straight into the HP (as already mentioned).

The other question though is why is the Asus bottlenecking with LAN traffic though? In theory it should just be an integrated switch. You aren't running DD-WRT or other custom firmware are you? Or some complex firewall rules going on? Can't see what should max the routers CPU with LAN traffic otherwise.

(But as above - remove the LAN traffic and let the Router just route internet traffic)
Click to expand...


I think I mentioned in one of my posts that I was running Shibby's Tomato which is what Asus's Merlin was based of. I started doing some digging and people were saying Tomato was slower.


Anyways, this whole post was about checking whether plugging the D-Link into the HP would help and/or if it was a better design... I think almost of all you have basically said yes to that so I will be tinkering when I am next back home (I work away).
 
Last edited:
bledd said:
Why no patch panels :(

Having self made cables turning into ports like that puts strain on the jacks. You should use patch panels and then short molded cat5e patch leads between panel and switch.




Currently the cameras go through the Dlink, Asus and HP.

I would use the HP as the main device, just have a single cable going from the Asus to the HP, then HP to gigabit uplink of the Dlink, nothing else connected to the router.



So from the top would be..

Modem
Asus
HP
-Connect all to HP.
-Connect Dlink to HP.


You could even do a 2GB trunk between the 2x switches.
Click to expand...




The server cabinet is messier because all the network cables and 16 Sky cables (from the dish) come in there. Every room is wired with Sky in case we ever wanted to have multiroom, and so it would be a simple matter of just connecting two or more of the cables :)

You are right about the patch panels and if this was a proper business setup then I would but its just something I enjoy tinkering with so am not overly fussed.

Good thinking on the trunking. I'll use this opportunity to trunk the second NAS as well. I probably don't need to trunk either but its not like I'm short on ports / cabling :D
 
Danger Phoenix said:
Just caught up on the replies (long day and night with work) and they made me laugh... especially the BS comment. Out of curiosity, @ov_sjo what smells?
Click to expand...

So you read my comment but ignored the question I asked? The BS wasn't aimed at you btw.

Let's try again..


1. Are you running a single subnet?

2. Have you checked switch port stats to see if there are any errors generated?

3. How are you testing performance? Exactly. From, to, application/scenario, expected performance, actual performance. etc.
 
ov_sjo said:
So you read my comment but ignored the question I asked? The BS wasn't aimed at you btw.

Let's try again..


1. Are you running a single subnet?

2. Have you checked switch port stats to see if there are any errors generated?

3. How are you testing performance? Exactly. From, to, application/scenario, expected performance, actual performance. etc.
Click to expand...


I've not slept since I woke up on Sunday morning so definitely wasn't intentional.

1) Yep

2) I have and nothing obvious that I can see

3) I haven't done any proper tests, just noticed things grind to a halt if I am downloading something at ~150Mbit from the internet, whilst copying 200GB from the PC to the main NAS (download location and source of the copy are on different drives... one is a M.2 and the other a WD Black). When this is going on, I cannot even access the router's admin page from any device either on the LAN or WAN access.
 
Thanks. What's the CPU usage when you do this? Any AV running? Anything in particular that isn't Defender?

Can you browse normal internet sites? Is it just the router you can't get? Can you browse to the NAS?
 
150Mbit internet, maybe an Edgerouter isn't such a bad idea, they're made for gigabit connections :D
 
I suppose in theory you'd want one switch plugged into the other. If you have router -> switch 1 -> switch 2, and a device on switch 1 is saturating bandwidth talking to a device on switch 2, then at least all the other devices on switch 1 can access the internet fine. If the switches were both plugged into the router then there's a bottleneck.

Could be totally wrong though, just imagining the layout in my mind.
 
You must log in or register to reply here.
Back
Top Bottom