Microsoft Virtualization Discussions

PowerShell Toolkit 9.11.1.2208 - iSCSI command not working

AHowell
1,725 Views

When I upgraded to the latest toolkit, the "Get-NcIscsiInitiator" command started issuing TSIH parameter errors.  I can't figure out how to avoid the error.  

 

I was able to fix my connection errors by adding a "-ONTAPI" switch, but that doesn't seem to help with the "Get-NcIscsiInitiator" command.

 

Any ideas?

 

PS H:\> Get-NcIscsiInitiator
Get-NcIscsiInitiator : Tsih parameter specified, which is not supported for ONTAPI call
At line:1 char:1
+ Get-NcIscsiInitiator
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-NcIscsiInitiator], ArgumentException
+ FullyQualifiedErrorId : Tsih parameter specified, which is not supported for ONTAPI call,DataONTAP.C.PowerShell.SDK.Cmdlets.Iscsi.GetNcIscsiInitiator



PS H:\> $q = Get-NcIscsiInitiator -Template
Get-NcIscsiInitiator : Tsih parameter specified, which is not supported for ONTAPI call
At line:1 char:6
+ $q = Get-NcIscsiInitiator -Template
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-NcIscsiInitiator], ArgumentException
+ FullyQualifiedErrorId : Tsih parameter specified, which is not supported for ONTAPI call,DataONTAP.C.PowerShell.SDK.Cmdlets.Iscsi.GetNcIscsiInitiator
 

 

1 ACCEPTED SOLUTION

mbeattie
1,666 Views

Hi,

 

Thanks I've sent your feedback to the developers and this bug is being tracked as BURT: 1501452

As a workaround you can use Invoke-NcSsh or Invoke-NcSystemApi until it's resolved in a future release

 

/Matt

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

View solution in original post

2 REPLIES 2

mbeattie
1,667 Views

Hi,

 

Thanks I've sent your feedback to the developers and this bug is being tracked as BURT: 1501452

As a workaround you can use Invoke-NcSsh or Invoke-NcSystemApi until it's resolved in a future release

 

/Matt

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

AHowell
1,642 Views

Thank you. 

I was able to successfully use "Invoke-NcSystemApi" as a workaround.

Public