Relocating of MAS 2.2 running Nu-Point in clustered environment 1

[Jakt99]

Hi All,

Grateful any input please

Current setup:
Standalone MAS 2.2 running Nu-Point located at site 1: Serving as a centralised voicemail facility for approx. 300 users for 5 clustered 3300
controllers (MCD6.3). One operating at site 1 and the remaining four remotely located at sites, 2 - 5.
- Connectivity between sites is via a private WAN. Each site operates a unique 24 bit IP sub-nets.
- Site 1 controller hosts Voicemail & HCIroute hunt groups for connectivity to Nu-Point line group 1.

Task:
Relocate MAS server from site 1 to site 5, as site 1 will be closing, keeping current voicemail functionality and mailbox data intact.
Site 1 controller will remain in service for a short time, to allow communications with skeleton staff closing the
office and will be removed from the cluster when the private WAN is decommissioned.

I was thinking the configuration steps to achieve are something like this:

3300 controllers
- Site 1: Delete Voicemail Hunt groups and trusted device connections
- Site 5: Add Voicemail Hunt groups and trusted device connections

- MAS while at site 1:
Backup configuration
- Nu-Point:
Delete existing line group 1 triplet member mapping to site 1 controller
Change default ICP from site 1 to site 5 controller
Add new line group 1 triplet member mapping to site 5 controller
Check connectivity with site 5 and test voicemail operation from all sites

- MAS:
Backup configuration
Shutdown server and relocate to site 5
** Install server and power up. From console change IP address and reboot
Check connectivity with site 5 and test voicemail operation from all sites


** My biggest concern is what will happen to MAS and Nu-Point configuration after the change of IP address

 

[Billz66]

Changing Ip address is not as bad as you might imagine.
Is it a physical server or vmware based?

I have done similar with hosted servers that were running on vmware onsite and were relocated to cloud.


Create backup before changing anything.
create screenshot of local networks.
run admin menu from console , configure my server , change base ip addresses/ subnet mask gateway and reboot
log into web and re-add in local networks (changing gateway removes all the old entries)
go to network element and change pabx address
activate nupoint when prompted
- check any area that had Ip address information for the pabx ( UCA blade, MBg etc and update)
- check AWC settings and update sip server IP address

You will need to do something with the old pilot number to ensure it routes to the correct MCD
- ARS will bedirecting it to the site that you are removing

if you create a new one within site 5 numbering plan , check all sites for fwds / reroutes etc
- also make sure the correct numebr is set on the network element on the MAS .

If I never did anything I'd never done before , I'd never do anything.....

 

[Jakt99]

Thanks Billz66,

Much appreciate feedback and detailing additional points and areas to consider.

MAS is built on a physical device, not operating in VMware environment and fortunately I only have to consider Nu-Point & MSL base.
MBG, UCA & AWC etc are not used and / or configured.