Microsoft Virtualization Discussions

Getting HTTPS error using New-NaVol command

manuelsanchez
5,828 Views

Here is the command syntax that I am using:

New-NaVol -Name $Vol_Name -Aggregate $Aggr -Size $vol_size -SpaceReserve $Space_R -LanguageCode en_US

This command works with no issues when I use RPC connection to other controllers.

However, for those controllers in my environment where I cannot use RPC and I use HTTPS the same command does not work.

Here is the error output after running "New-NaVol" command:

New-NaVol : Could not connect to xyz.xyz.com on port 443 for protocol

HTTPS.

At C:\posh\create_lun_template.ps1:211 char:10

+ New-NaVol <<<<  -Name $Vol_Name -Aggregate $Aggr -Size $vol_size -SpaceReserv

e $Space_R -LanguageCode en_US

    + CategoryInfo          : InvalidOperation: (msp0nfas04.etdbw.com:NaContro

   ller) [New-NaVol], NaConnectionException

    + FullyQualifiedErrorId : ApiException,DataONTAP.PowerShell.SDK.Cmdlets.Vo

   lume.NewNaVol

Write-Warning : A positional parameter cannot be found that accepts argument 'n

4a2_msp0lwasq020_u01_1'.

At C:\posh\create_lun_template.ps1:213 char:20

+       Write-warning <<<<  "`n ERROR - Could not create new volume: "$Vol_Name

    + CategoryInfo          : InvalidArgument: (:) [Write-Warning], ParameterB

   indingException

    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell

   .Commands.WriteWarningCommand

Here is my connection info:

PS C:\batch> $global:CurrentNaController | Format-List *

Ontapi             : 1.14

OntapiMajorVersion : 1

OntapiMinorVersion : 14

Version            : NetApp Release 7.3.5.1P2: Thu Mar 31 14:05:59 PDT 2011

Vfiler             :

Protocol           : HTTPS

Proxy              :

TimeoutMsec        : 10000

Name               : xyz.xyz.com

Address            : 167.19.251.18

Port               : 443

Credentials        : System.Net.NetworkCredential

ValidateIncoming   : False

ValidateOutgoing   : False

Trace              : False

1 ACCEPTED SOLUTION

timothyn
5,825 Views

Are you sure you can connect ok via HTTPS?  Can you try a simple sequence like:

Connect-NaController xyz.xyz.com -HTTPS -Credential root
Get-NaAggr

The other possibility is that latency is high enough and/or the command is taking long enough to cause a timeout.  

The timeout defaults to 10000 (10 seconds), but you can set the timeout manually on the NaController object:

$global:CurrentNaController.TimeoutMsec = 60000

View solution in original post

11 REPLIES 11
Public