Detailed analysis of common Broadband Router faults

For many users who use broadband routers, Broadband Router faults are often encountered. Here we will introduce the solutions to the problems of Broadband Router faults. Finally, check the hardware. After a Broadband Router fault is identified in the above steps, if the fault is found to be a hardware Broadband Router fault, you need to remove the host and replace the hardware components. However, this process generally does not require you to do it yourself. It is often implemented by engineers of suppliers or vendors.

In addition to our own experience, product manuals, and vendor websites, we must quickly think of your product suppliers and contact them when encountering a failure of our VBR, to help solve the problem quickly. The longer the time it takes, the longer the product subscription and replacement period will be.

Broadband Router failure: virus causes router overload

The topological structure of the fault location of the Broadband Router is as follows: An EnterasysSSR8000 is used as the border router, and it is also used to divide the campus into eight virtual networks, each virtual network has a stack of Two-layer switches as the access device for desktops and laptops. The trunk is 1 Gigabit and MB to the desktop.

On that day, I received a call for help from a colleague, saying that his machine could not access the internet. The virtual network and network center of the colleague's host are not in the same virtual network. I heard from my colleagues that I was able to access the Internet five minutes ago. Moreover, the system installed on his machine is Windows XP. Recently, no new programs have been installed, computers have been moved, and network cables have not been pulled. First, troubleshoot the incorrect configuration of the network client. Run the IPCONFIG command in MSDOS mode to check the IP Address Configuration of the Host:

C:> ipconfig
Windows IP Configuration
Ethernet adapter local connection:
Connection-specific DNS Suffix .:
IP Address ......: 210.16.2.30
Subnet Mask ......: 255.255.255.0
Default Gateway ...... 210.16.2.1

The configuration shown above is correct, and ping your own IP Address:

C:> ping 210.16.2.30
Reply from 210.16.2.30: bytes = 32 time <1 ms TTL = 128
Reply from 210.16.2.30: bytes = 32 time <1 ms TTL = 128

This indicates that the IP address is valid and the NIC works normally. Run the PING command to test the connection from the local machine to the Gateway:

C:> ping 210.16.2.1-t
Reply from 210.16.2.1: bytes = 32 time <1 ms TTL = 128
Reply from 210.16.2.1: bytes = 32 time <1 ms TTL = 128
......

All the packets sent from the host to the gateway are responded, and the lines are connected. Open your browser and access the Internet normally. No problem at all. The current network is normal !? When I was wondering, I found that the Network was disconnected again! The ping packet failed to reach the gateway. Strange, it was okay. Why can't we get through now? Is there a problem with the NIC or system? Who knows after a while, and found again. Thanks to my laptop that day, I inserted the network cable on my desktop to my computer. After configuring the IP address, I pinged the gateway, and the intermittent disconnection also occurred. The disconnection lasted for about 50 seconds and then recovered to normal. This can basically eliminate host problems, because the probability of two unrelated hosts having the same problem is almost zero. In view of this phenomenon, I first ruled out the failure of the connection cable, because the connection cable cannot be subject to this situation of intermittent disconnection, the failure of a Broadband Router is most likely at the second-layer switch on the other end of the cable. So I came to the device room in the building and checked the switch status. This is a stack of two switches, one of which has an uplink gigabit port.