Remember a network interruption fault handling

The core of the user is Cisco’s 6807. The three major campuses are interconnected. A few days ago, the user’s telephone reaction was that one of the campuses could not access the Internet wirelessly. At first, they thought there was a wireless problem. After logging in to the controller, they found that the controller could not be connected. Other hosts in the network segment are unavailable! It seems that it is not just a wireless problem. Visiting the core of another park also found that the problem is coming!

The core of the logged-in user checked the logs and found that a large number of logs appeared in the morning, as follows:

Picture.png

Open Baidu search:

Picture.png


I found that Baidu can't find anything, I can only search through bing

Picture.png

Although there are only two, at least there are results, right?

Let me talk about other topics here. You can’t use Baidu to search for IT-related topics. You can either use bing or gxxgle. Baidu's mostly advertising!

Later, through the searched links, I found that this problem may be a BUG

Picture.png

Then the problem comes again, what if it is a BUG?

1. Perform a restart operation to see if the fault can disappear.

2. Upgrade IOS. If it still fails, you can only open CASE to solve it.

Here I performed a restart operation. After the restart, the connection between the core and another campus returned to normal! The wired network and wireless network access are normal.





Guess you like

Origin blog.51cto.com/05wylz/2597024