Motorola WS5100 Series User manual


WS5100 Series Switch
Troubleshooting Guide

© 2007 Motorola, Inc. All rights reserved.
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. Symbol is a registered
trademark of Symbol Technologies, Inc. All other product or service names are the property of their respective owners.

Contents
Chapter 1. Overview
1.1 Wireless Switch Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1.1 Switch Does Not Boot Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1.2 Switch Takes a Long Time to Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.3 Switch Does Not Obtain an IP Address through DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.4 Switch is Stuck in a Booting Loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.5 Unable to Connect to the Switch using Telnet or SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.1.6 Web UI is Sluggish, Does Not Refresh Properly, or Does Not Respond. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.1.7 Console Port is Not Responding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.1.8 Shutting Down the Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.1.8.1 Shutting Down the Switch Using the 1.4.x/2.x Shutdown Command . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.1.8.2 Shutting Down the Switch Using the Halt Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.2 Access Port Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.1 Access Ports are Not Adopted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.3 Mobile Unit Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.3.1 Access Port Adopted, but MU is Not Being Associated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.3.2 MUs Cannot Associate and/or Authenticate with Access Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.3.3 Poor Voice Quality Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.4 Failover Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.4.1 Switch is Not Failing Over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.4.2 Switch is Failing Over Too Frequently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.5 Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.5.1 After Upgrade, Version Number Has Not Changed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.6 Miscellaneous Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.6.1 Excessive Fragmented Data or Excessive Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.6.2 Excessive Memory Leak. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.7 System Logging Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Chapter 2. Syslog Messages &
MU Disassociation Codes
2.1 Syslog Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 MU Dissasociation Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Chapter 3. Security Issues
3.2 RADIUS Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.1 Troubleshooting RADIUS Accounting Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.3 Rogue AP Detection Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4 Troubleshooting Firewall Configuration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

TOC-ii WS5100 Series Switch Troubleshooting Guide
Chapter 4. Network Events and Kern Messages
4.1 KERN Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Chapter 5. LED Information
5.1 LED Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.1 Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.2 Primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.3 Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.4 Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Chapter 6. Updating the System Image
6.1 Upgrading the Switch Image from 1.4.x or 2.x to Version 3.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.2 Downgrading the Switch Image from Version 3.x to 1.4.x or 2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Chapter 7. Troubleshooting SNMP Issues

About This Guide
Introduction
This guide provides information for troubleshooting issues on the WS 5100 Series Switch.
Documentation Set
The documentation set for the WS5100 Series Switch is partitioned into the following guides to provide
information for specific user needs.
•WS5100 System Reference - describes WS5100 Series Switch Web UI configuration activities and the
resulting network behavior.
•WS5100 Installation Guide - describes the basic setup and configuration required to transition to more
advanced configuration of the switch.
•WS5100 CLI Reference - describes the Command Line Interface (CLI) and Management Information
Base (MIB) commands used to configure the WS5100 Series Switch.
•WS5100 Migration Guide - provides upgrade instructions and new feature descriptions for legacy
users of the WS5100 Series Switch.
Document Conventions
NOTE: Screens and windows pictured in this guide are samples and can differ from actual
screens.
NOTE: Indicate tips or special requirements.
CAUTION: Indicates conditions that can cause equipment damage or data loss.
WARNING! Indicates a condition or procedure that could result in personal
injury or equipment damage.
!

-viii WS5100 Series Switch Troubleshooting Guide
Notational Conventions
The following additional notational conventions are used in this document:
•Italics are used to highlight the following:
• Chapters and sections in this and related documents
• Dialog box, window and screen names
• Drop-down list and list box names
• Check box and radio button names
• Icons on a screen.
•GUI text is used to highlight the following:
• Screen names
• Menu items
• Button names on a screen.
• bullets (•) indicate:
• Action items
• Lists of alternatives
• Lists of required steps that are not necessarily sequential
• Sequential lists (e.g., those that describe step-by-step procedures) appear as numbered lists.

Overview
This chapter describes common system issues and what to look for while diagnosing the cause of a problem.
Wherever possible, it includes possible suggestions or solutions to resolve the issues.
The following sections are included:
•Wireless Switch Issues
•Access Port Issues
•Mobile Unit Issues
•Failover Issues
•Installation Issues
•Miscellaneous Issues
•System Logging Mechanism
1.1 Wireless Switch Issues
This section describes various issues that may occur when working with the switch. Possible issues include
•Switch Does Not Boot Up
•Switch Takes a Long Time to Start Up
•Switch Does Not Obtain an IP Address through DHCP
•Switch is Stuck in a Booting Loop
•Unable to Connect to the Switch using Telnet or SSH
•Web UI is Sluggish, Does Not Refresh Properly, or Does Not Respond
•Console Port is Not Responding
•Shutting Down the Switch
1.1.1 Switch Does Not Boot Up
The switch does not boot up to a username prompt via CLI console or Telnet.
Table 1.1 provides suggestions to troubleshoot this issue.

1-2 WS5100 Series Switch Troubleshooting Guide
1.1.2 Switch Takes a Long Time to Start Up
Until DHCP is enabled (and if static IP addresses are not being used), startup can be extremely slow. This is
normal.
1.1.3 Switch Does Not Obtain an IP Address through DHCP
The switch requires a routable IP address for the administrator to manage it via Telnet, SSH or a Web
browser. By default, the switch boots up with a non-routable static IP address.
Table 1.2 provides suggestions to troubleshoot this issue.
1.1.4 Switch is Stuck in a Booting Loop
The switch continuously boots and does not change context to a user name prompt.
Table 1.3 provides suggestions to troubleshoot this issue.
Table 1.1 Switch Does Not Boot Up Troubleshooting Notes
Possible Problem Suggestions to Correct
Switch has no power • Verify power cables, fuses, UPS power. The front panel LED lights up when
power is applied to the switch.
• Verify the power switch on the back of the switch is in the I(on) position.
• Have a qualified electrician check the power source to which the switch is
connected.
Chassis fans and/or CPU
fan not rotating
• Visually inspect the fans located inside the switch chassis.
• If one or more of the CPU fans are not running, contact the Motorola Support
center for further instructions.
All else... Contact Motorola Support.
Table 1.2 Switch Does Not Obtain an IP Address through DHCP Troubleshooting Notes
Possible Issue Suggestions to Correct
DHCP is not configured, or
not available on same
network as the switch
• Verify the configuration for the switch has DHCP enabled. By default, Ethernet NIC 2
is DHCP enabled. Otherwise, refer to the CLI reference for instructions on enabling
the Ethernet interfaces.
• Ensure the WS5100 is on the same network as the DHCP server and verify the server
is providing DHCP services.
• Connect another host configured for DHCP and verify it is getting a DHCP address
DHCP is not enabled on
NIC 2 (that is, the Ethernet
port that is not managing
the RF network)
• Enable DHCP, use the CLI command or the GUI to enable DHCP on the Ethernet port
connected to your network.
• Verify DHCP packets are being sent to NIC 2 using a sniffer tool
• If DHCP packets are seen, check to ensure that the switch is not configured for a
static IP on NIC 2.
All else.. Contact Motorola Support.

