azure gateway as priority traffic manager
We have a set-up an azure gateway of tier WAF V2 (so it would be zone-redundant). It has a backend pool containing 2 WebApps -AppServices (supposedly a Primary and a Secondary).
The idea behind it was to use the gateway similarly to priority traffic manager: Routing usually to the primary WebApp, and only routing to the secondary WebApp in case the first one goes down.
The Problem is that the only way I found to do that is to order the rules associated with the listeners of the backend pool (because I believe azure prioritizes them according to the order they are listed). But given that both Apps are in the same backend pool, Im unsure of how to do that.
So now the gateway randomly routes to either the first or second WebApp.
Any advice or suggestions would be much appreciated,
Thank you
Note: Also we have tried setting a traffic manager in between the gateway and the WebApps, but the gateway keeps connecting to the primary WebApp even when its down and its probe becomes of health status unknown.
azure gateway azureportal azure-traffic-manager asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
add a comment |
We have a set-up an azure gateway of tier WAF V2 (so it would be zone-redundant). It has a backend pool containing 2 WebApps -AppServices (supposedly a Primary and a Secondary).
The idea behind it was to use the gateway similarly to priority traffic manager: Routing usually to the primary WebApp, and only routing to the secondary WebApp in case the first one goes down.
The Problem is that the only way I found to do that is to order the rules associated with the listeners of the backend pool (because I believe azure prioritizes them according to the order they are listed). But given that both Apps are in the same backend pool, Im unsure of how to do that.
So now the gateway randomly routes to either the first or second WebApp.
Any advice or suggestions would be much appreciated,
Thank you
Note: Also we have tried setting a traffic manager in between the gateway and the WebApps, but the gateway keeps connecting to the primary WebApp even when its down and its probe becomes of health status unknown.
azure gateway azureportal azure-traffic-manager asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
add a comment |
We have a set-up an azure gateway of tier WAF V2 (so it would be zone-redundant). It has a backend pool containing 2 WebApps -AppServices (supposedly a Primary and a Secondary).
The idea behind it was to use the gateway similarly to priority traffic manager: Routing usually to the primary WebApp, and only routing to the secondary WebApp in case the first one goes down.
The Problem is that the only way I found to do that is to order the rules associated with the listeners of the backend pool (because I believe azure prioritizes them according to the order they are listed). But given that both Apps are in the same backend pool, Im unsure of how to do that.
So now the gateway randomly routes to either the first or second WebApp.
Any advice or suggestions would be much appreciated,
Thank you
Note: Also we have tried setting a traffic manager in between the gateway and the WebApps, but the gateway keeps connecting to the primary WebApp even when its down and its probe becomes of health status unknown.
azure gateway azureportal azure-traffic-manager asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
We have a set-up an azure gateway of tier WAF V2 (so it would be zone-redundant). It has a backend pool containing 2 WebApps -AppServices (supposedly a Primary and a Secondary).
The idea behind it was to use the gateway similarly to priority traffic manager: Routing usually to the primary WebApp, and only routing to the secondary WebApp in case the first one goes down.
The Problem is that the only way I found to do that is to order the rules associated with the listeners of the backend pool (because I believe azure prioritizes them according to the order they are listed). But given that both Apps are in the same backend pool, Im unsure of how to do that.
So now the gateway randomly routes to either the first or second WebApp.
Any advice or suggestions would be much appreciated,
Thank you
Note: Also we have tried setting a traffic manager in between the gateway and the WebApps, but the gateway keeps connecting to the primary WebApp even when its down and its probe becomes of health status unknown.
azure gateway azureportal azure-traffic-manager azure gateway azureportal azure-traffic-manager asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
asked Nov 19 '18 at 7:31
A.J AlhorrA.J Alhorr
11214
11214
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Application Gateway is a layer 7 load balancer, which means it works with web traffic only (HTTP/HTTPS/WebSocket). It supports capabilities such as SSL termination, cookie-based session affinity, and round robin for load balancing traffic. This indicated that the application gateway frontend randomly distribute the incoming traffics to the endpoint if both endpoints are healthy. So you could see the gateway randomly routes to either the first or second WebApp. See the application gateway FAQ. The app gateway does not work like priority-based traffic manager which always requests to the primary web app unless the primary web app is unhealthy.
About the health status unknown, the most common reason is that access to the backend is being blocked by an NSG or custom DNS. Ref: Troubleshooting bad gateway errors in Application Gateway
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
Thanks you, gonna have to revert to traffic manager with the gateways between the traffic manager and the WebApps I guess.
– A.J Alhorr
Nov 20 '18 at 8:51
It' recommend using traffic manager in front of the application gateway as failover. Refer to this. Also, if the traffic manager between them, it might add some health probe issue due to the DNS resolution or DNS cache.
– Nancy Xiong
Nov 20 '18 at 9:16
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370107%2fazure-gateway-as-priority-traffic-manager%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Application Gateway is a layer 7 load balancer, which means it works with web traffic only (HTTP/HTTPS/WebSocket). It supports capabilities such as SSL termination, cookie-based session affinity, and round robin for load balancing traffic. This indicated that the application gateway frontend randomly distribute the incoming traffics to the endpoint if both endpoints are healthy. So you could see the gateway randomly routes to either the first or second WebApp. See the application gateway FAQ. The app gateway does not work like priority-based traffic manager which always requests to the primary web app unless the primary web app is unhealthy.
About the health status unknown, the most common reason is that access to the backend is being blocked by an NSG or custom DNS. Ref: Troubleshooting bad gateway errors in Application Gateway
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
Thanks you, gonna have to revert to traffic manager with the gateways between the traffic manager and the WebApps I guess.
– A.J Alhorr
Nov 20 '18 at 8:51
It' recommend using traffic manager in front of the application gateway as failover. Refer to this. Also, if the traffic manager between them, it might add some health probe issue due to the DNS resolution or DNS cache.
– Nancy Xiong
Nov 20 '18 at 9:16
add a comment |
Application Gateway is a layer 7 load balancer, which means it works with web traffic only (HTTP/HTTPS/WebSocket). It supports capabilities such as SSL termination, cookie-based session affinity, and round robin for load balancing traffic. This indicated that the application gateway frontend randomly distribute the incoming traffics to the endpoint if both endpoints are healthy. So you could see the gateway randomly routes to either the first or second WebApp. See the application gateway FAQ. The app gateway does not work like priority-based traffic manager which always requests to the primary web app unless the primary web app is unhealthy.
About the health status unknown, the most common reason is that access to the backend is being blocked by an NSG or custom DNS. Ref: Troubleshooting bad gateway errors in Application Gateway
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
Thanks you, gonna have to revert to traffic manager with the gateways between the traffic manager and the WebApps I guess.
– A.J Alhorr
Nov 20 '18 at 8:51
It' recommend using traffic manager in front of the application gateway as failover. Refer to this. Also, if the traffic manager between them, it might add some health probe issue due to the DNS resolution or DNS cache.
– Nancy Xiong
Nov 20 '18 at 9:16
add a comment |
Application Gateway is a layer 7 load balancer, which means it works with web traffic only (HTTP/HTTPS/WebSocket). It supports capabilities such as SSL termination, cookie-based session affinity, and round robin for load balancing traffic. This indicated that the application gateway frontend randomly distribute the incoming traffics to the endpoint if both endpoints are healthy. So you could see the gateway randomly routes to either the first or second WebApp. See the application gateway FAQ. The app gateway does not work like priority-based traffic manager which always requests to the primary web app unless the primary web app is unhealthy.
About the health status unknown, the most common reason is that access to the backend is being blocked by an NSG or custom DNS. Ref: Troubleshooting bad gateway errors in Application Gateway
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
Application Gateway is a layer 7 load balancer, which means it works with web traffic only (HTTP/HTTPS/WebSocket). It supports capabilities such as SSL termination, cookie-based session affinity, and round robin for load balancing traffic. This indicated that the application gateway frontend randomly distribute the incoming traffics to the endpoint if both endpoints are healthy. So you could see the gateway randomly routes to either the first or second WebApp. See the application gateway FAQ. The app gateway does not work like priority-based traffic manager which always requests to the primary web app unless the primary web app is unhealthy.
About the health status unknown, the most common reason is that access to the backend is being blocked by an NSG or custom DNS. Ref: Troubleshooting bad gateway errors in Application Gateway
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
edited Nov 20 '18 at 7:58
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
answered Nov 20 '18 at 7:27
Nancy XiongNancy Xiong
2,623118
2,623118
Thanks you, gonna have to revert to traffic manager with the gateways between the traffic manager and the WebApps I guess.
– A.J Alhorr
Nov 20 '18 at 8:51
It' recommend using traffic manager in front of the application gateway as failover. Refer to this. Also, if the traffic manager between them, it might add some health probe issue due to the DNS resolution or DNS cache.
– Nancy Xiong
Nov 20 '18 at 9:16
add a comment |
Thanks you, gonna have to revert to traffic manager with the gateways between the traffic manager and the WebApps I guess.
– A.J Alhorr
Nov 20 '18 at 8:51
It' recommend using traffic manager in front of the application gateway as failover. Refer to this. Also, if the traffic manager between them, it might add some health probe issue due to the DNS resolution or DNS cache.
– Nancy Xiong
Nov 20 '18 at 9:16
Thanks you, gonna have to revert to traffic manager with the gateways between the traffic manager and the WebApps I guess.
– A.J Alhorr
Nov 20 '18 at 8:51
Thanks you, gonna have to revert to traffic manager with the gateways between the traffic manager and the WebApps I guess.
– A.J Alhorr
Nov 20 '18 at 8:51
It' recommend using traffic manager in front of the application gateway as failover. Refer to this. Also, if the traffic manager between them, it might add some health probe issue due to the DNS resolution or DNS cache.
– Nancy Xiong
Nov 20 '18 at 9:16
It' recommend using traffic manager in front of the application gateway as failover. Refer to this. Also, if the traffic manager between them, it might add some health probe issue due to the DNS resolution or DNS cache.
– Nancy Xiong
Nov 20 '18 at 9:16
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370107%2fazure-gateway-as-priority-traffic-manager%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
