Connect-NaController: -rpc needs twice the time of -http

wippel — Thu, 05 Jun 2025 06:26:17 GMT

PS R:\> $s1=Connect-NaController t3 -http -Credential jw
2012-05-29 13:42:45,103 INFO DataONTAP.PowerShell.SDK.ConnectNaController - Cmdlet invocation: $s1=Connect-NaController t3 -http -Credential jw
2012-05-29 13:42:45,118 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connecting to t3 via HTTPS
2012-05-29 13:42:45,808 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAPI version is 1.14
2012-05-29 13:42:46,421 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAP version is NetApp Release 7.3.6P5: Sat Dec 10 02:14:41 PST 2011
2012-05-29 13:42:46,423 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3 using HTTP
2012-05-29 13:42:49,602 DEBUG NetApp.Ontapi.NaServer - <results status="passed"><system-info><system-name>t3</system-name><system-id>0135112935</system-id><system-model>FAS2040

PS R:\> $s1=Connect-NaController t3
2012-05-29 13:43:19,198 INFO DataONTAP.PowerShell.SDK.ConnectNaController - Cmdlet invocation: $s1=Connect-NaController t3
2012-05-29 13:43:19,207 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connecting to t3 via RPC
2012-05-29 13:43:21,759 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAPI version is 1.14
2012-05-29 13:43:22,474 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAP version is NetApp Release 7.3.6P5: Sat Dec 10 02:14:41 PST 2011
2012-05-29 13:43:22,475 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3 using RPC
2012-05-29 13:43:28,977 DEBUG NetApp.Ontapi.NaServer - <results status="passed"><system-info><system-name>t3</system-name><system-id>0135112935</system-id><system-model>FAS2040

PS R:\> $s1=Connect-NaController t3 -http -Credential jw
2012-05-29 13:44:09,751 INFO DataONTAP.PowerShell.SDK.ConnectNaController - Cmdlet invocation: $s1=Connect-NaController t3 -http -Credential jw
2012-05-29 13:44:09,760 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connecting to t3 via HTTPS
2012-05-29 13:44:10,266 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAPI version is 1.14
2012-05-29 13:44:10,830 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAP version is NetApp Release 7.3.6P5: Sat Dec 10 02:14:41 PST 2011
2012-05-29 13:44:10,831 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3 using HTTP
2012-05-29 13:44:14,530 DEBUG NetApp.Ontapi.NaServer - <results status="passed"><system-info><system-name>t3</system-name><system-id>0135112935</system-id><system-model>FAS2040

PS R:\> $s1=Connect-NaController t3
2012-05-29 13:44:22,208 INFO DataONTAP.PowerShell.SDK.ConnectNaController - Cmdlet invocation: $s1=Connect-NaController t3
2012-05-29 13:44:22,216 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connecting to t3 via RPC
2012-05-29 13:44:25,374 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAPI version is 1.14
2012-05-29 13:44:27,294 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3, ONTAP version is NetApp Release 7.3.6P5: Sat Dec 10 02:14:41 PST 2011
2012-05-29 13:44:27,295 DEBUG DataONTAP.PowerShell.SDK.ConnectNaController - Connected to t3 using RPC
2012-05-29 13:44:36,137 DEBUG NetApp.Ontapi.NaServer - <results status="passed"><system-info><system-name>t3</system-name><system-id>0135112935</system-id><system-model>FAS2040

Re: Connect-NaController: -rpc needs twice the time of -http

bsti — Thu, 31 May 2012 16:27:39 GMT

I notice the same thing, but I think this is expected. I don't think HTTP and HTTPS communicate as fast as RPC. IT's nice to have the alternateive methods available to communicate though, in case for some reason RPC won't work. I know two cases where thsi happens:

1) You have a firewall between you and the controllers that blocks random high ports

2) You need to pass in credentials other than those you are logged on currently with.

Re: Connect-NaController: -rpc needs twice the time of -http

bsti — Thu, 31 May 2012 19:37:51 GMT

Obviously, I misread your question. I'm still not entirely clear on what your question is, but my guess is that you are expecting to see what I do, in that RPC connects faster than HTTP/HTTPS, correct?

I won't remove my post, as the information is still valid and perhaps helpful to someone else. Do you have a firewall between the machine you are running Powershell on and the controllers? Do you have CIFS setup properly on the controllers and is it configured to use Active Directory for authentication? THe long paus you are seeing with RPC is likely related to the controller trying to query Active Directory. Do you have any known issues with your AD controllers, errors in the even logs, etc...?

Have you run a cifs domaininfo from the command line and looked at the output for errors? How about a cifs testdc?

Both of those commands may shed some light on whether or not the long pause is AD-related or not.

Re: Connect-NaController: -rpc needs twice the time of -http

wippel — Fri, 01 Jun 2012 09:50:06 GMT

Thanks

topic Re: Connect-NaController: -rpc needs twice the time of -http in Microsoft Virtualization Discussions

Connect-NaController: -rpc needs twice the time of -http

Re: Connect-NaController: -rpc needs twice the time of -http

Re: Connect-NaController: -rpc needs twice the time of -http

Re: Connect-NaController: -rpc needs twice the time of -http