Try narrowing your API call to a specific node. It’s possible it’s trying to query the node that’s down and causing the timeout.
API might not be smart enough to know to ignore a node that is not up.
Also be sure to check that it did fail over properly as tmac mentioned. And that the cluster is in quorum. (set diag; cluster show; cluster ring show)
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of tmac Sent: Wednesday, March 30, 2016 8:59 AM To: Vladimir Zhigulin Cc: toasters@teaparty.net Subject: Re: NetApp SDK for cDOT: any API call fails if a cluster node is not available
Did the cluster interface failover correctly? can the host doing the API calls "ssh" into the cluster address?
--tmac
Tim McCarthy, Principal Consultant
On Wed, Mar 30, 2016 at 8:34 AM, Momonth <momonth@gmail.commailto:momonth@gmail.com> wrote: Hi All,
We extensively use NetApp API calls to monitor 7Mode filers, and took the same approach for cDOT monitoring.
Here is a very unpleasant discovery:
1. Take one node (or more nodes) *offline*, eg power it off for maintenance. 2. Try to run *any* API call against cluster interface and get the following error:
OUTPUT: <results reason="RPC: Port mapper failure - RPC: Timed out" status="failed" errno="13001"></results>
It effectively makes your cluster wide monitoring useless.
Any ideas? Is it a feature or a bug?
Cheers, Vladimir _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters