From: Richard Gallagher (rgallagh@cisco.com)
Date: Thu Aug 19 2004 - 09:59:59 GMT-3
Did you try to debug it? Works for me:
Router1#debug ip bgp updates out
BGP updates debugging is on (outbound)
Router1#
Router1#
*Aug 19 12:58:33.538: %BGP-5-ADJCHANGE: neighbor 10.0.0.2 Up
*Aug 19 12:58:33.766: BGP(0): 10.0.0.2 computing updates, afi 0, neighbor version 0, table version 6, starting at 0.0.0.0
*Aug 19 12:58:33.766: BGP(0): 10.0.0.2 send UPDATE (format) 10.10.10.1/32, next 10.0.0.1, metric 0, path
*Aug 19 12:58:33.766: BGP(0): 10.0.0.2 1 updates enqueued (average=56, maximum=56)
HTH, Rich
On Thu, 2004-08-19 at 14:35, gladston@br.ibm.com wrote:
> Is there a way to check the BGP attributes of advertised routes from R2 to R3 using commands on R2 (suppose you can not access R3)
>
> For example,
>
> r2#sh ip bgp ne 172.16.23.3 advertised-routes
> BGP table version is 42, local router ID is 172.16.2.2
> Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 172.16.1.0/24 172.16.12.1 0 0 1 i
>
> R2 is advertising 172.16.1.0 to R3, but the Next Hop and Path are not the attributes used on the UPDATE send to R3.
>
> Below are the attributes received by R3, but is there a way to see them on R2 besides debuging?
>
> r3#sb
> BGP table version is 36, local router ID is 172.16.3.3
> Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 172.16.1.0/24 172.16.23.2 0 2 1 i
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:46 GMT-3