<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Dear BIRD community,</p><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">I am running a BMP collector and encountering an issue where no monitoring messages are exported over BMP, even though I am using the latest BIRD version (3.2.1), which should include the fix for the previous route export bug:</p><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><a href="https://gitlab.nic.cz/labs/bird/-/commit/2500b450b404ab41eeff3b2d92ba943d0178fb50">https://gitlab.nic.cz/labs/bird/-/commit/2500b450b404ab41eeff3b2d92ba943d0178fb50</a></p><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">We tested this both in our lab and with a network operator, and consistently observe the following behavior:</p><ul style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><li><p>If the BMP session is activated before the BGP sessions, everything works as expected, and monitoring messages are exported.</p></li><li><p>If the BGP sessions are established before enabling BMP, then BMP does not export monitoring messages at all.</p></li></ul><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">This suggests that BMP does not correctly pick up already-established BGP sessions.</p><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Below is a minimal configuration example. The behavior depends solely on the order in which the sessions are established :</p><pre style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><code class="language-bird">debug protocols all;
router id 192.168.222.54;
protocol kernel {
ipv4 {
export all;
};
}
protocol device {
scan time 10;
}
filter ALLOW_ALL { accept; }
protocol bmp {
station address ip 192.168.222.1 port 4567;
monitoring rib in pre_policy;
tx buffer limit 1024;
}
protocol bgp peer_asn_10 {
local 192.168.222.54 as 11;
neighbor 192.168.222.52 as 10;
multihop 255;
ipv4 {
import all;
export all;
next hop self;
import table on;
};
ipv6 {
import all;
export all;
next hop self;
import table on;
};
}
protocol bgp peer_asn_12 {
local 192.168.222.54 as 11;
neighbor 192.168.222.53 as 12;
multihop 255;
ipv4 {
import all;
export all;
next hop self;
};
ipv6 {
import all;
export all;
next hop self;
};
}
</code></pre><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Has anyone else experienced similar behavior? Could this be another bug related to BMP?</p><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Thanks in advance for your help.</p><p style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Best regards,<br>Thomas</p></body></html>