Should we go for /16 or /24 while designing the segment?

Castlewood
Castlewood used Ask the Experts™
on
We just acquired a new facility and are re-assigning a new IP segment for it. There are about 90 users and 120 computers/network devices in that facility.
Based on what we have now we would like to assign the segment 10.1.16.0. My boss tends to use
10.1.16.0/16 for it but instead of such a big segment I suggest using three smaller segments:
10.1.16.0/24 for data
10.1.17.0/24 for VPN
10.1.18.0/24 for voip

Can you comment on the above two proposals and give your suggestion please? Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Scott CSenior Engineer
Commented:
I'd go with the 3 smaller segments.  One of our customers has a large segment and has some devices that are killing network performance for everyone.

If the devices were on their own segment, I feel that the entire network would not have been impacted.
Ken BooneNetwork Consultant
Commented:
Definitely 3 /24 segments.  For a myriad of reasons.

It is a whole lot quicker to scan a /24 than a /16 if you are looking for something.
You mentioned voice.  Best practice is to ALWAYS have voice on its own network segment.
Management - Much easier to identify what traffic is what when they are broken out.  
Security - You can put ACLs on the vlans to limit traffic flows between vlans if you need to.
With that amount of devices, I think that /16 is overkill. 3 smaller subnets is MORE than adequate. What I might be tempted to do if it were me though, is create the subnets as:-

10.1.16.0/24 - DATA
10.1.20.0/24 - VPN
10.1.21.0/24 - VOIP

That way, if ever you want to expand your data scope, you could re-subnet as:-

10.1.16.0/22 - that way you would have DATA addresses from 10.1.16.0 - 10.1.19.254 and wouldn't have to worry about re-subnetting VPN or VOIP
I will give my take too.  /16 is overkill, however, if you have multiple facilities I recommend a /16 for site.  This will make the route tables smaller for remote sites connecting, they know that 10.16.0.0/16 is new facility.

Then in the new facility use 3 subnets, 10.16.1.0/24, 10.16.2.0/24, 10.16.3.0/24 ect......   You can add more subnets in the future with ease,
Similar to Bryant's comment, if you decide on three /24 subnets, then I'd suggest a /22 for the whole site, which you can break up into four /24 subnets.  Then you only have one routing table entry for the whole site.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial