topic Re: error: Failed to connect to cluster node in Active IQ Unified Manager Discussions

error: Failed to connect to cluster node

kofchur — Fri, 01 Nov 2013 13:36:27 GMT

Anyone ever get this? Connectivity if fine with other work flows and when I test the connection via WFA it if fine.

Here is the ouput from the logs:

16:26:03.640 INFO [null] ***** Workflow Execution Started *****

16:26:03.734 INFO [No-Op Cluster-Mode] ### Command 'No-Op Cluster-Mode' ###

16:26:05.590 INFO [No-Op Cluster-Mode] Executing command: ./No-Op__Cluster-Mode287812791300535551.ps1 -ClusterName bbcs1va2.blackboard.com -VolumeName wfa_opsmart_test_va2 -VserverName vsnfsbbl

16:26:05.606 INFO [No-Op Cluster-Mode] This Command does nothing

16:26:05.668 INFO [No-Op Cluster-Mode] Command completed, took 1934 milliseconds

16:26:05.762 INFO [Create CM Qtree Quota] ### Command 'Create CM Qtree Quota' ###

16:26:07.618 INFO [Create CM Qtree Quota] Executing command: ./Create_CM_Qtree_Quota2887597892783720890.ps1 -Cluster bbcs1va2.blackboard.com -QtreeName wfa_opsmart_test_va2_qtree -VolName wfa_opsmart_test_va2 -VserverName vsnfsbbl

16:26:07.665 INFO [Create CM Qtree Quota] Get-NaCredentials -Host bbcs1va2.blackboard.com

16:26:07.712 INFO [Create CM Qtree Quota] Connect-NcController (without credentials) -Name bbcs1va2.blackboard.com

16:26:08.055 ERROR [Create CM Qtree Quota] Failed to connect to cluster node: bbcs1va2.blackboard.com.

The requested name is valid, but no data of the requested type was found

16:26:08.289 ERROR [Create CM Qtree Quota] Command failed for Workflow 'BB_Set_Path_Quota' with error : Failed to connect to cluster node: bbcs1va2.blackboard.com.

The requested name is valid, but no data of the requested type was found

16:26:08.289 INFO [Create CM Qtree Quota] ***** Workflow Execution Failed *****

Thanks.

Re: error: Failed to connect to cluster node

kandati — Mon, 04 Nov 2013 18:18:22 GMT

Hi,

Have you added the credentials for the host : bbcs1va2.blackboard.com, in the WFA (Execution->Credentials page).!

If you have added it, can you please try to test the connectivity for this host by using Test Connectivity option in the Credentials page by providing the host name(bbcs1va2.blackboard.com), you can do this by right clicking on that page,( I guess you are still using pre-2.1 build,where you don't find any tool kit icons on the top of the page)..!

In generally we get the below log message when we don't have the entry in Credentials page for that particular host.

16:26:07.712 INFO [Create CM Qtree Quota] Connect-NcController (without credentials) -Name bbcs1va2.blackboard.com

Warm Regards

Sivaprasad K

Re: error: Failed to connect to cluster node

kofchur — Tue, 05 Nov 2013 15:34:30 GMT

Credentials are fine. I have already tested them with the method you speak, and other workflows are working, so it is not a communication problem or a credential problem per se:

Re: error: Failed to connect to cluster node

F_SCHUBERT — Wed, 09 Apr 2014 15:23:18 GMT

Hi, we experience exactly same problem. Did you find any solution?

We figured out that it only happen on newly created SVM.

The diffenrence in the log shows that SVM1 and SVM2 uses an IP address while SVM3 (the problematic one) uses the the hostname (not FQN).

regards Frank

Re: error: Failed to connect to cluster node

glennhuang — Thu, 01 Dec 2016 11:45:50 GMT

Hi Did you find any solution?

Re: error: Failed to connect to cluster node

jauling_chou — Fri, 16 Jun 2017 11:46:57 GMT

It would be nice if there was a feature in WFA to tune connection retries and as well as connection timeout values.

Re: error: Failed to connect to cluster node

sinhaa — Fri, 16 Jun 2017 15:01:18 GMT

@jauling_chou

It would be nice if there was a feature in WFA to tune connection retries and as well as connection timeout values.

---

This doesn't need a feature. This is already possible to have connection retires and timeout as parameters into command code. Just modify your code accordingly.

@kofchur @F_SCHUBERT @glennhuang

Have you been able to resolve your issue?

sinhaa

Re: error: Failed to connect to cluster node

jauling_chou — Fri, 16 Jun 2017 15:15:57 GMT

This is true, except that certified commands can't be modified, so they'd need to be cloned, then tuned AFAIK. We have a few CDOT clusters located in multiple geographies which sometimes have minor connectivity issues with WFA.

Re: error: Failed to connect to cluster node

sinhaa — Fri, 16 Jun 2017 19:52:46 GMT

@jauling_chou

A certified command covers the most common generic use cases to fulfill the most common requirements. User specific requirements will always have to be fulfilled by creating custom contents and cloning of a certified command and then modifying makes it so much easier than starting from zero.

There is functionally NO differnce between a certified command and a custom command. But if you need certification and support, NetApp professional services is the option for you.

@ We have a few CDOT clusters located in multiple geographies which sometimes have minor connectivity issues with WFA.

-----

I understand this, but this problem needs to be dealt at the command code and not by having new a WFA feature.

sinhaa