Upgrade from 8.0.5.12 to MCD 5.0 SP2 PR2 1

[floppy1]

Hello and thanks in advance for any assistance.

3300 CXi on 7.7.7.77 not clustered, resilient or IP networked does have Teleworker on separate server not on APC. DHCP provided by customer server not the 3300.

SWA is in place I do have the 512 RAM module and a new 80 GIG HD.

Not sure why the HD was ordered so may or may not use it as it will bring additional complications and lengthen an already lengthy process but would like to install it given time.

Will be upgrading the system to MCD 5.0 and having trolled through the various release notes and postings here I am still not entirely clear. Please advise if below is not the correct procedure and or any tips.

I intend to use the SI tool although given your replies may go with manual install to speed up the process.

I believe I will need to first upgrade to MCD 4.0 SP4 and that this requires a new AMC password. Perform the migration to SDS then upgrade to MCD 5.0 SP2 PR2 requires another new AMC password.

My assumption is that as we have only just got SWA in place that I will need to upgrade to MCD 4.0 do the SDS migration and on to 5.0 and all of this while updating AMC as I go to ensure that the licencing gets converted.

So where do the new AMC Passwords come into play and do I need one or two new AMC passwords. I thought that there were no longer options for an AMC password on 5.0

The unclear bit is do I have to go to 9.0 > 4.0 > 5.0 or can I go from 8 to 4.0 convert to SDS then to 5.0 for some reason something tells me I have to go to 9.0 first

 

[kwbMitel]

The software installer tool takes care of the password so don't worry about that.

Yes you need to go 8.0 > 4.0SP4 > 5.0

The new hard drive is prudent as the old one is probably near EOL.

Backup
Upgrade > rel4.0 (This step may require a full install, read release notes)
Backup
Migrate > SDS Mode
Backup
Upgrade > rel 5.0

I would not use the manual process to save time. The SI tool is quick enough and takes care of all of the steps.


**********************************************
What's most important is that you realise ... There is no spoon.

 

[floppy1]

Thanks kwb for the quick response

I will take your advice and use the SI tool. It’s a relief to know there is no need to go to 9.0 first. As to the HD I will use it because as you say the one in the controller must be knocking on a bit.

What approach would you use to install the new HD

I believe it will come with 4.1 on it. I thought I would upgrade the current HD to 4.0 do the migration to SDS then take a backup install the new HD and restore before proceeding.

 

[kwbMitel]

With the new drive having 4.1

More detailed list

Backup 8.0
Export IP Telephones All (Shows which phones are in service)
Check Alarms - Clear Issues
Maint Command - "Alarm" - Observe alarm thresholds (Thresholds are reset on upgrades)
Upgrade/(full install?) > 4.0SP4
Export/compare IP telephones all (Make sure all phones that were in service are in service again)
Check Alarms - Clear Issues
Alarm Thesholds - Do not reset at this time (if reset necessary)
Backup 4.0SP4
Migrate DB > SDS
Backup SDS DB
Install New Hard Drive
Full Install with restore from previous backup > 5.0
Export/compare IP telephones all (Make sure all phones that were in service are in service again)
Check Alarms - Clear Issues
Alarm Thesholds - Reset is required
Backup 5.0



**********************************************
What's most important is that you realise ... There is no spoon.

 

[floppy1]

Thanks again kwb

You have been very helpful and detailed in your responses.

I feel I should award a star but this must have been a mere titbit of knowledge from what is clearly quite a large bank of Mitel knowledge so a star would probably be readily dismissed by yourself as a trivial compliment.

The alarm thresholds will be ok but I will note as I go along. I wonder why the IP Phones need scrutiny in the way you describe

 

[caknfd]

Just another thought. I would back up the system, replace the drive and proceed as discussed. This way if the upgrade was to go south on you for whatever reason you can just reinstall the original drive and be back in service.

Craig

 

[kwbMitel]

@caknfd - Realistically, with a spare drive and backup in hand, going back should not be necessary.

