EIGRP non-equivalent load balancing, connecting an article.

eigrp non-equivalent load balancing, followed by an article.
Network Diagram As follows:
IP address configuration:
R1 13.1.1.1 12.1.1.1 11.1.1.1 (PC1 is 11.1.1.2 used to test connectivity)
R2 12.1.1.2 24.1.1.2
R3 13.1.1.3 34.1.1.3
R4 24.1.1.4 34.1.1.4 44.1.1.1 (PC2 is 44.1.1.2 used to test connectivity)
The whole network realizes eigrp
The configuration method is as in the previous article.
eigrp non-equivalent load balancing, followed by an article.
The configuration is complete After checking the routing table of the R1 route, I found that the road to 44.0.0.0 is 13.1.1.3.
Looking at the topology, there are two paths: via 13.1.1.3 via 12.1.1.2
But the FD value of the sub-optimal path is too high, divided by the FD of the optimal path is greater than 128, so load balancing cannot be performed.
I changed the FD value by modifying the bandwidth of the se 2/0 port from R1 to R2.
eigrp non-equivalent load balancing, followed by an article.
R1>
interface se 2/0 enters se 2/0 port
bandwidth 100000 changes the bandwidth to 100000kb bytes
Check the routing table and find that there is still only one way to 44.0.0.0. Check the topology and find the FD of the suboptimal path. The value is much smaller.
Using the FD of the sub-optimal path / FD of the optimal path + 1 rounded = 17
route eigrp 100
variance 17
Check the routing table again and find that there are two paths leading to 44.0.0.0 NS. In this way, load balancing is done.
eigrp non-equivalent load balancing, continue with an article.

< p>

WordPress database error: [Table 'yf99682.wp_s6mz6tyggq_comments' doesn't exist]
SELECT SQL_CALC_FOUND_ROWS wp_s6mz6tyggq_comments.comment_ID FROM wp_s6mz6tyggq_comments WHERE ( comment_approved = '1' ) AND comment_post_ID = 2382 ORDER BY wp_s6mz6tyggq_comments.comment_date_gmt ASC, wp_s6mz6tyggq_comments.comment_ID ASC

Leave a Comment

Your email address will not be published.