Some others come to mind...
1. update source address issues
2. next hop self (with and without using the "next-hop-self" argument of the neighbor address)
3. ebgp-multihop when don't expect it - like when using tricky routing features that cause ebgp-multihop to be required to make the peer come up.
4. Route-reflector issues effecting next hop - cluster id, cluster list
Can you post the questions if any you have seen which caused your doubts?
The trickiest thing I faced in my studies was having to use ebgp-multihop with issues where I had "ip unnumbered" and similar features configured.
-Joe
-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Jeferson Guardia
Sent: Thursday, August 05, 2010 12:06 AM
To: groupstudy
Subject: BGP blueprint doubt
GS,
While going through INE`s expanded blueprint, I found this topic under the
BGP`s section.
(2) Next Hop Issues
What kind of issues can I expect with next hop besides the problem on BGP
not installing a prefix on its network table
when it doesnt know how to reach the next hop via IGP? Any other thoughts on
this matter? I could not clearly get
to the point that the blueprint is asking on this item.
Best regards,
Blogs and organic groups at http://www.ccie.net
Received on Thu Aug 05 2010 - 01:11:11 ART
This archive was generated by hypermail 2.2.0 : Wed Sep 01 2010 - 11:20:52 ART