Michael, One think to look for is recursion of next-hops. What is the next hop for the route to 145.45.35.35?
On Fri, Aug 21, 2009 at 1:00 PM, Michael Lipsey <[email protected]>wrote: > So – having spent far too much time on one single task I am still left > with some problematic behavior. > > > > The idea is that each router has a pair of loopbacks addressed 10.2.x.x and > 10.3.x.x. > > > > The task is to configure BGP so that 10.2.x.x circles clockwise and > 10.3.x.x circles counter clockwise. > > > > Fun eh? Far from impossible and I did it first with local preference > adjustment and then per the proctor guide’s solution (weight). Both worked > about the same and I ran into about the same problems at different points. > I think with this small of a network local preference and weight are about > equal in effect since each AS most of time is a single router. > > > > Except in one spot – that’s where the major problems are but those are > workable too. > > > > Right now I’m just getting super odd behavior on R4 which has a peer with > R6 and Cat 1 (145.45.35.35). > > > > Here is what I’m seeing – the routes in the route table look correct for my > route to 10.2.5.5 and the BGP table looks right too. > > > > R4(config-router)#do sho ip bgp 10.2.5.5 > > BGP routing table entry for 10.2.5.5/32, version 55 > > Paths: (1 available, best #1, table Default-IP-Routing-Table) > > Advertised to update-groups: > > 1 > > 89 5 > > 145.45.35.35 (metric 20) from 145.45.35.35 (145.45.35.35) > > Origin IGP, localpref 100, weight 32000, valid, external, best > > R4(config-router)#do sho ip route 10.2.5.5 > > Routing entry for 10.2.5.5/32 > > Known via "bgp 4", distance 20, metric 0 > > Tag 89, type external > > Last update from 145.45.35.35 00:06:29 ago > > Routing Descriptor Blocks: > > * 145.45.35.35, from 145.45.35.35, 00:06:29 ago > > Route metric is 0, traffic share count is 1 > > AS Hops 2 > > Route tag 89 > > > > When I do a trace route though I get this: > > > > R4(config-router)#do traceroute 10.2.5.5 > > > > Type escape sequence to abort. > > Tracing the route to 10.2.5.5 > > > > 1 145.45.245.6 4 msec 0 msec 0 msec > > 2 145.45.245.4 4 msec 4 msec 0 msec > > 3 * * * > > 4 > > > > Which is clearly wrong – I can’t even fathom why it’s trying to send the > packets that way when the routes say do something else entirely. Maybe I’ve > fried myself and I can’t see the issue. > > > > O_o I hate this lab. > > > > -Mike > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Bryan Bartik CCIE #23707 (R&S), CCNP Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
