0

After fixing some bad config lines in old MIB's, I'm finally getting somewhere trying to walk an old hardware device. However, an error is still occuring on this particular OID which I can't understand. I would greatly apprecaite any clues:

Here is the -DALL output from walking just that particular OID:

Here is the entire output

1 Answer 1

0

The OID is this one:

.1.3.6.1.2.1.11.32

SNMPv2-MIB::snmpProxyDrops
snmpProxyDrops OBJECT-TYPE
  -- FROM       SNMPv2-MIB
  SYNTAX        Counter32
  MAX-ACCESS    read-only
  STATUS        current
  DESCRIPTION   "The total number of Confirmed Class PDUs
            (such as GetRequest-PDUs, GetNextRequest-PDUs,
            GetBulkRequest-PDUs, SetRequest-PDUs, and
            InformRequest-PDUs) delivered to the SNMP entity which
            were silently dropped because the transmission of
            the (possibly translated) message to a proxy target
            failed in a manner (other than a time-out) such that
            no Response Class PDU (such as a Response-PDU) could
            be returned."
::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) snmp(11) 32 }

Most of the debug output seems to be indexing and parsing your MIBs (I counted 336 of them). At the end, the device returns "0" as the answer to the poll:

.1.3.6.1.2.1.11.32.0 = Counter32: 0

Hope this helps.

11
  • Thanks and apologies for posting too much of the log file. Actually, I'm not sure what to do with the info you've suggested. Any more clues?
    – MFB
    Jul 27, 2020 at 5:25
  • What kind of clues are you looking for? Or, could you elaborate a bit on the error you're seeing? What I was trying to say is that I didn't really see an error - you polled an OID and the device sent you an answer for it.
    – NSD
    Jul 27, 2020 at 5:35
  • Oh I see. Actually immediately after that OID response, Error in packet. Reason: (genError) A general failure occured
    – MFB
    Jul 27, 2020 at 5:38
  • I incorrectly assumed the error would also be in the -DALL output, perhaps with more useful info.
    – MFB
    Jul 27, 2020 at 5:41
  • OK, thanks. And, it actually was, just a little bit before the answer. So, I'd suggest to take a look at the device you were polling, if possible. In the debug there were two identical polls. Device returned "Error in Packet" for the first poll, and then responded properly to the second, identical poll. First poll ID: sess_process_packet: sending message id#1746859277 reqid#800284050 len 43 Answer from device: snmp_synch: Response (ReqID: 800284050 - Cmd 162) Error in packet. Reason: (genError) A general failure occured
    – NSD
    Jul 27, 2020 at 5:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .