Synopsis: <problem with network statements in bgpd.conf>
Category: <user i386 system>
Environment:
System : OpenBSD 5.4
Details : OpenBSD 5.4 (XXX) #7: Thu Mar 13 10:08:46 MSK 2014
[email protected]:/usr/src/sys/arch/i386/compile/XXX
Architecture: OpenBSD.i386
Machine : i386
Description:
I have noticed that bgpd does not route decision if pt_entry (for VPNv4 prefix)
has different RD.
How-To-Repeat:
bgpd.conf route-collection turned off.
mpls-PE route-reflector advertises two prefixes with different RD
and set of ATTR, both appeared in bgpd RIB-in as expected.
Now, bgpd should import prefixes to rdomain by import-targets
and then it should make route decision based on ATTR.
In this case lpref is set for second prefix by bgpd filter
allow from mpls-PE community yyyy:1805 set lpref 120.
But it seems that bgpd always sets up best for the prefix which was
placed first to the rde LIST, no matter which attributes was set to make
prefix 2 best.
BGP routing table entry for rd xxxx:10895 10.100.41.0/30
xxxx
Nexthop 172.16.1.2 (via 172.16.1.2) from mpls-PE (172.17.2.1)
Origin incomplete, metric 0, localpref 100, weight 0, external, valid, best
Last update: 02:32:18 ago
Communities: xxxx:9004
Ext. communities: rt xxxx:103231
BGP routing table entry for rd xxxx:12193 10.100.41.0/30
xxxx yyyy
Nexthop 172.16.1.2 (via 172.16.1.2) from mpls-PE (172.17.2.1)
Origin IGP, metric 0, localpref 120, weight 0, external, valid, best
Last update: 02:32:20 ago
Communities: xxxx:9001 xxxx:9801 yyyy:1107 yyyy:1805
Ext. communities: rt xxxx:103231
Fix:
Didnt find any workarounds.
--
