IP500 4.2 to 8.1 upgrade

[Varlin]

Hi, I have an IP500 Control Unit running R4.2(11) and the following licenses...

IP500 Upgrade Standard to Professional
Mobility Features
Phone Manager
VMPro TTS (Generic)
Voicemail Pro (4 ports)

I'd like to upgrade this to R8.1 but I'm a little confused on the license requirements. I believe I need a IPO LIC UPG 8.1 upgrade license and an Essential edition license, is this correct and am I missing anything else that I need?

Any advice will be gratefully received.

 

[tlpeter]

You will need to get indeed the essential edition license and the upgrade license.
You also need to upgrade to 7.0 or 8.0 first for both the IPO and VMPro.
Only then you can upgrade to 8.1
If you do not do this in two steps then your config and callflow can go corrupt.
You standard to professional license and mobility licenses will go dormant as both are not used anymore.
All users can use mobile twinning from 8.0 and there is no professional anymore.
The Phonemanager pro licenses can used for office worker which allow you to use One-X Portal.
Phonemanager is not supported any more from the latest 8.1 releases and up.


BAZINGA!

I'm not insane, my mother had me tested!

 

[DanACS]

does the old VMPro licence not contain a virtual essential edition for systems upgraded anymore? I thought it did.



ACSS - SME
APSS - SME
APDS - Unified Communications
ACS - IP Telephony
ACA - IP Telephony

 

[tlpeter]

No, the chassis itself can contain a virtual essential edition license but if it breaks down then you loose it and you do not want to order licenses when a system is dead and needs to be replaced
Also when you replace it with an IP500v2 for example then you need to do a license swap and then order the essential edition license and only then you are back in the air.
Too much hassle for just a couple of hundred dollars.


BAZINGA!

I'm not insane, my mother had me tested!

 

[Varlin]

Thanks for the clarification, very much appreciated

 

[budbyrd]

You didn't mention the type of sets you have. If they are IP sets you will also need endpoint licenses. You might consider just getting a V2 and swapping the licenses.

Think twice, speak once~~!!~~

 

[Varlin]

Moving to a V2 might be something I'd consider doing at the same time, am I right in thinking the above statement on the licenses would still be true if I did the chassis at the same time as the software upgrade?

 

[tlpeter]

When you get a new IP500v2 then you do not need the upgrade license but you will need the essential edition license after getting the licenses swapped to the new dongle.
So do a swap and then order the essential edition license on the new dongle or order it on the old dongle and then do the swap.


BAZINGA!

I'm not insane, my mother had me tested!

 

[Varlin]

This upgrade has finally been bought off and therefore I'll be doing it in the next week or so, having never done an upgrade that involves swapping from an old chassis I was hoping someone might be kind enough to confirm my understanding of the process is correct, or advise if I have missed something (I have read the relvant installation guides and tech bulletins so hopefully I haven't missed something).

1. Take a backup of the existing IPO configuration
2. Upgrade the existing IP500 from R4.2 to R8.0
3. Re-create the new SD card as R8.0 and add the Essential edition license
4. Take a copy of the configuration from the old IP500 and import it on to the new IP500v2
5. Upgrade the IP500v2 to R9.0
6. Take a backup of Voicemail Pro (call flows etc)
7. Upgrade VMPro to R8.0
8. Upgrade VMPro to R9.0

The other question I have is, should the worst happen and I need to restore the old IP500 to R4.2 how is this done? I could do it on a V2 using a card reader but not sure how it works with the older chassis.

Many thanks in advance.

 

[hairlessupportmonkey]

just to reiterate Peters point - Upgrade to rel 7.0 first....

ACSS - SME
General Geek

 

[Gunnaro]

Don't forget the "new" endpoint policy:

You need one IP Endpoint for every Avaya IP phone/IP Dect handset.
You might get some or all you need for free, depending on what you have of licenses and cards in your current config.

VCM32/64 card = 12 IP Endpoints
VCM ch. license = 3 IP Endpoints

Example: You have 1x VCM32 card and 8 VCM ch licenses => 4 + (8 x 3) = 28 IP Endpoints.
If you have more phones than your licensed for, you will need to buy extra endpoint licenses (not so expensive).

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

 

[Varlin]

Thanks both,

The main reason I'm querying this is down to the Avaya technical centre advising a different approach, they suggested...

1) Format the new SD card for R9.0 and install the Essential edition license
2) Move all modules and cards across to the new Control Unit and upgrade to R9.0
3) Import the R4.2 configuration and make manual changes where necessary.

This sounds much simpler than going through the above process but I'm not sure how feasible it is in practice.

Also, is there any reason why you suggest R7.0 first, the tech bulletin says R8.0 and then to R9.0 - am I missing something?

 

[intrigrant]

I did this today, replaced a 412 at R4.1 to a IP500v2 R9.
These steps I have done:
I first recreated the SD card to R9, then I copied the R6.0 ip500v2.bin file in the SYSTEM folder of the SD Card.
Put the SD card in the chassis without any base cards and power up.
Send the 4.1 config offline to the IPO, it will ask you to upgrade from 412 ( or 406v2 ) to IP500, confirm and reboot IP500.
When running insert the new licenses and take a copy of the config ( just to be sure if afailure occur later on )
Turn off IP500v2 and copy the R8 ip500v2.bin file to the SYSTEM folder of the SD card.
Put the SD card in the chassis without any base cards and power up.
When running take a copy of the config.
Turn off IP500v2 and copy the R9 ip500v2.bin file to the SYSTEM folder of the SD card.
Put the SD card in the chassis without any base cards and power up.
When running take a copy of the config.
Power down, insert the base cards and power up again.
Check the config and adjust what needs to be changed, note that the trunks are OK, sometimes tha old trunks are not assigned to the added hardware so delete the old trunks and re-program the new ones.
In my case the old tri=unks were added correctly to the new hardware ( Dual PRI and a BRI8 ).
Make sure to correct all errors shown in Manager.
Done.
in my experience any other route leads to strange behaviour like CLI presentation on analog station fail intermittend, analog stations do not ring randomly, digital sets with wrongly formatted display or no display at all etc.etc.
I never do the R7 step because all docs say to upgrae to R8.0 and then to R9.
The R6 step is just to make sure that the alog stations work fine after the upgrade.
The whole process takes about 90 minutes but the advantage is that it is done well, if no other changes are necessery you can replace the old system with the new oe and leave the premise knowing you won't have to go back for strange problems.
Wow, typing this took nearly as long as the upgrade process...

 

[Varlin]

Thanks intrigrant, I appreciate you taking the time to write this.

If I'm underastanding it correctly it looks as though I can do this remotely up to the point where I need to install the base cards and transfer the existing licenses over.

Thanks again

 

[Varlin]

I'm failing miserably with this :-(

When trying to send the offline configuration to the IP500v2 I keep getting access denied!

I'm trying to use the Service User Name Administrator with the same password but no joy - have I missed something?

 

[Varlin]

Never mind, finally managed to guess a password that worked.
All ready to swap out tomorrow and insert the base cards.

 

[intrigrant]

Nice, I hate takeovers on Friday, if you encounter a problem you'll be home late and there is always something not going as expected or something the customer did not tell or they take advantage of the upgrade by telling you after the replacement they have some program changes to do ( usually a complete reprogramming of the system ).