AP Error Log

Hi

Over the past week we have noticed that we have a handful of SM’s that just seem to drop off (they do not power cycle, just lose registration). Out of 12 registered to an AP, it seems to only be half of them, not all. There is no direct correlation between any of them, except that they all look at the same AP. On that AP, after an event of the SM’s dropping off, the AP error log showed the following:

01:20:48 UT : 01/19/00 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 516 System Log Cleared
01:23:51 UT : 01/19/00 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 3585 TxVC = 0x000078 NumPendInts = 0
01:23:51 UT : 01/19/00 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 3586 FatalError()
01:23:09 UT : 01/19/00 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1055 Time set
01:23:09 UT : 01/19/00 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 914 System Reset Exception – External Hard Reset WatchDog Cur ExtInt 254 Max ExtInt 658 Cur DecInt 43 Max DecInt 33 Cur Sync 0 Max Sync 51 Cur LED 0 Max LED 1 Cur EthXcvr 0 Max EthXcvr 1 Cur FEC 60 Max FEC 202 Cur FPGA 91 Max FPGA 332 Cur FrmLoc 105 Max FrmLoc 133 AAState 0
01:23:09 UT : 01/19/00 : File root.c : Line 908 System Startup
01:23:09 UT : 01/19/00 : File root.c : Line 913 Software Version : CANOPY 6.1 Dec 08 2004 09:22:02 AP-DES
01:23:09 UT : 01/19/00 : File root.c : Line 917 Software Boot Version : CANOPYBOOT 3.0
01:23:09 UT : 01/19/00 : File root.c : Line 923 FPGA Version : 051104
01:23:09 UT : 01/19/00 : File root.c : Line 927 FPGA Features : DES

Not understanding the log very well, I am guessing that something caused the fatal error, causing the AP to reset connections. Does anybody have any ideas as to the cause, or how to progress / troubleshoot further? The AP never goes down, or loses network connectivity.

Rgds

Vinay

According to the event log the AP did go down and had to have lost network connectivity after the error was logged. There is a rare issue in releases prior to 7.1 where an SM reboot would reset the AP. I would recommend upgrading to 7.2.9 as there have been a lot of fixes since 6.1.

I put in a question to engineering regarding the error message so I will respond when I receive it.