Change tlan IP addresses co-res CS1000 3

[JonathanPPP]

I need to move the tlan addresses on our CS1000 to a new subnet, the elan addresses are all staying the same.

The CS1000 is on 7.5 and the sig server is co-res with the CS. As far as I can see there are two addresses allocated. One for the linux base and one for the sig server.
I can change the address for the Linux Base together with the subnet mask and gateway in UCM and when I do this the call server will reboot.
Then I can go to EM>System>IP Network>Nodes:servers, Media cards and choose the node to change the tlan address and subnet mask for the sig server.
Finally I can update the DNS entry for the sig server and the DHCP that gives out the sig server details.
Is that everything I need to do to to change the tlan addresses?

I also need to change the ip address of the clan interface on the callpilot. Do I just do this from the windows network applet in the control panel or is there another way of doing it?
Once I have changed that IP address is there anywhere in UCM I need to update apart from the IP address in the Elements?
Our call pilot is only being used for basic voicemail we don't have any desktop or fax integration in use.

So to summarise
1. Change IP, mask and gateway for Linux Base, server will reboot
2. Change IP and mask for the node in element manager
3. Update DNS and DHCP with new IP address
4. log in to callpilot as the windows administrator and change the clan address, mask and gateway
5. Change the callpilot ip address in the element list of UCM

Have I missed anything here?

 

[JonathanPPP]

Looks like I also need to run the configuration wizard in call pilot manager to update the clan address after I have changed it in Windows.

 

[Jeffnortel]

1. Change IP, mask and gateway for Linux Base, server will reboot
I would change via CLI not base manager. (Good luck! Id recommend reinstalling Linux OS.)

2. Change IP and mask for the node in element manager
Yes. You will also need to change all Media Gateway TLAN IP's from EM also.

3. Update DNS and DHCP with new IP address
Yes for DNS... DHCP for IP phones??? If so, YES. (Hopefully your using "Full DHCP")

4. log in to callpilot as the windows administrator and change the clan address, mask and gateway
Log on to CP server then CP Manager. Run "Configuration Wizard" to change IP.

5. Change the callpilot ip address in the element list of UCM
Yes

The Linux portion of this may be be troublesome, prepare to possibly reinstall from scratch!!!

"Be there, done that",
Jeff

 

[JonathanPPP]

thanks for your help Jeff, a few questions

1. Any particular reason for using cli rather than base manager to perform this task? Is the CLI method more reliable?

2. Thanks for the note about Media Gateway addresses, my Media Gateway has two addresses (one for the DSP daughtercard) are there likely to be any other IP addresses that I have forgotten about?

4. Does this mean I don't have to change the address in the windows control panel or should I do that first then run the configuration wizard?

thanks again for your help.

 

[janaya]

If your co-res is the primary security server, it doesn't like to be changed. But it doesn't say you can't. Just don't change the host and domain names, that requires a rebuild.

From linux prompt: baseparmasconfig is the command. You can do this now, just don't commit the changes, so you can see what you will need,
it will walk you through the IP information
ELAN/ELAN/DNS Servers/Time Settings, it will show you everything and then reboot. Network Identity in the Base Manager will do the same thing, but CLI just looks cleaner, in my opinion.

Media Gateway has:
1. ELAN address for card
2. TLAN address for card
3. TLAN address for each DSP Daughterboard.

don't change the Call Pilot IP addresss from the Network Connections window, do it from Config Wizard. You are on the right track with this.

Allot yourself time for a slew of testing. The Sig Server will be the biggest thing. You can test set/trunk registrations by LD 117: stat ss. Do this before and after to make sure you are the same before and after. If you have troubles, don't try too long to troubleshoot, just reload, it may be quicker. Jonathan has you moving the right direction. Just get an adequate maintenance window to do this.



Hope this helps.

 

[JonathanPPP]

Thanks guys
You'll be pleased to know everything went well all IPs successfully changed.

Some notes from the experience for anyone else coming to this thread later.

1. Rebooting the call server took a long time, on our CPMG128 card shutting down took almost 20 minutes and booting up took around 10. I had a console cable plugged into TTY1 so I could watch the progress and a couple of times I thought the system had given up and got stuck but it got there eventually. Also I couldn't access the UCM for around 5 minutes after the console showed the system as booted.

2. When you change the node address you have to resync the node and then restart the applications, the EM prompts you to do this so pay attention to the info on screen.

3. When you change the MG and DSP addresses the system says you have to manually restart the MG but mine restarted automatically.

4. The IP change on the call pilot is straight forward and fairly quick about 5-10 minutes including rebooting the card

The whole process took around 1h15' to get back to a point where IP phones could register against the system.

 

[357951258]

I performed the same mission
Here a tip for 2. Change IP and mask for the node in element manager
Delete the node files first otherwise the system will never accept a new Node IP .

 

[janaya]

the CPMG cards take the longest out of all the new processors. I'm not a fan, but I do understand the economics behind the card. The reason for the Manual start of the MGC card, is it sometimes doesn't take. Manually resetting just the MGC portion doesn't take long. If you begin to run into any TDM/IP issues, press the reset button on the card to start.

Good deal that all went well.