Snmp giving strange output

Question

I'm trying to configure snmp to allow monitoring on 'solarwinds' software. This is just a simple server health monitor so I didn't think the setup would be complicated (I still don't think it will be, I must be missing something basic).
Anyway I have confirmed the daemon is running and created a snmpd.conf file containing only the system location, system contact and a rocommunity string of public.
Then when I run a 'snmpwalk -c public localhost' command in terminal it only returns the system contact then says - 'No more variables left in this view (it is past the end of the MIB tree)'
I have 4 servers, 2 of which return this and won't work with the monitoring software and 2 of which work exactly as expected. As far as I can tell they have the same snmpd.conf settings, I've triple checked the community names and all have the service confirmed running.
If anyone has any ideas about this then I'd be grateful for the advise, I'm about to pull my hair out.

Answer 1

just to be clear my snmpd.conf file looks like this :
# snmpd.conf
#   - created by the snmpconf configuration program
# SECTION: Access Control Setup
#   This section defines who is allowed to talk to your running
#   snmp agent.
# rocommunity: a SNMPv1/SNMPv2c read-only access community name
#   arguments:  community [default|hostname|network/bits] [oid]
rocommunity  public
# 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  "B1_D15"
# 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  [email protected]
So I would expect a giant stream of data with a simple snmpwalk command but what I get is the following. I have the same configuratoin on other servers and they seem to work perfectly well :
chskod02mp:snmp admin$ snmpwalk -c public localhostSNMPv2-MIB::sysContact.0 = STRING: [email protected]
SNMPv2-MIB::sysContact.0 = No more variables left in this MIB View (It is past the end of the MIB tree)