diff options
Diffstat (limited to 'docs/source/faq/oids-not-increasing.rst')
| -rw-r--r-- | docs/source/faq/oids-not-increasing.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/source/faq/oids-not-increasing.rst b/docs/source/faq/oids-not-increasing.rst index 5952d09e..e08652cd 100644 --- a/docs/source/faq/oids-not-increasing.rst +++ b/docs/source/faq/oids-not-increasing.rst @@ -4,22 +4,22 @@ Dealing with the "OID not increasing" error Q. I'm walking a particular Agent with the `nextCmd()` or `bulkCmd()` functions. It works for some OIDs, but invariably fails at certain - OID with the *OID not increasing* diagnostics. What does it mean and + OID with the *OID not increasing* error. What does it mean and how do I fix that? A. The Agent you are talking to seems to be broken. The *OID not increasing* message means that in the course of fetching - OIDs from Agent, Manager receives an OID that is not greater than those - used in request. + OIDs from the Agent, Manager receives an OID that is not greater than those + passed in request. Due to the nature of GETNEXT/GETBULK algorithm, passing the same or lesser OID to Manager would result in fetching the same set of OIDs over and over again effectively creating an infinite loop between Manager - and Agent so they may never reach the end of MIB. So Manager tries - to intervene and prevent loop from happening. + and Agent so they may never reach the end of MIB. To prevent this the + Manager tries to intervene and prevent such loop from happening. If you have to work with a broken Agent and can terminate the - GETNEXT/GETBULK app at some point, you can pass the - `ignoreNonIncreasingOid` keyword parameter to the `nextCmd()` or `bulkCmd()` + GETNEXT/GETBULK command at some point, you can pass the + `ignoreNonIncreasingOid=True` keyword parameter to the `nextCmd()` or `bulkCmd()` to disable OID verification at the Manager side. .. code-block:: python |