To achieve a better network experience, I usually upgrade the router firmware. Similarly, when router software malfunctions, a firmware upgrade can often fix it. Of course, if you want to upgrade your router firmware, it is best to have some basic computer knowledge; otherwise, you might run into unnecessary trouble. Here, we’ll use a Netgear router as an example to introduce this knowledge.
1. Garbled Text Appears
After taking out the router and powering it on, I connected via the Console port and found a lot of garbled text on the terminal screen. Could the Console port be damaged? If the Console port is broken, the terminal screen usually continuously outputs a lot of garbled characters. If garbled text appears after pressing Enter, the baud rate might be incorrect. I changed the default value from 9600 to 115200, and the router booted successfully. After it started up, using show run indeed confirmed that the Console speed was set to 115200.
2. Insufficient Memory Causes Upgrade Failure
The Netgear router I was upgrading had VPN functionality. I downloaded a new IOS file from the internet, which was 18 MB in size. The upgrade process was as follows:
1. Configure the IP address of the router’s Interface 0/0. First, use copy flash:tftp to back up the original IOS, and then upload the new one using the copy tftp flash command.
2. After restarting the router, a prompt appeared indicating there was not enough memory to run the IOS. Checking the official website revealed that the upgraded firmware required the router to have 64 MB of RAM and 16 MB of Flash. From the boot information above, it was clear this router only had 32 MB of RAM, so naturally it failed to start. After upgrading the memory, the router booted successfully.
3. TFTP IOS Upload Verification Failed in ROM Mode
Assuming the router IOS upgrade failed and I wanted to restore the original IOS, there are two recovery methods: FTP and Xmodem. TFTP offers faster transfer speeds, while Xmodem is relatively slow. In ROM mode, I used TFTP to upload the IOS.
1. Configure the IP address on Interface 0/0 and check it with the set command. By default, the IP address configured in ROM mode is assigned to Interface 0/0, and it should be on the same subnet as the TFTP server.
2. I used the tftpdnld method for downloading. Initially, I used Cisco’s TFTP server, but the transfer timed out halfway through. After switching to 3Cdaemon, the transfer completed, but a warning appeared. Upon restarting the router, it failed to boot, displaying an IOS verification error. I downloaded the file again, but the issue persisted. It seemed the IOS file