3300 MXe III can not boot successfully

[nguyenhung]

Hi,

Now I install a new MiTel 3300 MXe III with a blank HDD and I have a problem in boot process (please kindly find my attachment). I did install “FileZilla Server” software and “MCDSoftwareInstallerSetup_12.0.3.1” on my PC. I also connect directly 1 ethernet cable from my PC to “10/100/1G LAN 1” port of 3300 MXe III PBX, but I can not ping to 192.168.1.2 successfully from my PC (My PC was set IP Address 192.168.1.123). Could you please let me know how to fix this problem? If possible, please kindly instruct to me step by step.

I set these parameters on my IP-PBX following Technician's Handbook (MCD 6.0):

Press <SPACE><SPACE><SPACE> to stop auto-boot AFTER countdown starts...
<7><6><5><4><3><2><1><0>
auto-booting...


boot device          : ata=0,0
unit number          : 0
processor number     : 0
host name            : bootHost
file name            : /partition1/RTC8260
inet on ethernet (e) : 192.168.1.2:ffffff00
gateway inet (g)     : 192.168.1.1
user (u)             : ftp
ftp password (pw)    : ftp
flags (f)            : 0x0
other (o)            : qefcc

Thanks and best regards,
Spencer

[x-man]

Your HDD is not partitioned correctly. You need to change the boot parameter to fixpartition where it now says other (0)    :qefcc.

[pmhaynes]

Your setup sounds correct.
the 3300 is on 192.168.1.2 /255.255.255.0
make sure your subnet on your pc is also 255.255.255.0
The system will ping even if you had no hard drive in it.
I would attach a serial cable to the front of the 3300 and watch what is happening, then post a pic here.

When your pings start working......

Is the harddrive from mitel? IF not it will need formating/partitioning

See attached image

[sarond]

Assuming you have your FTP Server setup correctly and is reachable by the Mitel change the following

boot device          : motfcc
unit number          : 0
processor number     : 0
host name            : bootHost
file name            : Boot_Install
inet on ethernet (e) : 192.168.1.2:ffffff00
gateway inet (g)     : 192.168.1.1
user (u)             : ftp <-- FTP Username to connect to FTP Server
ftp password (pw)    : ftp <-- FTP Username for FTP Server
flags (f)            : 0x0
other (o)            : FixPartition

The fix partition option will format the HDD to the Mitel Spec as per the previous post.

[nguyenhung]

Hi all,

It still boot unsuccessfully. I did change these parameters as below:

boot device          : qefcc <-- I changed "boot device" to motfcc, but it is still qefcc as default
unit number          : 0
processor number     : 0
host name            : bootHost
file name            : Boot_Install
inet on ethernet (e) : 192.168.1.2:ffffff00
gateway inet (g)     : 192.168.1.1
user (u)             : ftp
ftp password (pw)    : ftp
flags (f)            : 0x0
other (o)            : FixPartition

Please kindly find my attachment for more details. My PC was set IP Address 192.168.1.21 255.255.255.0 but i still can not ping to 192.168.1.2. My HDD is from MiTel and also i did format this HDD already. Have you got any solutions to continue helping me to fix this problem? I still don't know why I can not ping to the default IP address of 3300 MXe III PBX 192.168.1.2

Looking forward to your quick responses

Thanks and best regards,
Spencer

[sarond]

Are you sure it is reaching your ftp server?
If you look at the admin window of Filezilla Server you should see the Mitel trying to connect. Be sure to turn off your firewall on your laptop.

You will need more than just the MCDSoftwareInstaller, you need the software to install into your ftp directory.

[bluewhite4]

You also don't have your inet host address set to be your pc's 192.168.1.21, so the 3300 isn't looking for the software on your pc.

[x-man]

qefcc is correct for the MXe111.

[lundah]

You need to set the "host inet" field in the boot parameters to the IP address of the FTP server.

[pmhaynes]

It you can not ping it then sounds like the E2T card is faulty.
You should always be able to ping the system right from the very beginning of turning it on, before anything has loaded.
Even with a fault hard drive or a formatted hard drive or a missing hard drive!

If you cant ping it don't bother with FTP etc

[lundah]

A faulty E2T wouldn't be causing the symptoms. OP is trying to load software manually from an FTP server, but hasn't told the controller where the FTP server is, so naturally it will fail. Correct the "host inet" field first.

[pmhaynes]

A faulty E2T wouldn't be causing the symptoms. OP is trying to load software manually from an FTP server, but hasn't told the controller where the FTP server is, so naturally it will fail. Correct the "host inet" field first.

If it wont reply to a ping its broken. Unless user error or something like VLAN in use
If he cant ping it it cant get to his PC or FTP server.

Can we see a screen shot or video of what you see from a terminal programme when you boot it.

I have upgraded many many 3300 manually, before we had the software installer when we needed an apple mouse cable to get into the E2T card!

Although i have been in this game long enough to know that nothing is impossible

I'm not one hundred percent sure but aren't the E2T card and the RTC card both on the same board now?
The board that sits right under neath the main board. If you were looking at the contoller from the front it would be left hand side infront of the hard drive.  Its the board that the hard drive plugs into ( not the IDE or Raid card that sits on top of the hard drive chassis)it also  has the Ram and processor on. Sits underneath MMC1
When you expanded it over a certain amount of users you install a second one next to the first.

Maybe i should have called it the MXe Processor card RTC/E2T, like the manual does

[lundah]

I've never seen an MXe processor that failed in that way, and I've seen thousands of them. Every system I've ever seen with IP connectivity issues has been from a bad MIPS processor, and those will stay up for a good 20 minutes after power-up before failing.

Besides, the system isn't bootstrapping to the point where the full IP stack is even running to respond to pings, because it doesn't know where to read the boot file from.

[pmhaynes]

I still say that the system needs to be returning pings before any upgrade will work.
Also i thought the system reply to ping before you get to press space space space

lundah are u saying that if he doesnt have the ftp server ip address programmed the system wont return a ping?

Also where do u think it gets the Boot_install file from....the FTP server
The first line of qefcc means boot from network! not hard drive meaning the network must be up and running, and returning pings, for it to work.

I've seen two processor cards fail, from memory.

One where the customer accidentally pulled the power at the wrong time,during upgrade, and killed it!

Cant remeber why he other failed.

Would quite like to see who right now, and obviously help out nguyenhung of course 

Again willing to be proven wrong and keep on learning

[sarond]

You also don't have your inet host address set to be your pc's 192.168.1.21, so the 3300 isn't looking for the software on your pc.

Can't believe I missed that