@Napsterbater 

Hi all

I've just got a call from one of my clients. One EAP 660HD firmware version 1.2.10 connected to a ER7212PC, the AP just stopped working, the network SSID was not visible and no errors on the logs. All clients suddenly dropped.

It took a AP restart to make it working again. It's the first issue I've seen in the 15 days it's been online. I'm worried because it's a VR installation in a remote location with about 50 clients, 10 hours straight every day.

Cannot help with logs because there is nothing on the log or event viewer that might indicate anything.

  @digitalFounders 

Hopefully that ER7212PC allows you to power cycle the port that the AP is connected to. 

Unfortunately, if your situation's like mine, the only option I had to solve it permanently was to revert the unit all the way back to 1.1.1, support was absolutely useless.

I may try again if and when the next firmware comes out but it took TP link almost two years to release these broken firmwares, So I'm not holding my breath.

Hank21 wroteH

Hi @digitalFounders 

If the SSID was invisible, may I confirm whether the EAP was still powered on? We may need to confirm the hardware connection first.

 

Meanwhile what was the status on the EAP when you found them drop?

 If it's the same as in my case, the APs are still powered still show a power light. They're just completely absolutely frozen and locked up. 

 It no longer broadcast an SSID, generates absolutely zero packets at all once it's locked up. This can be confirmed by any Smart Switch showing a pack of counter that has been reset once it's locked up or using a span port and monitoring the traffic. 

 It's a kenji your PC being so locked up that it doesn't respond to your keyboard, your keyboard  or mouse or control alt delete or anything.

Hi  @Hank21 

Yes, the EAP was powered on all the time. In detail, this is what I found out. All times UTC+1.

The EAP was installed about 15 days ago and has been working every day since. About 50 VR headsets connect to the WiFi for about 12 straight hours every day. We choose a EAP660 HD, as it has more CPU, RAM and antennas to handle high density scenarios, and this is the configuration that we also have running on 10 other installations with no issue.

On Sunday, at around 19:00h, the client calls saying that the VR headsets do not connect. The client previously performed a unit reboot (the ER7212PC) some minutes before but the headsets could not see the SSID. When the controller became online, I entered and checked that the AP was turned on for 8 hours (more on this later), I performed a power cycle on the AP and when back online, the headsets could see the SSID and connected normally.

One issue I saw was that the AP said that it had been online for 8 hours, which did not make sense because 19:00-8:00 = 11:00h, and the installation starts at 10:00h. So I was looking in the graphs and found out that at 11:10h, the AP went offline for a slight moment (about 5 minutes) and the wireless traffic dropped during that time. Later at about 17-17:30h all wireless traffic dropped. There was the hard reboot of the router, which seems strange because the AP was still powered on all time (so the 8 hours uptime) and nothing was solved until the AP power cycle.

We'll be following this issue because it might indicate a defective unit. We have installed a lot of them and work with no issues. The firmware of the ER7212PC is 5.8.36 and the AP firmware is 1.2.10.

Meanwhile, is there a way to get more verbose logs of what might have happened? I've checked all event logs and found some entries of constant IP changes on the AP (sorry about the screenshot, the one I have is very wide and I had to make it smaller).

Thanks!