Server Management - Systems Insight Manager
1836533 Members
4634 Online
110101 Solutions
New Discussion

Re: Device Identification

 
Stefan Laemmer
Valued Contributor

Device Identification

Hi all,
strange problem with SIM 5: When the Device ID runs, i get inconsistent results as to what will show up in the System List(s).. Yesterday, all Systems were ID'd properly, today, after i run a Device ID every night at 11pm, only 30% are ID'd. When i ran it manually on a selected group, it actually wiped out the previously found ID and now i have 50 blank machines (I only see the System Name, Type is Unknown, IP# is there, but no Product Name or OS Name). I triple checked all the SNMP settings and they seemed to be ok. The Trap is set to the CMS, community name and strings are set properly as is the Permitted Managers section.. Any help appreciated.. Thanks..
11 REPLIES 11
Stefan Laemmer
Valued Contributor

Re: Device Identification

Looks like i am closing in on something:
I took off WBEM (after reading in a thread that it gives dupe's) to run only on SNMP & DMI.. Ran a Data Collection and get tons of errors (The device does not have any supported instrumentation.).. On exactly the same machines that dont have the ProdID etc showing.. Mmmmmmhhhhhhh...
I am trying a fix (Options-Protocol Settings-All Systems, setting Global Protocol Settings to all machines, in a another thread).. Let's see if that does it.
Stefan Laemmer
Valued Contributor

Re: Device Identification

Thats a NO..

Looks like i figured it out though: The Trusted Management Servers Certificate seems to have been the issue. I manually deleted the local and re-added from the SIM server, restarted SMH and voila, info shows up and Data Collection works fine.. I'll leave this open for now, just because i have been burnt before, but hopefully this is it.
Stefan Laemmer
Valued Contributor

Re: Device Identification

Yeah, i should have known..

It worked ok on 2 machines, but not the rest. Back to the drawing board...
Stefan Laemmer
Valued Contributor

Re: Device Identification

Re-Enabled WBEM, ran a Data Collection on a machine:
"An error occurred connecting to this system with the WBEM protocol. Check the system configuration"

Checked System Properties:
Unknown WBEM problem..

Great..
Stefan Laemmer
Valued Contributor

Re: Device Identification

More info:
I did take off WBEM again, didnt do me any good anyway..

I did a SNMPWALK and get a Timeout for the machines that have issues. Works ok (from CMS) to the ones that show some info..
I'll keep updating this more for reference...
Stefan Laemmer
Valued Contributor

Re: Device Identification

We did a Sniff on what happens when i do the SNMPWalk (with the proper Community string): The receiving machine denies the request with an Authentication Failure (Error 4).. It's configured the same as the other machine that works fine. Same Community String, although it seems that the SNMPWalk attempts Public twice before it goes through with the customized Community String.. Both machines are on the same segment, same Permitted Managers, Same Trap Destination..

I am running out of ideas, if anyone can help me out here, i'd apprecite it.

Thanks
Stefan Laemmer
Valued Contributor

Re: Device Identification

Continuing on this:
I enabled the Events for SNMP Authentication Errors. I tested to do an ID on a system and get 8 Authentication Error Events for that. (To enable the Event's go to Options -> Events -> SNMP Trap Settings, choose rfc1215.mib and the Authentication Failure TrapName, and below Enable Trap Handling).
ALso, i changed the SNMP Community Names in the GlobalSettings.props to ours (see thread http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=967743), same effect: Nothing.

Still scratching my head...
Stefan Laemmer
Valued Contributor

Re: Device Identification

Looks like i got something:
I enabled WBEM again (with the domain user first) and when i went to force the Protocol Settings out to All Systems, i set the SSH user name and password. That seems to have done the trick. I am running a ID Systems and it is returning info and takes minutes at a time, instead of failing immediatly. Very strange, as i dont have SSH installed on any of my servers.

Again, i'll leave this open to make sure this sticks.

Hope all this bumbling around helps somebody.
Jorgen Stenberg
Occasional Advisor

Re: Device Identification

Have you come to a final solution on this?
Stefan Laemmer
Valued Contributor

Re: Device Identification

Jorgen,
seems like Systems Insight Manager 5.0 with SP3 fixed my issues on this problem for good.
Stefan Laemmer
Valued Contributor

Re: Device Identification

SIM 5 SP 3 seems to have fixed this issue