From: Moin, Imran (imoin@virtela.net)
Date: Mon Feb 20 2006 - 01:26:21 GMT-3
Victor,
This was a tricky requirement. Normally, on R2, you would prepend the Local AS on the peer relation with R5. However, in Task 5.4, you configured the weight on this BGP announcement to be 100. Therefore, traffic for Vlan 2 will always go from R5 to R2, since Weight gets preferred over AS_PATH_PREPEND in the BGP decision process.
Therefore, the solution to this problem is BGP conditional advertisement. Since the prefix watched under "non-exist-map" needs to be present in the BGP table, the HDLC link between R2 and R3 has to be announced via BGP.
Hope this helps.
-Imran.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Victor Cappuccio
Sent: Sunday, January 15, 2006 5:24 PM
To: ccielab@groupstudy.com
Subject: IEWB-RS Lab 3 Vol3 Task 5.5
All,
IEWB-RS Lab 3 Vol3 Task 5.5, the solution guide is advertising the HDLC link
and also uses the BGP Conditional Advertisement, Why??
Is there any special reason for this..
I believe that this task could also be done by prepending the Local AS to
peer relation with R5
Comments are appreciated
Thanks
Victor.
This archive was generated by hypermail 2.1.4 : Wed Mar 01 2006 - 11:28:18 GMT-3