Share via

Must the Gateway Load Balancer Frontend IP be in its own subnet?

Martin Bright 0 Reputation points
2025-03-11T22:42:18.5033333+00:00

hi!

Recently our deployments with Azure Gateway Load Balancers stopped forwarding traffic back to their chained public load balancers. To solve the issue, we put the GWLB frontend IPs in dedicated subnets beside our NVAs. Is this necessary? Has anything changed to cause this behavior?

Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
489 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Martin Bright 0 Reputation points
    2025-03-12T19:05:54.36+00:00

    Yes, the issue was resolved when we moved the GWLB frontend IP to a dedicated subnet that was different from the subnet that contained the NVAs.

    However, we don't understand why. In the attached diagram, the cPacket broker scale set was in the same subnet as the GWLB frontend IP. This stopped working. So we moved the GWLB to its own subnet and it started working again.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.