Jump to content
mpr

ENS620EXT Firmware Upgrade Failures from 1.0.0 to 3.0.0

Recommended Posts

I have a set of ENS620EXT radios and was attempting to upgrade one to the latest firmware.  Downloaded version 3.0.0.33 from the site, as a RAR file.  Unpacked it and found these instructions:

1) Factory Rest the ENS620EXT
2) Upload the ENS620EXTaddCAPWAP.bin file first to the ENS620EXT
3) Factory Reset the ENS620EXT
4) Upload the ENS620EXT-int-3.0.0.33_C1.8.53.bin to the unit
5) Factory reset unit
6) The unit should be ready to work with EWS switch or ezMaster Network Managment Software.

A bit more than I'm used to seeing, but I began following it step by step.  Steps 1 and 2 went fine, but after doing the factory reset in step 3, the device no longer boots and I can't ping it at 192.168.1.1 (except for a few brief seconds when it powers up). 

Has anyone successfully performed this firmware update?  From looking at the Javascript code on another radio, I believe the exact version of the current firmware I'm on is 1.0.0.29.

Share this post


Link to post
Share on other sites
4 hours ago, mpr said:

I have a set of ENS620EXT radios and was attempting to upgrade one to the latest firmware.  Downloaded version 3.0.0.33 from the site, as a RAR file.  Unpacked it and found these instructions:

1) Factory Rest the ENS620EXT
2) Upload the ENS620EXTaddCAPWAP.bin file first to the ENS620EXT
3) Factory Reset the ENS620EXT
4) Upload the ENS620EXT-int-3.0.0.33_C1.8.53.bin to the unit
5) Factory reset unit
6) The unit should be ready to work with EWS switch or ezMaster Network Managment Software.

A bit more than I'm used to seeing, but I began following it step by step.  Steps 1 and 2 went fine, but after doing the factory reset in step 3, the device no longer boots and I can't ping it at 192.168.1.1 (except for a few brief seconds when it powers up). 

Has anyone successfully performed this firmware update?  From looking at the Javascript code on another radio, I believe the exact version of the current firmware I'm on is 1.0.0.29.

This should be the correct steps on how update the firmware of the ENS620EXT. At step 3. Perform a 30 second hardware reset (exactly 30 seconds). 

Share this post


Link to post
Share on other sites

I tried doing the thirty second reset (stopwatch in front of me).   That entails plugging in the device and letting it boot completely (several minutes).  Then I push the pin in and hold for thirty seconds.  Release.  Check to see if the lights go out.  This doesn't seem to work--the light patterns don't change.  But I find that if I hold the reset button for 28 or 29 seconds (just a hair under 30) then release, that does make the light patterns change.  I pull the power immediately as soon as the lights go out (this was suggested to me by an Engenius support person over the phone).  Wait 30 seconds.  Then power the device back up.

But after the reset the device never comes back up at 192.168.1.1.  The light patterns are power(ON), LAN1(ON and blinking OFF every second or so), LAN2(off), 5G(ON every second), 2.4G(ON every second).  

Now I know it's gonna be tempting to say I have my IP address on my own machine wrong or whatever, but just minutes earlier after the first factory reset things were fine and I could reach 192.168.1.1.  And I can reach other Engenius equipment I have in the office (mostly ENS500EXT) just fine.

Can anyone else actually confirm that they've taken an ENS620EXT from firmware version 1.0.0.29 to 3.0.0.33_C1.8.53 using the six steps described in the README?

Share this post


Link to post
Share on other sites

Ok so I set aside RADIO1 as a brick and pulled grabbed a new ENS620EXT I had just provisioned.  Firmware version 1.0.0.29 according to the Javascript in the admin interface.

* Began the firmware upgrade steps with a factory reset.  Held reset button for ~30 seconds.  Removed power.  Waited 30 seconds.  Applied power again.  Device comes up at 192.168.1.1.  Good so far.

* Uploaded ENS620EXTaddCAPWAP.bin.  SHA256 sum of that file I have is: ac119efb30dd1c05054f79f71f9415d88410cc4f1f9c501e43c9660752f4d375

* Firmware upgrade timer starts at 600 seconds.  I let it be and come back and can get to the device fine at 192.168.1.1.   The admin page shows its version to be "1.0.0 + 1.8.53".

* Proceed with second factory reset.  Held reset button for ~30 seconds.  Removed power.  Waited 30 seconds.  Applied power again.  Device does NOT come up at 192.168.1.1. 

So I've got two bricks now.  Unless I'm doing something really wrong, or we have a box of bad radios, I have to suspect there could be a bug in the firmware upgrade process from 1.0.0.29 to the latest.

Share this post


Link to post
Share on other sites
3 hours ago, mpr said:

Ok so I set aside RADIO1 as a brick and pulled grabbed a new ENS620EXT I had just provisioned.  Firmware version 1.0.0.29 according to the Javascript in the admin interface.

* Began the firmware upgrade steps with a factory reset.  Held reset button for ~30 seconds.  Removed power.  Waited 30 seconds.  Applied power again.  Device comes up at 192.168.1.1.  Good so far.

* Uploaded ENS620EXTaddCAPWAP.bin.  SHA256 sum of that file I have is: ac119efb30dd1c05054f79f71f9415d88410cc4f1f9c501e43c9660752f4d375

