Hello Syed The issue you are observing is simply because of Synchronization rule. As you mentioned that all routers are configured with no synchronization , the router R3 is behaving as Black hole. You may be able to see the routes at R2 but not a R3 . R3 won't be having any information about the networks.
To resolve the issue either you need to redistribute the BGP into IGP (which you don't want) or you can configure MPLS, core router don't have CE information. HTH On Mon, Oct 19, 2009 at 2:26 PM, Syed Zaidi <[email protected]> wrote: > Hi, > I have made the attached BGP setup on GNS3 running on Ubuntu to test my > skills with this protocol and I have managed to attain a full connectivity > between all the subscribers including at the time of failover on any link, > especially for multihomed subscribers, but I have a few queries, which I > would be glad to receive answers for, but before that I would like to > mention the configuration details of TRANSIT BGP AS. > > OSPF is the IGP with passive interface configure at ebgp peering > interfaces. > iBGP is fully meshed in both the transit AS with "no syncronization". > All ebgp & ibgp peering is between loopback interfaces. > Default routes are configured on all subscribers to the transit AS, with > multihomed subscribers having two default routes to each transit AS. > Static routes are configured to reach loopbacks between ebgp neighbors. > > Query.. > Within the AS I am able to ping the subsribers only from ebgp peers. > for ex: if I ping 4.4.4.4 from R1 to R4 it is successful but when I ping > 9.9.9.9 from R1 to R14 i get timeouts. > I have remedied this issue by redistributing ospf into bgp in both the > transit AS, this has led to announcing of internal routes on both the > transit AS to each other and to the subscribers as well. With this I can > successfully ping 9.9.9.9 from R1 to R14. > > What I would liked to do is this.. > > I don't want to announce internal subnets of both the transit AS by > redistributing or adding network statements but still achieve pinging from > R1 to R14, how can I do this? > > Without redistributing or adding a network statement I am very much stuck > up in troubleshooting connectivity issues between R3 to R4 & R5 loopbacks or > R13 to R4 & R5 Loopbacks. > > What would be the most simplest method of achieving a full connectivity > both between all the subscribers and within each router of a transit AS to > subscribers with announcing my internal routes?? > > Pls note that I don't intend to redistribute BGP into IGP in both the > transit ASs > > Thanks & lot... > > With Regards, > Syed > > > > > > > > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Thanks®ards Vishal +91-997111066 Best way to predict the future ..... is to create it
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
