topic Re: SIM file system utilization reporting incorrect drive letter in Server Management - Systems Insight Manager

SIM file system utilization reporting incorrect drive letter

Harrison Sauls — Tue, 05 Feb 2008 14:24:06 GMT

What would cause the file system usage threshold to alert for the wrong drive letter? G: is exceeding its threshold, but the alert reports Q: - which is the quorum for the cluster and has 99% free space.

Restarting the storage and foundation agents had no affect. Any suggestions would be appreciated.

Re: SIM file system utilization reporting incorrect drive letter

Harrison Sauls — Wed, 13 Feb 2008 20:07:30 GMT

Hello? Is this thing on?

Re: SIM file system utilization reporting incorrect drive letter

Andrea Giangone — Wed, 08 Oct 2008 14:58:49 GMT

I'm having the same issue.
The alert shows:
Event Name: (SNMP) Rising Threshold Passed (10005)
URL: https://goliath.kddiglobal.com:2381/
Event originator: Goliath
Event Severity: Critical
Event received: 08-Oct-2008, 11:26:40

Event description: Rising Threshold passed. An alarm entry has crossed its rising threshold. The instances of those objects contained within the variable list are those of the alarm entry which generated this trap.

Description: K:\ [Backup:NTFS] disk space
Severity Level: warning
Current Value: 60
Threshold Top: 60
Threshold Owner: Insight Web Agent

In reality the drive hitting the threshold is drive E.
E:\ [MSA30L2:NTFS]
Drive K is at 15% utilization.
How do we fix the mapping in SIM?

Re: SIM file system utilization reporting incorrect drive letter

Harrison Sauls — Wed, 08 Oct 2008 15:27:05 GMT

Andrea,

We never did find a resolution to this problem. We ended up just making note that the drive letters were different so that when we get alerts from the Q: drive on this server, we know that it's actually G:

Please respond with any resolution you happen to find.

Regards,
Harrison

Re: SIM file system utilization reporting incorrect drive letter

Andrea Giangone — Wed, 08 Oct 2008 16:37:39 GMT

Hi Harrison,

another workaround is to set the thresholds slightly off from each other so that you know which one it is being triggered.
I'm not running some queries in the SIM database to see if the answer lies in there.
I'll post if I get anywhere.
Andrea