* Firmware upgrade timer starts at 600 seconds.  I let it be and come back and can get to the device fine at 192.168.1.1.   The admin page shows its version to be "1.0.0 + 1.8.53".

* Proceed with second factory reset.  Held reset button for ~30 seconds.  Removed power.  Waited 30 seconds.  Applied power again.  Device does NOT come up at 192.168.1.1. 

So I've got two bricks now.  Unless I'm doing something really wrong, or we have a box of bad radios, I have to suspect there could be a bug in the firmware upgrade process from 1.0.0.29 to the latest.

Never had any issues updating the firmware of my ENS620EXT using the same exact procedure posted on the website.

Share this post


Link to post
Share on other sites

We're gonna have another one of our team try it tomorrow with a 3rd radio and see if he has any better luck. 

I've updated firmware so many times on these things though it's just hard for me to fathom that I could be screwing it up somehow.

laireV do you know if the set of radios you've been updating from was on 1.0.0.29, or something more recent?

Share this post


Link to post
Share on other sites
24 minutes ago, mpr said:

We're gonna have another one of our team try it tomorrow with a 3rd radio and see if he has any better luck. 

I've updated firmware so many times on these things though it's just hard for me to fathom that I could be screwing it up somehow.

laireV do you know if the set of radios you've been updating from was on 1.0.0.29, or something more recent?

I see. There is no other firmware release after 1.0.0.29. It has the same firmware as yours.

Share this post


Link to post
Share on other sites

I took a third ENS620EXT fresh out of the box and attempted 1) Factory Reset 2)Flash file #1 3)Factory Reset 4) Flash file #2 5) Factory Reset  from a Windows 10 environment. Only deviation I made from mpr's approach is I used the factory reset button from the interface, as opposed to the manual reset on the device.  

I also went back and attempted to connect to the "bricks" from mpr's attempt yesterday.  Both devices came up on 192.168.1.1 and ran through the steps.  All on the latest firmware.

Not sure if it was the manual resets or the Linux environment that caused the issues... or just bad luck. Going to attempt to recreate the scenario on a different linux machine, chromebook, network switch , ect...  but as of now I am wondering if devices were actually "bricked" or just being petulant.   Will post results of progress...

Share this post


Link to post
Share on other sites

Ok after taking a break from this I have done some more investigation and believe we are on to something here!

On my machine, I usually run a DHCP server in addition to the static IPs.  So I'll have, for example, 192.168.1.59 and 192.168.59.1 as my static IPs.  I'll also have a DHCP server dishing out IPs in the 192.168.59.200-255 range.

So I break out another fresh radio (this time ENS500EXT-AC) and this one, out of the box, I can't ping it at 192.168.1.1.  I run traceroute on it anyway though:

traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets
 1  192.168.59.247 (192.168.59.247)  0.735 ms  0.565 ms  0.617 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *

Ahh here we go!  The device is actually at 192.168.59.247.  It's gotten a DHCP address, but is still responding (kinda?) to 192.168.1.1.  I'm guessing this is a new behavior in firmware version "1.0.0 + 1.8.53".

I'd suggest in the next firmware to update it to not use DHCP, or to amend the manual @ https://www.engeniustech.com/engenius-products/enturbo-outdoor-5-ghz-11ac-wave-2-wireless-access-point/ to note that it will come up in DHCP by default.

 

Share this post


Link to post
Share on other sites
On 10/25/2017 at 2:24 PM, mpr said:

Ok after taking a break from this I have done some more investigation and believe we are on to something here!

On my machine, I usually run a DHCP server in addition to the static IPs.  So I'll have, for example, 192.168.1.59 and 192.168.59.1 as my static IPs.  I'll also have a DHCP server dishing out IPs in the 192.168.59.200-255 range.

So I break out another fresh radio (this time ENS500EXT-AC) and this one, out of the box, I can't ping it at 192.168.1.1.  I run traceroute on it anyway though:

traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 60 byte packets
 1  192.168.59.247 (192.168.59.247)  0.735 ms  0.565 ms  0.617 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *

Ahh here we go!  The device is actually at 192.168.59.247.  It's gotten a DHCP address, but is still responding (kinda?) to 192.168.1.1.  I'm guessing this is a new behavior in firmware version "1.0.0 + 1.8.53".

I'd suggest in the next firmware to update it to not use DHCP, or to amend the manual @ https://www.engeniustech.com/engenius-products/enturbo-outdoor-5-ghz-11ac-wave-2-wireless-access-point/ to note that it will come up in DHCP by default.

 

Thanks for all the effort and finding in regards to the above issue. Yes you are correct, the IP setting of the ENS620EXT will become DHCP after updating to firmware version 1.0.0 c1.8.53.

            Rationale: So the EWS Controller and ezMaster can easily find, add, manage, and control the access point.

I will forward this to the engineers for confirmation and possible manual revisions.

Share this post


Link to post
Share on other sites

Did anyone figure out how to upgrade the ENS620EXT?  I have six that are running v1.0.0 and I'm unable to upgrade them to the ENS620EXT-int-3.0.0.33_C1.8.53.bin.  I too am unable to find the capwap version for download if the middle step is still required.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.