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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Would Like to know if anyone Upgraded their AYAYA Aura 6.x to 7.x Using existing Servers???? 1

Status
Not open for further replies.

jvc57

MIS
Jan 31, 2013
44
US
If anyone already went trough an upgrade on your Avaya Aura 6.x to 7.x using Existing Servers (Session/System Manager/CM )and was successful We would like to ask a few questions regarding the upgrade. If we can talk offline would be great.
Thanks for any info you can Provide! Joe
 
Have done it for a number of customers of ours. You basically backup the old servers - the application backups and if you can do old server image backup using backup softwares like Acronis that will be much better. If you don't make sure you have copy of all the 6.x softwares (SP,CM ISO template,SM Kickstart/software,SMGR ISO, etc.) in case you need to revert back. It is the revert back process that is the most critical one as you are going to wipe-out all the 6.x.

Process would be:
1. Backup all 6.x systems
2. Download softwares you need 6.x in you revert back and 7.x OVAs, patches, SM/SMGR data migration utility
3. Deploy 7.x systems VMs (AVP or VMware)
4. Run data migration
5. PLDS licensing rehost

Hope this helps.

jtc22
 
I upgraded System Manager from 6.3 to 7.1. At the time Avaya released bad migration data scripts. It took several days to actually diagnose the problem and fix it. In addition, Avaya requires system manager 7 to have a license. I performed the upgrade not realizing this "feature" and it took my business partner well over a month to resolve it. They ended up having to escalate to Avaya to figure out which codes they needed.
 
Here's some of the system and licensing changes from 6.3 to 7.1

1. Although it is $0 license SMGR 7.1 now is licensed so make sure this is in the quote file.
2. Utility Services 7.1 is also licensed. US 7.1 support for HTTP is disabled by default it needs to be manually enabled in CLI.
3. System Platform is discontinued and replaced by Avaya customized VMware hypervisor the AVP and this is also licensed.
4. CM FTP backup method is disabled. New and stronger Ciphers are aes128-ctr,aes192-ctr,aes256-ctr so your existing backup servers may not support this or Avaya have to go in there and enabled back the weak ciphers again with your permission.
5. System Manager root access is disabled.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top