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

Monitoring services in cluster (Active/Passive)

Hi,

I'm novice in Orion.

We have a cluster with 2 virtual server Active/Passive.

We need monitoring one service on them, that running on one host at a time.

If i create component "Windows service monitor" on both hosts - passive host always in "warning" status and Application always in "down" status.

We don't need receive these statuses (and alerts), until host becomes active.

Is there a way to fix this?

Find more posts tagged with

cluster

Accepted answers

bscherer

I add each cluster service as a node and then monitor the cluster resources on that node.

For example. I have a 2 node sql cluser

node1 - monitor local resources(os boot for example)

node2 - monitor local resources(os boot for example)

Cluster Service - monitor cluster resources(volumes,sql service,etc..)

I hope this made sense, but it has worked well for me.

All comments

bscherer

I add each cluster service as a node and then monitor the cluster resources on that node.

For example. I have a 2 node sql cluser

node1 - monitor local resources(os boot for example)

node2 - monitor local resources(os boot for example)

Cluster Service - monitor cluster resources(volumes,sql service,etc..)

I hope this made sense, but it has worked well for me.

bardeev

Thanks, I'll try your method.

xjames212x

bscherer, This is the method I employ as well.. and it works perfect... However my perfect world was turned upside down when an auto-discovery was put in place. All of the cluster members which owned resources at the time of the discovery were modified with the cluster resources to their node.

Pre-discovery:

node1 - monitor local resources(os boot for example)

node2 - monitor local resources(os boot for example)

Cluster Service - monitor cluster resources(volumes,sql service,etc..)

Post-discovery

node1 - monitor local resources(os boot, volumes,sql service,etc..)

node2 - monitor local resources(os boot for example)

Cluster Service - monitor cluster resources(volumes,sql service,etc..)

Any experience for solving for this condition? I have stopped the discovery job on the cluster subnet, but have a LOT of stuff to remediate. I don't want this to happen again ;>

bscherer

I dont use auto-discover, but....

Maybe do a sql agent job or ps script that performs cleanup? Or a Orion action that triggers a cleanup script? Probably some more elegant solutions, just off the top of my head.