Hi Karl,
I've never tried to change PHP to work with SNMPv2.
So I don't know the problems that may appear.
Javier
Karl S. Hagen wrote:
Javier,
I did find one very interesting bug with changing PHP to using SNMPv2c rather than v1. Basically, while JFF now graphs 64bit mibs, the discovery routines are very much broken.
v1 returns an error while v2 returns a msg.
[discovery]# /opt/net-snmp-5.0.9/bin/snmpget -v 2c -c ##### aa.bb.cc.dd .1.3.6.1.4.1.311.1.7.3.1.1.0 SNMPv2-SMI::enterprises.311.1.7.3.1.1.0 = No Such Object available on this agent at this OID [discovery]# /opt/net-snmp-5.0.9/bin/snmpget -v 1 -c ##### aa.bb.cc.dd .1.3.6.1.4.1.311.1.7.3.1.1.0 Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: SNMPv2-SMI::enterprises.311.1.7.3.1.1.0
Fun Fun. Im looking at fixing snmp_* to return false if "No Such Object" is found in the return.
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Javier Szyszlican, Project Leader, JFFNMS [EMAIL PROTECTED]
I hope JFFNMS or I were helpful to you, if you can, please donate at http://jffnms.org/donate
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
jffnms-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jffnms-users
