Mitel 3300 ICP - Logs

[stickymicky27]

Hi all,

I need to remove all the maintenance logs as the log has built up to a stupid size and its now causing the 3300 to reboot...

Can anyone please let me know the command to do so or do i need to create a FTP connection to the box to clear them?

Any help would be appriecated.

 

[IrwinMFletcher]

What is shown on the system that would lead you to this conclusion? If it is truly the logs that cause the reboot, then I'm surprised it starts since a reboot generates yet more logs....

 

[bobcheese]

I agree with Irwin. This cannot be correct of maintenance logs as this would happen on all systems at some point.

 

[stickymicky27]

Must admit i have never seen it before... but the system has generated 500 pages of logs... as it was a faulty extension causing a very odd error...

I have read on some other posts that there 3300 rebooted at stupid times because the system logs were full and that the system would reboot when it liked...

Im not totally sure it even is this yet but it is just an avenue I am exploring...

 

[LoopyLou]

I have seen years ago on the SX2000 an instance where due to corruption of the file system, that logs did fill up the maintenance log buffer and couldn't be overwriten which is the normal case for the SX2000 and the 3300. This happened to the point that it locked the SX2000 up. I would suggest you have something similar since the logs get overwrittten.

The single biggest problem with communications is the illusion that it has taken place.

 

[stickymicky27]

Well our next step is going to be a system upgrade as there is a newer version out than ours... so i'll be doing that very shortly and well see if the problem is resolved!

 

[wireman50]

WE recentley had a similar problem with a MCD4 system. Faulty ISDN2e circuit was causing the buffers to fill up (amongst other things) and locking the system. It sat there with no alarms or error lights but dead to the world, no access to the system even by the console...reboot fixed it till next time.

 

[stickymicky27]

Cheers Wireman50... i'll bear this in mind... only problem is that im not sure the customer has a spare T1/E1 card... but it might a good beat with error logs showing 73% loss in ISDN trunks around the time of the reboot?

 

[wireman50]

To be clear it was the ISDN2e lines themselves causing the problem NOT the card. We did change the BRI card )mitel tech support asked us to) but it was the line fault itself causing the problem. Thinking back we had a similar problem a few years ago with a PRI as well.

 

[mitelmmaniac]

Whats the reset code in the SD Logs?

Desk Jockey Lunacy

 

[IrwinMFletcher]

A logfile can have 5000 entries, which matches your 500 pages. Once it gets to that point it just wraps around.

 

[stickymicky27]

Well I have turned off the automatic reboot should a critical system problem come up so im hoiping if it is a ISDN issue the system will just sit there so I can see fault to then diagnoise!...

 

[Supernova99]

it is still possible to delete (purge) log files if required.
I am not sure this is possible from the ESM but it can be done via the 'backdoor'
You will need to telnet into the system first then login as user system and password sx2000
at the maintainance screen you can type
logs purge maint all
logs purge soft all

or just a few logs

logs purge maint new xx



Share what you know - Learn what you don't

 

[wireman50]

Its not the logs causing the issue its the fact that the 3300 uses the isdn for timing for a whole lot of its functions and when it gets a lot of errors it just throws a wobbly and gives up. Setting it to not reboot will just cause it to sit there dumb till you reboot it. The system timer should be linked to an external clock if fitted according to MTS but it made no difference in my case.

In other news if you try and licence a system which cannot for some reason get any answer from the AMC it just sets a stale task...too many of them will also cause a reboot due to critical errors.