Error: `EIGRP is restricted to stub configurations only on this platform`

  • We just bought some new Cat4507R+E distribution switches. When we bought the switches, we asked for an Advanced Services K9 image, but our reseller told us they only come with a Universal K9 image. I didn't know better, so I said OK.

    However, when I tried to bring the switches online in production, I had a problem with a huge number of unreachable subnets. After sweating it for a very long fifteen minutes (while my boss insulted me for not testing the switch), I finally tracked the problem down to eigrp stub connected in the EIGRP process.

    I tried remove the "eigrp stub" statement but I couldn't. When I tried, the switch errors out with EIGRP is restricted to stub configurations only on this platform.

    I had to roll back to our original distributions and my boss got even hotter about it.

    My google searches blame this problem on the ip base license, which only supports EIGRP stub routing. Our reseller says it will take at least 24 hours and thousands of dollars to get the Advanced Services K9 upgrade. We didn't budget for the extra expense and we have other business units waiting on the upgrade. Oh yeah, and my boss isn't happy.

    Before we borrow money from another department, is there anything else we can do to get this working now?

  • I really don't like how Cisco crippled EIGRP in the ipbase image... at a minimum, you should get some kind of warning that your configuration won't work, but they haven't done that either.

    As you discovered, eigrp stub prevents EIGRP from advertising downstream routes from the switches connected to your distribution.

    You can trick EIGRP into advertising routes it learned from other rotuers (even as a stub router) by using a stub leak-map...

    ip prefix-list p~MATCH_ANY seq 5 permit 0.0.0.0/0 le 32
    !
    route-map r~MATCH_ANY permit 10
     match ip address prefix-list p~MATCH_ANY
    !
    router eigrp 100
     no auto-summary
     network 172.16.0.0
     eigrp log-neighbor-warnings
     eigrp log-neighbor-changes
     eigrp stub connected summary static redistributed leak-map r~MATCH_ANY
    

    Technically, you can get away with using eigrp stub leak-map indefinitely, without upgrading your ipbase image.

    We indeed had the same problem and also solved it with the stub leak feature? Works well

    Thanks, above solution is working perfectly for me. however i am in process to upgrade the IOS but this solution made be confident that this was IOS level issue only.

    As today this is still working or was already patched in latest iOS releases? Another question: can I do this trick in the IP Lite IOS version?

License under CC-BY-SA with attribution


Content dated before 7/24/2021 11:53 AM