Retail Network Segregation Opinions Needed

SirSub42

Honorable
Aug 31, 2013
367
1
10,960
So this is my situation.
I am a computer science student working at a health food retail store. We don't exactly have an IT department, and our Systems Administrator's knowledge is limited mainly to the software which keeps our systems running. Our store manager apparently took notes from Howard Hughes regarding paranoia. I say this because we currently have 31 IP security cameras installed (relatively small store too) and he wants to double this number.

Only problem is, our network is congested because whoever set it up, set the entire network on a /8. So while my knowledge of network communications is limited, I am guessing ~81 hosts all communicating on the same broadcast network is a terrible idea. Here is a breakdown of our network
(3) Switches, Linksys GS724TP (this one powers the IP cameras as it offers PoE), GS724T & JGS542.
(1) Motorola Router SBG6580
(9) Network Printers
(7) Network Scales (for weighing sandwiches, meats etc, requires network access so that we can program ingredients, prices etc).
(25) Desktop computers + (1) Laptop
(31) IP cameras, only two of which record audio as well.
(2) Wireless Scanners
(1) Windows 2008 Server
(1) Credit card processing server
(1) POS server
(1) IP camera server + Storage

I am pretty sure I can work some sort of deal with tuition reimbursement plan if I can solve this problem. I am hoping to put into action whatever plan on Thanksgiving, as it will be the only time I may have ~36 hours to work straight since the store will be closed.

My first question I suppose is, as far as network segmentation goes. I would guess creating two networks from our 10.0.0.0/8, into let's say 10.0.1.0/24 & 10.0.2.0/24. One network for only cameras and one for everything else.

Second question is concerning the hardware. To the best of my knowledge, we do not run any sort of port security, ACLs etc, but I would like to down the line if I am permitted further freedom to tinker. But for now, I would assume with the increased routed transactions, we will need something more powerful than our current SoHo router.

Third question, for something such as a network bandwidth monitor. Does anyone have suggestions? I would like someway to physically map out what is using X % of the bandwidth so I can put some sort of presentation or packet together to present. And where would this be installed to? I would say the router, but from what I remember from my Cisco training, since everything is on the same network, the router pretty much only deals with requests to the outside. So I would say switch, but since we have three, would each switch only indicate the performance for the 24 slots it has filled? Then I figure on the server itself, but the boss man seems to want to protect access to this like fort knox. Even though our POS has its own dedicated server, our credit cards are processed through a dedicated server. He seems to believe that breaking our Windows server will cause the store not to function. So he generates a random password and locks it in the safe, generating a new one each time the old one is used. Which is fantastic and all, but keeps the default logins for just about everything else.

Thanks to those of you who reached this point, I know it was quite a doozie of a question, but hopefully someone has a similar experience and can share some hindsight. Look forward to the feedback ~Sub

 
Solution
Since these are managed switches you should be able to log in and look at the port utilization. I have not used this brand but if you are lucky there will be a single screen that shows all the ports and their utilization's. Almost all modern switches can run what is called non blocking or wire speed. This means every port on the switch can be doing 1g up and 1g down simultaneously and the switch will not drop any packets. The only ports that could be a issue are the uplinks between the switches...but you have 1g which is huge amount of bandwidth. I have run many hundreds of users on a single gig uplink with no issues. I would look for ports that are running 100m or many got into half duplex or are taking some other errors. If...
At questions 1 and 2: like you said, you could segment your network in two subnets, one for IP cameras one for everything else, if communication between both networks is needed then make sure your router supports vlans (so it can have 2 IP addresses, one for network 10.0.1.0/24 and another for 10.0.2.0/24) and inter-vlan routing, if it does support then it should be able to handle your network even with the new cameras to be added.

Third question is undoubtedly the key here, to be completely sure about whether your router (and your switches) will be able to handle your network traffic, you'll need to monitor the bandwidth usage, I suggest using Syslog, like kiwi syslog (free) or another more advanced one if you can afford it, a syslog server should be able to extract data from your network components and show you the activity on them, from bandwidth usage to CPU usage etc.

Get that running to see where you really need the upgrades/changes to have your network running flawlessly.

P.S.: maybe your router/switches will need an extra configuration to work with syslog, like turning on the feature on them.
 
Not sure what the last switch is but the good news is the other 2 switches have a lot of useful features.

