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

426 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. @ReneMolenaar @lagapides have a question concerning the filter-list filtering. This may sound like a silly question. Why did you do the configurations to add AS 11 to the AS path out going 2001:db8:0:1::/64 traffic on R1. Why didn’t you do it on router R2?.

    R1(config)#router bgp 1
    R1(config-router)#address-family ipv6
    R1(config-router-af)#**neighbor 2001:db8:0:12::2** route-map PREPEND out

    Since we are using the neighbor command. Shouldn’t the command be affecting the neighbor router and not the local router. Please, i need clarification.

  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