Overview 1-3
1.1.5 Unable to Connect to the Switch using Telnet or SSH
The switch is physically connected to the network, but connecting to the switch using SSH or Telnet does not
work.
Table 1.4 provides suggestions to troubleshoot this issue.
1.1.6 Web UI is Sluggish, Does Not Refresh Properly, or Does Not Respond
When configuring the switch, it is easy to overlook the fact that the host computer is running the browser
while the switch is providing the data to the browser. Occasionally, while using the Web UI (GUI) the switch
does not respond or appears to be running very slow; this could be a symptom of the host computer or the
network, and not the switch itself. Table 1.5 provides suggestions to troubleshoot this issue.
Table 1.3 Switch is Stuck in a Booting Loop Troubleshooting Notes
Possible Issue Suggestions to Correct
Bad flash memory module Remove the flash memory and install it in a different switch.
Switch not getting enough
ventilation
Verify the CPU fan is operating properly.
All else... Contact Motorola Support.
Table 1.4 Unable to Connect to the Switch using Telnet or SSH Troubleshooting Notes
Possible Issue Suggestions to Correct
Console is not on network • Check all cabling and terminal emulation program settings to be sure they are
correctly set. See Console Port is Not Responding issue, or the WS5100 Series
Switch System Reference Guide for more details.
• From a another system on the same network. attempt to ping the switch.
Telnet is not enabled
and/or SSH is disabled
Verify Telnet or SSH are enabled using the CLI or GUI (By default, telnet is disabled.).
Max sessions have been
reached
Maximum allowed sessions is 8 concurrent users connected to a switch. Verify that
the threshold has not been reached. .
Primary LAN is not
receiving Telnet traffic
Verify Telnet traffic is on the primary VLAN.
All else... Contact Motorola Support.
Table 1.5 Web UI is Sluggish, Does Not Refresh Properly, or Does Not Respond Troubleshooting Notes
Possible Issue Suggestions to Correct
Bad connection between
switch and console system
Verify the line between the switch and the host computer is functioning normally.
Slow transmission of data
packets
Verify the data packets are being sent to and from the switch using a sniffer tool.
Access ports may try to
adopt while country code is
not set
Set the country name for the switch, which is set to “none” by default.

1-4 WS5100 Series Switch Troubleshooting Guide
1.1.7 Console Port is Not Responding
The switch console port is physically connected to the host computer’s serial port, but pressing the [Enter]
key gets no response from the switch.
Table 1.6 provides suggestions to troubleshoot this issue.
1.1.8 Shutting Down the Switch
The CLI commands used to shutdown the switch have changed with the release of the 3.x version WS5100
Series Switch. Please refer to the following to differentiate between the shutdown command
(1.4.x and 2.x) from the halt command (3.x).
1.1.8.1 Shutting Down the Switch Using the 1.4.x/2.x Shutdown Command
To gracefully shutdown the WS 5100, issue the shutdown command from the configure context in the CLI:
WS5000.(Cfg)> shutdown
This command will halt the system.
Packet storm Check Syslog for any type of a packet storm.
Overburdened with a large
number of access ports
With large numbers of access ports, changing the configuration quickly may cause the
switch to not refresh properly, at least immediately following configuration.
Java JRE is out of date Be sure you are using Sun Java JRE 1.5 or later. To download the appropriate for your
system go to: http://www.sun.com/java/
All else... Contact Motorola Support.
Table 1.6 Console Port is Not Responding Troubleshooting Notes
Possible Issue Suggestions to Correct
Cabling issue Ensure that a NULL-modem cable is connected from the WS5100 console port to the
host computer’s serial port.
Not using a terminal
emulation program
Verify a serial terminal emulation program, such as HyperTerminal, is in use.
Settings in terminal
emulation program are
incorrectly set
Check the serial port settings in the serial terminal emulation program being used. The
correct settings are:
All else... Contact Motorola Support.
Table 1.5 Web UI is Sluggish, Does Not Refresh Properly, or Does Not Respond Troubleshooting Notes (Continued)
Possible Issue Suggestions to Correct
Terminal Type VT-100
Port COM 1-4
Terminal Settings 19200 bps transfer rate
8 data bits
no parity
1 stop bit
no flow control

