Skip to main content
NetApp Knowledge Base

CPU and Memory OIDs not visible in SNMP walk dump

  1. Last updated
  2. Save as PDF
Views:
391
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
san
Last Updated:

Applies to

  • Brocade switch
  • FOS version: v8.2.1c

Issue

  • CPU and Memory OIDs not visible in SNMP walk dump post SNMP configuration.

  • In the trace data, snmpget could be seen in the switch and being processed.
    Example in trace of snmp gets:

    2022/07/05 01:18:37.369939 Pr:2192 Lv:05 SNMP_LOGMSG AUDIT: Updated entry added at index : 0
    2022/07/05 01:18:37.370241 Pr:2192 Lv:05 PROCESS_SNMP_REQUEST InPacket Len:215, OutPacket Len:214
    2022/07/05 01:18:37.382904 Pr:2192 Lv:05 SNMP_GET_NEXT OID=1.3.6.1.2.1.2.2.1.2.805306370

  • The name lookup in the MIB works fine, the query works fine, but the agent responds that no such object exists in trace of snmpget:
    No such object available on this agent at this oid
    Variables found: 1
     

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.