即使返回200,Azure Traffic Manager端点也会显示降级 [英] Azure Traffic Manager Endpoints show Degraded Even when 200 is Returned

查看:48
本文介绍了即使返回200,Azure Traffic Manager端点也会显示降级的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个带有两个端点的Azure Traffic Manager配置文件(Linux VM正在运行RabbitMQ).

I have an Azure Traffic Manager Profile with two Endpoints (Linux VM's running RabbitMQ).

终结点的类型为" Azure终结点",目标资源类型为"公共IP地址".

The endpoints are of Type "Azure Endpoint" and the Target Resource Type is "Public IP Address".

当我查看流量管理器配置文件"时,它报告配置文件的状态为"已启用",而监视器状态为"已降级".

When I look at the Traffic Manager Profile it reports that the Status of the profile is "Enabled", and the Monitor Status is "Degraded".

在每个端点上,它报告其状态为已启用",而监视器状态为已降级".

On Each of the endpoints it reports that their Status is "Enabled" and the Monitor Status is "Degraded".

我将流量管理器配置文件配置为协议"为"HTTP",端口配置为"15672",路径配置为"/index.html".

I have the Traffic Manager Profile configured with Protocol as "HTTP" and Port as 15672 and the path as "/index.html".

问题是我不知道为什么它报告降级",因为如果我执行wget命令.

The problem is I can't tell why it is reporting "Degraded" because if I do a wget command.

wget <vmname1>.cloudapp.azure.com:15672/index.html

Resolving <vmname1>.cloudapp.azure.com... <ip address>
Connecting to <vmname1>.cloudapp.azure.com|<ip address>|:15672... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1419 (1.4K) [text/html]

所有文档"(对于Azure来说都是令人沮丧的只是博客文章)都说,如果返回200,则应为联机"而不是降级".

All the "documentation" (which for Azure is frustratingly just blog posts) says that if it returns 200 then it should be "Online" and not "Degraded".

推荐答案

根据您的回复,问题很可能是您的NSG规则阻止了流量管理器的运行状况检查.

Based on your reply, it is very likely that the issue is that the Traffic Manager health checks are being blocked by your NSG rules.

如今,我们尚无简便的方法在NSG中配置流量管理器,也没有发布流量管理器运行状况检查源IP地址.这些都是我们计划填补的空白.同时,建议的解决方法是为Traffic Manager使用在其他TCP端口上运行的专用运行状况检查页,并将NSG仅应用于应用程序使用的端口.

We don't have an easy way to configure Traffic Manager in NSGs today, nor do we publish the Traffic Manager health check source IP addresses. These are gaps we are planning to fill. In the meantime, the recommended workaround is to use a dedicated health check page running on a different TCP port for Traffic Manager, and apply the NSG only to the port used by your application.

这篇关于即使返回200,Azure Traffic Manager端点也会显示降级的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