Overview 1-5
A manual power cycle will be required to re-start the switch.
Do you want to proceed (yes/no) : yes
System shut down might take a few mins....
Shutting down the switch...
Shutting down dhcp daemon.. done
Shutting down apache server in the OPEN mode...done.
Shutting down cell controller........ done
Shutting down snmpd agent...done.
Shutting down Postgres....done.
INIT: Sending processes the TERM signal
Shutting down PacketSwitch interface .....
Shutting down dhcp daemon.. done
Shutting down apache server in the OPEN mode...done.
Cell controller not running.
i2c-core: Device or resource busy
Shutting down Postgres....done.
Stopping periodic command scheduler: cron.
Stopping internet superserver: inetd.
Saving random seed... done.
Stopping deferred execution scheduler: atd.
Stopping kernel log daemon: klogd.
Stopping system log daemon: syslogd.
flushing ide devices: hda
System halted.
As directed, wait 10 seconds and turn off the device by toggling the power switch.
1.1.8.2 Shutting Down the Switch Using the Halt Command
To shut down the WS 5100 from the CLI, issue a halt command, as the halt command is now used to shut
down the switch with the release of the 3.x version WS5100 baseline:
WS5100#halt
Wireless switch will be halted, do you want to continue? (y/n):y
The system is going down NOW !!
% Connection is closed by administrator!
WIOS_SECURITYMGR[395]: DNSALG: Shutting down.
WIOS_SECURITYMGR[395]: FTPALG: Shutting down.
The system is halted.
NOTE: The WS5100 will power off after issuing a halt command through a software
toggle of the power supply. Be sure to flip the power switch to the Off position. If the
power cord is removed and reinstalled, or power is lost and restored, the switch will
power back on.

1-6 WS5100 Series Switch Troubleshooting Guide
1.2 Access Port Issues
This section describes various issues related to access ports within the switch network.
1.2.1 Access Ports are Not Adopted
Access ports are not being adopted. Table 1.7 provides suggestions to troubleshoot this issue.
1.3 Mobile Unit Issues
This section describes various issues that may occur when working with the Mobile Units associated with
the wireless switch or associated Access Ports. Possible issues include:
•Access Port Adopted, but MU is Not Being Associated
•MUs Cannot Associate and/or Authenticate with Access Ports
•Poor Voice Quality Issues
1.3.1 Access Port Adopted, but MU is Not Being Associated
Access port associated with an MU is not yet being adopted. The following table provides suggestions to
troubleshoot this issue.
Table 1.7 Access Ports are Not Adopted Troubleshooting Notes
Possible Issue Suggestions to Correct
Access port is not
configured
Verify the license key that is set in the switch.
Country code for switch is
not set
Verify the country code is entered into the switch prior to adopting any access ports.
The switch is not fully functional until a country code is set.
Access ports are off-
network
Verify the access ports are connected to the network and powered on.
Switch is configured as
Standby switch
Verify the switch is not configured as a Standby system prior to adopting any access
ports. Even if a Standby switch is not in use, the Primary switch must be in an active
state in order for it to adopt access ports.
The state is automatically determined by the failover system. From the CLI or Web UI
check the standby state to see if the switch is either Primary or Standby
Access ports are restricted
in configuration
Verify the switch is not configured with an access control list that does not allow
access port adoption; verify that access port adoption is not set to “deny”.
Ensure that the access port adoption policy is added with a WLAN.
Access Port is on Exclude
List
Verify the ACL adoption list does not include the access ports that are not being
adopted.
Miscellaneous other issues • Check the access port LEDs for “Loadme” message on start-up.
• With a packet sniffer, look for 8375 (broadcast) packets
• Reset the switch. If the switch is hung, it may begin to adopt access ports properly
once it has been reset.
All else... Contact Motorola Support.

