Low disk space notifications possible from SIM???

[Jason Salgado]

Is it possible to get low disk space notifications from HP SIM 5.3 for servers that are configured properly?
Right now a big majority of our production servers need to have the subscription to WBEM events pushed down. When they were built, this was not done, so I don't see a lot of the physical server specs when doing a data report which I am guessing is needed to properly get the notifications if that is even possible.

For servers that are properly set up is there a way to set it up or does HP SIM do it automatically or does it need help from MOM?
Any help would be appreciated as I am new to HP SIM.
Thanks

[Jason Salgado]

Well digging around I found that you can go to the system management page of the "individual servers" and set thresholds on the servers themselves.
This is a step in the right direction, but can it be done globally from HP SIM itself? Seeing as we have over 600 servers doing so would be a lot of work.

[AdamJ]

Yes, it can be done globally. If you go to the configure menu in SIM and then to Disk Thresholds. You will then be able to set thresholds for multiple servers.

Adam

[Jason Salgado]

hum, this is an error message i get when trying to set it from HP SIM...
"Could not set the disk threshold, the agent did not accept the request."

When I went to the server itself, and set the threshold, it is set, but I am not getting any notifications. I set the:
Warning = 20
Critical = 25

Right now I have 21% free disk space on that server and getting no notifications. It is an Win08 server with PSP 8.25A.

[AdamJ]

Have you imported the SIM certificate into the Systems Management Homepage of the servers that you are trying to modify?

[Jason Salgado]

Well that is what I was confused about. Right now I am in the middle of wiping the server to put 2003 back on.
When I was in the "client" server homepage, it said "trust by certificate" and it had the fqdn of our HP SIM server in there. Also if I looked at the HP SIM cert, the one that comes preinstalled on the SIM server, it is the same hash as when I look on the "client" server.
If that is set up do I still need to physically export the cert and import it into the "client" server? I even tried to put in the HP SIM server name and it said the cert import was successful.

[Jason Salgado]

I deleted the test server out of HP SIM.

OK, 2003R2 server is up. PSP is installed and I went to the System Management Homepage of the server.
Settings>SMH>Security>trusted management servers... clicked Get Cert Information and typed the name of the HP SIM server FQDN and clicked add. Server cert was successful. Now listed under Trust Mode, Trust by Certificate is checked and when I click on Trusted Certificate it takes me back to the certs where i see the cert in FQDN format, and I click on DETAILs and it is there.

Ran a discovery from HP SIM on the test server.

Data collection report shows all hardware and services. Looking good so far.

Try to set the disk threshold critical = 25, warning = 20 and "Could not set the disk threshold, the agent did not accept the request."

[AdamJ]

Is WBEM enabled globally in SIM and have you set Global WBEM Credentials?

[Jason Salgado]

I just installed SSH on the test server, but this is what HP SIM shows on the test server.

HTTP:, WBEM:1.0, SMH:2.0, SSH:SSH-2.0-OpenSSH_5.1

[Jason Salgado]

Global Sign in credientals are set for a domain admin account that was created for HP SIM itself.

testserver WBEM / WMI domain/xxxx Global: Sign-in
testserver Sign-in domain/xxxx Global: Sign-in
testserver Single Sign-On Certificate HP Systems Insight Manager
testserver SSH domain\xxxx Host-based key

[Jason Salgado]

I also went to Manage Communications and ran the test on the testserver:

Secure Shell (SSH) is installed and configured correctly on the managed system(s). System Management Homepage (SMH) is installed on the managed system(s). Trust relationships on the managed system(s) are configured to trust HP SIM.
Applies to testserver

I'm at a loss here as to why I can't set disk thresholds.

[Jason Salgado]

I ran a itentify system from HP SIM on the testserver and this is what it returned.

Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
Received a response from the system management homepage on the SSL port, this system supports SMH.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn't have a server CIMOM installed locally, or cannot connect to it using all credentials specified
Running WBEM rules based identification.
Got ComputerSystem WBEM/WMI data from the system
Running VM Identification.
The system is not a VM Host, or WBEM credentials may not be specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system responded to a SNMP request, it supports SNMP.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
System has the SNMP ProLiant server (foundation) agents installed, adding system type.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
Running SNMP System Type Manager identification.
No matching SNMP System Type Manager rule was found.
Checking for DMI protocol support.
DMI is globally disabled, skipping DMI identification.
Running DMI System Type Manager identification.
DMI is globally disabled, skipping DMI identification.
Running HP-UX DMI identification.
DMI is globally disabled, skipping DMI identification.
Running HP/Compaq Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running HP DMI Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running Generic DMI identification.
DMI is globally disabled, skipping DMI identification.
Running SSH Protocol identification.
The system supports SSH protocol
Running SSH Identification.
This system cannot be logged in using ssh; check credentials or use a non-root user
Running Storage identification.
This system has some storage related information, additional storage systems may be added.
This system has some storage related information, additional storage systems may be added.
This system has some storage related information, additional storage systems may be added.
This system has some storage related information, additional storage systems may be added.
This system has some storage related information, additional storage systems may be added.
Storage identification completed.
Running HP Service Guard Identification.
The system is not part of HP Service Guard cluster
Running SNMP Subtypes identification
No additional subtypes found from SNMP
Create bare-metal device nodes if OA is discovered with "Automatic Device discovery" option enabled.
Create bare-metal server node if ILO is discovered with "Automatic Server discovery" option enabled.
Running VM identification.
VMM Integration is not enabled, skipping VM Identification
Building system relationships.
Running limited data collection for common attribute.
The SSH is configured on this system
SMH trust status is true.
Running node communication diagnosis
System identification done with this system.

[Jason Salgado]

I think I found the solution. On the test server in the HP Management software the "Data Source" was set to WBEM. I changed this to SNMP without doing anything else and I was able to push down the disk threshold to the test server from HP SIM.