Discussion Locked

Number of servers on a LAN

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Out of curiosity, what would be a "good" number of servers or a maximum number of servers to have on a LAN. For example, if I am running a number of Novell servers (10 or more), WINS servers (2 or more), DNS servers (2 or more), Exchange servers (2or more) and various application servers (too many to count)...

I would tend to believe that these servers should be broken up by services into separate LAN's. I would think that by doing so, broadcast traffic and multicast traffic would be reduced, easing network traffic. Also, troubleshooting separate LAN's would be easier, right?

5 replies

by jim-h

How Many? : Estimating a good number of servers is difficult without knowing what type of LAN or how much data each Server needs to use. A good way to look at it is to monitor Bandwidth used by each Server and then compare that to the type of LAN that you have adding all the Server up that would be on the same LAN.

Multiple LANs? : Yes, it can be easier and more efficient to separate Servers by function into Separated LANs and Broadcast Domains. This is especially true if you are running multiple protocols. Separating your purely IP Servers with IPX and/or IP Servers can cut down on the chit-chat that is unneeded for those running the other protocol. Troubleshooting can also be simplified because isolation of problems can be limited to an individual LAN or Broadcast Domain.

Hope it helps out, good luck!
-Jim

by jim-h

Alright, sounds like you have quite the server list. Since you are using Virtual LANs grouping will be easy to change if you ever needed/wanted to...This can make the grouping fun. :-)

As far as suggestions for groups I am more comfortable separating by functions. This way I can scale my preventative maintenance and security to cater to each VLAN. For example I might have a setup like this:
VLAN1 ? Network Users with Static IP (User Desktops)
VLAN2 ? Network Users with Dynamic IP (Laptop and Wireless Users)
VLAN3 ? Internal User Services (WINS/DHCP/Exchange/File-Sharing-Servers)
VLAN4 ? Back-up Network (Backup Servers from VLAN3)
VLAN5 ? Externally Accessible Servers or Maybe DMZ (WWW/POP3/DNS)
VLAN6 ? Public Internet Outbound (Routers to Internet)

Naturally you can group your stuff based on what you have but this is a setup that comes to mind. What I like about this is that I can tweak my access between VLANs ?just in case? something gets compromised. For example, if a user laptop is broken into from the outside then only allowing VLAN3 to VLAN4 would protect your Back-up Servers at a bare minimum. Obviously you could do a ton of methods to protect VLANs from other VLANs in case of a compromised system.

Now if youare running IPX, Appletalk, and/or TCP/IP then would consider separating these as well as best you can to keep the chatter on the saem broadcast domain.

Keep in mind that the more LANs that you create the more that you have to administer. I currently have Network that I am trying to fix because there is literally only 2 Servers per VLAN making the Admin work a nightmare. To add a device it means adding a new VLAN, Subnet, etc?

Thanks,
-Jim

by cjnmis

How many....good gosh. Seems I forgot to add in backup servers, compounding that Exchange is replicating on the very same LAN.

What kind of grouping would you recommend? For example, DNS servers grouped with DHCP servers on VLAN 1, WINS serverson VLAN 2, Exchange servers on VLAN 3, etc...?

What have your experiences been?

by wlbowers

If I have the chance to design a system. I go by the rule if they don't have to communicate they don't need to be tied together.

Coming into a system like yours I would contact Computer Associates and inquire about their lan management software. It can monitor traffic patterns and let you see problems as they build.

Good Luck your gonna need it

Lee

Traffic management and analysis in a system such as yours is a must.

by nettek

Multiple LANs is a bad idea. You'd have to maintain multiple subnets, multiple routers, and reconfigure nodes so that they have access to the correct LANs. And if you have a connectivity problem between LANs, you have to troubleshoot multiple LANs. That doesn't sound easier to me.

If your biggest concern is traffic, simply install switches in place of hubs. This gives you a mini-LAN for each switch port. Not to mention it is much easier to maintain a single LAN as opposed to multiple LANs.

This discussion is closed to new replies.