Overview 1-7
1.3.2 MUs Cannot Associate and/or Authenticate with Access Ports
MUs cannot associate and/or authenticate with access ports. The following table provides suggestions to
troubleshoot this issue.
1.3.3 Poor Voice Quality Issues
VOIP MUs, BroadCast MultiCast and SpectraLink phones have poor voice quality issues. The following table
provides suggestions to troubleshoot this issue.
1.4 Failover Issues
This section describes various issues related to the failover capabilitie of the switch. Possible issues include:
•Switch is Not Failing Over
Table 1.8 Troubleshooting When Access Port Is Not Yet Adopted
Possible Issue Suggestions to Correct
Unadopted access port Verify the switch has adopted the access port with which the MU is trying to
associate.
Incorrect ESSID applied to
the MU
Verify on the MU the correct ESSID has been applied to the MU.
Ethernet port configuration
issues
Verify the Ethernet port connected to thenetwork and has a valid configuration.
If DHCP is used, verify that the Ethernet cable is connected to the same NIC upon
which DHCP services are enabled.
Incorrect security settings Verify the correct security settings are applied to a WLAN in which the MU is tryng to
associate.
All else... Contact Motorola Support.
Possible Issue Suggestions to Correct
Preamble differences Verify the Preamble matches between switch and MUs. Try a different setting.
Device key issues Verify in Syslog that there is not a high rate of decryption error messages. This could
indicate that a device key is incorrect.
MU is not in Adopt List Verify the device is not in the “do not adopt ACL”.
Keyguard not set on client Verify Keyguard is set on the client if the Security/WLAN Policy calls for Keygaurd.
Possible Issue Suggestions to Correct
Traffic congestion with data
traffic
• Maintain voice and data traffic on separate WLANs.
• Use a QoS Classifier to provide dedicated bandwidth if data and voice traffic are
running on the same WLAN.
Long preamble not used on
Spectralink phones
Verify that a long preamble is used with Spectralink phones.

1-8 WS5100 Series Switch Troubleshooting Guide
•Switch is Failing Over Too Frequently
1.4.1 Switch is Not Failing Over
Switch is not failing over (Hot Standby) as appropriate.
The following table provides suggestions to troubleshoot this issue.
1.4.2 Switch is Failing Over Too Frequently
Switch failing over too frequently (flapping).
The following table provides suggestions to troubleshoot this issue.
1.5 Installation Issues
Before upgrading or downgrading any system, save a copy of the system configuration to an FTP or TFTP
server.
Possible Issues Suggestions to Correct
Primary and Standby
switches are not both
enabled
Verify the Primary and Secondary switches are Standby enabled and have the correct
MAC address configured for the correct Primary/Secondary switch.
Primary and Standby
switches have mismatched
software versions
Mismatch configurations are not allowed. Verify that the Primary and Secondary
switches have the same software versions running.
Primary and Standby
switches cannot
communicate with each
other
Verify the Primary and Secondary switch are configured properly and attempt to ping
each switch (using the ping command) from each switch.
Other problems, as listed in
switch logs
Review the local logs on the Standby switch.
MAC address configuration
issues
Review the Syslog. The correct MAC address should be seen when checking the
Syslog heartbeat messages.
Conflicting addressing on
same network
If more than one Primary switch exists on the same network, then use MAC addresses
to configure.
All else... Contact Motorola Support.
Possible Issues Suggestions to Correct
One of the switches is
crashing
Check the CPU usage using the CLI or Web UI Diagnostics information.
All else... Contact Motorola Support.

Overview 1-9
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.
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.
1.6.2 Excessive Memory Leak
Excessive memory leak. The following table provides suggestions to troubleshoot this issue.
Possible Issues Suggestions to Correct
Improper upgrade process • 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.
All else... Contact Motorola Support.
Possible Issues Suggestions to Correct
Fragmentation • 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.
All else... Contact Motorola Support.
Possible Issues 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 Motorola Support.

1-10 WS5100 Series Switch Troubleshooting Guide
1.7 System Logging Mechanism
The 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.

