Here you can see different scenarios: http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a00800945bf.shtml#conf1
I think that multiple sessions is more stable variant, although it requires more memory. Peering with loopbacks won't work in case any of the links is up, but does not forward traffic. Static route persists but session is down. Only dynamic routing will help that way. On 17 July 2011 22:25, marc abel <[email protected]> wrote: > If you have two ebgp neighbors with multiple links between them, what > is the best way to handle the peering? You could make a separate > peering over each link, or you could peer between loop-backs. Are > there drawbacks to one over the other? What are the considerations > here. > > With loopbacks it would seem you need to make sure that the loopbacks > are reachable to each other as well as add ebgp multi-hop to the > configs. > With two separate links, you have twice the config, and probably need > to make sure filtering and such is done on both links. > > What else? > > Thanks, > > Marc > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
