当我尝试连接到节点的公共 IP 地址上的端口时，50％ 的时间 Azure 没有响应，并且 nmap 将其标记为“已过滤”。
当我尝试使用本地主机从节点连接到同一端口时，它 100% 有效。
我在 Azure 上始终看到这种行为，但在 AWS 和 DigitalOcean 上从未见过。
有什么想法吗？
Nmap done: 1 IP address (1 host up) scanned in 3.23 seconds
root@AZURE_HOST:~# nmap -Pn -p 28015 AZURE_PUBLIC_IP
Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-11 17:36 UTC
Nmap scan report for AZURE_PUBLIC_IP
Host is up (0.0012s latency).
PORT STATE SERVICE
28015/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 3.15 seconds
root@AZURE_HOST:~# nmap -Pn -p 28015 AZURE_PUBLIC_IP
Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-11 17:37 UTC
Nmap scan report for AZURE_PUBLIC_IP
Host is up.
PORT STATE SERVICE
28015/tcp filtered unknown
Nmap done: 1 IP address (1 host up) scanned in 3.23 seconds
root@AZURE_HOST:~# nmap -Pn -p 28015 localhost
Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-11 17:37 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000088s latency).
PORT STATE SERVICE
28015/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 1.06 seconds
root@AZURE_HOST:~# nmap -Pn -p 28015 localhost
Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-11 17:37 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000070s latency).
PORT STATE SERVICE
28015/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 1.08 seconds
root@AZURE_HOST:~# nmap -Pn -p 28015 localhost
Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-11 17:37 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000066s latency).
PORT STATE SERVICE
28015/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 1.05 seconds
答案1
暂时关闭此问题，因为目前此问题与 DC 范围内的网络问题有关。如果此问题解决后我可以重现此问题，我将删除此问题。
网络基础设施和存储 - 美国东部 2 - 部分服务中断 24 分钟前从 2015 年 11 月 11 日 16:40 UTC 左右开始，工程师正在调查网络基础设施影响美国东部 2 存储的问题。