Forwarding this on, someone should be in touch if they haven’t already.
From: Af [mailto:[email protected]] On Behalf Of Ryan Ray via Af Sent: Friday, September 26, 2014 4:12 PM To: [email protected] Subject: Re: [AFMUG] PMP450 AP stopped responding I will try loading the beta as soon as I get my dump from the AP. I phoned in and created a support case as well. I tried to run the gather support info and I get the following. Launching: java -cp C:\Canopy\NetworkUpdater\tools\CNUTSupportInfoTool.jar null Start Time: September 26, 2014 2:04:34 PM PDT java.lang.NoClassDefFoundError: null Caused by: java.lang.ClassNotFoundException: null at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) Could not find the main class: null. Program will exit. Exception in thread "main" Tool Complete with exit status:1 End Time: September 26, 2014 2:04:35 PM He also said I would be getting an email with information about submitting the dump and I haven't got that either. On Fri, Sep 26, 2014 at 1:44 PM, Aaron Schneider via Af <[email protected]<mailto:[email protected]>> wrote: Hi Ryan – While I can’t say for certain what caused the Ethernet Core to get stuck, there are two things in 13.2 that will help with this. First off, there was a bug in this reporting mechanism that wasn’t allowing a recovery to take place. That recovery should have been an AP reboot but the logging itself was preventing that. Secondly, for PMP450, in 13.2, there were architectural changes made such that this type of a problem can’t happen anymore. Those changes are related to the speed improvements gained with the 13.2 release on PMP450. PMP430 could still be susceptible to this type of a condition, but the first point I mentioned will correct the recovery in that it won’t let the device sit there unresponsive, it will reset itself if it gets stuck in this kind of condition. Please try the 13.2 Build 30 beta if you can. We are close to the 13.2 general release. Regards, -Aaron From: Af [mailto:af-bounces+aaron.schneider<mailto:af-bounces%2Baaron.schneider>[email protected]<mailto:[email protected]>] On Behalf Of Ryan Ray via Af Sent: Friday, September 26, 2014 3:17 PM To: [email protected]<mailto:[email protected]> Subject: [AFMUG] PMP450 AP stopped responding About 30 minutes ago I had a 2.4 AP loaded on 13.1.3 just quit responding. CTM said there was still normal power draw, link was up up on the cisco switch with no errors. No traffic. Reset the port from the CTM and it came back. I have another AP up there right beside it on the same software that I haven't seen issues yet. Anyone ever seen this before? I saw this on the bootup log. ******System Startup****** System Reset Exception -- Software Version : CANOPY 13.1.3 AP-DES Board Type : P12 Device Setting : 2.4GHz MIMO OFDM - Access Point - No valid accounts configured. Using default user account - 2460.0 MHz - 20.0 MHz - 1/16 - CC 4 FPGA Version : 011514 FPGA Features : DES, Sched, US/ETSI; 12/31/2010 : 17:00:24 PDT : Bridge Core : Acquired sync pulse from Power Port. 09/25/2014 : 01:18:10 PDT : : Bridge Core : Time Set 12/31/2010 : 17:00:00 PDT : : Bridge Core : 01/01/2011 : 00:00:00 UTC : : Bridge Core : Time Set 12/31/2010 : 17:00:00 PDT : Bridge Core : ******System Startup****** System Reset Exception -- Watchdog Reset Software Version : CANOPY 13.1.3 AP-DES Board Type : P12 Device Setting : 2.4GHz MIMO OFDM - Access Point - No valid accounts configured. Using default user account - 2460.0 MHz - 20.0 MHz - 1/16 - CC 4 FPGA Version : 011514 FPGA Features : DES, Sched, US/ETSI; 12/31/2010 : 17:00:24 PDT : Bridge Core : Acquired sync pulse from Power Port. 09/25/2014 : 15:03:05 PDT : : Bridge Core : Time Set 09/26/2014 : 13:10:02 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:05 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:09 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:12 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:16 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:20 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:23 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:27 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:31 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:34 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:38 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:42 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:45 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:49 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:52 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:56 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:00 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:03 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:07 PDT : : Bridge Core : Ethernet Core failing to report. Cheers
