O
O
Oleg Popov2015-12-20 14:47:58
Network administration
Oleg Popov, 2015-12-20 14:47:58

The choice of equipment for the local network?

Hello.
In general, we have a large car service, which will open closer to spring, and now the choice of equipment for the server room has become, tell me how and on what it is better to implement all this.
So we have:
1. About 20-30 IP cameras + 2 registrars.
2. Working network (20-30 computers + printers + 1C, etc.)
3. Working wifi network
4. Guest wifi network
At the moment, I figured that MikroTik <RB1100AHx2> will be in the core of the network. On it, several dhcp servers will be deployed (namely 4 pcs).
Then I plan to use gigabit Dlink to connect to places.
Under wifi, I want to use Ubiquiti UniFi AP 3-pack to deploy 2wifi networks on them.
In general, such a scheme is emerging. Maybe there is something better? Should I deploy dhcp on hardware or use win2012 to deploy dhcp?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
T
throughtheether, 2015-12-20
@throughtheether

This is how I would solve your problem.

1. About 20-30 IP cameras + 2 recorders.
Bring all the cameras to a separate switch, connect the NVR there, from it an L3 link to the office, in order to remotely look at the pictures. Register all addresses statically, without DHCP.
2. Working network (20-30 computers + printers + 1C, etc.)
By switchboard per floor/department. DHCP is for user computers only. Use vlanes.
3. Working wifi network
4. Guest wifi network
I'm not an expert on wi-fi, my comment is unlikely to be useful. The only thing is that under wi-fi I would single out separate prefixes ("subnets"), i.e. would not use bridging if it is not necessary.
Should I deploy dhcp on hardware or use win2012 to deploy dhcp?
I think it makes sense to use DHCP on the device acting as the client's default router. Naturally, it is necessary to correctly assign IP prefixes ("subnets"). The feasibility of having a separate DHCP server is questionable.
I would also like to note a couple of points:
1) power network equipment through a UPS.
2) a separate server (possibly virtual) for monitoring everything (UPS, network devices, link status)
3) Sooner or later, one of the user PCs will create an L2 loop (via wi-fi and ethernet in case of wifi bridge mode; incorrect inclusion IP phone with built-in switch, etc.). It is necessary to provide for this.
Regarding the equipment: it is not clear why gigabit links are needed in the office. You may need gigabit links to servers and NVR. Instead of new D-links, if the budget is limited, I would use used switches of the catalyst 3560, 2960 lines.

A
alexdora, 2015-12-20
@alexdora

I used to deal with networks, or rather I was the technical director of the provider and I will answer what I should pay attention to when building a network based on the task:

  1. It makes sense to deploy a DHCP network only with binding to a MAC address. The object itself (number of computers) is too small to deploy DHCP at all. In this case, it is more a crutch than a useful stray.
    Main disadvantage: A device that should always work. It doesn't matter what device it is. It will not be a pleasant story if the reboot of this one falls exactly at the moment when some devices renew the lease. Or, after a power failure, the device turned on for a long time and some devices did not wait for the IP address, and you have a critical component - cameras.
    Regarding 4 DHCP servers, I did not understand anything. One device and 4 DHCP servers? Do you mean DHCP server on different subnets? If so, then I get scared.
  2. You forgot the most critical components. You say: There will be such and such a server on the gateway, such and such Wi-Fi. I did not see something in your opus: I will use second-level switches for communication between computers. Your network will fan out on ordinary "stupid" switches after infecting a single computer. And you will run clutching your head and not understand: What happened, why the network itself freezes. At the heart of the network should be L2 switches (100 Mbps). Without configuration, they will give the most important thing - the network will not collapse if one of the computers starts a broadcast storm.
  3. Based on what I have read, I recommend putting ice on your head and cooling it down a bit. Your entire network needs to be simplified. If you do this, then it will turn out reliable. Then say thank you.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question