VPN equivalent/non-equivalent load balancing

1. when multiple paths exist at the destination, and the metric values of multiple paths are the same, the equivalent load balancing can be performed, 650) this. width = 650; "src = ".. /attachment/201210/171627301 .jpg" border = "0" alt = "" data-pinit = "registered"/> after completing the configuration, view the neighbor table, topology table, and route table a on R1. neighbors table 650) this. width = 650; "src = ".. /attachment/201210/173147668 .jpg" border = "0" alt = "" data-pinit = "registered"/>
B. topology table 650) this. width = 650; "src = ".. /attachment/201210/173225426 .jpg" border = "0" alt = "" data-pinit = "registered"/> c. route table 650) this. width = 650; "src = ".. /attachment/201210/173252914 .jpg" border = "0" alt = "" data-pinit = "registered"/>
View the topology table and find that there are two paths from router R1 to 10.10.2.0/24, one passing through R2, one passing through R4, and the two paths have the same metric value, both of which are 286720. View the route table and learn that R1 can perform balanced forwarding through two links when forwarding data packets.
D. verify the equivalent load balancing 650) this. width = 650; "src = ".. /attachment/201210/204434473 .jpg" border = "0" alt = "" data-pinit = "registered"/>

2. the topology of the non-equivalent Link Experiment changes: the Eth1/0 port of R1 connects to the F0/1 port of R4, And the F0/1 port of R1 connects to the PC as a gateway. In this way, all ports from R1 to 10.10.2.0/24 are different, which will affect the path metric. 650) this. width = 650; "src = ".. /attachment/201210/185349164 .jpg" border = "0" alt = "" data-pinit = "registered"/> after completing the configuration, view the neighbor table, topology table, and route table a on R1. neighbors table 650) this. width = 650; "src = ".. /attachment/201210/190337850 .jpg" border = "0" alt = "" data-pinit = "registered"/> B. topology table 650) this. width = 650; "src = ".. /attachment/201210/190351323 .jpg" border = "0" alt = "" data-pinit = "registered"/> c. route table 650) this. width = 650; "src = ".. /attachment/201210/190406972 .jpg" border = "0" alt = "" data-pinit = "registered"/>
View the topology table and find that there are two links from R1 to 10.10.2.0/24. The metric value of one link is 286720, and that of the other link is 309760. View the route table and learn that the two links are not equivalent. The smaller metric link is used as the next route and is displayed in the route table. 650) this. width = 650; "src =" ../attachment/201210/193826810 .jpg" border = "0" alt = "" data-pinit = "registered"/>

Note: The metric value of the link is only the outbound port of the router. Two Links: R1 → R2 → R3 → PC2; R1 → R4 → R3 → PC2, the outbound port is a red circle port. 650) this. width = 650; "src = ".. /attachment/201210/192457342 .jpg" border = "0" alt = "" data-pinit = "registered"/> because of this: the metric value of the link from router R3 to 10.10.1.0/24 does not change because of the Eth1/0 change of the R1 interface, and there is still an equivalent link. A. topology table 650) this. width = 650; "src = ".. /attachment/201210/193057713 .jpg" border = "0" alt = "" data-pinit = "registered"/> B. route table 650) this. width = 650; "src = ".. /attachment/201210/193114610 .jpg" border = "0" alt = "" data-pinit = "registered"/> c. tracetroute 10.10.2.1 650) this. width = 650; "src = ".. /attachment/201210/193715281 .jpg" border = "0" alt = "" data-pinit = "registered"/>

3. on the basis of the experiment topology of the non-equivalent link, configure the command: 650) this. width = 650; "src = ".. /attachment/201210/195558584 .jpg" border = "0" alt = "" data-pinit = "registered"/>
View the neighbor table, topology table, and route table a of R1. neighbors table 650) this. width = 650; "src = ".. /attachment/201210/200931821 .jpg" border = "0" alt = "" data-pinit = "registered"/> B. topology table 650) this. width = 650; "src = ".. /attachment/201210/200957557 .jpg" border = "0" alt = "" data-pinit = "registered"/> c. route table 650) this. width = 650; "src = ".. /attachment/201210/201040565 .jpg" border = "0" alt = "" data-pinit = "registered"/>
View the topology table and find that the network segment 10.10.2.0/24 has changed from "1 successors" to "2 successors", but the FD value has not changed. View the route table and find that a link "[90/309760] via 172.16.14.4, 00:14:15, Ethernet1/0" is added ".
D. verify non-equivalent load balancing 650) this. width = 650; "src = ".. /attachment/201210/203302951 .jpg" border = "0" alt = "" data-pinit = "registered"/>