DX Unified Infrastructure Management

  • 1.  Failover Cluster Monitoring.

    Posted Aug 11, 2015 09:13 AM

    Dear All,

     

    We are using UIM, UMP of release 8.0.

     

    The customer wants to monitor the windows failover clustering servers.Lets there are three windows servers in failover clustering environment.

    Is there any specific probe for it ??

     

    How can we accomplish this requirement ?

     

    Regards,

    Suffian.



  • 2.  Re: Failover Cluster Monitoring.

    Posted Aug 11, 2015 09:53 AM

    Hi Suffian,

     

    If I understood properly, you can use cluster probe to monitor the failover.

     

    -kag



  • 3.  Re: Failover Cluster Monitoring.

    Posted Aug 18, 2015 06:12 AM

    Thank you kanandaguberan.



  • 4.  Re: Failover Cluster Monitoring.

    Posted Aug 11, 2015 11:14 AM

    Configure Cluster probe in your robot.



  • 5.  Re: Failover Cluster Monitoring.

    Posted Aug 18, 2015 07:45 AM

    The customer has a Microsoft Cluster server named "DR-C01" with IP of 10.109.50.4, which has three cluster servers nodes as (1) DR-C01-N01 with IP(10.109.50.11) , (2) DR-C01-N02 with IP(10.109.50.12) and (3) DR-C01-N03 with IP(10.109.50.13).

     

    We have been installed the windows robots on all three cluster servers nodes and distributed/configured the 'cdm' probe on all three nodes as well.

     

    The 'cluster group' is only showing under the node 'DR-C01-N01', not on other two nodes. And that cluster group's 'shared' & 'profiles' have showing cdm metrics.

     

    Secondly, the "Available Storage" on DR-C01-N02 with IP(10.109.50.12)  is showing cross with red color, but in actually this is UP.

     

    We have attached the screenshot of 'cluster probe' and three logs files of three nodes running cluster probe (Note: 10.109.50.x used for communcation with all our networks and 192.168.168.x is used for communication with in cluster)..

     

    Any help would be greatly appreiated.



  • 6.  Re: Failover Cluster Monitoring.

    Posted Aug 18, 2015 12:26 PM

    That sounds like how it should show for an empty cluster. Do you have any roles / resources currently configured in the cluster? They should show up in the cluster probe. Modern day wsfcs don't necessarily have any storage in them, unfortunately the probe won't understand that and will always show it as red cross. You can work around this by enabling storage in the cluster without adding anything into it, but that is kind of ugly. I'm not seeing the screenies or logs, though.

     

    -jon



  • 7.  Re: Failover Cluster Monitoring.

    Posted Aug 19, 2015 02:35 AM

    Thank you for your response.

     

    Actually we are facing issue to add log files here.

    Below is a screenshot, could you please guide me where we can add roles/resources.We have been configured the 'shared' and 'profiles' on which by selecting the 'cdm' drop down menu.

     

    Secondly, these are the log files lines from cluster server node 02 where the 'available storage' is offline showing; (Note: 10.109.50.x used for communcation with all our networks and 192.168.168.x is used for communication with in cluster)

    "Aug 19 11:15:07:872 cluster: InitalizeCluster - this node 'DR-C01-N02' was found in the configuration

    Aug 19 11:15:07:872 cluster: InitalizeCluster - this node=DR-C01-N02 IP=10.109.50.12

    Aug 19 11:15:07:872 cluster: Initialize Cluster OK!

    Aug 19 11:15:07:888 cluster: Initialize Resource Groups OK!

    Aug 19 11:16:00:852 cluster: (updateNodeConf) - Session Send failed to ip/host=192.168.168.1

    Aug 19 11:16:47:956 cluster: (updateGroupConf) - Session Send failed to ip/host=192.168.168.1

    Aug 19 11:17:32:028 cluster: (updateGroupConf) - Session Send failed to ip/host=10.109.50.13

    Aug 19 11:18:19:083 cluster: (updateNodeConf) - Session Send failed to ip/host=192.168.168.1

    Aug 19 11:19:05:140 cluster: (updateNodeConf) - Session Send failed to ip/host=10.109.50.13"



  • 8.  Re: Failover Cluster Monitoring.

    Posted Aug 19, 2015 02:45 AM

    What I meant by roles / resources are cluster resources. You seem to have them there, such as "vMSDR-V5AppSrv02" etc.

     

    I see you have some replication errors there, you probably want to check that the robots are using the correct IP and not the replication network interface. You'll also want to make sure that if firewalls are enabled, that you allow the probe range between those machines as they interact with each other directly in this case.

     

    in "shared" section you add configurations that you want to exist concurrently on a probe on each of the nodes, for example messages. In profiles you add the actual checkpoints that move with the cluster resources, for example SQL services.

     

    -jon



  • 9.  Re: Failover Cluster Monitoring.

    Posted Aug 19, 2015 05:39 AM

    Thank you Jonhcw

     

    There are no firewalls configured between them and the robots are using the

    correct IP.

     

    We have configured the 'shared' and 'profiles' on UP resources, but we

    could not see any 'metrics' on the USM.

     

    Secondly, why the 'available storage' on node 02 is being showing offline,

    which is actually online/up.

     

     

    Please find below the latest cluster probe log file.



  • 10.  Re: Failover Cluster Monitoring.

    Posted Aug 19, 2015 05:59 AM

    Hmm hard to say.. it looks like a connectivity issue to me.

     

    -jon



  • 11.  Re: Failover Cluster Monitoring.

    Posted Aug 19, 2015 07:27 AM

    Hi,

     

    Just see if there is any firewall blocking communication between the servers?

     

    -kag



  • 12.  Re: Failover Cluster Monitoring.

    Posted Aug 19, 2015 07:43 AM

    There are no firewalls configured between them.


    kanandaguberan, Is there any thing interesting in node 02 log file ?