Routers and subnetting

F

Thread Starter

Fluoronator

I have a growing control system network which is in need of spring cleaning. It has a total of 21 client nodes including HISs, PLCs, printers and a SQL server. All of these devices are currently haphazardly connected into a few stacked Ethernet switches. They have a potpourri of IP addresses and workgroup names and as a result, not every device can communicate with every other device.
Several new devices will be added as the plant expands this summer. I would like to clean up the network before this happens by choosing a common network address and subnetting each department. I know very little about networking but I assume this requires at least one router sitting between the subnets.

My topology is fairly simple…
|Department A|---fiber---|Department B|---fiber---|Department C|

Can I simply place a router with at least 3 ports in department B and connect the first port to departments A’s cable (the other end of department A’s cable connects to a switch in department A), the second to Department B’s switch and the third to Department C’s cable (and of course provide all of the correct settings)?

Assuming the answer is yes, here is my next question… What kind of router do I need? I’ve shopped the web and found an overwhelming pool of choices and am quite confused. First, every major computer store lists pages of devices they call DSL/Cable/Broadband/VPN etc… routers for around $100. The descriptions are vague but most of them have a picture on the box showing one computer connected to each port and then the last port connected to the internet via a cable modem or whatever. Am I correct to assume that these routers WILL NOT route between my subnets? Am I looking for the $1000 routers that say Cisco or Adtran on the box that virtually no BestBuy sales guy has ever heard of?

Again, assuming the answer is yes, I’m hoping you guys can point me to a router that will meet my requirements but be featureless enough that this "farm boy turned controls guy" can figure out how to set it up.

Thanks…
 
Dear Fluoronator,

Going for a router is a good idea only if you have a lot of traffic on the network and you wish to segregate traffic to individual departments as you call them. Routing at Ethernet wire-speed is rather expensive and yes you will have to go for the cisco 'types'. One more idea is to go for a layer-3 switch as it is known. It will offer you 10/100 mbps Ethernet ports alongwith some fibre ports as per the options you purchase. It is also a good idea to purchase media converters (optic fibre - copper for Ethernet) as this will reduce overall cost. All-optic routers will cost a bomb. The cheapest solution that I would prefer, provided the network is dedicated to plant control system traffic, is to clean up the subnetting and keep the system on the original switched network. Purchase a managed switch if required for acting as the go-through between various networks. Hope this helps.

Tomy Zacharia
 
You can daisy chain routers but it is not good practice. If your hardware is all in the same building I would recommend using just one switch and use the SQL server to handle the IP's and protocols. You can then manage the network from one location.
 
Thread starter Similar threads Forum Replies Date
P General Communications Chat 14
A General Communications Chat 3
Top