On my previous post I said that the problem was on R3. It could also have
been on R2, if R2 rejected the update....

I used a debug on R2 to locate the problem. R3 did send the update but R2
rejected it. Please note the keyword "withdrawn" at the end of the output
below:

R2#
1d11h: %BGP-5-ADJCHANGE: neighbor 10.10.1.2 Down User reset
1d11h: %BGP-5-ADJCHANGE: neighbor 10.10.2.2 Down User reset
1d11h: %BGP-5-ADJCHANGE: neighbor 10.10.1.2 Up
1d11h: BGP(0): 10.10.1.2 computing updates, afi 0, neighbor version 0, table
version
1, starting at 0.0.0.0
1d11h: BGP(0): 10.10.1.2 update run completed, afi 0, ran for 0ms, neighbor
version 0
, start version 1, throttled to 1
1d11h: BGP(0): 10.10.1.2 rcvd UPDATE w/ attr: nexthop 10.10.1.2, origin i,
metric 0,
path 101
1d11h: BGP(0): 10.10.1.2 rcvd 172.16.0.0/16
1d11h: BGP(0): Revise route installing 172.16.0.0/16 -> 10.10.1.2 to main IP
table
1d11h: %BGP-5-ADJCHANGE: neighbor 10.10.2.2 Up
1d11h: BGP(0): 10.10.2.2 computing updates, afi 0, neighbor version 0, table
version
2, starting at 0.0.0.0
1d11h: BGP(0): 10.10.2.2 send UPDATE (format) 172.16.0.0/16, next 10.10.2.1,
metric 0
, path 101
1d11h: BGP(0): 10.10.2.2 1 updates enqueued (average=46, maximum=46)
1d11h: BGP(0): 10.10.2.2 update run completed, afi 0, ran for 12ms, neighbor
version
0, start version 2, throttled to 2
1d11h: BGP(0): 10.10.2.2 rcvd UPDATE w/ attr: nexthop 10.10.2.2, origin i,
path 103 1
00 101
1d11h: BGP(0): 10.10.2.2 rcvd 172.16.0.0/16
1d11h: BGP(0): 10.10.1.2 computing updates, afi 0, neighbor version 1, table
version
2, starting at 0.0.0.0
1d11h: BGP(0): 10.10.1.2 update run completed, afi 0, ran for 0ms, neighbor
version 1
, start version 2, throttled to 2
1d11h: BGP(0): 10.10.2.2 rcv UPDATE about 172.16.0.0/16 -- withdrawn


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=51188&t=51169
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to