This blog was originally started to better help me understand the technologies in the CCIE R&S blueprint; after completing the R&S track I have decided to transition the blog into a technology blog.
CCIE #29033
This blog will continue to include questions, troubleshooting scenarios, and references to existing and new technologies but will grow to include a variety of different platforms and technologies. Currently I have created over 185 questions/answers in regards to the CCIE R&S track!! Note: answers are in the comment field or within "Read More" section.
You can also follow me on twitter @FE80CC1E
The routing table on R3 should be able to reach 192.168.1.0/24 through 192.168.2.2 and not through 192.168.3.5.
Restrictions: You cannot modify administrative distance or do any type of filtering. The network192.168.1.0/24 must be advertised on R2 in both OSPF and BGP. You must ensure that R2 and R3 are not sending OSPF advertisements to R5. R5 can only use BGP as its routing protocol and must advertise its loopback.
2 comments:
My first option would be to use the "network 192.168.1.0 backdoor" BGP command on R3.
My second option could be to enable BGP between R2 and R3 (on 192.168.2.x/24 net).
Thats right!
R3
__
router bgp 300
network 192.168.1.0 mask 255.255.255.0 backdoor
Your second option would have worked since I did not specifically restrict creating an EBGP relationship between R2 and R3. (although I tried to indicate such in the drawing :) )
Good stuff!
Post a Comment