04-27-2016 06:34 AM - edited 03-08-2019 05:30 AM
Hello all,
My company is planning to completely change from their RFC 1918 Class C IP address space to a Class A for their internal networks. The public IPs will remain the same. We have IP Phones, a central DHCP server (for private addresses), and remote sites. Also, we're running PAT to a public IP address.
Have any of you planned and successfully accomplished this? I've done the usual research on the internet and found a few planning considerations already, including this one:
Get IT Done: IP addressing scheme changes require a cutover plan - TechRepublic
Since there's nothing like advice from someone having done this already, I pose the question to the group.
I'm most concerned with which devices and/or interfaces to do first, is it an all-or-nothing approach, one subnet at a time, hot cut-over, etc
Perhaps a partial planning document to share would be great.
Thanks, in advance for your help
Al
04-27-2016 07:54 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Your referenced document mentions using secondary addressing. Secondary addressing is very helpful when changing topology addressing. However, I didn't notice whether the document mentioned, that by default, Cisco devices will only DHCP relay for the primary interface network.
Also, your referenced document mentions using secondary addressing on hosts. I've found, once the network supports primary and secondary addressing, hosts with static IPs can usually just be migrated from old to new addressing, when convenient and/or during a maintenance window.
04-27-2016 01:57 PM
The current C network - is it a single class C with no subnetting, that you intend to migrate to multi segment network (i.e. core + servers + clients + printer subnets)? How many switches does all of the current network reside on, and are you doing any network upgrades at the same time?
One mode if migration if you have the possibility and a few extra switches, is to allocate a new core infrastructure, and on it declare the old C network (s) as subnets hanging off one port of the new/reallocated core. Then you can move client switches to the new addressing one at a time. Servers are moved to the new core (or new server farm switch) one at a time, or during several evening/weekend migrations.
Eventually the old core and subnet is retired / reallocated or set up for redundancy with the new one.
This allows you to migrate slowly; or you can still do it in a weekend or two; but does allow you to "experience" any issues prior to a big bang.
Internet connection and WAN connections can proceed with the above; or even stay with the old C address if you don't have to give it up.
Caveats:
1. Printers - they might be more work than you think. In client subnet, or a dedicated printer one?
2. Windows servers, Active directory, and DNS. Sometimes there's a replication time involved.
3. Internet and PAT - don't forget it ! Firewall rules may need extensive overhaul.
4. Licensing, if any applications are tied to IP addresses.
5. Make sure to have access to all the little oddball devices you have out there - cameras, power monitoring, modems, security systems, network management, PBX, the president's printer...
04-28-2016 06:54 PM
pww
Current network is subnetted and a dozen or so switches. Definitely a lot of careful planning in the works and thanks for the caveats. Doubt this can be done in a weekend or two, and there are network upgrades also happening.
Don't have all the answers yet, but the real planning starts next week. Watch this space and I'll try to post any progress or further development.
Al
04-28-2016 06:59 PM
Joseph,
DHCP will work on sub interfaces as well and accommodates attached VLANS nicely.
I like your point regarding secondary addressing on hosts, hadn't thought of that... only secondary addressing on routers.
Watch this space and feel free to post lessons learned here.
Al
04-29-2016 04:33 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
DHCP will work on sub interfaces as well and accommodates attached VLANS nicely.
True, if you have a router hosting the gateways and not a L3 switch.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide