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
Store

Advice on clustered drives please.

I have built a clustered SQL application monitor, it is quite small with only two nodes added (I have added the clusters IP address, rather than the two nodes themselves.) They share, like probably all clustered environments, the drives and the services.

I would like to monitor the drive(s) so that if the cluster ever fails and the drive swaps over, I can have a notification to know where the drive is.

I was playing around with the drive and couldn't find a way to resolve this. As a small fix, I added the drive to both nodes and tried to come up with a work around.

I have been thinking that as the cluster is being monitored, shouldn't it be true that EVERYTHING is monitored within that cluster? If that is the case, why, when I failover to the passive node, did my cluster display that the two shared drives were down? This is the reasoning for me adding both drives to each node.

Also, with regards to the alerts. I have been trying to set an alert up. I don't care if the drive swaps over, only that I know that the drive swaps over. I was playing around with alerts yesterday and trying to get my alert to work, but I couldn't.

I was monitoring the drives themselves and looking for any state changes. Again, I don't care if the drive moves from one node to the other, just that if the node moves, then I need to know about it.

Is there.

I hope someone can assist me.

Failover+cluster+test.xml

Find more posts tagged with

Accepted answers

shaun_9999

I think I have figured it out.

When you failover, it takes seconds to move from the active to the passive. So I will never see an alert about it.

Is it still worth having an alert to see if the cluster fails.

All comments

shaun_9999

I think I have figured it out.

When you failover, it takes seconds to move from the active to the passive. So I will never see an alert about it.

Is it still worth having an alert to see if the cluster fails.

skyblademonkey

Could monitor each cluster node for local resources only

Clustered resource for shared resources only

server 1

cpu,memory,local disks/resources

server 2

cpu,memory,local disks/resources

Cluster VIP

cpu,memory,shared disks/resources

the snmp system name will be returned as the clustered node the resource sits on so If the cluster nodes flips over from one node to the other then you might see the snmp system name change and setup an alert to alert on system name change. Also possible to search event logs but does depend on the protocols available to use,

shaun_9999

I have kinda figured it out. I don't like how solarwinds have done clusters. Both SQL and non-SQL. I would like them to maybe invest a little more time within clusters, such as getting them monitored and built correctly. Having three nodes within solarwinds seems a little ill thought out.

Why can't they have them build and monitored as clusters are built. I have suggested that they develop a little more with a couple of ideas, but we will see what happens. I'm new to this type of job role, so for me it's also a steep learning curve. So I might just be really bad at solarwinds.