Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Windows Cluster VIP's

Dear All,

A quick question here. How to monitor volumes on Windows Cluster VIP's. Currently I'm monitoring these VIP's via ICMP (for status alone).

Scenario:

A - Active Cluster (All volume disks are green)

B - Passive Cluster (All volume disks are down/red)

C - Windows Cluster VIP (To neglect this down/red alert on passive node, I'm in need to monitor this VIP).

How to monitor this VIP..? We can't deploy agent. Is there any other way/credential to be set to monitor this as node..?

Kindly suggest. Thanks in advance..!

Regards,

Solaiy.

@silverbacksays @aLTeReGo

Find more posts tagged with

Accepted answers

sturdyerde

Yes, edit the node details and change its monitoring type to WMI (or SNMP if that is what you're using on each of the cluster nodes).

silverbacksays

Hey @Solaiy

Sorry for the late response on this. I had a long weekend due to the public holiday in the UK, and missed your mention!

When I monitor Windows clusters, I follow this process:

For each cluster node, monitor via SNMP or WMI (or the Orion Windows agent!), and when selecting your resources, ONLY select the resources which are permanent on that node. DO NOT select any cluster resources which happen to be currently mounted on that node!.
For cluster resources, add the cluster IP to Orion as you would any other node (again using WMI, SNMP, or agent), but when you come to selecting your resources, ONLY include the cluster objects, and DESELECT all the others (CPU/RAM, non-cluster drives, interfaces, hardware health, asset management if you have SAM and so on). This will avoid polling the information twice and unnecessary license use, as you'll be getting the non-cluster resources from the node's you are already managing.

That's it! Hope the above, and what @sturdyerde already provided, helps. Please let us know how you get on.

All comments

sturdyerde

In each cluster node's details page, click the 'List Resources' button and deselect the clustered resource's volumes. Then, go to the node details page for your cluster VIP (aka cluster name object) and use 'List Resources' to select those cluster resource volumes.

Solaiy

Hello @sturdyerde

Thanks for your reply. But here is the issue case. I couldn't open "List resources" page on Cluster VIP as it is managed via ICMP (only for status alone). I couldn't able to deploy an agent on this cluster VIP. Is there any other way to manage this cluster VIP as node..?

Regards,

Solaiy.

sturdyerde

Yes, edit the node details and change its monitoring type to WMI (or SNMP if that is what you're using on each of the cluster nodes).

Solaiy

From your reply, I could understand that we can monitor VIP's via WMI or SNMP.

So proper credentials needs to be created for VIP's. I'll check with my team on this & get back to you.

Thanks much.

Regards,

Solaiy.

silverbacksays

Hey @Solaiy

Sorry for the late response on this. I had a long weekend due to the public holiday in the UK, and missed your mention!

When I monitor Windows clusters, I follow this process:

For each cluster node, monitor via SNMP or WMI (or the Orion Windows agent!), and when selecting your resources, ONLY select the resources which are permanent on that node. DO NOT select any cluster resources which happen to be currently mounted on that node!.
For cluster resources, add the cluster IP to Orion as you would any other node (again using WMI, SNMP, or agent), but when you come to selecting your resources, ONLY include the cluster objects, and DESELECT all the others (CPU/RAM, non-cluster drives, interfaces, hardware health, asset management if you have SAM and so on). This will avoid polling the information twice and unnecessary license use, as you'll be getting the non-cluster resources from the node's you are already managing.

That's it! Hope the above, and what @sturdyerde already provided, helps. Please let us know how you get on.

Solaiy

Thanks much @silverbacksays & @sturdyerde.

It worked. I could able to deploy the VIP's via WMI & ICMP method. Monitoring the clustered resources via VIP & the non-clustered resources via nodes.

Regards,

Solaiy.