EIGRP stub

Task 7.3 suggests setting R16 and R17 as EIGRP stub to prevent the hub router R18 from sending QUERY packets in case a route goes active. I agree that this is the desired method, but there is a problem with the "servers", i.e. the VRFs on R15. If you do as the solution guide suggests, R15 loses all of his routes beyond the DMVPN spoke routers.

I originally thought I would include summary routes and advertise a default towards R15, but this breaks OSPF on R16. I'm wondering if any of you have an opinion on how to get around this problem. Perhaps we could add all the routes received via R18 into a leak-map.

Comments

  • The task solutions have been slightly modified to account for this issue - please revisit the solution. 

  • Looks good - thanks!

  • I solved this lab recently and my solution was exactly to use a leak-map, since I didn't think about using summarization. Here is what I did on R16 and R17 and worked fine so far: (I know some prefix-list lines may not be necessary on both but time is money [8-|])

    ip prefix-list PL_LEAK permit 172.23.160.0/24

    ip prefix-list PL_LEAK permit 172.25.170.0/24

    ip prefix-list PL_LEAK permit 172.27.192.0/24

    ip prefix-list PL_LEAK permit 192.122.3.17/32

    ip prefix-list PL_LEAK permit 192.122.3.19/32

    ip prefix-list PL_LEAK permit 192.122.3.20/32

    !

    route-map RM_LEAK permit 10

     match ip address prefix PL_LEAK

    !

    router eigrp 123

     eigrp stub connected redistribute leak-map RM_LEAK

Sign In or Register to comment.