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!

Tags: , ,


Forum Replies

  1. “You can use this for both eBGP and iBGP but there is one catch…the remote routers have to be in the same AS.”

    If the clause says remote routers have to be in same AS, doesn’t it mean it is iBGP ?? How does dynamic peering then supported in eBGP scenario ?

    I may be wrong, just to clarify

  2. Hi Ren,

    Could you help me clarify the difference between 0.0.0.0/0 and 0.0.0.0/32. According to my understanding, 0.0.0.0/0 means any network. However, in this lab, when we use 0.0.0.0/0 in the Prefix-list, why was only default route permitted but not any prefixes?

    Thanks.

  3. “we’ll start with eBGP with the same AS number on all spokes”. It’s probably a typo error. Should be different AS number on each spoke ?

  4. kayoutoure’s typo comment still not fixed. and another one below also:

    “The default route is installed and we can see 1.1.1.1/32. It would be best to get rid of the network command on the hub, we don’t need this entry. Let’s see if the spokes can still reach each other:”

    Removing the network command (network 0.0.0.0) also removes default route from spokes. Spokes no longer can reach each other.

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