BGP SoO extcommunity not attached to prefix update

mkoschay123 · ‎03-04-2016

Can anybody explain me why the ASR is ignoring the soo community in my route-map export-400 config?

vrf definition 400
rd 172.16.224.7:400
!
address-family ipv4
import map import-400
export map export-400
exit-address-family

ip extcommunity-list standard vpn-400 permit rt 65000:400
ip extcommunity-list standard soo-400-3040 deny soo 65000:4003040
ip bgp-community new-format

route-map import-400 permit 10
match extcommunity vpn-400
!
route-map export-400 permit 10
set extcommunity soo 65000:4003040
set extcommunity rt 65000:400
!
route-map soo-vpn-400 permit 10
set extcommunity soo 65000:4003040

Source-PE Update
Mar 4 2016 11:41:22.431 MET: BGP(4): (base) 172.16.224.1 send UPDATE (format) 172.16.224.7:400:10.140.150.0/24, next 172.16.224.7, label 50, metric 0, path Local, extended community RT:65000:400

Received-PE (Junos)

Received-PE (Junos)
show route table bgp.l3vpn.0 10.140.150.0/24 community 65000:* detail

bgp.l3vpn.0: 16 destinations, 32 routes (16 active, 0 holddown, 0 hidden)
172.16.224.7:400:10.140.150.0/24 (2 entries, 0 announced)
*BGP Preference: 170/-101
Route Distinguisher: 172.16.224.7:400
Next hop type: Indirect
Address: 0x934d0f0
Next-hop reference count: 3
Source: 172.16.224.2
Next hop type: Router, Next hop index: 733
Next hop: 172.16.224.65 via ge-3/0/2.0, selected
Label operation: Push 34, Push 301328(top)
Label TTL action: prop-ttl, prop-ttl(top)
Protocol next hop: 172.16.225.7
Push 34
Indirect next hop: 95e4740 262152
State: <Active Int Ext>
Local AS: 65000 Peer AS: 65000
Age: 14:43 Metric: 0 Metric2: 200
Task: BGP_65000.172.16.224.2+55706
AS path: I (Originator) Cluster list: 172.16.224.2
AS path: Originator ID: 172.16.225.7
Communities: target:65000:400
Import Accepted
VPN Label: 34
Localpref: 100
Router ID: 172.16.224.2
Secondary Tables: 400.inet.0

Any help is appreciated

Thanks,

Michael

Nagendra Kumar Nainar · ‎03-04-2016

Hi Michael,

AFAIK, export route-map for SoO is not supported. By setting SoO to all prefixes advertised outbound, we might advertise prefixes received from a VRF neighbor without backdoor to remote PE with SoO appended causing it to not advertise to CE nodes. This might cause routing issues.

SoO configuration should be on a CE basis (which is expected to have backdoor connections between other sites). You can use an inbound route-map and map it to the CE or use "neighbor <> soo <>". Alternately, you can use the vrf sitemap configuration and associate it to the interface connecting the CE.

HTH,

Nagendra

mkoschay123 · ‎03-04-2016

Hi Nagendra,

thank you for reply.

Maybe you get me wrong. I have PE1 and PE2 connected to the same customer site CE1. I want to mark all prefixes received from CE1 on PE1 with a SoO attribute (export) and filter this SoO on PE2 (import) to CE1. This is exactly what we do on Junos.

I do I'm wrong with this?

Thanks

Michael