RV130W Not accessible after online firmware upgrade attempt

[Dimitar Todorov]

Hello everyone

I was investigating a DNS issue trough VPN and as one of the measures to troubleshoot it I set up my RV130W to download and install new firmware from Cisco servers. After some time the internet stopped and VPN dropped. Waited for some time to see if the router will reboot but no avail. The power light is flashing rapidly and the manual clearly says it's because of a bad firmware. Tried reset to factory defaults and set up a PC with 192.168.1.x address, but there is no ping to 192.168.1.1, neither to 192.168.0.1 which was before the upgrade. I see there is a procedure for other Cisco routers to put the firmware anew with TFTP and , but can't find the same for this model. Also, tried to TFTP the FW and I got timeout. Any suggestions prior sending it back to Cisco? I have a spare router to do the job now and some time to experiment with the faulty one also. The DNS issue was found and fixed in the DNS server.

[Dimitar Todorov]

It is Cisco RV130W

[cbjwthwm · Accepted solution]

I never normally do this type of firmware update--I always download the firmware and upload the file manually but I tried this once on a RV130 remotely and it bricked itself as well.

Luckily in my case the router was still accessible by its default IP (which is on a different subnet than I use for it) of 192.168.1.1.  It provided a boot block recovery type boot with a limited interface only allowing for upload of the firmware, and I was able to re-submit my usual downloaded file and it recovered to a normal state.

I'm pretty sure it lost its configuration and I needed to restore my backup, but I was thoroughly unimpressed with firmware update bugs this severe at least 4-5 releases into the router's life.

[Dimitar Todorov]

Thank you, this helped me and I have restored the router. Now it works normally again. It even has retained its configuration. Previously I had backed it up by copy to backup configuration.

I had no ping and I was connecting it wrong trough another switch. I connected it directly to port 1, set my IP manually and just opened the browser and voila - the limited interface was up waiting for the firmware file :)

Thanks again!