I'm inheriting an Avaya CM 6 with a duplicate server, a messaging server, and 5 G450's. I have been tasked with migrating to a different network but am not sure as to where I need to start. I figured I will need about 12 ip addresses for the different platforms and gateways but which order do I do this in? Does Avaya have a worksheet or a cutover guide?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Network migration
- Thread starter jlroeder
- Start date
Not really! You'd be best to get a partner in to manage that procedure.
Are all your gateways in the same place and going to cut all at once? Are some at different locations and going to manage to move to new IPs before the core site does and have the added complexity of making the system juggle old and new IP addressing for your connectivity?
Depending on what platform your CM runs on and with which mix of things, changing IP addresses may or may not be possible without a reinstall and restoring a backup.
Maybe a partner can nudge you towards VMWare, stand up the VMs, restore backups, and you can cut them over on to the new voice network and have both instances of your 6.3 stuff up at the same time if you want to roll back.
Are all your gateways in the same place and going to cut all at once? Are some at different locations and going to manage to move to new IPs before the core site does and have the added complexity of making the system juggle old and new IP addressing for your connectivity?
Depending on what platform your CM runs on and with which mix of things, changing IP addresses may or may not be possible without a reinstall and restoring a backup.
Maybe a partner can nudge you towards VMWare, stand up the VMs, restore backups, and you can cut them over on to the new voice network and have both instances of your 6.3 stuff up at the same time if you want to roll back.
DAVIDPAYNE
IS-IT--Management
Do you have any LSP? Are the CM running on System Platform? Do you have a System and Session Manager, and if so are they running on System Platform?
I just went through this with a much larger system, and it is a pain in the !#$.
I just went through this with a much larger system, and it is a pain in the !#$.
- Thread starter
- #4
It can be quite a pain.
Check your RAID batteries are still good. Check for no hardware alarms. Check for how everything is licensed and against what WebLM.
What about your network regions? How might this impact them at all? Lots of call routing is based on what IP you're coming from to determine where you are.
Are any other IPs changing in your environment beyond just your core Avaya stuff?
For the most part, it really is as easy as blanking out the controller list in the gateways and changing the PBX IPs, but without the whole picture there'd be no safe way to get you set up to work without a net on something like that.
You'd want to make sure IP forwarding is on on all your System Platforms and validate connectivity to your G450s on the services port so you can reach them all locally. Validate access, know when the changes are being made and know your VLANs and networking inside out when it isn't working the LAN guy is telling you it's your problem, etc.
If you can't test that out A to Z in a lab first, I don't suggest trying with a production system.
Check your RAID batteries are still good. Check for no hardware alarms. Check for how everything is licensed and against what WebLM.
What about your network regions? How might this impact them at all? Lots of call routing is based on what IP you're coming from to determine where you are.
Are any other IPs changing in your environment beyond just your core Avaya stuff?
For the most part, it really is as easy as blanking out the controller list in the gateways and changing the PBX IPs, but without the whole picture there'd be no safe way to get you set up to work without a net on something like that.
You'd want to make sure IP forwarding is on on all your System Platforms and validate connectivity to your G450s on the services port so you can reach them all locally. Validate access, know when the changes are being made and know your VLANs and networking inside out when it isn't working the LAN guy is telling you it's your problem, etc.
If you can't test that out A to Z in a lab first, I don't suggest trying with a production system.
DAVIDPAYNE
IS-IT--Management
I agree with Kyle55, if you have a choice, I dont recommend this.
My org. was purchased by another, and they did not give us a choice, we had to re-ip everything. And we have a large voice platform, and other server.
That project has being going on for almost a year. Voice is finial complete, unless we find something else that no one knew anything about, and there have been a few.
More then likly your CM are running on top of system platform. If they are, then this will be one of you bigger pain points. Make good backup before you try, and even then, you may crash them. We ended up having to rebuld ours form scatch. And I hope you are not a 24hr/365 shop. If you are, get a BP to help. List out your node-names and check every IP there to make sure you know what it is, and the new IP.
My org. was purchased by another, and they did not give us a choice, we had to re-ip everything. And we have a large voice platform, and other server.
That project has being going on for almost a year. Voice is finial complete, unless we find something else that no one knew anything about, and there have been a few.
More then likly your CM are running on top of system platform. If they are, then this will be one of you bigger pain points. Make good backup before you try, and even then, you may crash them. We ended up having to rebuld ours form scatch. And I hope you are not a 24hr/365 shop. If you are, get a BP to help. List out your node-names and check every IP there to make sure you know what it is, and the new IP.
- Thread starter
- #7
Thanks guys. From what I can tell only one network region is set up and all the equipment is located on site. I'm able to get into CM on both servers and get all the IP's associated, but I was never given the info for system platform or the info to putty into the gateways. This project is going to be a challenge.
if you can cli into CM, you can "ssh cust@dom0.vsp" and @cdom.vsp. There's default user names and passwords if they were never changed. There's also a little LDAP in System Platform, so user accounts are sync'd across all VMs for management. That's not to say all your CM accounts are in there, but at the least there should be a cust and admin account in dom0 and CDOM that are the same.
If you can manage to pull that off from each CM and your voicemail server you can at least validate all software versions, hardware and stuff like that.
If you can manage to pull that off from each CM and your voicemail server you can at least validate all software versions, hardware and stuff like that.
- Status
Similar threads
- Question
- Locked
- Question