4.2 Sofware on a 3300 with an E2T 1

[paulrdavey]

Dont Do it. As of this morning i understand Mitel has this back in Engineering. Ive upgraded 5-6 system with 4.2 and all went fine until last night. this system has an E2T and would not come up. Kept rebooting. So i rolled it back to partition 4 and ... now i find this out.. Hope you folks dont have the Day i had. Good Luck all!

 

[kwbMitel]

Thanks for sharing.

Gave you a star for your efforts.

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

 

[paulrdavey]

Thanks Ive been using your suggestions for quite some time glad to be able to help.

 

[nytalkin]

I had one this morning, found if I changed bootline on E2T it worked fine. Sataic address from DHCP failed.

NO GOOD DEED GOES UNPUNISHED!

 

[mitelchi]

Thanks for your sharing.
Do you mean that there is a problem on Mxe Expanded with MCD4.2?

Kelvin

 

[paulrdavey]

What it seems now is certain Hardware versions of the E2t might work if you do a upgradebootrom all but I would be real careful upgrading until you hear from your distributor that this software is good with the known issues. by the way we had RA.5 for the PCB Assembly and Rev level for our E2T

 

[kwbMitel]

Problems are not apparently universal. I have heard from 1 source that has upgraded a MXe expanded to 4.2 without issues.

Best be safe and check with distributor (or Mitel) if you have access.

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

 

[Supernova99]

You should always use upgradebootrom all after a software upgrade if your system has an E2T.
The software upgrade only upgrades the firmware of the RTC and DSP modules, the E2T is a manual upgrade.

Share what you know - Learn what you don't

 

[mitelmania]

Would be worth checking the bootrom of your E2T BEFORE attempting the upgrade as there is no guarantee the this has been done properly on the last upgrade, I maintain a lot of LX controllers that had not had the E2T upgraded when the previous maintainer had done the last lot of upgrades. Possibly the boot rom of this E2T that you had problems with was really old.

 

[Webmany]

We found that if we changed the IP address from default, then the E2T would not boot using dhcp. If we put in a static address then it would be ok.

This was on 2 new MXe 3 servers. Non expanded.

 

[veenstrahiem]

I have upgraded an MXe Controller last friday from 8.0UR5 to mcd 4.2 and only on the E2T did I get a message after giving the upgradebootrom all command that the upgrade bootrom from the E2T failed.
The E2T has a static ip-adres and it is working fine.

 

[Lundah]

Anyone know if this problem appears on the older hardware as well, like the 512MB LX boxes? I have a large (590 nodes) network, with about 100 of these, that will eventually be upgraded, I'm still on release 9.0UR3 for now.