In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Network Security >
Share
Shulou(Shulou.com)06/01 Report--
Today, what the editor shares with you is the solution to the network failure caused by the repetition of Router ID in the OSPF network. I believe that most people do not know how to solve the problem. In order to make you understand better, the editor summed up the following content for you. Without saying much, let's move on.
Repetition of OSPF network Router ID causes network failure
The network topology is shown in figure 9.1. The three routers run the OSPF protocol and all belong to area 0. The network plan is as follows:
The interconnection address of n R1 and R2 is: 10.0.0.0Compact 30. The interconnection address of R1 and R3 is: 30.0.0.0amp30.
N use the Loopback0 interconnection address of the router as the Loopback0:2.2.2.2/32,R3 Loopback0:3.3.3.3/32 of the Loopback0:1.1.1.1/32,R2 of Route-id,R1
N use the Loopback1 interface of the router to simulate the internal client host of the company, the Loopback1 of R1: 192.168.1.0 Loopback1:192.168.2.0/24,R3 of R2, Loopback1: 192.168.3.0
Figure 9.1 Router ID repetitive problem network topology in OSPF network
After the network configuration is complete, it is found that the users with R2 and R3 cannot access each other, and the routing entries on R1 are incorrect. The configuration (interface configuration is correct, omitted) is as follows:
R1 configuration
Router OSPF 1
Router-id 1.1.1.1
Network 1.1.1.1 0.0.0.0 area 0
Network 10.0.0.0 0.0.0.3 area 0
Network 30.0.0.0 0.0.0.3 area 0
Network 192.168.1.0 0.0.0.255 area 0
R2 configuration
Router OSPF 1
Router-id 2.2.2.2
Network 2.2.2.2 0.0.0.0 area 0
Network 10.0.0.0 0.0.0.3 area 0
Network 192.168.2.0 0.0.0.255 area 0
R3 configuration
Router OSPF 1
Router-id 2.2.2.2
Network 2.2.2.2 0.0.0.0 area 0
Network 30.0.0.0 0.0.0.3 area 0
Network 192.168.3.0 0.0.0.255 area 0
This case is used to troubleshoot physical link problems. The specific troubleshooting ideas are as follows:
1. Configure a static route to see if the failure has been restored. If it is restored, it may be due to a routing problem caused by a configuration problem, and if it cannot be restored, it may be due to a physical link or device port failure.
2. Check the router configuration and relevant alarms. The following alarms appear on the router:
* Mar 1 01 in area 51V 27.967:% OSPF-4-DUP_RTRID_AREA: Detected router with duplicate router ID 2.2.2.2 in area 0
It means that there is the same route-id in the area, and the routing problem can be solved by changing the configuration because the same route-id leads to the failure of the routing entry.
This is the solution to the network failure caused by the repetition of Router ID in the OSPF network. I hope the above content can be of certain reference value to everyone and can be applied. If you like this article, you might as well share it for more people to see.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.