Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
15 Reply
Re:Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details
2022-05-17 05:03:56 - last edited 2022-05-17 05:04:23

Not sure if related, but during the upgrade I get this error in server.log with the MAC of the AP:

 

WARN [manage-work-group-12] [] c.t.s.o.m.d.p.t.h.a(191): send set request to OmadacId(...) DeviceMac(...) fail, com. tplink. smb. ecsp. common. TransResult@65eaeb30[errCode=2600,msg=ERR_DEVICE_SEND_TCP_TIMEOUT,result=<null>,addressDTO=<null>]

 

(added spaces to com tplink smb common TransResult to get around some weird URL filter)

  0  
  0  
#12
Options
Re:Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details
2022-05-17 14:57:11

  @karlshea 

 

I'm going to suggest you try to downgrade the AP back to 1.0.6 from 1.1.0, then go straight to 1.1.1 from there.

<< Seeking a new reason to stick around... >>
  0  
  0  
#13
Options
Re:Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details
2022-05-17 16:36:42

  @d0ugmac1 Upgrading back to 1.0.6 also fails in the same way.

  0  
  0  
#14
Options
Re:Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details
2022-05-17 16:53:10
You tried the use the controller to do it right? No, you must basically factory reset the device and use it's native (local) web interface to try the downgrade.
<< Seeking a new reason to stick around... >>
  0  
  0  
#15
Options
Re:Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details-Solution
2022-05-23 05:47:44 - last edited 2022-05-23 05:50:39

Finally figured this out. I was binding the HTTP ports to a specific IP address, because 80 & 443 were in use by another site on the same server. Binding the 29810-29814 ports to a specific IP never worked because of broadcast issues, so they were bound to 0.0.0.0.

 

I changed the HTTP ports so they didn't conflict, and removed the IP address binding, and the upgrade succeeded.

 

My guess is that the EAP and/or the controller was getting confused, or the way firmware files were send/fetched changed in the latest controller or firmware, and the EAP was trying to fetch the file from a management port on an IP that it wasn't bound to. The port FAQ (which is also out of date) says that one of the 2981x ports is used for upgrades, but now apparently one of the management HTTP ports is also used.

Recommended Solution
  0  
  0  
#16
Options