[cisco-voip] IP address migration

[kevin knowlen]

Tim,

Unfortunately, we are stuck in an odd situaiton where the subnet that
CM is on needs to be changed.  The subnet will no longer belong to us.
 More consideration should have been put into this at the start, so we
wouldn't have to make such a frightening change.  Our operation is
24hrs a day 7 days a week.  We are going to do this at hours with the
lowest call density.  If we do this right, I think we can pull it off
with just a couple of phone resets.  The only caveat is that we have a
small number of phones that are statically configured a number remote
sites.  They will be notified in advance of the changes.

Here's a couple of things I forgot about in my previous message
-Enterprise Parameters
-Change IP's in CM that point to Gateways

Your thoughts are appreciated


On Fri, 10 Dec 2004 08:13:11 -0500, Tim Reimers
<tim.reimers at asheville.k12.nc.us> wrote:
> Since I regard changing the IP subnet of the phone system as a royal
> pain in the ....
> 
> I have to ask - are you running private addressing?
> If so, can you supernet the network? (change the subnet mask from
> 255.255.255.0 to 255.255.0.0, for example?)
> 
> Can you VLAN off some of the phones to a different network, leaving the
> CM devices and gateways on their own network?
> 
> We run a different VLAN and subnet for each of our sites here- a
> Catalyst 4006 supplies routing between subnets-
> 
> Consider adding VLANs and subnets for phones, not changing the CM setup
> around...
> That way, all you're changing is phone IPs, and not the difficult stuff
> of the CMs themselves...
> 
> I can probably help with this if you want more advice on specifics..
> (I'm a Cisco engineer, working for a school district)
> 
> tim
> 
> 
> 
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of kevin knowlen
> Sent: Thursday, December 09, 2004 5:09 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] IP address migration
> 
> All,
> 
> I must go through the painfull process of migrating the entire CM
> network to a new subnet.  Our network has grown bigger than we
> originally planned.  I've thought about this in detail on how to best
> transfer all the IPs and I'm not sure I've covered everything.  Anyone
> ever done this before?  Is there a guide or established procedure on
> how to do this?  Any caveats that I've missed?
> 
> Proposed Procedure
> -Create sub-interfaces on all Voice gateways for new ip addresses
> (routing is provided by core router/switch and the router guys have
> already added new subnet)
> -Ensure successful ping of new IP addresses on the voice gateways.
> -Ensure dial-peers point to the ip of the subscriber callmanager and
> will be selected first
> -Change IP address of Publisher
> -Change LMHOST file on the subscriber reflecting new publsher IP.
> -Change DHCP scope to reflect new subnet, gateway, and TFTP addresses
> -Change callmanager group to make publisher primary for phone
> registration
> -Test by resetting one IP Phone, ensure that it registers with
> Publisher, and place calls down each voice gateway (if success
> continue)
> -Reset all IP Phones, watch and ensure they register with Publisher
> -Contact distant end of intercluster trunks and have them add the new
> IP address of the subscriber and reset trunk when I change the IP
> -Change IP address of Subscriber to new IP
> -Change LMHOST file on publisher to reflect new subscriber IP
> -Change session target ip address of dial-peers that point calls to
> subscriber.
> 
> --
> Kevin
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 


-- 
1LT Knowlen, Kevin