[c-nsp] Redistributed connected / static prefixes to upstream and set as-path prepend

James Bensley jwbensley at gmail.com
Mon Nov 6 04:32:26 EST 2017

> On Wed, Oct 25, 2017 at 1:24 AM, CiscoNSP List <CiscoNSP_list at hotmail.com>
> wrote:
>> Hi,


>> We are redistributing our own prefixes via iBGP with redist connected +
>> static with route-map :
>> router bgp AAAA
>>  address-family ipv4
>>   redistribute connected route-map OUR_RANGES
>>   redistribute static route-map OUR_RANGES
>> route-map OUR_RANGES permit 10
>>  match ip address prefix-list PL_OUR_RANGES
>>  set community AAAA:1000 AAAA:1301 AAAA:14000
>> ip prefix-list PL_OUR_RANGES seq 5 permit XXX.XXX.XXX.0/20 le 32
>> Which is working fine

I guess you managed to sort out that issue as per your other thread
when the community wasn't being added?

On 1 November 2017 at 18:55, Florin Florian <florin.florian at gmail.com> wrote:
> Hi,
> You have to use the "ip bgp-community new-format" in order to see the
> community in the format.
> You should try to configure "neighbor x.x.x.x send-community" for the
> community to be sent to the peer (upstream provider in this case).
> Setting it in the route-map alone will not do it.

Assuming you have enabled send-commuity on your upstream facing session...

>> #sh ip bgp neighbors  WWW.WWW.WWW. advertised-routes
>>      Network          Next Hop            Metric LocPrf Weight Path
>>  *>i XXX.XXX.XXX.0/20  YYY.YYY.YYY.218           0    100      0 ?

This won't show you the pre-pends. This command shows the routes
before they are processed by any policies, you can't see them
post-processing in IOS/IOS-XE. You'd need to capture the BGP UPDATE
messages on the wire or get your peer to send you output from their
router (or check their looking glass if they have one). I don't think
you can see AS-PATH in debug messages.


More information about the cisco-nsp mailing list