Summit WM3000 Series Controller System Reference Guide 505
System Logging Mechanism
The Extreme Networks wireless LAN controller provides subsystem logging to a Syslog server. There
are two Syslog systems, local and remote. Local Syslog records system information locally, on the
controller. The remote Syslog sends messages to a remote host. All Syslog messages conform to the RFC
3164 message format.
Troubleshooting SNMP Issues
The following SNMP-releated issued could require troubleshooting as SNMP issues are experienced
with the Extreme Networks wireless LAN controller.
● 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
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.
Not able to SNMP WALK for a GET
● Check whether the MIB browser has IP connectivity to the SNMP agent on the the controller. Use IP
Ping from the client system which has the MIB Browser.
● Check if the community string is the same at the agent side and the manager (MIB Browser) side.
The community name is case sensitive.
Possible Problem Suggestions to Correct
Memory leak 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.
Too many concurrent
Telnet or SSH sessions
Keep the maximum number of Telnet or SSH sessions low (6 or less),
even though up to 8 sessions are allowed.
All else... Contact Extreme Networks Support
To Next Page
Loading...