I work for a non-profit with some slightly more antiquated hardware. We have 3 locations, about 700 devices across them. Right now our locations are set up as:
Location 1 (Main) - /23 with a DHCP server. Range is 10.0.0.0 - 10.0.1.254
Location 2 - /24 with a DHCP server. Range is 192.168.0.0 - 192.168.0.254
Location 3 - /24 without a DHCP server. This location has the subnet issued by our ISP and all devices are pointed back to our primary and secondary DNS servers via adapter management (often via scripts).
We are rolling out VoIP at the end of the month and I'm not confident we have the necessary IPs to handle the incoming hardware at Location 1 and Location 2. I'm looking for thoughts on the following:
Moving Location 1 to a /22. This location has a ton of static devices (DVRs, Routers, Printers, reserved leases, most of our servers, etc). This would be quite a bit of work.
Moving Location 2 to a /23. This has fewer static devices and probably wouldn't be as difficult.
Here are my questions / issues that are causing me to be conflicted:
I actually don't know how many open IP addresses we have at Location 1. Unfortunately, my predecessor didn't use reservations, so I have no way to see all of the static devices on the network outside of just..knowing. In addition, the scope was set to only 150 addresses of the potential 512, but it was set in the middle of the subnet and I can't figure out why.
I think it would be nice to have all of the VoIP phones on their own cluster of 256, even if I don't NEED the addresses, maybe I should expand and scope it anyway?
I know that /24 has always been the ideal scenario for a network, but anymore is this really necessary? Does anyone see any issues with /22?
We don't have vLANs and our switches are dummy switches. I've been pushing for managed (or partially managed) switches at the minimum, but they aren't approved yet, so vLANs aren't really an option right now.
A final note, all of our servers are physical devices and not virtualized. Again, working on approval, but hard to come by with tight budget constraints. This means that changes are not easily snapshotted or restored from backup.
Anyone have some thoughts or suggestions on what you would recommend?