the "output" of the command you have executed locally will *always* display the *real* next-hop! Execute the sh ip bgp <neigh> routes/received-routes - depending on config to *see* what your peer sees as next-hop!
The more-important question *IS* - why do you have 'next-hop-self' configured? 1) e-bgp-speaker speaker sending updates to its i-bgp peer/s? 2) All peers(E an I on same broadcast segment OR part of an NBMA-cloud)- the behavior is the same! ./Randy --- On Sat, 10/8/11, "Rolf Hanßen" <[email protected]> wrote: > From: "Rolf Hanßen" <[email protected]> > Subject: [c-nsp] Output of bgp advertised-routes with next-hop-self > To: [email protected] > Date: Saturday, October 8, 2011, 4:12 PM > Hi, > > I was just wondering about the output of: > sh bgp ipv6 unicast neighbors xxxxx advertised-routes > sh ip bgp neighbors xxxxx advertised-routes > > I have configured "next-hop-self" and think that the "Next > Hop" column > should show the IP of my side of the (e)BGP session. > Quagga and Foundry XMR behave that expected way, Cisco 7600 > does not > (shows my internal nexthop no matter with or without > "next-hop-self", > shutting session has no influence either). > > Is that a bug or a "feature" ? > > Version: > Cisco IOS Software, c7600s72033_rp Software > (c7600s72033_rp-ADVIPSERVICESK9-M), Version 15.1(2)S, > RELEASE SOFTWARE > (fc1) > > kind regards > Rolf > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
