I am struggling with tripping max-prefixes with BGP peers when rebooting. This happens both when the peers are active and also when they are shutdown in the configuration. I'm theorizing that FRR is establishing the connections before the whole configuration has been loaded.
One example (the peer is shutdown):
neighbor 91.xx.yy.69 { address-family { ipv4-unicast { prefix-list { export ASLOCAL } soft-reconfiguration { inbound } } } description ispx remote-as 65500 shutdown }
After rebooting the router, notice how the peer has MsgRcvd and MsgSent even though it was shutdown in the configuration during the reboot:
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 91.xx.yy.69 4 65500 4695 2032 0 0 0 00:06:02 Idle (Admin)
Excerpt from frr.log
Jan 2 17:50:07 vyos bgpd[1074]: %ADJCHANGE: neighbor 91.xx.yy.69(Unknown) in vrf default Up Jan 2 17:50:09 vyos bgpd[1074]: %ADJCHANGE: neighbor 91.xx.yy.69(Unknown) in vrf default Down Peer closed the session