Syslog Messages &
MU Disassociation Codes
2.1 Syslog Messages
The following table provides information and descriptions of Syslog Messages.
Number Mnemonic Severity Syslog Message Meaning / Cause
1. AUTOUPCONFIG 4 Loaded new startup config If checksum compares for new and
running configurations are different –
new config overwrites the running
one. This may happen during auto-
install.
2. AUTONOUPCONFIG 4 Available config is same as
last loaded - will not be
reloaded
New and running configurations are
the same. This may happen during
auto-install.
3. AUTOUPCLCONFIG 4 Loaded new cluster config If checksum for new and running
config are different – new config
overwrites the running one. This may
happen during
auto-install.
4. AUTOINSTCLCFGNOCOPY 3 Could not overwrite the
cluster config file [str]
Copy temp to cluster-config failed.
Overwriting running-config with
cluster-config, wrong url path for files
display this error.
5. AUTOUPNOCLCONFIG 5 Available cluster config is
same as last loaded - will
not be reloaded
Config is the same.
6. AUTOINSTCLCFGNOREAD 3 Could not read the cluster
config file [str]
Cluster config copy to temp failed.
7. AUTONOIMAGEUPODATE 5 Requested image matches
running image - will not be
loaded
New and installed image versions
match.
8. AUTOIMAGEUPODATE 5 Attempting to load
requested image
Local image version does not match
required image version.

2-2 WS 5100 Series Switch Troubleshooting Guide
9. AUTOINSTNODHCP 5 DHCP did not provide any
configuration information -
no autoinstall action taken
DHCP information got update but file
cannot be opened.
10. AUTOINSTTIMEDREBOOT 7 Autoinstall delayed reboot -
shutting down system now
Auto-install rebooting the system.
11. AUTOCLCONFDISAB 5 Autoinstall of cluster
configuration is disabled
No autoinstall options were enabled.
12. AUTOINSTNODHCP 5 Autoinstall of startup
configuration is disabled
No autoinstall options were enabled.
13. AUTOINSTSIGWCCP 7 Changed cluster config -
signalling WCCP daemon
pid [int]
Cluster config changed. Need to
inform WCCP – Wireless Cluster
Control protocol, which handles all
cluster services.
14. AUTOINSTSIGWCCPUNKO
NWN
7 Tried to signal wccpd using
pidof because pid was not
read
Failed to open wccpd UID file, trying
plan B. By plan B we mean that we
using alternative method to find and
kill the process.
15. AUTOINSNOCLCFGCHAN
GE
7 Autoinstall did not change
cluster config - not
signalling wccpd
No cluster config changes
16. AUTOIMAGEDISAB 5 Autoinstall of image
upgrade is disabled
Image upgrade is not set – upgrade
will not run
17. AUTOINSTSTART 6 Autoinstall triggered DHCP triggered auto-install to start
18. AUTOINSTSCHEDULED 7 Autoinstall starting DHCP should have written the config
to the file, if we can read the config
and assemble the URLs then – start
auto-install.
19. AUTOINSTTOOLATE 6 Too late for DHCP triggered
autoinstall
If uptime is over 10 minutes – auto-
install will not run.
20. TKIPCNTRMEASEND 4 TKIP countermeasures
ended on WLAN [uint]
End of the countermeasures timer.
21. TKIPCNTRMEASSTART 4 TKIP countermeasures
started on WLAN [uint]
Two MIC failure within pre-defined
period of time – countermeasures are
starting – WLAN will be disabled.
22. DOT11ISUCCESS 6 Station [mac] completed
dot11i (tkip/ccmp)
handshake on WLAN [uint]
If this is a hotspot or a mac-
authentication MU, then there is
authentication work needed, else we
are done. Mark the MU as
successfully completed 802.11i
authentication.
23. DOT11IFAILURE 6 Station [mac] failed dot11i
(tkip/ccmp) handshake on
WLAN [uint]
Failure could occur due to 4-way
handshake timeout; or unknown state
of authentication (HOW?); or too
many retries; or IE element is
different than during association; or
key routine returned error.
Number Mnemonic Severity Syslog Message Meaning / Cause

