5000 Error Log Info

[Magic Dave]

Hi, Had a customers 5000 go down last week and after a while it came back up. The customer said he had a problem with a switch and it brought down a lot of other things on his network, but when he rebooted the 5000 as a stand alone system it still had problems. Below is a copy of the error logs and I was hoping someone could explain the M999 errors and the system reset type = code change.

Jun 20 15:30:51 CS5200-COLCHEST CP[1513]: System Reset Type = 'Code Change'
Jun 20 15:30:58 CS5200-COLCHEST DEI[1631]: M999 dei: 5.1.20

Jun 20 15:31:01 CS5200-COLCHEST DEI[1660]: M999 update_dei: 5.1.20

Jun 20 15:31:05 CS5200-COLCHEST DEI[1660]: M999 update_dei: FPGA build DATE:10-16-08,1

Jun 20 15:31:55 CS5200-COLCHEST CP[1513]: A000 ALARM Alarm Automatically Cleared

Jun 20 15:32:40 CS5200-COLCHEST CP[1860]: System Reset Type = 'Database Restore Complete'

Jun 20 15:35:44 CS5200-COLCHEST DEI[1974]: M999 dei: 5.1.20

Jun 20 15:35:46 CS5200-COLCHEST DEI[1990]: M999 update_dei: 5.1.20

Jun 20 15:35:49 CS5200-COLCHEST DEI[1990]: M999 update_dei: FPGA build DATE:10-16-08,1

Jun 20 15:35:53 CS5200-COLCHEST DEI[2044]: M999 update_dei: 5.1.20

Jun 20 15:35:55 CS5200-COLCHEST CP[1860]: A114 ALARM Dual T1/E1/PRI Module (T1M-2) 1 Port 1 In Red Alarm

Jun 20 15:45:18 CS5200-COLCHEST CP[1860]: Alarm 114 Automatically Cleared

Cheers

[acejavelin]

Code Change is typically seen after an upgrade, it's supposed to mean the firmware has changed, but I've seen it in normal operation as well. Nothing about these logs concerns me.

I would pull the logs and look for any old, archived logs, but my guess is they didn't get written to disk because something went wrong. Typically in this situation I would run live log captures and continue normal operation, if it recurs you have the logs, if not just write it off as a fluke.

Sent from my MotoG3 using Tapatalk

[Magic Dave]

Cheers, it's an old CS controller that might be swapped out for a HX so i'm oping that will clear the fault if there is one.

[Tech Electronics]

Magic Dave & Ace Javelin,

We have run into the "code change" error when there are power issues on the system as well. So if the system is shutdown unexpectedly or if it does a reset due to a brown out or a bad square-wave UPS then you will get this error and possibly some corruption.

Thanks,

TE

[DND ON]

Rid he reboot the system or just pull the power cord? If he yanked the cord, that log looks correct.

[Tech Electronics]

Magic Dave,

Do they have more than one DEI attached to the CS controller? It may be having an issue with trying to verify the version and the update is failing, which would be the M999 issue I suppose.

You may need to try and flash each DEI one at a time and see if there is an issue if that keeps happening.

Thanks,

TE

[Magic Dave]

Hi TE, the customer got this back working before i could attend site so any info came from him. Yes he does have dei's plugged in and when he disconnected everything the system came back up. I think he did pull the power cord out of the back to reboot the system after the first crash.

So it looks like the CCU had issues with the DEI's before it could complete its boot up. As it stands this happened about 8 days ago from now and we haven't heard of any other issues from the customer.

Thanks for the reply's, i had looked in the guide for error codes and could not find the M999 codes. If i get any other problems then i'll try and flash the DEI's to see if this clears the issues.