Ad Widget

Collapse

SNMP error [(noSuchName) There is no such variable name in this MIB

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arshad160
    Junior Member
    • Nov 2008
    • 2

    #1

    SNMP error [(noSuchName) There is no such variable name in this MIB

    Hi Everyone,
    This seems to be more of an SNMP issue than Zabbix, but if anyone can assist me with this issue, it will be greatly appreciated.

    Background:
    I have zabbix server 1.8.5 installed on a Cent OS 5.5 64 bit Dell Power Edge Server.
    below is the results for rpm -qa | grep snmp
    net-snmp-devel-5.3.2.2-9.el5_5.1
    net-snmp-5.3.2.2-9.el5_5.1
    net-snmp-utils-5.3.2.2-9.el5_5.1
    net-snmp-libs-5.3.2.2-9.el5_5.1

    Hosts x:
    Dell Power Edge R510 Server with Dell Open Manage server Administrator version 6.4 running Linux Cent OS 5.5 64 bit.
    below is the results for rpm -qa | grep snmp:
    net-snmp-libs-5.3.2.2-9.el5_5.1
    net-snmp-utils-5.3.2.2-9.el5_5.1
    net-snmp-5.3.2.2-9.el5_5.1
    net-snmp-devel-5.3.2.2-9.el5_5.1

    Host Y:
    Is also the same exaxt Dell Power Edge R510 Server with Dell Open Manage Server Administrator 6.4 running Windows server 2008 r2 64 bit.
    Windows snmp is installed and configured correctly.

    The Problem: I'm using the provided Dell Open Manage Template on both hosts. The template works great with Host Y (The windows machine), However, on Host X (the linux server) all items give a status of "item not supported" with an error message of "SNMP error [(noSuchName) There is no such variable name in this MIB"

    From the zabbix server, I did a couple of test snmpwalk commands.

    This one works:
    snmpwalk -c public -v 2c HostYIP .1.3.6.1.4.1.674.10892.1.300.10.1.11.1
    SNMPv2-SMI::enterprises.674.10892.1.300.10.1.11.1 = STRING: "9HBB8P1"

    This one fails:
    snmpwalk -c public -v 2c HostXIP .1.3.6.1.4.1.674.10892.1.300.10.1.11.1
    SNMPv2-SMI::enterprises.674.10892.1.300.10.1.11.1 = No Such Object available on this agent at this OID

    I am sure that Dell Open Manage is configured exactly the same on both machines, so I'm not sure why it would fail on the linux machine and work perfect on the windows machine.

    below is a copy of my snmp.conf file from HOSTX:


    Code:
    ###########################################################################
    #
    # snmpd.conf
    #
    #   - created by the snmpconf configuration program
    #
    ###########################################################################
    # SECTION: Extending the Agent
    #
    #   You can extend the snmp agent to have it return information
    #   that you yourself define.
    
    # pass: Run a command that intepretes the request for an entire tree.
    #   The pass program defined here will get called for all
    #   requests below a certain point in the mib tree.  It is then
    #   responsible for returning the right data beyond that point.
    #   
    #   arguments: miboid program
    #   
    #   example: pass .1.3.6.1.4.1.2021.255 /path/to/local/passtest
    #   
    #   See the snmpd.conf manual page for further information.
    #   
    #   Consider using "pass_persist" for a performance increase.
    
    pass .1.3.6.1.4.1.4413.4.1 /usr/bin/ucd5820stat
    
    ###########################################################################
    # SECTION: Access Control Setup
    #
    #   This section defines who is allowed to talk to your running
    #   snmp agent.
    
    # rwuser: a SNMPv3 read-write user
    #   arguments:  user [noauth|auth|priv] [restriction_oid]
    
    rwuser1  rwuser1  
    rwuser1   auth 
    
    # rouser: a SNMPv3 read-only user
    #   arguments:  user [noauth|auth|priv] [restriction_oid]
    
    rouser  "read-only user"  
    
    # rocommunity: a SNMPv1/SNMPv2c read-only access community name
    #   arguments:  community [default|hostname|network/bits] [oid]
    
    rocommunity  public 10.0.4.0/24 
    rocommunity  somestring 10.0.4.0/24  
    
    # rwcommunity: a SNMPv1/SNMPv2c read-write access community name
    #   arguments:  community [default|hostname|network/bits] [oid]
    
    rwcommunity  WriteSNMP! 10.0.4.0/24 
    
    ###########################################################################
    # SECTION: System Information Setup
    #
    #   This section defines some of the information reported in
    #   the "system" mib group in the mibII tree.
    
    # syslocation: The [typically physical] location of the system.
    #   Note that setting this value here means that when trying to
    #   perform an snmp SET operation to the sysLocation.0 variable will make
    #   the agent return the "notWritable" error code.  IE, including
    #   this token in the snmpd.conf file will disable write access to
    #   the variable.
    #   arguments:  location_string
    
    syslocation Unknown (edit /etc/snmp/snmpd.conf)
    syslocation  rtp
    
    # syscontact: The contact information for the administrator
    #   Note that setting this value here means that when trying to
    #   perform an snmp SET operation to the sysContact.0 variable will make
    #   the agent return the "notWritable" error code.  IE, including
    #   this token in the snmpd.conf file will disable write access to
    #   the variable.
    #   arguments:  contact_string
    
    syscontact Root <root@localhost> (configure /etc/snmp/snmp.local.conf)
    syscontact  
    
    #
    # Unknown directives read in from other files by snmpconf
    #
    com2sec notConfigUser  default       public
    group   notConfigGroup v1           notConfigUser
    group   notConfigGroup v2c           notConfigUser
    view    systemview    included   .1.3.6.1.2.1.1
    view    systemview    included   .1.3.6.1.2.1.25.1.1
    access  notConfigGroup ""      any       noauth    exact  systemview none none
  • arshad160
    Junior Member
    • Nov 2008
    • 2

    #2
    Issue Resolved

    Issue resolved. I had to enable the Dell Open Manage snmp service and restart it. here are the command I used:

    To enable:
    /etc/init.d/dataeng enablesnmp

    To Restart:
    service dataeng restart

    Comment

    Working...