License Migration feature is not available for IP 500

[trinetintl]

I am experiencing the message in the Subject when running the migration tool from R11 manager on an IPO 500 V1 running 9.0, never seen this before, any ideas what is going on or how to make it work? I have experimented with the R10 migration tool even on 406 R5.0 and the tool runs, I get a blank "invalid XML" file as expected but the tool runs, it has always run for me in the past except for today.


RE

http://www.trinet-intl.com

APSS, AIPS

 

[Westi]

It only works on V2 chassis

with the V1's you have to take the config and get Avaya or your distributor to do the rest.

I am not involved in the ordering process but it is a nightmare apparently for our purchaser.

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

 

[trinetintl]

Westi,

I kind of figure that was the problem, what confused me and the reason I posted this question is that I have actually run the R10 migration tool on an old R5.0 installation, just for kicks, as a test, that site has a mix of 406 and 500 V1 controller units and the migration tool never popped up this message, the tool actually pulled in an XML file from both boxes but it was blank and a small message said that the XML was invalid. When I ran the test I was not expecting any happy surprises since the R10 offer definition clearly states that the migration tools is supposed to work on 6.0+ but the message I got today should have popped up back then and it didn't maybe it is an R10/R11 difference/bug. I was actually going to load up the licenses on a brand new V2 controller running 9.1 but I ran out of time today, I want to see if the migration tool pulls in the XML even if the licenses are invalid, will try this experiment tomorrow and update this post. If I cannot pull the XML in I will definitely touch base with my distributor tomorrow, I was unaware that they could help. Thanks..!



RE

http://www.trinet-intl.com

APSS, AIPS

 

[trinetintl]

Tried everything I could think about and every single XML I tried on A1S comes up as basic mode, the only thing I have not changed is the migration tool, I am still using R11 instead of R10. A1s ignores all the licenses I am trying to upgrade. Following you advice I contacted my distributor but so far they told me that I should be able to pull a valid XML, not sure how, anybody knows how? Right now I just need to have something to quote!

RE

http://www.trinet-intl.com

APSS, AIPS

 

[joe2938]

As stated the box needs to be a v2 version and manager has to be at least version 10.

 

[trinetintl]

joe2938, the box is a brand new V2 that was downgraded from R11 to R9.1 and manager is R11, any ideas why A1S is not pulling up the licenses from the XML file?

RE

http://www.trinet-intl.com

APSS, AIPS

 

[IPGuru]

Just send the original CFG file to your distributor & let them do the rest, it is what you pay them for


Do things on the cheap & it will cost you dear

 

[trinetintl]

IPGuru, my distributor's sales guys was not familiar with the upgrade process for such an old system and was resisting my request but he contacted his tech support team and they requested the CFG file, we are good to go. I put together a proposal on my own based on my experience with other XML files I have run and the A1S output, it is going to be nice to see how close I was.

RE

http://www.trinet-intl.com

APSS, AIPS

 

[trinetintl]

My distributor emailed me a AUS BOM quote that doesn't make any sense to me because it includes an R11 Essential's License Upgrade however how do I obtain the upgrade license before I actually upgrade the system? I don't get it! In a previous post Intrigrant said "We take a new IP500v2 from the shelf, add the required hardware as offered for the new situation, bring it to 9.1 and upload the old config and create the XML file." I did exactly that and the XML file came in Muppet mode like I posted here before, I assume because all the licenses are tagged as "eINVALID" in the XML file. I am wondering if the only step I am missing, maybe it is an obvious one and nobody is pointing it out, is that I actually need to swap the licenses to the new SD card to where once I merge the config on the IPO500 V2 R9.1 the licenses will now show as valid and I will be able to generate the XML file even if the system does NOT have a valid Essential Edition License? Or do I need to follow ATAC's suggestion and purchase the R9.1 Essential Edition in order to complete the system and to allow me to properly create the XML file on a valid and fully functional and licensed controller?


RE

http://www.trinet-intl.com

APSS, AIPS

 

[AACon]

trinetintl, we had a similar issue with the basic edition crap. There is a bug somewhere. It took a MONTH to get licenses migrated. We normally do not have this issue, but it seems when migrating from V1 licenses lately it's been a pain in the arse. Avaya finally gave in and gave us what we needed, but not without a bunch of bullshit.

-Austin
I used to be an ACE. Now I'm just an Arse.

 

[trinetintl]

AACon, what you are saying is that Avaya initially was having issues selling the R11 Upgrade Licenses because you only had a cfg files instead of a valid XML migration file and in the end they release the order for you guys without the XML migration file? Was this process completed through distribution or did you have to deal with Avaya directly?

RE

http://www.trinet-intl.com

APSS, AIPS

 

[TouchToneTommy]

http://files.engineering.com/downlo...R10_Migration_Procedure_Doc_174994_Oct_28.pdf

Migrating IP Office to R10 in SMB and IP Office in Midmarket

