SNMP/WMI test fails on server running SIM

[Damien Young]

Hi, I'm new to servers/server management so please bare with me

I've installed HP SIM (5.0.2) on a Proliant DL370G2 Running Server 08 Standard and it's able to contact and monitor other servers on the network (i.e. should a RAID drive fail) but I can't seem to get it to monitor itself.

Neither the SNMP Agent nor the WMI will install, claiming its not needed. Will configure but when it comes to testing it fails

When I attempted to configure WMI I got this error
Subscribe to WBEM / WMI Indications (DONE)[SUCCESS]
Windows configuration command (START)
Setting SNMP trap destination (DONE) [SUCCESS]
Sending test indication to HP SIM CMS (START)...
Send test WBEM/ WMI indication from the system (DONE)[FAILED]
Error accessing SMS WMI namespace


And the same basically occurs when trying to configure the SNMP agent
"Setting SNMP trap destination (DONE)[SUCCESS]
Sending SNMP test trap (START)
Sending SNMP test trap (DONE)[FAILED]
Could not load SNMP Trap generating utility."

I'm not sure what's going on, it seems to configure ok but fails at testing. Does anybody have any ideas?

Cheers

[marsh_1]

DAMIEN,

in the smh for the hp sim server what do you have set as the trap destination for snmp , i have used my hp sim ip address rather than name.

hope this helps

[Damien Young]

Hi Mark, I had a look around the SM Homepage but found it to be pretty empty. Basically only containing links to Array config, version control agent and repository manager. Settings were all to do with security (i.e. IP binding, trust mode etc)

I went into services.msc though and found the trap "hprepair" was set to the servername. I changed that to its IP and re-ran the test in SIM/manage communications but it still failed.

Cheers,

[Damien Young]

Minor update,
I've noticed that SMH is unable to identify the system model (say's unknown).

After hunting around I found a suggestion in the knowledgebase to add 127.0.0.1 to the trap destination and restart the SNMP service.
However, sadly this did nothing also

Not sure if that's a separate issue or not but it's worth a mention. If only to aid the process of elimination

[Damien Young]

Aha, finally.

I went back to basics and reopened the Proliant Support Pack install and found the WBEM "additional option" wasn't installed.

I also remembered that it complained about Insight management agents couldn't be installed due to no Advanced System Management Controller Driver and/or iLO drivers.
They still won't install but I figure it's because there's no drivers available for Server 2008. Searching HP site found nothing (only 2003)

Anyway since I didn't know what Insight was at the time I ignored it. Rookie mistake :)

Once I installed the optional WBEM component it could identify fine and unplugging a RAID5 drive tested the monitoring portion successfully.

[Damien Young]

Installed WBEM component. Identifies fine

[David Claypool]

This is a good example of not using the ProLiant Support Pack and trying to manually figure out the pre-requisites. The PSP is there to provide a single download and install for all the HP drivers/utilities/agents.

You shouldn't have to "search" the site. Start at http://www.hp.com and select the big "Support & Drivers" button, and follow down the prompts. The PSP for both Windows Server 2008 x32 and x64 are there.

[Damien Young]

Hi David,

Yes I did install the Proliant Support pack first. Version 8.15 for Windows Server 2008 w32 and it installed most things
The only thing it didn't were the Insight management agents which said it couldn't due to a lack of a driver described above. I didn't notice the WBEM optional install before either.

Later on after installing the SIM and going through the process of adding the servers and ensuring they can communicate
It was then when I went into the setup of the support pack again and noticed the WBEM component.
The WBEM component worked, I only searched the site for a driver to allow the PSP insight agents to install out of curiosity, not necessity

Hence why I said reopened the support pack in the above post, not downloaded the support pack.
I had it to begin with and it was the latest version