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!

Migrating Licenses to PLDS 3

Status
Not open for further replies.

ltxn

Technical User
Nov 23, 2007
81
BE
The ADI to PLDS license migration proces requires to upload a specific file in One Source. This file is obtained with an IP Office Manager R10.
The procedure doesn't state that the licenses on the IP Office should be valid when using the license migration tool.
In other words, you shouldn't upgrade the IP Office prior to downloading the file.

It kinda makes sense if you think about it. Though, this might save you some time, trying to migrate to PLDS.
We lost a few days opening service requests with Avaya, trying to find a solution.

IP Office Manager Help said:
[bbox]Migrating Licenses to PLDS[/bbox]
IP Office release 10 and higher supports only the Product Licensing and Delivery System (PLDS) to manage license files. If you are upgrading from a previous release, you must migrate all of your pre-R10 licenses (ADI, PLDS, mix of ADI/PLDS, virtual) to R10 PLDS licenses. The license migration tool extracts all the licensing information from an IP Office system and saves it to a file. This file can then be used prepare a software upgrade quote in the Avaya One Source Configurator in order to obtain the required new PLDS R10 licenses.

For Server Edition deployments, the License Migration tool collects licensing information from every node in the solution.
[ul]
[li]Note[/li]
[ul]
[li]You must use the release 10 or higher Manager client to generate the license inventory file.
You can install Manager before upgrading to release 10. See the procedure Installing Manager.[/li]
[li]License migration is supported on all IP Office modes, release 6.0 and higher.[/li]
[li]The license migration tool can only be used with an online configuration. The Tools > License Migration option is disabled for offline configurations.[/li]
[li]The license migration tool is not available on UCM and Application servers. When you run the license migration tool on a Server Edition server, the tool collects licensing information from every node in the solution.[/li]
[li]The generated file can be read but must not be edited. License migration will fail if the file has been edited.[/li]
[/ul]
[/ul]
Before you begin
Ensure all licenses are loaded on the system before performing the license migration. For Server Edition deployments, ensure all nodes are online in order to capture the current view of systems in the solution.
The IP Office configuration must be opened online. The License Migration tool is not available in offline mode.

Procedure[ol 1]
[li]Log in to Manager and select Tools > License Migration.
The Save As window opens.[/li]
[li]Select a location to save the file and enter a file name.[/li]
[li]Click Save.
The file is saved with a .zip extension.[/li]
[/ol]

Next Steps
Use the file to prepare a software upgrade quote in the Avaya One Source Configurator in order to obtain the required new PLDS R10 licenses. Once you have the PLDS license files, apply them to the system.
 
i lost a few days too to understand the whole migration process.

For people like us who need to pass through a distributor to order license, the final step after uploading the XML file to OneSource is to order upgrade license (which cost 0.01 $ per license) to our distri.

Do you find another way to get the PLDS license after creating the quote in OneSource ?
 
Thanks for the share. Any idea why this is? --> The License Migration tool is not available in offline mode.
 
You have to connect to a IPO first?
 
You have to connect as some Licenses are only there when online, eg Virtual Licenses. Makes sure you don't lose anything.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer
 
The License Migration tool creates a .zip file that has inside the .xml file which looks an awful lot like the .xml file for the IPOSS onboarding process.
I bet they just made it easier now by putting this option into Manager rather than make you log into the WebManager.



Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
has anyone done IP400 upgrade to R10 with existing licensing?

NTSDirect
 
IP400 hardware isn't supported on R10, or 9.1 :)

 
Yes. I know that part. I'm talking about migrating a VMP Lic or anything else from an IP400 Dongle to PLDS.

NTSDirect
 
But it would have to exist on a 500 to allow the migration file to be created, so it can't exist on a 400 dongle? :)

 
License migration is supported on all IP Office modes, release 6.0 and higher

Considering 406v2 and 412 is supported on 6.0 one would expect that One Source would give a complete upgrade quote with required hardware/licenses that need to be added, but that might be wishful thinking =)

I don't have any customer on 4xx hardware anymore so can't even test what would happen.

"Trying is the first step to failure..." - Homer
 
Shows how much attention I paid.... :)

 
I'll bet it doesn't work on an external/400 dongle, it means R6 on a 500 I'd wager :)

 
People are having enough trouble getting it to work on IP500s with 9.1 so I wouldn't bet against =)

"Trying is the first step to failure..." - Homer
 
Figured I would play devils advocate. I guess you would need to transfer via adi to new SD card. Mail back the old dongle. install with 9.1 then upgrade to 10.0 via IPOSS? This seems like the only logical solution. A lot of work if you ask me.

NTSDirect
 
Does anyone know the process to migrate R9.1 ADI licenses to PLDS and STAY at R9.1 ????

APSS-SME
ACIS-SME
ACSS-SME
CTP+
 
That's not officially supported. And I don't see a reason why you want to do that.
 
So I just ran the Migration Tool on an IP Office R9.1 and BOOM! As soon as the file was created, All my phones say Wrong Set Type. I even uninstalled the R10 Manager and reinstalled R9.1 and restored from a backup from a couple days ago, no dice ... guess I'm heading to the client site to default the IPO and start from scratch!!! Great job Avaya, great job ****EVIL GRIN


JASON MORRISON
THINK CONVERGED
ACSS (SME)
APSS (SME)
 
jasonmorrison said:
So I just ran the Migration Tool on an IP Office R9.1 and BOOM! As soon as the file was created, All my phones say Wrong Set Type. I even uninstalled the R10 Manager and reinstalled R9.1 and restored from a backup from a couple days ago, no dice ... guess I'm heading to the client site to default the IPO and start from scratch!!! Great job Avaya, great job ****EVIL GRIN

o_O Has anyone else experienced this!?

Been there, done that
 
No, I've ran that tool about 4 or 5 times remotely and have not had a problem.

The end is near!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top