After a VPN gateway SKU migration, one BGP session to my FortiGate is up but the other is stuck in Active. Azure's configuration still shows the old peer addresses, while its operational peer view shows two different addresses. The firewall also rejects connections from one of the new addresses as an unconfigured peer.
There are two on-premises internet connections, with AS path prepending used to prefer the primary. How should I troubleshoot the address mismatch without breaking the working path?
3b+signalwicket_584:
A remote BGP router ID and the address used for the neighbor session are different things. The router ID alone doesn't prove which neighbor address should be configured.