Highlighted
Moderator
Moderator

InsightIQ about Configure InsightIQ to monito cluster.

HI there ..

Can Anybody know the reason below line has removed from IIQ 4.1.3 ?

 

Avoid specifying an IP address that can be transferred from one node toanother node.

 

Above comments has been in installation guides ( eg ,https://support.emc.com/docu79772_Isilon-InsightIQ-4.1.0-Installation-Guide.pdf?language=en_US Page26 ) and User guide ( eg ,https://support.emc.com/docu70283_InsightIQ-4.0.1-User-Guide.pdf?language=en_US Page 28 )

But Its gone in 4.1.3. In this version , OK to use Dynamic IP or Service IP for IIQ to monitor cluster ?

 

found this thread(  https://www.dell.com/community/Isilon/InsightIQ-monitoring/td-p/7001264 ) but nobody actually mention about this point . It seems to be better to use Dynamic IP ....

If you'd rather use and IP - point IIQ at a pool of dynamic IPs that has automatic failover. This way, if a node does go down, the IP will be moved to a different node.

 

Am I missing something ?

thanks !

0 Kudos
2 Replies
Highlighted
3 Zinc

Re: InsightIQ about Configure InsightIQ to monito cluster.

https://community.emc.com/docs/DOC-79731 - 

OneFS 8.2: Smartconnect Service IP Address (SSIP/VIP) does not allow connections beyond DNS traffic.

0 Kudos
Highlighted
2 Iron

Re: InsightIQ about Configure InsightIQ to monito cluster.

From the perspective of availability, I'd always suggest the following for any users of the API (including InsightIQ).

Create a dynamic pool with only one IP address. Use this pool as the name to connect to. This has the following characteristics:

  • IP is highly available. Unlike an IP from a static pool, the IP will move if the node hosting the IP becomes unavailable.
  • But in steady state, the IP will remain associated with a single node which allows for the more efficient cookie-based auth to be used rather than needing to re-authenticate for every request

I wouldn't use a pool with multiple IPs because that would break the second guarantee, and as @PhilLam mentioned, you can't use the SmartConnect Service IP for anything other than DNS (which is all it was ever intended for).

So the removal of the restriction is correct, taking the detail above into account.

Tim

0 Kudos