This is a minor alarm log from an XTS-MPB2 system. The customer rebooted it at 8:04 this morning, but said that the time on the displays showed that it was 6:27. This is exactly what it shows in this log as happening, but I'm wondering if anyone can tell what this means:

01/27 08:04 1999-Sys Restart 1 255 1009fa4c 00000000 10010000000000000000000000
000000
01/26 18:27 1030-Brd Absent 1 2 0000000d 00000003 18000000000000000000000000
000000
01/26 18:27 1030-Brd Absent 1 2 0000000c 00000003 13000000000000000000000000
000000
01/26 18:27 1030-Brd Absent 1 2 0000000b 00000003 12000000000000000000000000
000000
01/26 18:27 1030-Brd Absent 1 2 0000000a 00000003 11000000000000000000000000
000000
01/26 18:27 1030-Brd Absent 1 2 101ae7bc 101ae6c8 10000000000000000000000000
000000
01/26 18:27 3-Process T/O 6 0 00000000 00000000 00011019fef000000000000000
000000
01/26 18:26 3-Process T/O 6 0 101af29c 101af298 00011019fef00000000000000

Is this a 2 cabinet system?

Looks like maybe the cards in the second went out of service.

I says this because on the last set of numbers the first 2 numbers are card slots as i've always been told. 10, 11, 12, 13, 1800000000000.

Just a thought!

It is actually a 3-cabinet system Gary. I've always thought it was the third and fourth digits in the last string that identified the card slot, but I may be wrong. I did think the same thing about the first two digits. My first thought was that it might be an LMU card/cable issue, but then that would have caused codes for the third cabinet to be displayed. I'm confused.

Yes very strange! not sure, did you try your luck with tech support?

No, I figured I'd come here first. It is usually much faster, plus the issue can be shared amongst us in the future.

Why did the customer reboot the system?

The log looks like one that came out of a system I had a problem with. Spontaneous resets. I changed the cpu although I think that I could have reinitialized the first one and uploaded the database.

They rebooted it because it was locked up with the time display being 6:27. My guess is that the processor froze up at this point and they discovered it first thing the following morning.

Well, I wouldn't do anything unless it happens again, could have been caused by a power blip.

I agree with Derrick unless this is an ongoing occurence there? Maybe a proccesor or maybe a power issue? Its a weird one!!

Just curious but does this system have a Pathfinder IS in it? Is so is auto reboot enabled on the Pathfinder and what time is it set for?

No, it is just a node with three cabinets, about 150 stations, one PRI for networking to the hub across the street and one CO-PRI. The VM is a Pathfinder, but it is centralized and is not an in-skin one.

I agree that this may have just been a power glitch (although it is on a UPS), but the customer wants to know for sure if there isn't a serious problem. Hey, I'm happy to have a proactive customer here.