Another consideration may be the power of users inside a department. For instance, I did previously operate in a workplace by which a large number of users all labored in one building. For any lengthy time, there have been no exterior facilities. Within an atmosphere such as this, you are able to implement subnets, however the locations for individuals subnets may not be so obvious. I’ve come across some companies subnet by department, but this would be an awful idea since it is not unusual for any department to maneuver to a different area of the building and click home page for other details. Even worse, a might move a number of its employees, although not others. The answer would be to depend on something which will not change. For instance, you may subnet by floor (bottom floor, second floor, etc.), or by area (east wing, west wing, etc.)
Hopefully, you’re beginning to generate an agenda for the organization, but there’s yet another consideration you need to make. You have to stop and consider hardware placement. All the subnets must be linked together via a router (you most likely don’t wish to make use of the same router that connects your business towards the outdoors world). Therefore, you will have to evaluate which size router you will need, just how much that router will definitely cost, in which the router is going to be placed, where the router will connect with each subnet.
Likewise, each subnet will require its very own hubs or switches. You defeat the objective of subnetting if multiple subnets are discussing a typical hub.
One further consideration is server placement. It requires longer for any user to gain access to a web server in the event that server is within another subnet. The latency is not usually enough to become a problem, however if you simply have countless users constantly crossing a subnet to gain access to a web server, you very well may too not really have subnetted your network since you aren’t isolating much traffic.
There are a handful of methods to this problem. One possible solution is when you’ve got a server that services just one department, you may put the server in to the same subnet as those who is going to be being able to access it probably the most. For those who have servers that’ll be utilized by everybody within the organization, consider putting multiple NICs into each server and binding each NIC to some separate subnet.
One other way that you could cut lower on mix subnet visitors are by providing each subnet its very own domain controller. If you opt to do that though, make sure to define sites using your Active Directory. This way, users will have to authenticate via a domain controller in their own individual subnet/site.