[英]Azure VM Nic With Loopback Address and No Connectivity
we have a vm which is in Azure but we're not able to connect to it.我们有一个位于 Azure 中的虚拟机,但我们无法连接到它。 I checked the serial log under boot diagnostic and it has the following error:
我在启动诊断下检查了串行日志,它有以下错误:
======== Microsoft Azure VM Health Report - Start 2020-02-19T20:50:47.2786733Z ======== {"reportTime":"2020-02-19T20:47:44.9492172Z","networkAdapters":[{"name":"Loopback Pseudo-Interface 1","status":"Up","macAddress":"","ipProperties":[{"protocolVersion":4,"address":"127.0.0.1","isDhcpEnabled":false},{"protocolVersion":6,"address":"::1","isDhcpEnabled":false}]}],"remoteAccess":null,"accounts":{"windows":{"adminAccountPasswordExpired":false,"adminAccountDisabled":false}},"services":[{"errorControl":"Normal","exitCode":0,"name":"TermService","processId":2708,"serviceType":"Share Process","startMode":"Auto","startName":"NT Authority\\NetworkService","state":"Running","status":"OK"}
======== Microsoft Azure VM 运行状况报告 - 开始 2020-02-19T20:50:47.2786733Z ======== {"reportTime":"2020-02-19T20:47:44.9492172Z" ,"networkAdapters":[{"name":"Loopback Pseudo-Interface 1","status":"Up","macAddress":"","ipProperties":[{"protocolVersion":4,"address": "127.0.0.1","isDhcpEnabled":false},{"protocolVersion":6,"address":"::1","isDhcpEnabled":false}]}],"remoteAccess":null,"accounts": {"windows":{"adminAccountPasswordExpired":false,"adminAccountDisabled":false}},"services":[{"errorControl":"Normal","exitCode":0,"name":"TermService","processId ":2708,"serviceType":"Share Process","startMode":"Auto","startName":"NT Authority\\NetworkService","state":"Running","status":"OK"}
The key part I think is the "name":"Loopback Pseudo-Interface 1"
It has no mac address as above and uses IP of 127.0.0.1, Has anyone come across this before and know how to get the NIC to be recognised.我认为关键部分是
"name":"Loopback Pseudo-Interface 1"
它没有上面的mac地址,使用127.0.0.1的IP,有没有人遇到过这个并且知道如何识别NIC。 I've changed the NIC and changed IP, but cannot seem to resolve this.我已经更改了 NIC 并更改了 IP,但似乎无法解决此问题。
By default, 127.0.0.1 is assigned to a loopback interface.默认情况下,127.0.0.1 分配给环回接口。 It represents the localhost address.
它代表本地主机地址。 The captured health report is meanless and not enough to identify why you are not able to connect to that Azure VM.
捕获的运行状况报告毫无意义,不足以确定无法连接到该 Azure VM 的原因。
First, you can verify if the VM status is running on the overview of the virtual machine portal.首先,您可以在虚拟机门户的概览中验证 VM 状态是否正在运行。 Then check if there is any port blocking in the NSG on the networking of VM, then try to RDP or SSH to that Azure VM.
然后检查 VM网络上的 NSG 中是否有任何端口阻塞,然后尝试 RDP 或 SSH 到该 Azure VM。 You can get more details on diagnose and solve problems under overview.
您可以在概览下获得有关诊断和解决问题的更多详细信息。
If you still could not connect to it.如果您仍然无法连接到它。 Try to resize or redeploy your Azure VM.
尝试调整大小或重新部署Azure VM。 If you have important data, please backup your OS and data disk before you redeploy it.
如果您有重要数据,请在重新部署之前备份您的操作系统和数据盘。 You also could get more details on how to use boot diagnostics to troubleshoot virtual machines in Azure .
您还可以获得有关如何使用启动诊断对 Azure 中的虚拟机进行故障排除的更多详细信息。
Hope this could help you.希望这可以帮助你。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.