Syslog Messages & MU Disassociation
24. TKIPMICFAILRPT 4 Station [mac] reported a
TKIP message integrity
check fail on WLAN [uint]
MU reported MIC failure.
25. DOT11IKEYROTN 6 Rotating dot11i (tkip/ccmp)
keys on WLAN [uint]
Broadcast key rotation starting on
WLAN.
26. STATIONUNASSOC 6 Station [mac] un-associated
from radio [uint]
MU is disassociated due to AP being
gone for some reason; or received de-
authentication request from MU; or
switch sends de-authentication
message because of inactivity or non-
valid authentication or WPA failure or
MIC failure or AP is not found or there
is no valid Radius server or IDS
violation ; or received disassociation
request from MU.
27. TKIPMICCHECKFAIL 4 TKIP message integrity
check failed in frame on
WLAN [uint]
Switch reports MIC failure for MU
28. COUNTRYCODE 5 config: setting country code
to [str]
New country code is set. All APs will
be reset.
29. RADIOUNADOPTED 5 [str] radio on AP [mac] un-
adopted
Due to country code change or
heartbeats timed-out or switch
issued reset command.
30. MAXAPCAPACITY 4 Max APs capacity reached:
[int]
Cluster max AP capacity reached.
31. DISKFULL 4 "Flash Disk Full, file cannot
be created
File creation failed due to no memory.
32. DFSNOVALIDHANNEL 6 "Radio [uint] unable to get a
valid channel, configuration
deferred
DFS is unable to find a valid channel.
33. DFSMOVECHANNEL 6 Radio [uint] move to channel
[uint] - [uint] MHz
DFS is changing the radio channel.
34. RADIORADARDETECT 4 802.11a radio on AP [mac]
found radar on channel
[uint]
Radar detection notice. Channel will
be changed if possible.
35. RADIODFSEND 6 Radio [uint] has completed a
DFS scan on channel [uint]
Radar scan complete.
36. RADIODFSSTART 6 Radio [uint] starting a DFS
scan on channel [uint] -
[uint] MHz
Starting DFS scan.
37. STATIONDENIEDAUTH 4 Station [mac] denied
authentication :
unsupported authentication
method
Radius authentication timed-out, MU
timed-out or authentication is not
supported.
Number Mnemonic Severity Syslog Message Meaning / Cause

2-4 WS 5100 Series Switch Troubleshooting Guide
38. WEBAUTHSUCCESS 6 Station [mac] web
authentication success on
WLAN [uint]
Hotspot/Web authentication
success.
39. WEBAUTHDISC 6 Station [mac] has
disconnected WLAN [uint]
Hotspot MU disconnected
40. WEBAUTHFAILED 6 Station [mac] failed web
authentication on WLAN
[uint]
Hotspot/Web MU authentication
failure due to wrong password.
41. EXCESSAUTHSASSOCS
EXCESSPROBES
EXCESSDISASSOCS
EXCESSAUTHFAILS
EXCESS80211REPLAY
EXCESSCRYPTOREPLAY
EXCESSDECRYPTFAILS
"4 "MU [mac] tx [uint] in
detect-window, filtering for
[int] seconds
IDS Excessive number of
disassociations or authentication
failures, or excessive probes, or
excessive disassociations or
excessive replay or decrypt failures -
MU will be disassociated.
42. IDSNULLADDR
IDSSAMEADDR
IDSMCASTSRC
IDSWEAKWEPIV
IDSCNTRMEAS
"4 MU [mac]. Filtering for [int]
seconds
IDS failure - MU will be
disassociated.
43. IDSEVENTRADIO 4 IDS event [str] detected at
Radio [uint]
Events are:
• probe-requests
• association-requests
• disassociations
• authentication-fails
• crypto-replay-fails
• 80211-replay-fails
• decryption-fails
• unassoc-frames
• eap-starts
• null-destination
• same-source-destination
• multicast-source
•weak-wep-iv
• tkip-countermeasures
• invalid-frame-length
44. IDSEVENTSWITCH 4 IDS event [str] detected on
switch
Events are same as above. Violations
thresholds are user configurable on
IDS.
45. WLANKERBCFGCHG 6 WLAN [uint] de-
authenticated,
configuration changed
Set the WLAN as not authenticated.
Number Mnemonic Severity Syslog Message Meaning / Cause