Equal Cost Load Balancing in EIGRP

MrXpertMrXpert Member Posts: 586 ■■■□□□□□□□
in CCNP
I have three routers setup in a full mesh serial link topology. All interfaces have the same T1 bandwidth. Problem i'm having is that I can't seem to get load balancing working.For example R1 has two paths to get to the network between R2 and R3.

R1's routing table is this

C 192.168.12.0/24 is directly connected, Serial0/0
C 192.168.13.0/24 is directly connected, Serial0/1
D 192.168.23.0/24 [90/2681856] via 192.168.13.3, 00:17:52, Serial0/1
[90/2681856] via 192.168.12.2, 00:17:52, Serial0/0



However when I ping 192.168.23.2 or 192.168.23.3 he ALWAYS sends each packet to R3. He seems to love R3.

R2's routing table is this:

C 192.168.12.0/24 is directly connected, Serial0/0
D 192.168.13.0/24 [90/2681856] via 192.168.23.3, 00:19:44, Serial0/1
[90/2681856] via 192.168.12.1, 00:19:44, Serial0/0
C 192.168.23.0/24 is directly connected, Serial0/1

to reach the 192.168.13.0/24 network R2 sends every packet to 192.168.12.1 (R1). Why won't he send it to 192.168.23.3(R3). I verified this with debug ip packet. Have they had a fight? am i missing something?
I'm an Xpert at nothing apart from remembering useless information that nobody else cares about.
· Share on FacebookShare on Twitter

Comments

  • Architect192Architect192 Member Posts: 157 ■■■□□□□□□□
    MrXpert wrote: »
    I have three routers setup in a full mesh serial link topology. All interfaces have the same T1 bandwidth. Problem i'm having is that I can't seem to get load balancing working.For example R1 has two paths to get to the network between R2 and R3.

    R1's routing table is this

    C 192.168.12.0/24 is directly connected, Serial0/0
    C 192.168.13.0/24 is directly connected, Serial0/1
    D 192.168.23.0/24 [90/2681856] via 192.168.13.3, 00:17:52, Serial0/1
    [90/2681856] via 192.168.12.2, 00:17:52, Serial0/0



    However when I ping 192.168.23.2 or 192.168.23.3 he ALWAYS sends each packet to R3. He seems to love R3.

    R2's routing table is this:

    C 192.168.12.0/24 is directly connected, Serial0/0
    D 192.168.13.0/24 [90/2681856] via 192.168.23.3, 00:19:44, Serial0/1
    [90/2681856] via 192.168.12.1, 00:19:44, Serial0/0
    C 192.168.23.0/24 is directly connected, Serial0/1

    to reach the 192.168.13.0/24 network R2 sends every packet to 192.168.12.1 (R1). Why won't he send it to 192.168.23.3(R3). I verified this with debug ip packet. Have they had a fight? am i missing something?

    You have to use traceroute to see where the packet goes, not ping. Did you try that?
    Current: VCAP-DCA/DCD, VCP-DCV2/3/4/5, VCP-NV 6 - CCNP, CCNA Security - MCSE: Server Infrastructure 2012 - ITIL v3 - A+ - Security+
    Working on: CCNA Datacenter (2nd exam), Renewing VMware certs...
    · Share on FacebookShare on Twitter
  • RoguetadhgRoguetadhg Member Posts: 2,489 ■■■■■■■■□□
    What does the "show ip eigrp topology all-links" show?
    In order to succeed, your desire for success should be greater than your fear of failure.
    TE Threads: How to study for the CCENT/CCNA, Introduction to Cisco Exams

    · Share on FacebookShare on Twitter
  • unclericounclerico Member Posts: 237 ■■■■□□□□□□
    Disable CEF and set load balancing per packet. That string of pings is a single flow so each one will go the same route. Edit: disable CEF only to watch load balancing in action. Re-enable it after your done.
    Preparing for CCIE Written
    · Share on FacebookShare on Twitter
  • MrXpertMrXpert Member Posts: 586 ■■■□□□□□□□
    unclerico wrote: »
    Disable CEF and set load balancing per packet. That string of pings is a single flow so each one will go the same route. Edit: disable CEF only to watch load balancing in action. Re-enable it after your done.

    Thanks so much! that resolved it
    I'm an Xpert at nothing apart from remembering useless information that nobody else cares about.
    · Share on FacebookShare on Twitter
Sign In or Register to comment.