After Upgrade, Version Number Has Not Changed; Miscellaneous Issues; Excessive Fragmented Data Or Excessive Broadcast; Excessive Memory Leak - Motorola WS5100 Series Troubleshooting Manual

1.5.1 After Upgrade, Version Number Has Not Changed

After upgrading the version number has not changed. The following table provides suggestions to
troubleshoot this issue.
Possible Issues
Improper upgrade process
All else...

1.6 Miscellaneous Issues

This section describes various miscellaneous issues related to the switch, and don't fall into any of the
previously called out issue categories. Possible issues include:
•

Excessive Fragmented Data or Excessive Broadcast

•

Excessive Memory Leak

1.6.1 Excessive Fragmented Data or Excessive Broadcast
Excessive fragmented data or excessive broadcast.
The following table provides suggestions to troubleshoot this issue
Possible Issues
Fragmentation
All else...
1.6.2 Excessive Memory Leak
Excessive memory leak. The following table provides suggestions to troubleshoot this issue
Possible Issues
Memory leak
Too many concurrent Telnet
or SSH sessions
All else...
Suggestions to Correct
• Refer to the release notes and repeat the upgrade process exactly as stated in the
release notes.
• Verify the Syslog folder contents from the CLI Service Mode context. Repeat the
upgrade process if necessary.
Contact Motorola Support.
Suggestions to Correct
• Change the MTU size to avoid fragmentation on other ethernet devices.
• 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.
.
.
1-9
Overview