We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 581 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

295 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: , ,


Forum Replies

  1. Rene,

    i was working on the lab for myself. i have the exact same config. however my ports are different as i am using a different ios version router. my traceroutes would go from r1>r4>r5> where the 5.5.5.5 was at.

    after taking down a link i would get this output. what does this traceroute mean (below)

    Type escape sequence to abort.
    Tracing the route to 5.5.5.5

    1 192.168.12.2 108 msec
    192.168.13.3 88 msec
    192.168.12.2 44 msec
    2 192.168.35.5 112 msec
    192.168.25.5 72 msec
    192.168.35.5 120 msec

  2. my mistake. i found the issue. thank you for your quick response. layer 8 issue. lol

  3. Hello Rene

    I followed all the step but still see some issue in traceroutes .I guess if the destination is 5.5.5.5 and we are load balancing we have 2 path via R2 & R3 .why do I see both R2& R3 ip in the traceroute .

    ## traceroute :
    R1#traceroute 5.5.5.5
    
    Type escape sequence to abort.
    Tracing the route to 5.5.5.5
    
      1 192.168.13.3 64 msec
        192.168.12.2 64 msec
        192.168.13.3 64 msec
      2 192.168.25.5 60 msec
        192.168.35.5 64 msec
        192.168.25.5 60 msec
    R1#sh clock
    *14:34:04.131 UTC Sat Aug 19 2017
    
    
    
    R1#traceroute 5.5.5.5 source 192.168.13.1
    
    Type escape sequence to abort.
    Tracing the route to 5.5.5.5
    
      1 192.168.12.2 64 msec 60 msec 64 msec
      2 192.168.25.5 88 msec 64 msec 68 msec
    R1#traceroute 5.5.5.5 source 192.168.12.1
    
    Type escape sequence to abort.
    Tracing the route to 5.5.5.5
    
      1 192.168.12.2 36 msec 64 msec
        192.168.13.3 68 msec
      2 192.168.25.5 92 msec
        192.168.35.5 64 msec
        192.168.25.5 60 msec
    R1#traceroute 5.5.5.5 source 192.168.13.1
    
    Type escape sequence to abort.
    Tracing the route to 5.5.5.5
    
      1 192.168.13.3 64 msec
        192.168.12.2 76 msec
        192.168.13.3 80 msec
      2 192.168.25.5 92 msec 60 msec 72 msec
    R1#sh clock
    *14:34:54.827 UTC Sat Aug 19 2017
  4. Hello Rahul

    This is normal behaviour of traceroute when you have two equal cost routes. Traceroute sends ICMP packets and since both routes are equal, it will send them via both routes.

    So for your first attempt, you get the following:

    Note that for the first hop, indicated by the number 1, it shows three lines. The first is the first choice, the second is the second choice and the third is the actual route that was chosen between the two. So for the first hop, 192.168.13.3, or R3 was chosen as the route.
    The second hop, indicated by the number 2 also has two options, because both routes via R2 and R3 were used and there are two options to choose from once again. So either Fa 0/0 or Fa1/0 of R5 will be used as the next hop. We are told in the third line that 192.168.25.5 or Fa0/0 is used.

    In the next case, you are explicitly stating that you want to use interface E1/0 or IP address 192.168.13.1 as the traceroute source:

    Because you are stating this, there is no option of using the load balancing capabilities of EIGRP so only one option is indicated in each case.

    Now having said all of this, if the route via R2 and R3 from R1 were UNEQUALLY load balanced (using the variance command), this wouldn’t occur. Only one option would be displayed and used. You would only see one choice for each hop. The multiple choices for each hop indicate that there is EQUAL load balancing between the R2 and R3 routes. So you should check your configuration and make sure it is load balancing UNEQUALLY using the variance command.

    I hope this has been helpful!

    Laz

  5. Hi,

    I would like to know if you need to configure variance on R1 and R5 for the return traffic? I believe if you need to reach the network 5.5.5.5 from R1, variance needs to be configured on R1. But how about the return traffic of the packet? I believe this will only use the successor path going back, is that right?

    Thanks,

33 more replies! Ask a question or join the discussion by visiting our Community Forum