DX Unified Infrastructure Management

Expand all | Collapse all

Monitoring cluster elements in eHealth

  • 1.  Monitoring cluster elements in eHealth

    Posted May 12, 2015 10:23 AM

    We're currently monitoring two nodes that are clustered.  There are filesystems that will move with the active member of the cluster, but they aren't present on the inactive node.  How can we get the elements discovered so they can be monitored using Live Exceptions?

     

     

    Thanks

    Steve Moore



  • 2.  Re: Monitoring cluster elements in eHealth

    Posted May 12, 2015 11:28 AM

    Steve ,

     

      ehealth goes not support cluster monitoring .

    eg: If you have three partition A,B,C in  node 1  when you discover or re discover the elements will update .If there is a fail-over the partition  A,B,C will move to node 2 .During that time you can re-discover the device at Node 2 .



  • 3.  Re: Monitoring cluster elements in eHealth

    Posted May 12, 2015 01:58 PM

    Yeah, clustering is such a new technology.  I can understand why a top end product like eHealth wouldn’t support it yet.

     

    And now, eHealth is “not a strategic solution”…

     

     

    Thanks



  • 4.  Re: Monitoring cluster elements in eHealth

    Posted May 12, 2015 02:05 PM

    Does UIM support clusters yet?

     

     

    Thanks

    Steve



  • 5.  Re: Monitoring cluster elements in eHealth

    Posted May 13, 2015 07:20 AM

    UIM does support cluster monitoring.



  • 6.  Re: Monitoring cluster elements in eHealth

    Broadcom Employee
    Posted May 12, 2015 02:17 PM

    Microsoft Clustering is supported with the Microsoft Cluster AIM for VAIM.  Here is a list of the metrics that you can poll via eHealth and the AIM:

     

    http://ehealth-spectrum.ca.com/devices/private/114-cn-69-1717-mtfs.html



  • 7.  Re: Monitoring cluster elements in eHealth

    Posted May 12, 2015 02:23 PM

    Thanks for the information.  Unfortunately, this particular instance is an Oracle cluster on some Unix/Linux flavor.  We do have other Microsoft clusters though so the information isn’t wasted.

     

     

    Thanks

    Steve



  • 8.  Re: Monitoring cluster elements in eHealth

    Posted May 12, 2015 02:29 PM

    Does the agent for Microsoft Clustering get installed as a cluster resource?  That might not be the right terminology.  If the systemEDGE agent is already installed on each node, does it need to be reinstalled in a way that the agent will be “moved” with the cluster activity?

     

     

    Thanks

    Steve



  • 9.  Re: Monitoring cluster elements in eHealth

    Broadcom Employee
    Posted May 12, 2015 02:43 PM

    The cluster AIM uses WMI to communicate with the cluster and nodes:

     

    MSCS Architecture Diagram

     

    You can read more info about it here:

     

    CA Virtual Assurance for Infrastructure Managers Bookshelf Release 12.9

     

    I haven't tried installing SystemEDGE + MSCS AIM as a cluster service but perhaps someone else can chime in if they have experience with that.  Otherwise, installing on a Windows system outside of the cluster works.



  • 10.  Re: Monitoring cluster elements in eHealth

    Posted May 12, 2015 02:30 PM

    MSCS Aim is there for MS cluster .Hope there will not be a constant performance report  for partitions .



  • 11.  Re: Monitoring cluster elements in eHealth

    Posted May 12, 2015 02:44 PM

    Reporting is “as needed” when someone needs to justify their existence.  We’re looking to use Live Exceptions to establish utilization thresholds and send alerts before an app/service goes down because of lack of disk space.

     

     

    Thanks again.

     

    Steve



  • 12.  Re: Monitoring cluster elements in eHealth

    Broadcom Employee
    Posted May 12, 2015 02:06 PM

    What is the clustering technology that you're using? 



  • 13.  Re: Monitoring cluster elements in eHealth

    Posted May 13, 2015 07:18 AM
      |   view attached

    The attached document will provide some guidance with regards to monitoring cluster elements with eHealth.

     


    Attachment(s)