当我在没有任何参数的情况下运行它时,new-ntnxProtectionDomain打印“ protectionDomainName不能为null”,但是似乎不存在参数protectionDomainName。
new-ntnxprotectiondomainprotectrydomainname不能为null
帮助没有显示如何使用cmdlet:
获得新的ntnxprotectiondomain -fullnamenew-ntnxprotectiondomainsynopsIsAddd a保护域。syntaxDescriptionParametersistersistersistersisterscmdlet支持公共参数:冗长,调试,错误,错误,错误,警告性,警告性,可警告,可疑,Outbuffer,pipelineVarable和Outvararia-Outvararia。有关更多信息,请参见有关_CommonParameters(http://go.microsoft.com/fwlink/?linkid=113216)。InputsOutputsracsraced链接
IntelliSense提供了更多信息,但没有任何类似于“ protectionDomainName”的信息:
最好的答案CBROWN
\n\nI just ran some tests in the lab here, and it seems that the cmdlet uses the -Input flag for protectionDomainName. It also doesn't accept the PD Name without the flag, which it should. Here's what I ran in my lab:
\n
\nconnect-nutanixcluster [CVM_IP]
\n
\nAnd then
\n
\n$n = Get-NutanixClusterNew-NTNXProtectionDomain -Input testDomain -NutanixClusters $n
\n
\nor:
\n
\nNew-NTNXProtectionDomain -Input testDomain2 -Servers [CVM_IP]
\n
\nNow we can see the PDs created:
\n
\nGet-NTNXProtectionDomain -name testDomain
\n
\nname : testDomain
\n
\nGet-NTNXProtectionDomain -name testDomain2
\n
\nname : testDomain2
\n
\nI'm going to file a bug on this, the flag should be more intuative (having a -name flag would be much better), but in the mean time -input should work.","className":"post__content__best_answer"}">