As Hobbs mentioned do a "sh ip bgp neighbor <your bgp peer>" and look for the prefix activity part which will tell you about prefixes that didn't get sent to that peer for various reasons.
Have you looked at the communities attached to the prefixes you have learnt from your other peer that you aren't advertising?, do they have either no-advertise/no-export/local-as etc. on them? is the peer your receiving the feed from iBGP or eBGP? and is the peer your sending them to iBGP or eBGP? On Wed, Nov 18, 2009 at 5:40 PM, Skeeve Stevens <ske...@eintellego.net>wrote: > But, the router isn't even sending them to the next router... between > tagging them and re-sending them, they just aren't there.... so I would > assume the neighbour they are being sent to is nothing to do with it? > > ...Skeeve > > -- > Skeeve Stevens, CEO/Technical Director > eintellego Pty Ltd - The Networking Specialists > ske...@eintellego.net / www.eintellego.net > Phone: 1300 753 383, Fax: (+612) 8572 9954 > Cell +61 (0)414 753 383 / skype://skeeve > www.linkedin.com/in/skeeve ; facebook.com/eintellego > -- > NOC, NOC, who's there? > > > > > > Not sure off-hand, but you can do show ip bgp neighbor and far down in > > the > > output you will see a section showing stats about why prefixes were > > dropped > > (route-map, dist-list, etc). What does it say? > > _______________________________________________ > > cisco-nsp mailing list cisco-nsp@puck.nether.net > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
