SNMP outbound broken after 7.2 upgrade

[LGentile]

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.

Thanks

[BrianKelly]

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. 

[LGentile]

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. 

Thanks

[LesleyH]

Did HP provide any casue or resolution for this?

[BrianKelly]

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. 

Brian Kelly

[Andrew_Haak]

If you look in the SIM installation folder under the traps folder, do you see a lot of files?

[BrianKelly]

I don't have a lot of traps.  I monitored the folder for a day.  The traps came in and left normally.  I sent a debug file to HP last week.  I'm waiting for a reply. 

[LGentile]

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..

[Andrew_Haak]

Thanks LGentile for the info, didn't see that..

[shatra]

Hello Guys

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.

[LGentile]

Shatra,

I have not heard anything new from HP on this yet..

However, for IRS - you can see contract and warranty status, it is just not displayed in SIM (only in the IRS console). I am moving to 7.3 for supported devices anyhow (Gen 7/8 machines), but i will need to keep older systems in 7.2.2 for a while...

[BrianKelly]

I received a response from HP.  they want me to upgrade to SIM 7.4 that's supposed to come out in late October.  They closed my current case.  I don't get a warm and fuzzy feeling upgrading right after 7.4's released.  I'd rather wait to see if it has bugs like 7.3 did.  I'd also like to get the issue fixed before i upgrade.

Brian 

[shatra]

Hopefully will solve xml traps problems, bring back contract and warranty status in hp not in IRS(In IRS you can not grant granualr access on systems)

[LGentile]

I am setting up a secondary instance running 7.3 right now, and i can confirm everything works fine there, however as stated by others, some of us are stuck on 7.2.2 due to the use of Insight Remote Support Advanced for legacy hardware.

I'd move to 7.3 + IRS for all my SNMP servers, but there are some really ugly issues with IRS that will increase my already high administrative overhead for SIM and I'm not ready to deal with that. Traps are working for me, so I just need to restart SIM when i need to add new machines using SNMP.

[BrianKelly]

SIM 7.40 is out has anyone upgraded to it and if so has the issue gone away.

On a side note I received a security advisory that all versions of SIM below 7.4 have a vulnerability that's fixed in SIM 7.40.

It's simular to the Heartbleed exploite. 

Brian

[LGentile]

Brian,

L3 support claims this issue was fixed in 7.3, but there are a lot of customers that cannot upgrade their 7.2.2 instance due to its reliance on Insight Remote Support Advanced 5.80 for legacy hardware.

I can confirm everything works just fine in 7.3/7.4 as I set up a second CMS for Gen8+ modules, but my 7.2.2 is still broken.  I have a virual room meeting scheduled for next week with L3 to look into this.  If anything comes out of it, I will continue the updates here.  My case has been open since APRIL.

[Andrew_Haak]

Hello Gentile,

Is your 7.4 setup connected to a remote SQL or local if **bleep**'s remote is it a SQL 2012 ?

[LGentile]

Currently I am running SQL Express as I am waiting for my DB team to help me move the DB into a proper SQL cluster.