3.2. IP500 V1 to IP500 V2 and Upgrade to R10
Licenses should be swapped within the same release from the feature key card to a new blank SD card.
Partial license swaps are not supported; swaps must be 1:1. Following the license swap, customer would
upgrade to R10 per the existing procedures.
Customers migrating to the latest release will be required to have an IP500 V2 control unit. IP500 base
cards, trunk cards and expansion modules are supported with IP500 V2 control unit and may migrate to
the V2 control unit. Licenses will require a dongle swap to move from the IP500 key card to the IP500 V2
SD card.

So, YES, you need to build out your V2 control unit, do the license swap onto the SD card, add any licenses required by the new hardware (such as an Essential license, since the V1 never had one), then you will be able to generate the xml file and continue with the R10/R11 upgrade

 

[trinetintl]

TouchToneTommy, the problem is the essential license. ATAC said that you must have an ADI 9.1 Essentials license to allow you to run the migration tool and obtain the XML file and that makes sense, problem is that distribution no longer sells the R9.1 Essential license or at least that's what I was told. My question is very simple, if you swap the licenses to a new SD card and you put it a V2 on R9.1 WITHOUT an Essential License will you be able to obtain a valid XML file? A V2 without an essential license is a Muppet system. Now if you deploy the R10 or R11 Essential to the V2 you will now you have a mix environment with ADI and PLDS licenses and to the best of my knowledge, the ADI license will show up as obsolete or invalid or am I wrong?

By the way, my distributor just told me that the process to upgrade V1 or 406 controller is different than V2 and an XML migration file is NOT required.

RE

http://www.trinet-intl.com

APSS, AIPS

 

[IPGuru]

As suggested on numerous occasions
simply send the distributor the CFG file & ask them to sort, it i their job
if not find another distributor who wants the business

IPGuru, my distributor's sales guys was not familiar with the upgrade process for such an old system and was resisting my request

seems he does not want the business,tell him you are going to locate a decent distributor who does. they ave already cost you more money on this request through waisted time than you are going to make

Do things on the cheap & it will cost you dear

 

[trinetintl]

IPGuru, I am following your advice "Do things on the cheap & it will cost your dearly" this is the reason I have been asking so many questions is because I want to run my own design either to compare it to what I receive from the distributor or to submit it on my own and I want to be as close to 100% correct as possible, plus I simply want to know what I am doing, I want to learn! In the end, I am the one responsible for the design because if the distributor makes a mistake and I am unable to catch it I am the one stuck with the potentially costly correction and either a very angry customer or a lost sale. The distributor is not running the config through a special software that spits a BOM file, they are simply loading the configuration in manager, going in to analyze it, counting the licenses checking the hardware and putting everything in an Excel sheet template that Avaya has designed and provided for this purpose, it is not at all automated, it is prone to typos, miss readings, distractions, etc.
Additionally, the distributor is telling me that there is a 24 hour turn around on their design, in my book, that's too long to wait specially if I have to submit corrections or request additional hardware to be added to the quote or to submit questions because I do not find the design to my satisfaction. So far, I submitted my cfg file Thursday of last week and as of today I have received 2 quotes, the first one was missing literately everything, hardware and license wise, I was actually surprised it came back with the V2 controller box and an SD card, the second one they swing to the opposite side and they included external modules that do not need to be replaced because they are compatible with R11 and they still missed a bunch of additional licenses that the system will require, I am still waiting for the 3rd quote to see how that one looks.
To my surprise, I was also told that Avaya is advising that BPs do not design these type of upgrades on our own because we do not have the expertise to do them and we will probably mess up, we have to rely on the "expertise" of the distributor(s), yes, seriously!

RE

http://www.trinet-intl.com

APSS, AIPS

 

[TouchToneTommy]

if you swap the licenses to a new SD card and you put it a V2 on R9.1 WITHOUT an Essential License will you be able to obtain a valid XML file? A V2 without an essential license is a Muppet system.

You have to have a "live" configuration opened to run the migration tool. This means that you have to do the initial login to your new system, so you're going to put it in Standard mode, it won't be left in Muppet mode. After it reboots, add the ADI licenses. It won't have the Essential license, and thus the telephony features will be disabled, but YES, you will then be able to run the migration tool to generate a valid .xml file, and finish the process to migrate to PLDS and add a brand new R11 Essential license.

 

[trinetintl]

TouchToneTommy, thank you very much..!! I was just looking for somebody that had experienced the process on a real upgrade to tell me if the answer was yes or no. I do not have a set of old 5.0 licenses I can just swap otherwise I would have done it already to test. What I do not understand is why ATAC said no when I asked them the same exact question.

RE

http://www.trinet-intl.com

APSS, AIPS

 

[jamie77]

Put your licenses ontoan IP500v2 running R7.0. This will work as Essential only came out at R8.0+. This is exactly how we do these and it has always worked.

If the system isn't configured right and would actually work, you will have things missing. The .xml is an extraction of what the system can actually do. This includes virtual licenses and why you have to be logged in to get the .xml.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer