System Logging Mechanism; Troubleshooting Snmp Issues; Mib Browser Not Able To Contact The Agent - Motorola RFS Series System Reference Manual

The table below provides suggestions to troubleshoot this issue.
Possible Problem
Fragmentation
All else...
C.1.4.2 Excessive Memory Leak
Excessive memory leak. The table below provides suggestions to troubleshoot this issue.
Possible Problem
Memory leak
Too many concurrent Telnet
or SSH sessions
All else...
C.1.5 System Logging Mechanism
The Motorola RF Series Switch provides subsystem logging to a Syslog server. There are two Syslog systems,
local and remote. Local Syslog records system information locally, on the switch. The remote Syslog sends
messages to a remote host. All Syslog messages conform to the RFC 3164 message format.
C.2 Troubleshooting SNMP Issues
The following SNMP-related issued could require troubleshooting as SNMP issues are experienced with the
Motorola RF Series Switch.
•

MIB Browser not able to contact the agent

• Not able to SNMP WALK for a GET
• MIB not visible in the MIB browser
• SNMP SETs not working
• Not receiving SNMP traps
• Additional Configuration
C.2.1 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 Web UI can do this.
Suggestions to Correct
• Do not allow VoIP traffic when operating on a flat network (no routers or smart
switches).
• Move to a trunked Ethernet port.
• Move to a different configuration.
Contact Motorola Support.
Suggestions to Correct
Using the CLI or Web UI's Diagnostics section to check the available virtual
memory. If any one process displays an excessive amount of memory usage, that
process could be one of the possible causes of the problem.
Keep the maximum number of Telnet or SSH sessions low (6 or less), even though
up to 8 sessions are allowed.
Contact Motorola Support.
C-7