Add cluster to IIQ 4.1.1.3 vApp

Hi,

In my own lab (virtual), I've only used hard IP of specific nodes for InsightIQ connections.

I'm seeking comments from Engineering on this.  I'll get back to you.

Thanks.

Hi dynamox,

Response from Engineering is that SmartConnect is a tested/validated feature for IIQ.  As to why it is not working for you, we'd need to know the specifics of the environment.  Could you open a support case for this so Support could investigate?

Thanks.

Rob,

i have an SR opened, 30 days into it and we have not gotten anywhere.  SR 07391024

have you tested IIQ vApp with your cluster ?

identified as bug

Thanks.  I've been following the development in that SR.  The bug has been filed with Engineering.

unfortunately in typical Isilon support fashion it was blamed on my network, until I pointed out what the issue was which had nothing to do with my network.  Very disappointing customer experience.

Any chance there are underscores in the hostname? ( just ran into something similar on an unrelated project ).

> Very disappointing customer experience.

I have basically stopped opening tickets if at all possible due to the workload involved.

Eric,

no underscores, IIQ does not get restarted after changing network settings during IIQ deployment so it stays bound to loopback interface.

Hmmm I have found that in cases where tickets are not responded I had to either hammer the SR owner or get in touch with our Rep and have them get on it.

Dynamox, I was going to deploy this new version.  Are you using a cluster IP and avoiding the SIP for now?

Hi dynamox,

Very sorry to hear about your experience.  I know for a fact that there has been a recent re-engagement here from top to bottom to re-focus on customer satisfaction (we call “CSAT”).  This has the buy-in of all senior leaders.  Everyone from management to individual contributors are asked to improve CSAT however they can.  I will bring this case to the attention of product management, to see if we can identify this as a gap in the product or in the training.  I am certain that your experience with support will improve in the near future.

From looking at the technical details of this SR, the issue was first investigated by support, trying to repro the issue.  Upon successful repro of the issue, a more technical team member was able to debug this all the way “past” IIQ down to system libraries, to a “known issue” with the said library.  (“Known issue” as in known in the open source world.)  The defect that was filed was for a clarification of whether the application (InsightIQ) or the administrator that made the networking changes should take on the responsibility of reloading the modified configuration file.

Thanks for your understanding and your patience.

Robert,

You are mis-informed. For 30 days !!!  support was actively working on finding a way to blame my network, my smartconnect configuration. Finally i received a note from the "coach" that stated that i need to properly configured my smartconnect zones, or stop using SZ name because it's recommended to use IP which is complete non-sense. Best practices IS to use smartconnect zone name when adding cluster to IIQ.  Finally I found the issue, not support.

Yeah, I have been hearing about re-focus on customer satisfaction ever since Gordon Winters went to Isilon with promises to bring Isilon support to Symmetrix levels.  Still waiting ....

I'm sure we will get a refocus about the time we get truly non-disruptive upgrades/failover like NetApp.  We've been promised that since OneFS 6.5.