Question about upgrading net-snmp 5.4.2.1 to 5.7.1

Allen McWongahey <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Hello All,

I'm hoping someone can answer this for me.

Last year a co-worker was working on upgrading our net-snmp from 5.4.2.1 to something newer. She settled on 5.6.1.1 (instead of 5.7.1) but I don't know why. She cited some type of additional complication of going all the way to 5.7.1 but others she spoke to about this do not know the details. One co-worker seems to recall her talking about additional mib2c changes needed for 5.7.1 on top of what was needed to go to 5.6.1.1.

In the meantime I have upgraded to 5.7.1 and applied the mib2c changes and so forth which she applied for 5.6.1.1 and not only does everything compile nicely but I have it running on my target system and do not see any problems with the functionality. I have checked SNMP (full MIB walks) and am doing trap generation and so far all functionality appears to be working correctly.

If possible I'd like to clarify if any further changes should be needed between  what it would take to go to 5.7.1 vs. 5.6.1.1.

If it makes any difference we are running in Master Agent/sub-agent environment and SNMP and Traps are in two altogether different threads. We previously had both functionality in the same thread but had random crashes since it is not thread safe.

Any insight would be greatly appreciated.

Thanks very much,
Allen

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.