Get the App
SLTechnology News&Howtos  ›  Network Security  › 

Physical links cause RIP routing Oscillation

Shulou Source: shulou.com Published: 2022-06-01 02:52:27 10月04日 Update

Physical links cause RIP routing Oscillation

The use of the company network is normal, suddenly some network communication is abnormal, but generally after 1 or 2 minutes to recover. This phenomenon occurs irregularly, sometimes once in half an hour, sometimes once in three hours. When a failure is found in the rip routing table, there is no network segment with fault in the routing table.

When the above faults occur, they can be handled in the following order:

1. The cause of routing oscillation can be divided into two aspects.

1) routing changes due to changes in link state.

2) due to the lack of rigorous network design, there are a large number of the same value routing or routing status update oscillation, the main way to prevent the problem is to require all traffic and routing to be strictly calculated when designing the network.

two。 In the case of routing instability, you can first configure a static route, and when the physical link or equipment is normal, the service can be resumed after configuring the static route.

3. After the static route is configured, if the failure is restored, it is likely to be the route concussion caused by the configuration; if the failure is not restored, it may be the route concussion caused by the physical port or link outage

4. In the general check order, first check the alarm information of the device, and then check the configuration information of the device, which may also be a problem with the physical device.

5. There is no problem in checking the configuration information, but there are repeated UP/DOWN alarms on port F0 in the alarm. Check that the alarm time is basically the same as that of the network failure, and it is basically determined that the fault is caused by the port UP/DOWN. After further confirming whether it is an equipment failure or a link failure, the replacement port test can determine that the fault is caused by a physical link failure (physical link error, etc.).

* Sep 28 07 Line protocol on Interface FastEthernet0/0 31 1V 08.195:% LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up

* Sep 28 09 Line protocol on Interface FastEthernet0/0 31lo 18.975:% LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down

* Sep 28 09 Line protocol on Interface FastEthernet0/0 31 30.075:% LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up

* Sep 28 11 Line protocol on Interface FastEthernet0/0 31VR 32.983:% LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down

Tags: Routing failure link physical configuration network device situation port concussion information time problem static cause hour aspect state phenomenon sequence Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Shulou Tech Info MariaDB OPPO Reno Xiaomi macOS