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 606 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)


363 New Members signed up the last 30 days!


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

Forum Replies

  1. Hi Andrew,

    First off, Thank you for extending your help!

    I want to accomplish this WITHOUT distributing or redistributing into EIGRP neighbors within the same AS. I actually tried your recommendation (below) last week in my lab, thinking it would work, but apparently it didn’t!

    R1(config)#router eigrp 1

    Here’s what R1 has in its RIB table as static:

    ip route
    ip route (needs to be routed via EIGRP all the way to R4)
    ip route
    ip route (needs to be routed via EIGRP all the way to R4)
    ip route

    Also, I tried the following lab on actual Cisco routers and created 4 static routes on Carl, advertised two out of 5 static routes from Carl by using “network” and “” thinking they’d show up on Kingkong, Preston, and Ann. But no luck. I made up the default static route to see if I could advertise only two specific static routes.

    Andrew, please let me know if you have any questions. Much Appreciated!


  2. Hi Andrew,

    My lab is setup exactly as follows

    Only difference is that I added 6 static routes on Carl and attempted to advertise 2 out of 6 from Carl so they would show up on other EIGRP routers. No LUCK! What am I missing?

    However, it works with discard route (tested successfully), distribute-list / redistribution (as you suggested earlier). But it just wouldn’t work / propagate with a simple static and network cmd to other routers.

    Please take a look at the attached file.


  3. andrew says:

    Hi Syed,
    I have an answer for you. Your detailed information was very helpful, so thanks for that. EIGRP does NOT advertise static routes (except if you tell it to do redistribution), unless it considers the route to be connected to a local interface. To understand this, you should know that static routes can be defined two different ways:

    1. The route can point to a next hop address, as you have done: ip route
    2. The route can point to an interface such as: ip route serial0/0/0

    When you use an interface as the destination, the router assumes this is a point-to-point connect so there is only one possible destination (the router on the other side). In an multi-access environment, such as Ethernet, this will not work because there could be multiple devices on the other end of the connection.

    Now, let’s tie this back to EIGRP. As odd as it may seem, EIGRP considers any static route with an interface as a destination to be “directly connected” and thus eligible for advertisement within EIGRP via a “Network” statement. You can test this by doing the following:

    no ip route
    ip route null0

    By changing the static route from using a next hop destination to an interface destination (null 0 counts as an interface), you should see this route being shared within EIGRP.

    Now that you know this, you can solve your original problem where you had Internet->ASA-> R1-> R2 -> R3-> R4. You have to cheat a bit to do it, though. If you are determined not to use static route redistribution with a distribute-list for filtering, you can create a “fake” summary route on R1 that includes -, route that to null0, and it will be advertised via EIGRP. Try this via R1:

    R1(config)#ip route null0
    R1(config)#ip route null0
    R1(config)#router eigrp 1

    When you do this, R4 will be able to route to and without a default route like you wanted, but there will be extra subnets in there as well. If you wanted precisely just the 3 and 5 network, you would have to use redistribution with a distribute-list filter.


  4. Hello Linda!

    When you add the EIGRP implementation, make sure you are configuring the static neighbour relationship correctly.

    The frame-relay map <em>protocol protocol_address</em> [broadcast] command forwards broadcasts to the specified address when multicast is not enabled. By using static neighbour relationships for EIGRP we are inherently using only unicast so this command would make no difference.

    Check your config again and if you still have problems, copy and paste the relevant parts of your config so we can take a look.

    I hope this was helpful!


  5. Hello Hussein.

    When you set up a static neighbour on an EIGRP enabled interface of a router, the interface changes to using unicast EIGRP updates to the specific neighbour. This DISABLES multicast updates. You cannot have both unicast and multicast functioning on the same interface. They are mutually exclusive.

    I hope this has been helpful!


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