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

 

351 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!


Forum Replies

  1. Hi Rene,

    R2#
    interface FastEthernet0/0
    ip summary-address eigrp 12 172.16.0.0 255.255.0.0 5
    
     
    
    
    

    What does the number 5 mean in the show information above ?

     

    And what about leak-map ? when do we use it ?

     

    R1(config-if)#ip summary-address ei 1 172.16.0.0 255.255.254.0 ?
    leak-map Allow dynamic prefixes based on the leak-map
    <cr>
    

    thanks.

  2. Hi Hussein,

    The “5” here is the administrative distance of the summary.

    The leak-map option can be used to “leak” certain prefixes from your example. You can use this to advertise a prefix that normally falls within the range of your summary.

    For example, let’s say you want to advertise summary 172.16.0.0/16 but also one specifix prefix, 172.16.1.0/24. You can use the leak map to get 172.16.1.0/24 “out” of the summary so that it can be advertised.

    Rene

  3. Hi Renee,

    I didn’t see a topic on this. But is there a way to perform preferred route selection based on a source prefix from the local router? For example lets say I have a router that has two equal cost paths to a network. Let’s say this router has three prefixes it is advertising too. Lets say that only for one prefix will choose one explicit path and the other two prefixes will still use equal load balancing. The config should be made on the local router advertising the prefixes. Can this be done with EIGRP?

  4. Hi Mario,

    Routers normally only care about the destination, that’s it.

    If you want to make routing decisions based on the source then you can use policy based routing, take a look here:

    How to configure policy based routing

    Rene

Ask a question or join the discussion by visiting our Community Forum