网络接口查询的无法解释的“失败"置备状态

本文介绍了网络接口查询的无法解释的“失败"置备状态的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 你好有时，在查询网络接口时，"properties.provisioningState"字段(JSON响应)会遇到"Failed"值.重新启动附件后，该状态再次成功" 虚拟机. 1. 失败"状态的确切含义是什么? (关于网络接口/IP配置) 2.此状态可能是什么原因? 更多详细信息:我们的应用程序在Ubuntu 14 VM上运行.创建两个相同的设置，每个设置都有单个NIC以及单个本地和公共IP.两个NIC共享相同的子网.有时，其中一个应用程序(总是一个活动的应用程序和一个备份)使用Azure REST API在NIC之间交换公共IP.交换过程的一部分是验证NIC状态.为此，发送了有关NIC信息的查询，但如上所述 上面，有时响应的"provisioningState"字段处于失败"状态(我在"properties.provisioningState"和"properties.ipConfigrations [0] .properties.provisioningState"中都得到了此状态) 3.是否有任何日志可搜索此失败的原因? 希望我很清楚. 谢谢 Zion 解决方案 Hello,From time to time, I experience a 'Failed' value for the 'properties.provisioningState' field (JSON response) when querying a network interface. This state iis 'Succeeded' again after restarting the attached VM.1. What exactly the 'Failed' state means? (in regards to network interface/IP configurations)2. What may be the reason(s) for this state?Some more details:Our application is running on Ubuntu 14 VM. Two identical setups are created, each with single NIC and single local and public IP. Both NICs share the same subnet.From time to time one of the applications (there's always an active one and a backup) swaps the public IP between the NICs by using Azure REST APIs. Part of the swap process is to verify NIC status. For that a query for NIC info is sent, but as mentioned above, sometimes the response's 'provisioningState' field is in 'Failed' state (I'm getting this state in both 'properties.provisioningState' and 'properties.ipConfigrations[0].properties.provisioningState')3. Are there any logs to search for the cause of this failure?Hope I'm clear.Thanks,Zion 解决方案 这篇关于网络接口查询的无法解释的“失败"置备状态的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！