Re: [NV-L] SuSe SNMP Agent Issue

[Larry Fagan <larrytechie@yahoo.com>]

Jane,
No. We have not changed any config on snmpd.conf file on SuSe. Below is the config file. Could you please tell me how to enable responses from other than MIB-2.


###########################################################################
#
# 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.

# rouser: a SNMPv3 read-only user
#   arguments:  user [noauth|auth|priv] [restriction_oid]

#rouser   

# rocommunity: a SNMPv1/SNMPv2c read-only access community name
#   arguments:  community [default|hostname|network/bits] [oid]

rocommunity  "xxxxxxxxxxxxx" 
rocommunity  xxxxxxxxxxxxxx



###########################################################################
# SECTION: Trap Destinations
#
#   Here we define who the agent will send traps to.

# trapsink: A SNMPv1 trap receiver
#   arguments: host [community] [portnum]

trapsink  <snmp_manager host>

# trap2sink: A SNMPv2c trap receiver
#   arguments: host [community] [portnum]

trap2sink  <snmp_manager host>

# informsink: A SNMPv2c inform (acknowledged trap) receiver
#   arguments: host [community] [portnum]

informsink  <snmp_manager host>

# trapcommunity: Default trap sink community to use
#   arguments: community-string

trapcommunity  "xxxxxxxxxxxxxx" 
trapcommunity  xxxxxxxxxxxxxxx

# authtrapenable: Should we send traps when authentication failures occur
#   arguments: 1 | 2   (1 = yes, 2 = no)

authtrapenable  1


###########################################################################
# 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 Server Room
syslocation  California

# 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 Sysadmin (root@localhost)
syscontact  root@localhost

#
# Unknown directives read in from other files by snmpconf
#

# Allow Systems Management Data Engine SNMP to connect to snmpd using SMUX
smuxpeer .1.3.6.1.4.1.674.10892.1

Thanks,
Larry





Hi Larry,
I seem to remember my experience with the SuSE agent is that, by default, it only gives responses to the system part of MIB-2, nothing else.  Have you checked the agent config file in /etc/snmpd.conf?
Cheers,
Jane

---

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)