Subscribe
Accepted Solution

Rename-NaVol ending with error but successfully done

Hi,

im experiencing Problems when im running Rename-NaVol.

Im getting the following error:

Rename-NaVol : Could not connect to fas2101b on port 443 for protocol HTTPS.

At C:\Scripts\netapp\edit\netapp-move-snapvault-to-other-aggr.ps1:289 char:21

+ $temp = Rename-NaVol <<<<  -Name $volname -NewName $volname_new

    + CategoryInfo          : InvalidOperation: (fas2101b:NaController) [Rename-NaVol], NaConnectionException

    + FullyQualifiedErrorId : ApiException,DataONTAP.PowerShell.SDK.Cmdlets.Volume.RenameNaVol

Rename-NaVol : No volume named 'VAULT_TAS_T02_db_NL0' exists

At C:\Scripts\netapp\edit\netapp-move-snapvault-to-other-aggr.ps1:289 char:21

+ $temp = Rename-NaVol <<<<  -Name $volname -NewName $volname_new

    + CategoryInfo          : InvalidOperation: (fas2101b:NaController) [Rename-NaVol], EVOLUMEDOESNOTEXIST

    + FullyQualifiedErrorId : VolumeListInfoFailed,DataONTAP.PowerShell.SDK.Cmdlets.Volume.RenameNaVol

But after a look on the Netapp the volume was renamed successfully.

Also all other API calls ending with the "could not connect" error when im starting them right after. (Not happening when i run them solo)

So i expect there is something wrong with it?

Would be nice if someone else has the prob and a solution

greetz

Rename-NaVol ending with error but successfully done

I had a similra problem while creating a new volume.

The new volume was created. However, I had that same "port 443" error.

The problem went away when I change the connection timeout to 60 sec, per Eric Nicholson recommendation.

Like "$global:CurrentNaController.TimeoutMsec = 60000"

Please check "Getting HTTPS error using New-NaVol command".

Manuel

Rename-NaVol ending with error but successfully done

thanks for ur solution. working like a charm

Rename-NaVol ending with error but successfully done

Toolkit 1.5, released today, bumps the default timeout to 60 seconds.