After Upgrading I lost communications with my Bullet M2:
I tried to upgrade a Ubiquiti Bullet M2 from a 3.15.1.0b2 version to the current version. I used the following instructions someone gave me:
“If you are currently running 3.15.1.0b01 or 3.15.1.0b02 and plan to do an Over the Air (OTA) upgrade to "keep settings" when uploading 3.15.1.0b04, the process is as follows:
1) install the patch: "AREDN 3.15.1.0b* OTA Fixup"
2) Proceed to upload the sysupgrade 3.15.1.0b04 firmware <------------ I THINK YOU CAN GO STRAIGHT TO PRODUCTION RELEASE CODE HERE.”
Background:
With 3.15.1.0b2 installed, I was accessing Ubiquiti through my router by setting Setup to NAT, DHCP deselected and IP set to 192.168.0.240 AND it was working!
I had "keep settings" checked when I upgraded.
What I’ve tried without luck:
So far, thru my router, I tried to ping using 192.168.0.240.
With a direct cable to my Bullet I tried to ping using 192.168.1.20
I pressed the POE reset button for 15 seconds.
Thank You!
I tried to upgrade a Ubiquiti Bullet M2 from a 3.15.1.0b2 version to the current version. I used the following instructions someone gave me:
“If you are currently running 3.15.1.0b01 or 3.15.1.0b02 and plan to do an Over the Air (OTA) upgrade to "keep settings" when uploading 3.15.1.0b04, the process is as follows:
1) install the patch: "AREDN 3.15.1.0b* OTA Fixup"
2) Proceed to upload the sysupgrade 3.15.1.0b04 firmware <------------ I THINK YOU CAN GO STRAIGHT TO PRODUCTION RELEASE CODE HERE.”
Background:
With 3.15.1.0b2 installed, I was accessing Ubiquiti through my router by setting Setup to NAT, DHCP deselected and IP set to 192.168.0.240 AND it was working!
I had "keep settings" checked when I upgraded.
What I’ve tried without luck:
So far, thru my router, I tried to ping using 192.168.0.240.
With a direct cable to my Bullet I tried to ping using 192.168.1.20
I pressed the POE reset button for 15 seconds.
Thank You!
when you did:
----- What I’ve tried without luck: So far, thru my router, I tried to ping using 192.168.0.240. With a direct cable to my Bullet I tried to ping using 192.168.1.20 I pressed the POE reset button for 15 seconds.
-----
Was the node fully booted before you pressed the button for 15 secs?
Did it reboot afterwards?
Did you disconnect your CAT5 and reconnect afterwards?
Did you close your browser and re-open ?
Do you have your wifi on your pc DISABLED during this?
Thank you for your reply, I tied all of your suggestions with no results.
There must be some changes in b04 (between b02 and release) that are necessary for sysupgrade to function correctly. Conrad wrote this code and can confirm or we can dig through the code.
Joe AE6XE
After b02 we found and fixed some significant flaws in the upgrade process that were found thay would of been picked up when a mode was flashed with b04.
Paul
WB6IWT
the 15 second reset IP (hold for 15 seconds no more an no less as it is time sensitive) where the status 4 LED is solid it will turn off then flash then be solid again it will be then be at 192.168.1.1
the 192.168.1.20 is where you hold the reset button BEFORE the node boots to go into TFTP recovery mode (which is where you will likely want to go if you don't see it on 1.1 but it should be there assuming you wait for the node to fully boot before pressing and holding the button)
Bob W8ERD
Probbaly best to to pull your question into its own thread as it sounds different than the issue described in the original post.