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

478 Sign Ups in the last 30 days

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


Forum Replies

  1. Hi Rene,

    I think that it is a errata:

    This prefix-list checks the entire 2001::/16 range and permits subnets with a /64 or larger.
    It should be:

    This prefix-list checks the entire 2001::/16 range and permits subnets with a /64 o smaller

    Thanks you

  2. Cisco documentation from 2016 provides different order for outbound filtering:

    For inbound updates the order of preference is:
    prefix-list, distribute-list

    For outbound updates the order of preference is:

    route-map | unsuppress-map
    advertise-map (conditional-advertisement)
    ORF prefix-list (a prefix-list the neighbor sends us)


  3. @lagapides I understand. I am just a little bit confuse because when you use the neighbor command, it is most time used to configure things on neighbor router. But in this case, it is used to configure AS-PATH on the local Router (R1). What if instead of doing:

    R1(config)#neighbor 2001:db8:0:12::2 route-map PREPEND out

    i do the configurations from R2. I configure the ipv6 prefix-list and route-map on R2 and then use the command;

    R2(config)#neighbor 2001:db8:0:12::1 route-map PREPEND out

    Will this also work?.

  4. @lagapides thank you for clearing that out. That helped me a lot. Now i have a better understanding.

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