Monitor SQL 2000 Cluster

Ciaran

I have a similar problem that I've spent some time on as well.

  It discovers that sql is running on the cluster resource, as evident in the fact it shows up under computers within the Microsoft SQL Server view, but sql itself is coming up not monitored.  I've reviewed the overrides and nothing is disabled.  I have also checked the allow to act as a proxy tick box as ciaran did above.

Suggestions?

If you restart the agent on the active node this will initialize a new discovery.  After this you can check the Operations Manager log which should have some warnings and errors in to help you find why SQL isn't being discovered.

It is also worth checking that your Action Account or SQL RunAs accounts (if you have specified them) have the relevant permissions.  You can get more information about that in the SQL MP guide.

Also, have you upgraded to SP1 yet and do you have the latest MP version?

Hope that helps, post back if you still have problems.

There is a couple of things that I had to do to resolve the issue.

Check to make sure that the DNS name exists for the cluster name. If not add in in manualy. see below.

Also make sure that you have only on network name in each cluster group. the cluster network name and the sql instance name can not exist in the same group.

 hope this helps.

Ciaran

Ok,

   Ciaran, Great info.  I've updated the OperationsManager.dbo.MT_Computer fields appropriately.  You're absolutely correct.  Updating those fields and now I'm starting more info.  The strange thing I'm seeing now is that I'm getting only 1 cluster group out of 3.  Here's how I have it configured in Operations Manager:

 Both nodes in the cluster I have selected the check box so they act as a proxy agent.
 Updated the Operational DB with the proper DNSName to allow discovery

I've restarted the agents associated with these servers nearly 1 week ago ( post config changes as listed above )

Suggestions?

Dennis

Hope this helps.

Ciaran