On you security question these switches support 802.1x. This is the most secure form port authentication available it prevents installation of any type of router or switch. It also requires authentication before any traffic is allowed to pass. There are a number of ways to configure it but most people run a radius server on their domain controller to avoid having 2 separate logins.

The other thing these switches run is SNMP. You should be able to get one of the free network monitoring tools like MRTG,Nagios, or zabbix. All are unix based. You could run on the free trial of PRTG that runs on windows but its limitations may be too much. It also really is a netflow analyser more than a network. Key here will be figuring out the MIBS so that you know what to poll to get things like number of broadcast on a port or number of errors as well as the more normal input and output bytes. Someone may already have a template for these switches otherwise a MIB browser and lots of time with the SNMPWALK command will get you want you need.

I would run the monitors and see if you even have a problem. Key would be the CPU load on the switches and maybe the severs...assuming your boss lets you have SNMP access to the servers so you can monitor those too.

The recommendations for subnets was made long ago when the CPU and memory of devices was much lower. We commonly use /23 subnets which have many more devices that you have and have no issue at all.

If you do decide to route between subnets I would use a layer3 switch rather than a router. The key difference is a layer3 switch use asic to do the routing where a router most the time uses the processors. This means that anything that actually changes the packet very much cannot be done on a switch. Things like NAT,GRE tunnels and packet encryption come to mind as things a layer3 switch cannot do.
 

choucove

Distinguished
May 13, 2011
756
0
19,360
Segmenting your network into separate VLANs might not be a bad idea, but in reality you may not need separate VLANs but actually just physically separate them. This means operate your IP camera system and the server on its own switches that are not connected to other networks, which will mean that hardware is completely independent of each other. IP camera traffic will not be slowing down the rest of your network. I'm not sure if this is currently feasible with your existing hardware and setup, it's hard to determine exactly without actually being there and seeing how everything is currently connected and configured. But for a network running that many PoE IP cameras I have always heard it recommended to run a separate switch for that traffic. And if you don't need to have access to the camera video feeds from the internet, then there wouldn't be a need for even connecting that switch to your router at all, leave it as an internal-only LAN.

If you need to have access between the two networks (from your staff network to the IP camera network) then you can set up a layer 3 switch as Bill001g has suggested, or a firewall or router which supports multiple lans or VLANs. Having a firewall in place might be nice anyways given that your primary network router is a simple SOHO Motorola modem. That motorola unit is pretty nice and has a lot of features for a SOHO modem, but if the business manager is really so concerned about network security, he may feel more comfortable with an actual business-class firewall solution which is also capable of more fine control as well as features for your network like VLANs.
 

SirSub42

Honorable
Aug 31, 2013
367
1
10,960
Thank you choucove, bill001g and RaDiKaL for the responses. I will attempt to get the authenitation details for the switches on Monday. Based on the responses, it seems like segmenting the netowrk may not be necessary? The bandwidth problem is simply what I was told.

Would adding a second GS724TP & IP camera server be the simplest solution? I was finally given the login for the camera server and it seems the server CPU is at 100% 24/7. Odd question, but seeing as we have 31 cameras, and the GS724TP is a 24 port switch, I am assuming 7 additional cameras are running on a switch which is also used for our office network. Would this cause the sort of bandwidth "congestion" he is complaining about?

Will definitely look into adding an SNMP log server as well. Syslog looks promising, but seeing as it is late and I have been up for 17 hours, it seems we would need a dedicated system for an SNMP logging server?

Thanks again for all the answers and if anyone else has a last minute suggestion, I will be running a preliminary plan to my boss on Monday. Add a second camera server(or even upgrade the current one rather than two independant servers), add a second GS724TP.
 
Since these are managed switches you should be able to log in and look at the port utilization. I have not used this brand but if you are lucky there will be a single screen that shows all the ports and their utilization's. Almost all modern switches can run what is called non blocking or wire speed. This means every port on the switch can be doing 1g up and 1g down simultaneously and the switch will not drop any packets. The only ports that could be a issue are the uplinks between the switches...but you have 1g which is huge amount of bandwidth. I have run many hundreds of users on a single gig uplink with no issues. I would look for ports that are running 100m or many got into half duplex or are taking some other errors. If this all is good then you have to start to blame the servers for the delay since there is not a lot else.
 
Solution