SNMP Monitored Devices with "Timeout on Device” Events

Applies To

  • Zenoss Resource Manager 5.x
  • Zenoss Resource Manager 4.x
  • Zenoss Resource Manager 3.x


While monitoring an SNMP managed device, error events such as “Unable to read processes on device; Timeout on device”, or other timeout events can be generated. These events can be the result of a device that cannot return the requested number of OID instances per request. The solution to controlling these events is to limit the number of OIDs per request for the device.


Perform the following procedure to set a lower value for the number of OIDs per request for a device:

  1. Access the UI.
  2. Under the device Configuration Properties, search for zMaxOIDPerRequest.
  3. Double-click zMaxOIDPerRequest to open the Edit Config Property dialog.
  4. Adjust the Max OID Per Request value with the up/down arrows. Initially, lower the default value of 40 to 1.
  5. Click SUBMIT to save and close the dialog.
  6. Verify the timeout issue is resolved. When it is confirmed that the timeout issue is resolved, Zenoss recommends raising the zMaxOIDPerRequest value to the highest possible level that does not trigger an event.
    To determine the highest acceptable value for zMaxOIDPerRequest:
    1. Raise the zMaxOIDPerRequest value until the timeout event is again triggered.
    2. Lower the zMaxOIDPerRequest value below the value that triggered the event.


  • The zMaxOIDPerRequest configuration property sets the maximum number of OIDs sent by the SNMP collection daemons when querying information. Because lowering this value results in more SNMP queries, changing this configuration property for devices that do not return timeout error messages might not be useful.
  • To setup disparate configurations for devices in the same Device Class, create a new sub class containing those devices that have timeout problems and change the zMaxOIDPerRequest settings for the new class.
Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk