Hello, after relocating an SVM to a newly installed node, I can no longer connect to it with the Powershell toolkit. Same generic error if I use -https.
PS C:\Users\acac> Connect-NcController svm-fileshares.fqdn -Credential $Creds Connect-NcController : Could not connect to svm-fileshares.its.uow.edu.au on port 80 for protocol HTTP. At line:1 char:1 + Connect-NcController svm-fileshares.its.uow.edu.au -Credential $Creds + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidResult: (svm-fileshares.fqdn:NcController) [Connect-NcController], NaConnectionException + FullyQualifiedErrorId : HttpConnectionFailed,DataONTAP.C.PowerShell.SDK.ConnectNcController
Also currently having issues with snapdrive on exchange not connecting to its SVM after moving the svm to a new node. We moved the svm back to the old node as a work around for this. I have a ticket open for this.
Can't move svm-fileshares back to test if it starts working again until a maintenance day.
I just tested connecting with the IP addresses and get the same error.
Case number for this issue, 2008520018, was closed because powershell toolkit is not supported.
Case number for the Exchange Snapdrive issues, 2008521495, currently waiting for autosupport logs to be checked.
I have a feeling the issues are related because they are essentially the same symptoms - move svm to new nodes, then application (Snapdrive or powershell toolkit) doesn't connect with no real error message.