You are here

Rocket M2 upgrade to v3.22.8.0 failure

6 posts / 0 new
Last post
gm7urd
gm7urd's picture
Rocket M2 upgrade to v3.22.8.0 failure

Hi guys,

Not to sure where to post this but ive run into an issue upgrading one of my Rockets. Its the first rocket ive attempted to upgrade to the new v3.22.8.0.

Earlier i followed the same standard procedure in the admin section and upgraded an hAP without issue.

I dont have physical access to the device itself as its 40 feet in the air, but do have a poe with a reset that ive attempted to use (15sec reset) but that didnt seem to work.

I cant find it on the network and even did the tftp 192.168.1.x thing.

Anyway, looking through my binos i can vaguely see the LEDs from right to left are green, blank, slow flashing red, blank blank.

So a couple of questions:-
1. Does anyone know what the LEDs indicate (for future reference); and
2. Does anyone have an idea on how to recover the node?

Thank you in advance.

Dave

K6AH
K6AH's picture
Try WIFI

Seems I recall it comes up with WIFI turned on.  Try connecting to it with your cell phone via wifi.

Andre

nc8q
nc8q's picture
Failsafe: 15 second reset

The 15 second fail-safe reset should put the node on 192.168.1.1 with DHCP server enabled.
If your computer is set to DHCP client, then ethernet cable connected, it should obtain an IP
address in 192.168.1.x.
An ethernet disconnect then connect may be needed for the computer to initiate another DHCP reset.
Ensure that the computer's Wi-Fi is disabled.
Use 'ping' to test connection.
If Windows, use ipconfig to confirm status.

A 30 second reset may be necessary to put the device into TFTP state.

73, Chuck

 

gm7urd
gm7urd's picture
Unable to enter tftp state

Thank you, Andre and thank you, Chuck.

I studiously followed your advice, unfortunately the device is unreachable and not transmitting an ID (ran a scan on ch -4 to 11 with 5, 10 and 20Mhz bw)

Ive attempted several full resets and even tried using 2 different versions of linux laptops and a windows laptop (just in case). Nothing is working. It does power up though. Wondering if there is damaged pair on the cable?

I did also change the poe 24volt type still no change.

Cant really think of anything else... Any thoughts?

Dave
 

nc8q
nc8q's picture
Ive attempted several full resets and even tried using 2 differe
  1. Ive attempted several full resets and even tried using 2 different versions of linux laptops and a windows laptop (just in case).
  2. Nothing is working. It does power up though.
  3. Wondering if there is damaged pair on the cable?

Hi, Dave:
1. So, I assume that the rocket is in 'first boot' state.
If your test computer has a address in the 192.168.1.x network and
If a 'ping 192.168.1.1' fails, the node may not be in first boot state.
An ifconfig/ipconfig will confirm the state of the testing computer.

You might attempt to put the rocket into TFTP mode.
You may be able to confirm this state by viewing with your binoculars.
In TFTP state the rocket should respond to pings to 192.168.1.1. 

3. If the rocket was working before the upgrade, I would not assume a cable failure.

73, Chuck

 

n0kfb
n0kfb's picture
I'd start with the basics.

I'd start with the basics.
1) If you power up your Rocket and plug it into your computer, does the Ethernet port light up?

2) If the Ethernet port lights up, do you have an IP address (other than 169.x.x.x)?
     2a) If your computer is not getting an IP address, give it a static address at 192.168.1.99

3) If your computer is getting an IP address, can you ping the default gateway?

3) If you gave your computer IP address 192.168.1.99, can you ping either 192.168.1.1 or 192.168.1.20?

--Dan Meyer / n0kfb

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer