What does this actually mean? I have a few towers doing this, the readout from the SM is this…
22:42:22 UT : 01/02/01 : File root.c : Line 955 FPGA Version : 070605
22:42:22 UT : 01/02/01 : File root.c : Line 959 FPGA Features : DES Sched
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset
00:00:00 UT : 01/01/01 : File root.c : Line 940 System Startup
00:00:00 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 SM-DES
00:00:00 UT : 01/01/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
00:00:00 UT : 01/01/01 : File root.c : Line 955 FPGA Version : 070605
00:00:00 UT : 01/01/01 : File root.c : Line 959 FPGA Features : DES Sched
04:23:04 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset
00:00:00 UT : 01/01/01 : File root.c : Line 940 System Startup
00:00:00 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 SM-DES
00:00:00 UT : 01/01/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
00:00:00 UT : 01/01/01 : File root.c : Line 955 FPGA Version : 070605
00:00:00 UT : 01/01/01 : File root.c : Line 959 FPGA Features : DES Sched
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset
00:00:00 UT : 01/01/01 : File root.c : Line 940 System Startup
00:00:00 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 SM-DES
00:00:00 UT : 01/01/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
00:00:00 UT : 01/01/01 : File root.c : Line 955 FPGA Version : 070605
00:00:00 UT : 01/01/01 : File root.c : Line 959 FPGA Features : DES Sched
04:28:12 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset
00:00:00 UT : 01/01/01 : File root.c : Line 940 System Startup
00:00:00 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 SM-DES
00:00:00 UT : 01/01/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
00:00:00 UT : 01/01/01 : File root.c : Line 955 FPGA Version : 070605
00:00:00 UT : 01/01/01 : File root.c : Line 959 FPGA Features : DES Sched
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset
00:00:00 UT : 01/01/01 : File root.c : Line 940 System Startup
00:00:00 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 SM-DES
00:00:00 UT : 01/01/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
00:00:00 UT : 01/01/01 : File root.c : Line 955 FPGA Version : 070605
00:00:00 UT : 01/01/01 : File root.c : Line 959 FPGA Features : DES Sched
04:30:53 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
04:31:28 UT : 01/01/01 : File httptask.c : Line 733 Reboot from Webpage.
04:31:05 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
04:31:05 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset WatchDog
04:31:05 UT : 01/01/01 : File root.c : Line 940 System Startup
04:31:05 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 SM-DES
04:31:05 UT : 01/01/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
04:31:05 UT : 01/01/01 : File root.c : Line 955 FPGA Version : 070605
04:31:05 UT : 01/01/01 : File root.c : Line 959 FPGA Features : DES Sched
22:56:56 UT : 01/02/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
22:59:05 UT : 01/02/01 : File httptask.c : Line 733 Reboot from Webpage.
22:58:50 UT : 01/02/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
22:58:50 UT : 01/02/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset WatchDog
22:58:50 UT : 01/02/01 : File root.c : Line 940 System Startup
22:58:50 UT : 01/02/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 SM-DES
22:58:50 UT : 01/02/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
22:58:50 UT : 01/02/01 : File root.c : Line 955 FPGA Version : 070605
22:58:50 UT : 01/02/01 : File root.c : Line 959 FPGA Features : DES Sched
23:04:08 UT : 01/02/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
00:00:00 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 918 System Reset Exception – External Hard Reset
There are many SMs with this same thing. They all have tons of re-registers. One tower is timed through the “one hop” deal with the back-hual slave on that tower, the other is generating sync way out in the country. The one in the country just started, whereas the other has been doing this for months. For now, I will install timing on the tower that started this month that is generating it’s own sync, and replace the cable giving the other one timing from the backhaul. I would like an efficient understanding of these logs though. Am I pursueing this problem right?
The version is still 7.2.9 I am in the process of getting ready up upgrade as I would think that may solve some problems however, the other 7 towers don’t seem to do this with the re-registers. They are up to the 500s on some customers. There is NO geographical similarity between the ones that work great, and the ones that get the re-registers. Everything is running hardware scheduling.
I have posted a similar question and had a great reply! I look forward to learning more. Thanks.
this usually means the timing has drifted and is being reset. (so i’ve been told)
Does this tend to be an issue that is normal, or when it happens a lot is it a bad pipe sync? bad timing source, cable, or AP? I will check all, but the AP part is kind of a pain to “check” as replacing it is the only real way. Has anyone else had this problem and found a fix? Are there any other known reasons that the APs and the SMs would show these errors? I’, not sure if interference is a possible culprit or not.
Thanks,
LP