Bidirectional retransmission step experiment

 

R1

[r1]rip 1

[r1-rip-1]version  2

[r1-rip-1]undo    summary

[r1-rip-1]network    12.0.0.0

[r1-rip-1]network   14.0.0.0

[r1-rip-1]network  1.0.0.0

R2

[r2]RIP 1

[r2-rip-1]version   2

[r2-rip-1]undo  summary

[r2-rip-1]network    12.0.0.0

[r2-rip-1]network   2.0.0.0
 

[r2]ospf 1 router-id    2.2.2.2

[r2-ospf-1]area  0

[r2-ospf-1-area-0.0.0.0]network   23.1.1.1 0.0.0.0         

R3

[r3]ospf 1 router-id  3.3.3.3

[r3-ospf-1]area  0

[r3-ospf-1-area-0.0.0.0]network    3.3.3.3 0.0.0.0

[r3-ospf-1-area-0.0.0.0]network    23.1.1.2 0.0.0.0

[r3-ospf-1-area-0.0.0.0]network    34.1.1.2 0.0.0.0

 

R4

[r4]ospf   1 router-id    4.4.4.4

[r4-ospf-1]area  0

[r4-ospf-1-area-0.0.0.0]network 4.4.4.4 0.0.0.0

[r4-ospf-1-area-0.0.0.0]network  34.1.1.1 0.0.0.0

[r4]rip  1

[r4-rip-1]version  2

[r4-rip-1]undo    summary

[r4-rip-1]network   14.0.0.0

see R3 My neighbor table :

see R1/R3 The routing ：

As can be seen from the above table R1 Only R2 The loopback of ,R3 Only R4 The loopback of , It indicates that the convergence is normal .

# Network wide accessibility ———— Reissue

R2

 [r2]ospf   1

 [r2-ospf-1]import-route   rip 1

 [r2]rip 1

 [r2-rip-1]import-route ospf   1

R4

[r4]RIP 1

[r4-rip-1]import-route   ospf  1

[r4]ospf 1

[r4-ospf-1]import-route  rip  1

see R1 The routing table for ：

 

3. Optimize

As can be seen from the figure above ,R4 The loopback of is loaded twice , That is, through OSPF Convergent /32 The routing ,/24 Is republishing into rip The routing , Because the mask is different, it is loaded twice , Simple speak R4 The re - release of the loopback classic has returned to ospf Area , It's feedback . therefore R2 and R4 There are two 4.4.4.0 Mask different routes , So there are two ways to deal with .

   First, modify the loopback network type , The second is to change the loopback ip The mask of is 32. I choose the second option 》

 

 [r4]interface LoopBack   1

 [r4-LoopBack1]IP address    4.4.4.4  32

After treatment , Still no change , Why? ？ It's better to deal with it further , Take another look at the phenomenon .

[r4]undo interface LoopBack  1

        By looking at R1 The routing table for , Find out 4.4.4.0/24 The routing entry for always exists , Without changing the loopback ,4.4.4.0/24 because rip、ospf Convergence and republishing technology of , When 4.4.4.0/24 Cycle to R3 when ,R3 Will pass it on to R4, because R4 With direct connection 4.4.4.0/24, So don't R3 Of 4.4.4.0/24, When people change R4 The loopback of , Because it has no direct connection 4.4.4.0/24, When R3 Turn again from R2 At convergence 4.4.4.0/24 issue R4, It will converge , And given a R1, So as to cycle back and forth . That's why R4 Why doesn't the loop of disappear . If R1~R4 function RIP agreement , When 4.4.4.0/24 The measurement of has been increasing , So they will be aware of the touch ring , Delete the route entry immediately .

Solve the above problems ： To break off R4 Restart the physical link interface .

[r4]interface GigabitEthernet    0/0/0

 [r4-GigabitEthernet0/0/0]shutdown

check R1 Table of :

  R1 To load balance all network segments , It indicates that the situation is normal .

Interference in routing

 1. Match traffic

[r2]ip ip-prefix  haha  permit    34.1.1.0 24

[r2]ip ip-prefix haha  permit    4.4.4.4 32

[r2]interface GigabitEthernet   0/0/0    

[r2-GigabitEthernet0/0/0]rip  metricout   ip-prefix   haha   2      // Interface , Add metrics .

R4：

[r4]ip ip-prefix  hehe  permit    23.1.1.0 24

[r4]interface  GigabitEthernet  0/0/1

[r4-GigabitEthernet0/0/1]rip  metricout    ip-prefix    hehe 2

 

R2：

[r2]ip ip-prefix   haha permit    2.2.2.0 24

[r2]route-policy   haha  permit   node    10

[r2-route-policy]if-match    ip-prefix  haha

[r2-route-policy]apply  cost-type  type-1

[r2]ip ip-prefix  haha  permit    12.1.1.0 24

[r2]route-policy  haha  permit   node    230

[r2-route-policy]if-match    ip-prefix  haha

[r2-route-policy]apply   cost-type  type-1  

[r2]route-policy  haha  permit   node   340

[r2]ospf 1

[r2-ospf-1]import-route   rip 1 route-policy   haha

 

R4

[r4]ip ip-prefix xixi  permit    14.1.1.0 24

[r4]route-policy  xixi permit   node  10

[r4-route-policy]if-match     ip-prefix xixi                                 

[r4-route-policy]apply  cost-type  type-1

[r4]route-policy xixi permit   node   20

[r4]ospf 1

[r4-ospf-1]import-route   rip  1 route-policy  xixi

4. test ： broken R2 Of g0/0/0 All interfaces follow the backup path , It indicates that the optimization is successful . As shown in the figure below ：

          Recover interface discovery R1 Go to R2 Loop back and load balance , First R2/R4 The routing table of has been shaken , because RIP Than OSPF Slow convergence , such R2 adopt ospf Converging to the route faster than rip Fast , Again from ospf Regionally convergent routes are republished into RIP to R1,R1 Because of horizontal segmentation , Cannot send route to R2, but R1 Go to R2 Load flow , In order to achieve the original optimization state , Sure down fall R2 Of ospf Area interface , Restart again , The route returns to normal .