Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Server & Application Monitor (SAM) > Node for Cluster Virtual IP replaces cluster member in Virtualization

Node for Cluster Virtual IP replaces cluster member in Virtualization

Created by Chris Foley, last modified by MindTouch on Jun 23, 2016

Views: 825 Votes: 1 Revisions: 4

Overview

This article provides brief information to prevent the issue when SAM Virtualization feature shows the Node for the cluster VIP linked to the ESX host, instead of the active cluster member.

Environment

  • All SAM versions
  • Cluster with Virtual Machines

Cause 

As queries to the cluster VIP are responded to by the active cluster member, SAM assumes these 2 systems are the same system.

Resolution

Notes:

  • When adding the Node for the cluster VIP, select the polling method of "ICMP".  
  • When adding the Nodes for the cluster members, select the polling method of "Agent".

 

As a result, the Nodes with a polling method of "Agent" will have a higher priority in the Virtualization calculations and the cluster VIP Node should be replaced with the active cluster member node under the ESX host.

 

 

 

 

Last modified

Tags

Classifications

Public