topic Re: Disk Threshold Error SIM 5.3 in Server Management - Systems Insight Manager

Disk Threshold Error SIM 5.3

JL123 — Fri, 27 Mar 2009 00:28:03 GMT

Hi,

After recently upgrading to SIM 5.3, I would like to get the disk threshold setup. Everything with the SIM server is now working fine, the trust relationships are fine, I can deploy firmware and PSP's etc. The only problem is the disk threshold's dont seem to be working for any servers and I have no idea why. A quick scout of these forums and I can't find any answers.

Here's the error.

Event description: The Set Disk Threshold task was run on a set of systems, see the details below to determine if it succeeded or failed on each system

Could not set the disk threshold, the agent did not accept the request.

Any help would be great.
Thanks.

Re: Disk Threshold Error SIM 5.3

Zhang, Jun-Wu — Fri, 27 Mar 2009 00:41:34 GMT

Hi

I notice the point is "the agent did not accept the request", so I think maybe you could check whether the communication protocols such as SNMP/WBEM are totally configured without any flaws.

Apart from that, I think account security should be also took into consideration.

good luck!

Re: Disk Threshold Error SIM 5.3

Zhang, Jun-Wu — Fri, 27 Mar 2009 00:41:57 GMT

Re: Disk Threshold Error SIM 5.3

JL123 — Fri, 27 Mar 2009 02:32:27 GMT

Thanks for the quick response.

Here's a screenshot of the protocols page. Everything else is working fine which leads me to believe it's not that.

The sim service account is also working for everything else, it's just the disk threshold which is not good, there must be something basic im missing.

Re: Disk Threshold Error SIM 5.3

Thomas Genzyme — Fri, 20 Nov 2009 11:51:59 GMT

It is possible to configure the treshold if using WBEM?
Could someone from HP respond please?

Re: Disk Threshold Error SIM 5.3

metalhead84 — Tue, 26 Jul 2011 19:43:41 GMT

Running into the same issue as well. Did anyone have luck getting this resolved?

Re: Disk Threshold Error SIM 5.3

shocko — Wed, 03 Aug 2011 18:52:13 GMT

It might be the SNMP configuration on the agents on the target servers. You MUST have at least one community string that is READ/WRITE in order to set the disk thresholds. The agents themselves communicate with the System Management Homepage using SNMP as far as I remember ;)