From: gladston@br.ibm.com
Date: Thu Aug 19 2004 - 09:35:02 GMT-3
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
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:46 GMT-3