Question on EIGRP route (traceroute weird)

R1 has two paths to get to 172.16.1.1
via 2.2.2.1 and via 3.3.3.1

Why does the trace look like this?:

1  2.2.2.1  4 msec
   3.3.3.1   4 msec
   2.2.2.1 0 msec

2  1.1.1.1  4msec
   4.4.4.2  4msec
   1.1.1.1  4 msec na
orusAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
rochey2009Connect With a Mentor Commented:
There are two paths

One of them goes from R1 to R2 via the 2.2.2.0 subnet and then onto R4 via the 4.4.4.0 subnet

The other goes from R1 to R3 via the 3.3.3.0 subnet, crosses the 1.1.1.0 subnet to R2 and then onto R4 via the 4.4.4.0 subnet. So this route is suboptimal due to the redistribution.
0
 
rochey2009Commented:
Hi,

It's alternating each probe over both paths.
0
 
orusAuthor Commented:
is this normal behavior?
0
 
rochey2009Commented:
yes the per packet load balancing is normal for equal cost routes (and with some configuration using the EIGRP variance command for unequal cost routes). However in your case both the paths are not really equal since the path to 172.16.1.1 through R3 is an extra hop but this is a consequence of redistribution between protocols and can sometimes introduce suboptimal routes such as the one through R3.

I think you can change the per packet loadbalancing behaviour.
0
 
orusAuthor Commented:
final question. What is the actual path between R1 and 172.16.1.1 (r4)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.