Reliable Update of RV042 V03 firmware.
I am updating the firmware in a number of RV042 V03 routers. From v4.2.3.07 to 4.2.3.08.
In some cases, the management interfaces (http, telnet) fail after the update (2 out of 3 so far).
It brings up the well-known:
But, since these are all V03, I'm wondering if there isn't a way to update the firmware more reliably?
I did it the same way each time:
Updated the firmware over the network using the http interface - where I was remotely controlling a local computer which had the new file on it and was connected to the RV042.
I admit that one of the failures happened over a wireless link but at least it was a good connection....
I'd like to continue to do this remotely. I see no reason why a local computer can't do it over the network if there's no wireless involved.
What's the most reliable method?
In some cases, the management interfaces (http, telnet) fail after the update (2 out of 3 so far).
It brings up the well-known:
404 Not Found
The requested server-side-includes filename, /usr/local/EasyAccess/www/htdocs/default.htm, does not seem to exist. But, since these are all V03, I'm wondering if there isn't a way to update the firmware more reliably?
I did it the same way each time:
Updated the firmware over the network using the http interface - where I was remotely controlling a local computer which had the new file on it and was connected to the RV042.
I admit that one of the failures happened over a wireless link but at least it was a good connection....
I'd like to continue to do this remotely. I see no reason why a local computer can't do it over the network if there's no wireless involved.
What's the most reliable method?
ASKER
John,
Well, you have lots of experience with these. So thanks for responding!
The remote connection is to a computer that's local to the router and doing the work. It connects through "the network" to the RV042. This entails a LAN switch and that's about all. Traffic levels are very low. And, indeed one of them updated fine - which is what I'd hoped for.
As long as I'm remote, I'm not able to power cycle the RV042. So, we'll see just how bad it is when I get on site.
Since you mention the RV325 and RV134AC routers, I see that the RV325 is dual-WAN like the RV042 and the RV134AC is single WAN but with WiFi. Do you have a favored router that's without WiFi and with but a single WAN port? I don't know if it matters that much re: price but just curious.
Well, you have lots of experience with these. So thanks for responding!
The remote connection is to a computer that's local to the router and doing the work. It connects through "the network" to the RV042. This entails a LAN switch and that's about all. Traffic levels are very low. And, indeed one of them updated fine - which is what I'd hoped for.
As long as I'm remote, I'm not able to power cycle the RV042. So, we'll see just how bad it is when I get on site.
Since you mention the RV325 and RV134AC routers, I see that the RV325 is dual-WAN like the RV042 and the RV134AC is single WAN but with WiFi. Do you have a favored router that's without WiFi and with but a single WAN port? I don't know if it matters that much re: price but just curious.
As long as I'm remote, I'm not able to power cycle the RV042. <-- If you are updating firmware, you need only restart, not power cycle. If that were necessary for some other reason, someone on site could do that.
I like the RV325 because it is a 14 port router (eliminates a switch) and I purchased the RV134AC later.
I could do all my tunnels with the RV134AC and have a switch. That would work as well
I like the RV325 because it is a 14 port router (eliminates a switch) and I purchased the RV134AC later.
I could do all my tunnels with the RV134AC and have a switch. That would work as well
ASKER
John,
Thanks. Well, if I could talk to the router after the update, that would be what I'd do.
But, it refuses to communicate http or telnet. And, I'm not sure it's working.
I can't do a successful preferential loose route trace route through one of them that's still connected.
But, it will respond to a PING.
Thanks. Well, if I could talk to the router after the update, that would be what I'd do.
But, it refuses to communicate http or telnet. And, I'm not sure it's working.
I can't do a successful preferential loose route trace route through one of them that's still connected.
But, it will respond to a PING.
If you use a browser on the workstation that you remoted into and did the firmware with that, it WILL come back. Always does for me. So use web GUI to update firmware, stay logged into the Workstation and watch, and it will come back (all my RVxx routers do).
ASKER
John,
I've done quite a few of these. In the recent evolution, 2 of 3 lost their GUI and telnet.
One of them was connected locally via a wireless link - so I'll discount that one. But, on that one, a cold boot didn't help.
(That is: I remote into local workstation; local workstation connects to network via wireless (good signal level); wireless access point connects to RV042 via ethernet).
I'll learn more tomorrow.
I'll likely not do any more of these remotely - if only to be there to see things through.
From my experience, this is unusual but not all that surprising. It does happen. So, I'd say that sometimes the interfaces won't come back on their own..... Always a nagging worry.
Similarly, I had two SG300 switches lose their interfaces autonomously - no updates involved. A physical power-cycle or "cold" reboot fixed.
So, the phenomenon isn't unknown.
I've done quite a few of these. In the recent evolution, 2 of 3 lost their GUI and telnet.
One of them was connected locally via a wireless link - so I'll discount that one. But, on that one, a cold boot didn't help.
(That is: I remote into local workstation; local workstation connects to network via wireless (good signal level); wireless access point connects to RV042 via ethernet).
I'll learn more tomorrow.
I'll likely not do any more of these remotely - if only to be there to see things through.
From my experience, this is unusual but not all that surprising. It does happen. So, I'd say that sometimes the interfaces won't come back on their own..... Always a nagging worry.
Similarly, I had two SG300 switches lose their interfaces autonomously - no updates involved. A physical power-cycle or "cold" reboot fixed.
So, the phenomenon isn't unknown.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!
You are very welcome and I a.m. always happy to help with your topics
ASKER
An update:
Cisco provides a procedure to deal with this kind of situation. It uses TFTP32 to upload new firmware.
The part I find interesting is something I'd not seen before:
But, it's in a mode where it will receive TFTP file transfers of a firmware file.
This worked on 2 of the "bricks" that I had in hand.
At least this applies to V03 - I don't know about the earlier models.
Cisco provides a procedure to deal with this kind of situation. It uses TFTP32 to upload new firmware.
The part I find interesting is something I'd not seen before:
To do the firmware recovery you need to put the router on recovery modeThis gets the router into a mode that will respond to pings (at 192.168.1.1) and, in my experience, that's all.
-Turn the router off
-Press and hold the reset button and turn the router on
-Hold the reset button until the orange diag led is flashing
-Assign a static IP address to your computer (192.168.1.x) and disable the firewall
But, it's in a mode where it will receive TFTP file transfers of a firmware file.
This worked on 2 of the "bricks" that I had in hand.
At least this applies to V03 - I don't know about the earlier models.
I do not have this configuration so I will provide what information I do have.
1. RV042 Firmware was V1.3.xx
2. RV042G Firmware was V4.2.xx which matches the firmware you stated above.
3. I have a spare RV042G V01 in the basement. It is running 4.2.3.08 dated 2/26/2017
I normally update firmware locally using a workstation that is connected by Ethernet to the RVxx router (right now RV325 and RV134AC routers).
I see no reason why you could not connect to a workstation connected to the router by Ethernet and upgrade the firmware. You lose the connection to the RVxx machine and it will come back. This should be the most reliable way short of being local.
I do not think I would attempt to upgrade firmware when connected remotely directly to my router.
Please let me know if I can answer any questions.