Please try using this snapshot:

  http://snaps.php.net/php5.4-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/

Please try another approach: all methods that performs remote agent query raise $object->errno == SNMP::ERRNO_OID_PARSING_ERROR even before query itself, indicating that some of OID (and/or type for set method) was not parsed correctly.

Since OO API allows to set multiple OID on single method call this should help.
Mind that OID parsing is made in chunks with length of $object->max_oids.
Thus if you supply array of OIDs that is bigger than $object->max_oids and bogus OID will be in the end of array, this error will be raised *after* processing (e.g. making query) the first part.

The idea sounds good but it does not seem to work. The "Invalid object identifier" is thrown only as PHP Warning, not set in SNMP->error:


 $ cat test.php 
 <?php
        $snmp = new SNMP(SNMP::VERSION_1, 'localhost', 'public', 0, 0);
        $oid1 = 'IF-MIB::ifAlias.1';
        $oid2 = 'DOES-NOT-EXIST-MIB::FOO';
        $oid3 = 'NOTIFICATION-LOG-MIB::nlmConfigGlobalEntryLimit.0';
        $snmp->get(array($oid1, $oid2, $oid3));
        printf("-------\n%s (%d)\n--------\n", $snmp->getError(), $snmp->errno);




 $ ../php-src-5.4/sapi/cli/php -d include_path=.:/usr/share/php  test.php 
 Warning: SNMP::get(): Invalid object identifier: DOES-NOT-EXIST-MIB::FOO in  /home/chammers/workspace/php_test/test.php on line 8
 -------
  (0)
 --------

Please check that you have ERRNO_OID_PARSING_ERROR in snmp extension sources. This constant appeared on 27th of august.

As of SVN revision 315762 from now, the constant only appears in the tests, not in the class source. Running the tests yield to:

Fatal error: Undefined class constant 'ERRNO_OID_PARSING_ERROR' in /home/chammers/workspace/php-src-5.4/ext/snmp/tests/snmp-object-errno-errstr.php on line 45

Maybe it's not yet committet?

Indeed. Commited sources into PHP_5_4 branch.

Now the following works..

  @$snmp->get(array($oid1, $oid2));
  if ($snmp->getErrno() == SNMP::ERRNO_OID_PARSING_ERROR) {
    throw new Exception($snmp->getError());
  }

... but why is there only a warning? Calling get() with a OID that does not even parses should throw an Exception? Especially as when using OOP, one does not expect having to call getErrno() after every call as we did in the last millenium or even worse don't catch this error.

Can you wrapt this into a nice SnmpOidParsingException?

I have read a bunch of threads on php-dev about extensions throwing exceptions and the last thing I remember that extension should not throw any exception except object creation if there is no way to disable them.

Anyway, if to throw exceptions, library will throw an exception for each error, not only parsing error.

Well, throwing exceptions everywhere is exactly what I'd with for but to discuss this I opened #55542. This one can be closed as we now have a way to check for the presence of a MIB (more or less convenient).

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.

Commits 315862 & 315865 forces OID check before any query is made. Though set method will check type&value in chunked mode. If SET query should be done in multiple chunks (OID array supplied is bigger that max_oids) a warning will be raised.

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.

 For Windows:

http://windows.php.net/snapshots/
 
Thank you for the report, and for helping us make PHP better.