troubleshooting Question
Network Supernetting/Subnetting Change
asked on
So I have a situation that I inherited and I am not quite sure how to successfully perform this subnet change.
I recently (2 months ago) started a new job as network admin for a small company going through a growth spurt. The existing network is a 192.168.1.0/24 subnet which has become too small. I would like to change this to a 192.168.1.0/22 subnet with minimal interruption to the network. Here is the caveat to this whole process. The routing of the network is being handled by a Cisco Pix 506e, currently addressed at 192.168.1.1. Technically I should be able to change the subnet mask on all the devices to make this work, but, what change do I need to make in the PIX to route these extra addresses? Route Add statement?
I want to keep the existing servers/printers on the 192.168.1.xx segment while moving DHCP to 192.168.2.x and VOIP to 192.168.3.x and thereby leaving 192.168.4.x for future expansion. Feel free to call me an idiot if I have this wrong, but I feel it's got to be something simple. Yes, I realize it's old equipment that needs to be changed out but being a small company it's baby steps to get that new ASA device and Switches =)
Thanks for any help that can be offered in advance......
I recently (2 months ago) started a new job as network admin for a small company going through a growth spurt. The existing network is a 192.168.1.0/24 subnet which has become too small. I would like to change this to a 192.168.1.0/22 subnet with minimal interruption to the network. Here is the caveat to this whole process. The routing of the network is being handled by a Cisco Pix 506e, currently addressed at 192.168.1.1. Technically I should be able to change the subnet mask on all the devices to make this work, but, what change do I need to make in the PIX to route these extra addresses? Route Add statement?
I want to keep the existing servers/printers on the 192.168.1.xx segment while moving DHCP to 192.168.2.x and VOIP to 192.168.3.x and thereby leaving 192.168.4.x for future expansion. Feel free to call me an idiot if I have this wrong, but I feel it's got to be something simple. Yes, I realize it's old equipment that needs to be changed out but being a small company it's baby steps to get that new ASA device and Switches =)
Thanks for any help that can be offered in advance......
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 19 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.