System Logging Mechanism - Brocade Communications Systems RFS6000 System Reference Manual

The table below provides suggestions to troubleshoot this issue.
Possible Problem
Fragmentation
All else...
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...

System Logging Mechanism

The Brocade RF Series 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 Brocade RF Series Controller.
•
•
•
•
•
•
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.
Brocade Mobility RFS6000 and RFS7000 System Reference Guide
53-1001858-01
Suggestions to Correct
•
•
•
Contact Brocade 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 Brocade Support
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
Do not allow VoIP traffic when operating on a flat network (no routers or
smart controllers).
Move to a trunked Ethernet port.
Move to a different configuration.
Troubleshooting SNMP Issues
B
551