topic Re: 3rd party agents in Server Management - Systems Insight Manager

3rd party agents

Greg Gover — Fri, 07 Jan 2005 14:51:20 GMT

Where can I find third party agents to run
on non-HP/ProLiant servers so that I can test
the WMI/WBEM functionality?

Re: 3rd party agents

David Claypool — Fri, 07 Jan 2005 15:27:43 GMT

No agents are involved for WMI. It is supplied by the operating system. For non-Windows WBEM providers, it depends on the manufacturer. HP supplies WBEM providers for HP-UX on PA-RISC and Itanium and WBEM providers for Linux on Itanium.

Re: 3rd party agents

Darrin Rawls — Fri, 07 Jan 2005 16:14:49 GMT

Just make sure you specify the login credentials for WMI/WBEM on the Global Protocols Settings page prior to running Discovery/Identification on those boxes.

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 16:19:53 GMT

SO I did a manual discovery first. Then modified my Global settings with a domain account with admin privilages for WBEM
under GLoabl Protocol Settings.

The server shows as unmanaged adn I don't see much WMI info.

I have done alot of WMI programming adn would just like to see what it picks up.

Maybe I'm looking in the wrong place or I need to delete the object and do another manual discovery now that my credentials are correct?

Re: 3rd party agents

Darrin Rawls — Fri, 07 Jan 2005 16:24:33 GMT

I would just put that one IP address in the Automatic Discovery page and let it do its thing on that one IP; now that you have everything set.

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 16:27:06 GMT

How can I get this from unmanaged to Client or server in the Type field?

Thks.

Re: 3rd party agents

Darrin Rawls — Fri, 07 Jan 2005 16:31:29 GMT

It should happen automatically. What kind of box w/which OS are you trying to discover?

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 16:33:35 GMT

Just a Dell Precsion workstation with XP
on it.

I just redid the discovery after deleting it, but it does not even pick up the OS.

Greg

Re: 3rd party agents

Darrin Rawls — Fri, 07 Jan 2005 16:36:38 GMT

Manual Discovery or the Automatic Discovery method? It should get a sub-set of WMI data....

Also, when you drill down to the System Page for that device from a list, it should show "WBEM" as a supported protocol if SIM could connect. If it does, there a Link called "Properties" that gets some of the WMI data real time from the device....

Re: 3rd party agents

David Claypool — Fri, 07 Jan 2005 16:44:41 GMT

Make sure neither the HP SIM host nor your workstation have DNS names containing an underscore (not allowed under DNS rules but allowed by Windows) or a dash. This breaks the WMI Mapper.

It may not be obvious what you should see when it properly finds WMI.

On the System Page under the Identity tab the "Management Protocols" should list "WBEM 2.6" if it has discovered it.

Under the Links tab, the "HP Systems Insight Manager pages" category will have a "Properties" link. That is where you'll find the WMI data.

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 16:47:08 GMT

No, on the identity page it does not show
any management protocols.

I was able to manually edit the prorties to show it as a workstation.

But it does not appear to be picking it up other than ICMP packets. I thought I had read that the username was supposed to be
domain\username?

does not appear I am getting any WBEM/WMI info.

also, under Options/Events there is a thing called Subscribe to WBEM events..........

but that appears to only be supported on HP-UX

thks,
greg

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 16:59:29 GMT

Automatic discovery did no better.

I must have a security issue. This isn't hte only box though, I have tried on 2-3 others with the same results.

My production servers are HP/Compaq, but my devel servers are mostly just high end workstations I've scrounged.

Greg

Re: 3rd party agents

David Claypool — Fri, 07 Jan 2005 17:03:09 GMT

Since you have some WMI experience, I'm going to assume you have validated that you can successfully connect to the workstation from the HP SIM server and get WMI data through a script or something.

Follow the chain for troubleshooting. We talk "pure WBEM" out of HP SIM (common information model data formatted in XML over HTTPS) which the WMI Mapper turns into DCOM for WMI.

- Check to make sure the "Pegasus WMI Mapper" is installed and the service is started
- If the service is working and it is attempting to connect to the workstation unsuccessfully, you should see some DCOM 10009 errors related to that in the Windows Event Log. That would probably indicate a malformed username/password combination.

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 17:21:42 GMT

The pegasus WMI mapper was not running. I restarted then deleted the workstation, then logged out of SIM.

I logged back in and re-added the PC witht the service running to no gain.

I checked the event logs of the pc adn sim server and saw no dcom errors.

WMI vbscripts run against this every hour
with my credentials.

I did have an issue getting my CMS server working. The cd I had loaded 4.1 which I could not get to work. So I loaded 4.2 and got that working. Do I need to possibly re-install the Pegasus? If so how AND FROM WHERE? The service was disabled when I initially looked at it upon your suggestion.

Greg

Re: 3rd party agents

David Claypool — Fri, 07 Jan 2005 17:24:27 GMT

If you downloaded the T24-blah-blah-blah.exe file you can open it with WinZip and you'll find the mapper in the "wmimap" directory as "WMIMapper.msi"

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 17:50:32 GMT

I reloaded the WMI mapper then rebooted the server.

All is fine now thanks to everyone for your help.

Greg

Re: 3rd party agents

Greg Gover — Fri, 07 Jan 2005 17:55:24 GMT

I reloaded the mapper and rebooted and all is well now.

Thanks again.