Hello Handian Sudianto
As per the above screenshot, you have created two BGP connections between Azure's two public IPs and two on-prem IPs, which are shown as connected in the green lines. However, you have not created cross-redundancy BGP sessions between Azure BGP peer (10.201.0.4) and on-prem BGP peer (10.201.0.201), and Azure BGP peer (10.201.0.5) and on-prem BGP peer (10.201.0.101), resulting in a connecting state as shown in the violet lines.
NOTE: If you want dual redundancy active-active mode, you need to setup full mesh connectivity of four IPsec tunnels between your Azure virtual network gateway and you're on-premises network.
In active-active mode, each Azure VPN Gateway instance has a unique public IP address and BGP peer IP. Both instances establish independent IPsec/IKE S2S VPN tunnels to your on-premises VPN devices. This ensures high availability and load balancing.
Your setup with two on-premises BGP peers (10.201.0.101 and 10.201.0.201) connecting to two Azure BGP peers (10.201.0.4 and 10.201.0.5) is correct. However, the additional "connecting" BGP sessions (10.201.0.101 to 10.201.0.5 and 10.201.0.201 to 10.201.0.4) might indicate that the on-premises devices are attempting to establish redundant connections to both Azure instances. This is expected behavior in active-active mode, as Azure supports multiple BGP sessions for redundancy.
I hope this has been helpful!
If above is unclear and/or you are unsure about something add a comment below.
please don’t forget to close the thread by clicking Accept the answer wherever the information provided helps you, as this can be beneficial to other community members.