New-NTNXProtectionDomain usage/documentation

  • 26 August 2014
  • 2 replies

Badge +5
I am experimenting with the Protection Domain Cmdlets and trying to use New-NTNXProtectionDomain. I am running into some issues and I hope there is someone around to point me in the right direction.

New-NTNXProtectionDomain prints "protectionDomainName cannot be null" when I run it without any parameters, but the parameter protectionDomainName doesn't seem to exist.

New-NTNXProtectionDomainprotectionDomainName cannot be null
The help doesn't show how to use the Cmdlet:

Get-Help New-NTNXProtectionDomain -fullNAMENew-NTNXProtectionDomainSYNOPSISAdd a Protection Domain.SYNTAXDESCRIPTIONPARAMETERSThis cmdlet supports the common parameters: Verbose, Debug,ErrorAction, ErrorVariable, WarningAction, WarningVariable,OutBuffer, PipelineVariable, and OutVariable. For more information, see about_CommonParameters ( INPUTSOUTPUTSRELATED LINKS
Intellisense gives some more info, but nothing that resembles "protectionDomainName":


Best answer by cbrown 28 August 2014, 18:04

View original

This topic has been closed for comments

2 replies

Userlevel 3
Badge +15
Hey Koen,

I 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:

connect-nutanixcluster [CVM_IP]

And then

$n = Get-NutanixClusterNew-NTNXProtectionDomain -Input testDomain -NutanixClusters $n


New-NTNXProtectionDomain -Input testDomain2 -Servers [CVM_IP]

Now we can see the PDs created:

Get-NTNXProtectionDomain -name testDomain

name : testDomain

Get-NTNXProtectionDomain -name testDomain2

name : testDomain2

I'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.
Badge +5
@cbrown Thanks for your thorough reply.