H/W Ver: A1
F/W Ver: 1.04B58_WW
Our department ordered a hand full of different brands of Gigabit VPN routers for evaluation so that we can pick a suitable replacement for our aging 100Mbps Cisco RV042's and RV082's.
The DSR-500 was one of the routers purchased for this evaluation.
As part of the evaluation, a firmware upgrade was to be performed to observe the functionality of the firmware upgrade process as well as any success or failure.
The firmware upgrade was first attempted via the web interface and using the USB method. The web interface indicated that it could see the file, but it would not allow update because it thought the firm was corrupt. After a few failed attempts it was determined to move on to the more traditional method of uploading the file via the web interface.
We proceeded with the upload process, which at first, appeared to be going just fine. Then the process stopped at 60% and went no further. We decided to give it ample time to finish, to ensure we did not interrupt the process prematurely. We let the router sit for nearly an hour before finally deciding to manually reboot the router.
The router went through its regular, yet extremely long (3 minute), reboot process and when it was finished the power LED was amber and not green. We could no longer get to the web interface.
We decided to use the console to access the device and we were suprised to get anything.
This is what is displayed.
U-Boot 1.1.1 (Development build, svnversion: exported) (Build time: Sep 1 2010 - 16:27:47)
Warning: Board descriptor tuple not found in eeprom, using defaults
CUST_DSR500 board revision major:2, minor:0, serial #: unknown
OCTEON CN5010-SCP pass 1.1, Core clock: 300 MHz, DDR clock: 200 MHz (400 Mhz data rate)
PAL rev: 0.00, MCU rev: 0.00, CPU voltage: 0.00
DRAM: 128 MB
Flash: 32 MB
*** Warning - bad CRC, using default environment
Clearing DRAM...... done
BIST check passed.
PCI Status: PCI 32-bit
PCI BAR 0: 0x00000000, PCI BAR 1: Memory 0x00000000 PCI 0xf8000000
Net: octeth0, octeth1, octeth2
Hit any key to stop autoboot: 0
Image name : ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
Image size : -1 bytes
Checksum value : 0xfffffc04
Verifying checksum... FAILED
D-Link DSR-500 bootloader#
I have searched these forms for about the past week looking for a solution to try and recover the device.
I have tried the Emergency Recovery with no success. I saw that several other people asked if this even works on this model and no answer was ever given. Does this recovery method actually work on a DSR-500?
We were wondering if there is any recovery method through the CLI using the console?
Or, is this thing just a brick and do I just need to contact D-Link to get an RMA going?