Chapter 7. Troubleshooting Snmp Issues - Motorola WS5100 Series Troubleshooting Manual

Troubleshooting SNMP Issues
The following SNMP-releated issues could require troubleshooting as issues are experienced with the
WS5100 switch.
MIB Browser not able to contact the agent.
General error messages on the MIB Browser: Timeout, No Response.
The client IP where the MIB browser is present should be made known to the agent. Adding SNMP clients
through CLI or Applet can do this. This can be verified by looking at /butterfly/snmp/snmpd.conf. The entries
are generally present towards the end of this file.
Not able to SNMP WALK for a GET.
First check whether the MIB browser has IP connectivity to the SNMP agent on the WS5K. Use IP Ping from
the PC which has the MIB Browser.
Then check if the community string is the same at the agent side and the manager (MIB Browser) side.
Community name is case sensitive.
MIB not visible in the MIB browser.
The filename.mib file should be first compiled using a MIB compiler, which creates a smidb file. This file must
be loaded in the mib browser.
If SETs still don't happen...
Check to see if environment variables are set. The following are the env variable to be set.
SNMPCONFPATH=/butterfly/snmp
MIBDIRS=/butterfly/snmp/mibs
MIBS=ALL
Restart the SNMP agent (the snmpd daemon)
Not getting snmptraps
Check whether snmp traps are enabled through CLI or Applet. Configure MIB browser to display notifications
or traps. (This would generally be a check box in the MIB browser preferences).
Still Not Working
Double check Managers' IP Address, community string, port number, read/write permissions, and snmp
version. Remember community string IS CASE SENSITIVE.