Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
1,178 questions
Restart of self hosted gateways causes outage on backend pool in the AAG
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 10%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAU%3C/text%3E%3C/svg%3E)
Andrew Unsworth
25
Reputation points
Restarting the Self hosted gateway in our production environment causes the AKS Pod it is running under to be given a new ip address. The new ip address is not automatically replicated to the AAG. This causes an outage on the AAG as it can no longer communicate with the Self Hosted Gateway.
To fix it we have to copy the new ip address of the POD in AKS to the ip address in the backend pool in the AAG.
This works fine on our PreProd environment and the ip addresses get automatically updated.
We cannot see any differences in the networks in Prod and PreProd.
Any help would be appreciated in fixing this. Any pointers to what process does the replication would be helpful
I can't find any support articles or documentation on this.
Azure Application Gateway
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,381 questions
{count} votes
-
Prrudram-MSFT 28,156 Reputation points2023-08-31T05:09:57.2066667+00:00 It sounds like you are experiencing an issue with the Azure Application Gateway (AAG) not automatically updating the IP address of the backend pool when the Self Hosted Gateway (SHG) is restarted in your production environment. Here are some troubleshooting steps you can try:
Check the configuration of the AAG backend pool to make sure that it is configured to use the AKS Pod IP address as the backend pool member. You can do this by navigating to the AAG backend pool settings in the Azure portal and verifying that the IP address is correct.
Check the configuration of the AKS Pod to make sure that it is configured to use a static IP address. If the Pod is using a dynamic IP address, it may change when the Pod is restarted, which could cause the AAG backend pool to become out of sync.
Check the logs and metrics for the AAG and SHG to see if there are any errors or warnings related to the IP address synchronization. You can use Azure Monitor to view the logs and metrics for both services.
Check the network configuration of your production environment to make sure that there are no network restrictions or firewalls that could be blocking the IP address synchronization process.
If you are still unable to resolve the issue, you may need to contact Microsoft support for further assistance. They can help you troubleshoot the issue and provide guidance on how to resolve it.
In general, the IP address synchronization process should be automatic and should not require manual intervention. If you are experiencing issues with the automatic synchronization, there may be a configuration issue or a bug in the software.
Sign in to comment
Sign in to answer