04-30-2014 10:39 AM
I finally upgraded to SIM 7.2.2 (latest version I can run due to IRSA) and shortly after, I noticed that discoveries and identify tasks fail with systems running SNMP. I also tried using the sytem types tool to pull OIDs from systems and it fails as well.
I stumbled across a blog where someone found that a new parameter existed in the globalsettings file - "JavaSnmpStack", and setting it to 'false' fixed the issue for me - for about 15 minutes! Without doing anything else, the same issue came back.
It's very strange.. yes the clients have valid SNMP community names and yes the SIM credentials are correct - i have thousands of devices so they all could not be wrong.
04-30-2014 11:37 AM
I have the same issue except not as bad. It happens to me about every 2 weeks. I reboot the SIM server and all is good again. It's a bit frustrating though because I made a collection of servers in alarm and they don't show up there when the issue arises. After the reboot they show up. Data collection and system identifies don't pull down data until after the reboot. Wondering what's changing to do this.
05-01-2014 05:17 AM
Yeah I am in a similar situation.
Traps seem to work just fine, but it screws up my collections since a lot of systems end up as 'unknown'. I also use the daily ID task to find broken agents or servers that are no longer responding to polls.. now the ID task takes 15+ hours and doesn't complete properly, so I can't really tell what servers really have issues since ALL the SNMP servers (Windows) come up as major failures..
I will open a case with HP on this one and post something if I hear back. We're not ready to use WBEM with Windows yet since we have a lot of legacy systems, so that really isn't an option right now. Same goes for agentless, can't do that due to IRSA in case anyone suggests that.
2 weeks ago
I have a case open w/HP for the issue. I'm working w/tier 3. I don't believe they have a work around yet because they still haven't nailed down what the issue is with my server. I'll keep you posted. As a hack work around I setup a sceduled task to run a batch file with the line MXSTOP. Then another one ten minutes later with MXSTART. I run it at midnight every night. Thankfully my server runs ok doing that. SIM 7.4 is coming out soon (October/November) I'd like to get it fixed before I upgrade.
2 weeks ago - last edited 2 weeks ago
Brian - interestingly enough, after 4 months, HP finally got back to me (L3 engineer working with the dev team) to acknowledge this issue.
Note that many customers cannot upgrade beyond 7.2.2 right now so HP should be obligated to fix this issue without needing to upgrade to 7.3 or better. I will not be able to upgrade my instance to 7.4 so HP told me they are testing a fix in 7.2 to see if it will work.
Andrew - this isn't about traps, it's SNMP outbound (discoveries, daily ID tasks, etc..) SNMP simply fails to connect (using a commandline SNMPGet utility, everything works just fine) - this something in SIM or the Java SNMP stack that SIM uses..
Friday - last edited Friday
I have exaclty same problem, after a random period of time new systems can no be discovered. All discovery task are finishing with error- "system does not respond to snmp" which is false.
Did you got any workarounds for this except restarting hp sim service?
I am in the same situation can not update to version 7.3 because of IRS(no contract and warranty status in hp sim, why?!!). I have a case opened at but it seems that they do not know what they are doing... for 2 months.