Azure Networking Challenges: Routing Strategies, and Load Balancing for Multi-Tier IoT Application
Hey community, It's been a while since I've been working on configuration of a complex network architecture in Microsoft Azure for a multi-tier application. I've successfully set up virtual networks, subnets, and security groups, but I'm encountering challenges in establishing efficient communication between different tiers and ensuring optimal traffic flow. Specifically, I'm interested in best practices for implementing Network Security Groups (NSGs) and effective routing strategies. Additionally, insights on leveraging Azure Load Balancers to enhance the scalability and resilience of my application would be greatly appreciated. If anyone has experience with similar configurations or can offer advice on optimizing Azure networking for multi-tier applications, I'd be grateful for your expertise. Thank you!How does Azure Load Balance SIP? Ref: Direct Routing setup with virtual SBC in Azure Cloud
With options under "health probe" to monitor TCP,HTTP and HTTPs ports can anyone help me understand how does the health probe monitors if the SIP services is accepting requests. Based on my reading, for HTTP, the health probe waits of 200 OK message. Will it be same for SIP ports (5060, 5061 or any other)? Example scenario, I have got 3 x virtual SBCs setup in an availability group with each SBC set for max 200 connections/sessions via CAC. I want that if all the 600 sessions on 1st SBC is occupied, the load balancer would sent new requests to 2nd SBC and so on. Now, if the Azure Load Balancer would just monitor if the SIP port is up, it won't find any issues since port 5060 (or any other as defined) would still be open on SBC01. I wanted to understand which kind of SIP message gets exchanged by the Azure Load balancer's health probe monitoring SIP interface/port.
