MiVB 9 software installation

[Tinos]

Hi all.
Please advise on how to install the above on MxeIII.
I get an error file not found when I use vxworks Boot_Install with the downloaded software in an FTP server.
Thank you.

 

[Tinos]

RAM is 512Mb and I understand that 1Gb is required. HDD is 80Gb.
At this point I am interested in rolling back to MCD8 but the boot process doen't reach the point where I stop the process and change parameters. Basically my system is in a brick state.
Any suggestions?

 

[jpruder]

I saw you said you got new ram. Why isn't it now 1GB?

 

[Tinos]

It is 512 now. The 1Gb was for testing and it did not change anything.

 

[nytalkin]

You need to get the documentation. If you are not a dealer, find one. You need a gig of ram to start.

I suppose you're entitled to your opinion, I'm just not going to suppose very hard.

 

[Tinos]

I have a 1 gig ram on a new 3300 that I managed to migrate to MiVB9 with no challenges.
It is the same 1 gig ram that I have tested with on the 33300 that is failing to boot up either MiVB 8 or 9.
I'm now interested in rolling back this particular 3300 to MiVB8 but the boot process is not allowing with the 1 gig ram installed.
The upgrade failure bricked the 3300. I'm asking for advice on how to rescue the 3300 other than ram as ram is there.

 

[Tinos]

Hi all.

Has anyone managed to reverse migrate a 3300 that had migrated halfway through?
When I halt the U-Boot and enter cmd run upd_bootrom_fromdisk I get the below response:

=> run upd_bootrom_fromdisk
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
bootrom.bin download failed
=>
I am at loss at what to do next. Please assist.

 

[DoubleUT]

Mitel has a video on the knowledge base on how to migrate a system and how to reverse migrate a system.

 

[Tinos]

Hi all.

Please note that I have done 6 successful migrations so far. It is not a matter of not knowing the migration procedure.
My 3300 did not fully migrate and aborted midway because at the time it had 512 RAM.
Now the 3300 is on 1Gb and longer has VxWorks. The migration tool wont connect. MiVB9 does not boot.
Reverse migration show the previously mentioned error.
Is there a way to install MiVB9 from the terminal (the equivalent of Boot_Install)as the migration tool wont work at this point?

 

[nytalkin]

What does the bootline look like right now?

I suppose you're entitled to your opinion, I'm just not going to suppose very hard.

 

[Tinos]

U-Boot 2015.10 (Aug 22 2018 - 11:28:13 -0400) mxeiii 1.0.1.3

Reset Status:

CPU: e300c1, MPC8360EA, Rev: 2.1 at 528 MHz, CSB: 264 MHz
Board: Mitel MXe-III, U-Boot 2015.10 (Aug 22 2018 - 11:28:13 -0400) mxeiii 1.0.1.3
Refresh UBOOTROM

Reset Cause (0x83 - POWER_ON_RESET)

Watchdog enabled
I2C: ready
DRAM:

Configuring DDR2 SODIMM using SPD drivers
DDR
Starting POST...

SDRAM CS1 Data Bit Walk 1................... PASSED
SDRAM CS1 Data Bit Walk 0................... PASSED
SDRAM CS2 Data Bit Walk 1................... PASSED
SDRAM CS2 Data Bit Walk 0................... PASSED
SDRAM CS1 Address Walk 1................... PASSED
SDRAM CS1 Address Walk 0................... PASSED
SDRAM CS2 Address Walk 1................... PASSED
SDRAM CS2 Address Walk 0................... PASSED
SDRAM CS1 March Test........................ PASSED
SDRAM CS2 March Test........................ PASSED

1 GiB (DDR2, 64-bit, ECC off, 264 MHz)
Flash: 4 MiB
PCI: Bus Dev VenId DevId Class Int
PCI:
00:16.0 - 1095:3512 - Mass storage controller
In: serial
Out: serial
Err: serial
Found valid environment in flash.
Slot id 0

do_mitel_stuff_inram Tests...
Sil5923Read: call to smbusSendByte() returned ERROR
SATA RAID Controller Not Present.
Net: UEC0

do_mitel_ethstuff_inram Tests...

do_mitel_programfpga Tests...
Decompressing FPGA image...615412 bytes decompressed successfully

Programming the FPGA image...OK

FPGA version 0002:6123 loaded


E2T card not installed.

Press <SPACE> key 3 times within 7 seconds to stop autoboot

Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>
Timeout waiting for command
Resetting the board.


U-Boot 2015.10 (Aug 22 2018 - 11:28:13 -0400) mxeiii 1.0.1.3

Reset Status:

CPU: e300c1, MPC8360EA, Rev: 2.1 at 528 MHz, CSB: 264 MHz
Board: Mitel MXe-III, U-Boot 2015.10 (Aug 22 2018 - 11:28:13 -0400) mxeiii 1.0.1.3
Refresh UBOOTROM

Reset Cause (0x83 - POWER_ON_RESET)

Watchdog enabled
I2C: ready
DRAM:

Configuring DDR2 SODIMM using SPD drivers
DDR 1 GiB (DDR2, 64-bit, ECC off, 264 MHz)
Flash: 4 MiB
PCI: Bus Dev VenId DevId Class Int
PCI:
00:16.0 - 1095:3512 - Mass storage controller
In: serial
Out: serial
Err: serial
Found valid environment in flash.
Slot id 0

do_mitel_stuff_inram Tests...
Sil5923Read: call to smbusSendByte() returned ERROR
SATA RAID Controller Not Present.
Net: UEC0

do_mitel_ethstuff_inram Tests...

do_mitel_programfpga Tests...
FPGA version 0002:6123 loaded


E2T card not installed.

Press <SPACE> key 3 times within 7 seconds to stop autoboot

 

[AH64Armament]

First off - I've been certified on MiVB 9.x since it came out. Each time I had an opportunity to upgrade a system to it, it fell thru.
Well finally! I have done my first migration. The system at the customer site was an MXe (GEN2) running MCD 6.0. I took their most recent backup and restored it to their new controller - an MXe-III running version 8.x.

I cleaned up the database today - removed the PER node and DSU Node. Changed the 5005 phones (Trusted extensions) to 5304.

And FINALLY going through the Migration tool (9.0.2.2) and upgrading the site to MiVB 9.0.2.16.

First thoughts - wow, they're still using Java - WTH Mitel???

Run through the tool to locate the unzipped software - The documentation isn't clear on what directory this needs to point to.. and failed the first several times because I was going into the folder 9.0.2.16 - where I should be pointing to the folder that contains the folder 9.0.2.16. The crappy interface is quirky and each time reverts back to the parent folder of the Migration tool.

Anyhow, I'm past that and working on the upgrade. I was in panic mode about 45 minutes ago because there's nothing telling me that it's doing anything - the View Log seemed to be stuck "Transferring file mivb-image-mxciii.tar.gz" Wow, that file is big. It hovered on that file for nearly an hour before it finally jumped through a dozen or so additional entries in the log.

Now it's just past Phase 4 - unpacking e2tfs into rootfs2/e2tfs.... We're at 1:40 total time as of right now.


I have to say - this upgrade is just as or more time intensive than SX2000 LW26 tape drive upgrades.

Bottom line - plan accordingly - plan for this upgrade to take several hours.