I noticed that although Large BGP Communities are indeed carried through the OpenBMP stack into the postgres database into the base_attrs table (large_community_list), the HASH (hash_id) does not update (is not recomputed) when just the large_community_list changes (i.e. the only BGP update that occurs is a change to large_community_list). I think this means that the openbmp/collector:2.2.3 is not including large_community_list in it's computation of the hash_id for base_attrs table.
The end result is that if a large-community is added to a route advertisement, and that's the only change to the route, then OpenBMP will still display the 'old' large_community_list. If some other BGP parameter is then changed later (like local-pref), then OpenBMP will display/store the correct/updated large_community, and the updated local-pref.
It seems maybe a patch would be needed to openbmp/collector:2.2.3 to fix this?
Let me know if anyone has any insight into this problem, and/or if it can be fixed.
Want to say thanks to the developer(s), this is a really cool BMP implementation.
I noticed that although Large BGP Communities are indeed carried through the OpenBMP stack into the postgres database into the base_attrs table (large_community_list), the HASH (hash_id) does not update (is not recomputed) when just the large_community_list changes (i.e. the only BGP update that occurs is a change to large_community_list). I think this means that the openbmp/collector:2.2.3 is not including large_community_list in it's computation of the hash_id for base_attrs table.
The end result is that if a large-community is added to a route advertisement, and that's the only change to the route, then OpenBMP will still display the 'old' large_community_list. If some other BGP parameter is then changed later (like local-pref), then OpenBMP will display/store the correct/updated large_community, and the updated local-pref.
It seems maybe a patch would be needed to openbmp/collector:2.2.3 to fix this?
Let me know if anyone has any insight into this problem, and/or if it can be fixed.
Want to say thanks to the developer(s), this is a really cool BMP implementation.