Comment 5 for bug 2020349

You can try to get logs from neutron with debug=true set in neutron.conf, not sure though if os-ken will log enough details. Another option would be to run tcpdump on the BGP session, my guess is still that this is happening due to the remote sending some bad data.

You could also add another peer running something like bird or frr in order to see whether that session would show the same issue or not.