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
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
Andre
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
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
- 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?
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
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
I just wanted to let everyone know the root cause of the failure.
Having exhausted all other options i decided to perform the following:-
1. cut the lan cable about 30cm up from the rg45 and terminate with a new connector.
2. still not working; also pinged but no response; also scanned 192.168.x.x from 0.1 to 1.255 and ports 1 to 6000. nada
3. put device into TFTP mode
4. scanned again and found device at 192.168.1.20
5. tftp 192.168.1.20 put factory.bin
Now back up and running.
Prior to changing the termination i was unable to get rocket into tftp mode.
So it seems that somehow the system upgrade was interrupted because of a break in one of the twisted pairs.
Fixing the cable and reinstalling the firmware to factory has recovered the device.
Thank you again
Dave