Physical links cause RIP Routing shocks

Physical link causes RIP Routing Shocks

Company network use Normal, suddenly some network communication abnormal phenomenon, but generally after 1, 2 minutes to recover their own time. This phenomenon occurs occasionally, sometimes half an hour, sometimes 3 hours, and when the View RIP routing table discovers a failure, there is no network segment that fails in the routing table.

When the above failures occur, they can be processed in the following order of processing:

1. The reason for routing oscillation is divided into two aspects.

1) routing changes due to changes in the link state.

2) due to the lack of rigorous network design, there are a large number of same-value routes or routing status updates oscillation, the main solution to prevent the problem is in the design of the network requires all the flow and route selection to be strictly calculated;

2. In the case of routing instability, a static route can be configured first, and when the physical link or device is normal, a static route can be configured to resume the business.

3. After configuring the static route, if the failure recovery is likely due to the configuration caused by the routing shock, if the failure is not restored may be due to physical port or link disruption caused by the routing shock;

4. The general check order, first check the device alarm information, and then view the device configuration information, may also be a physical device problem;

5. Check configuration information is not a problem, but the alarm has f0/0 Port has repeatedly up/down alarm, and then check the alarm time and network failure time is basically consistent, basically determine the fault is caused by the port Up/down. In the further confirmation is the equipment failure or the link fault, the replacement port test if the failure is still, it can be determined that the fault is a physical link failure (physical link error, etc.);

*SEP 07:31:08.195:%lineproto-5-updown:line protocol on Interface fastethernet0/0, changed

*SEP 09:31:18.975:%lineproto-5-updown:line protocol on Interface fastethernet0/0, changed

*SEP 09:31:30.075:%lineproto-5-updown:line protocol on Interface fastethernet0/0, changed

*SEP 11:31:32.983:%lineproto-5-updown:line protocol on Interface fastethernet0/0, changed

Physical links cause RIP Routing shocks