Mitel 3300 logging on

[andy4uk]

I have a 3300 which has been up and working for around 6 months, we are having problems logging on to the web browser how ever after a reboot you can then log on for a short time then it reverts back to unable to log on,
I have upgraded the system to version 5.2.5.4 and while the system was booting up i noticed the following error, Does any one have any ideas???????

BTable is 0xdd614700x
dd35000 (tDhcpHelper): nvs_BerkConvert.cpp:1377 - Error writing to db file.
0xWriteLogEntry withdd35000 struct Canno (t read soft log hetDhcpHelperader (0)
): Failure updating NVS, odb_rc=Otp_Logs_Client15
0xdd35000 (tDhcpHel->Defaper): nvs_BerkConvert.cultANSpp:1377 - Error writing t
o db file.
0xdd3ISoftwareCallb5000ack: Cannot inse (rt tuple (e0a2ad0)tDhcpHelper (0) ()!!)
:
Failure updating NVS, odb_rc=log typ15e = 1

 

[mitelman]

Have you verified if you see the same logs on another swithc that is rebooting? I know that when I have watched a few times I have seen some questionable stuff, but they don't seem to affect service. Kind of interested to know what tech support has said about this problem your having...

 

[MitelTech]

Have had this issue too, product support has the answer, we've applied it to 2 systems that were doing it, and both are fine now. Basically, it's a corrupt DHCP file.

 

[MitelTech]

If you have a MOL account, look up known product issues for the 3300, it is in there. Or look up "MN00066198 Intermittent ESM log-in".

 

[andy4uk]

Thanks gents, already had an idea it was the DHCP file but could not do anything untill last night,
Have deleted the file and re-created it, seems to have worked.

 

[MitelTech]

Unfortunatly it took product support and engineering 2 months of try this & try that to narrow it down for my customer. But once we landed that corrupt DHCP file we had a winner. We also had a different system doing the same thing and it turned out to be a bad sysid module.

 

[andy4uk]

Tech support informed us it needed a software upgrade, and then the problem would be sorted in the next 5.2 release.
Did'nt think so!!!!! They did'nt even mention the DHCP file could be corrupt? if I left it to tech support the customer would have been very unhappy for another month or so.