For the IP sets, you want to make sure all of the sets boot up on their new load before proceeding. There can be issues if they do not. So you make sure every phone that was up, is up, before moving on. If there are phones that for some reason or another are not activated they should be. It is best if all phones are upgraded sequentially along with the system. I've heard of issues where Mitel needed to get involved to repair the issue. I've never had an issue because I follow the process I've laid out for you.

For the backups, don't skip any. Should anything go wrong in an upgrade you want to be able to restore to the most recent stable state. I forgot to get one after the Migration once and paid dearly (4 extra hours)

Re: Stars, I've gotten stars for one word answers and not gotten stars for hours and hours of support. It's your choice. I appreciate them when I get them and I don't hold grudges when I do not.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[wireman50]

One to watch is the way that 5.0 treats Vlans set in the DHCP (i.e. the phones dont boot because there is a Vlan setting in there that is not used) So do as KWBMitel says and make sure the phones boot after every step.

 

[LoopyLou]

Agree with wireman. There are some changes in set firmware along the way and I think it would pay to make sure the sets boot so they get the firmware updates at each step. Quick read through everyones posts and I don't see the "upgrade bootrom all" mentioned. You should make sure you do that step to avoid issues with the E2T. The tech handbook has a procedure you can walk through for upgrades. Personally I would grab a copy of the release notes when you download the software and read through it. It has all the steps you need to do and many of the gotchas. Finally I would install at least SP2 so you get support for the new 53xxe sets.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[kwbMitel]

@LoopyLou re:upgradebootrom

It has been my experience that the command is only really required on MXe's with Expansion CPU's.

Anytime I've tried the command on a CX (other than during install), there have been no upgrades required.

Has your experience been otherwise?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

Missed the CX part but no experience otherwise. Just do it as force of habit but of course the CX will not have the extra E2T card.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[floppy1]

Thank you all for your help. I will follow your suggestions to the letter. I always do the upgradebootromall " force of habbit

 

[DoubleUT]

One remark I've not seen is the fact that you need to look at the Help file while on 4.0. Before the Migrate of the database please go into the help file and look at the migrate steps. Follow them and it might save you some hassle in the future.

 

[kwbMitel]

Actually, there is a step by step form checklist in 4.0 SP4

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

Well spotted.


I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[floppy1]

Hi all

The main reason we are upgrading this customer is due to major issues that appear to be software or database related “ I think “

We are getting the logs at the bottom of this post coming in thick and fast. Mitel will not talk to us about these until we get the customer on SWA and the latest and greatest. Looks like MCD 6 is now out but I think I will still upgrade this one to last MCD 5 release.

Symptoms are when a call is placed to a ring group “ 4 digit “or ext “ 3 digit “the caller hears ring back but the set or ring group that is called does not ring this is apparent on internal and incoming calls. Can’t see any digit conflicts mostly 5212 IP sets in the system.

After a system reset all works ok for a while and the symptoms soon return. Customer is resetting several times a day.

The customer reports that when calls fail internally the following characters appear in the call duration area of the display - - - This happens sometimes on the third digit dialled and sometimes on the fourth digit dialled. I have not yet been to site for various reasons to confirm this.

Could this be database corruption and I wonder if upgrading and then restoring the data base all the way through that we may still have issues. Any thoughts about this please.

Is it feasible to simply upgrade to 4.0 do the SDS conversion per documentation export all forms install the new HD do a fresh install of MCD 5.0 and import the forms or is this the same as a backup and restore. Am I missing something here ? will the exported forms import back to 5.0 ?

 

[LoopyLou]

Apparently not.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[floppy1]

Hi all



Thanks for all the guidance. The upgrade went well to 4.0 migrated to SDS made backups but when installing the new HD used the SI tool for a fresh install.



Noted that it seemed to freeze on creating RAM Disk 458mg. I waited 30min and SI tool did not seem to move on.



In the end I just did it manually from my laptop then licensed and restored the database all ok. No problems with IP sets booting up throughout.