Symbol WS5000 Owner's manual

WS5000 Series Switch

Troubleshooting Guide

Copyright

No part of this publication can be modified or adapted in any way, for any purposes without permission in writing from

Symbol. The material in this manual is subject to change without notice.

Symbol reserves the right to make changes to any product to improve reliability, function, or design.

No license is granted, either expressly or by implication, estoppel, or otherwise under any Symbol Technologies, Inc.,

intellectual property rights. An implied license only exists for equipment, circuits, and subsystems contained in Symbol

products.

Symbol, the Symbol logo are registered trademarks of Symbol Technologies, Inc.

IBM is a registered trademark of International Business Machine Corporation. Microsoft, Windows, and Windows NT are

registered trademarks of Microsoft Corporation. Novell and LAN Workplace are registered trademarks of Novell Inc. Toshiba

is a trademark of Toshiba Corporation. All other product names referred to in this guide might be trademarks or registered

trademarks of their respective companies and are hereby acknowledged.

Patents

This product is covered by one or more of the patents listed on the website: http://www.symbol.com/patents.

Contents

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. System Troubleshooting

1.1 Wireless Switch Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1.1.1 Switch Does Not Boot Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

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-3

1.1.5 Unable to Telnet into the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

1.1.6 GUI Applet is Sluggish, Does Not Refresh Properly, or Does Not Respond . . . 1-4

1.1.7 Console Port is Not Responding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1.1.8 WS5000 CLI Prompt Displays DIAG> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1.2 Access Port Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1.2.1 Access Ports are Not Adopted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

WS5000 Series Switch Troubleshooting Guide

iv

1.3 Mobile Unit Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

1.3.1 Access Port Adopted, but MU is Not Being Associated. . . . . . . . . . . . . . . . . . . 1-7

1.3.2 MUs Cannot Associate and/or Authenticate with Access Ports . . . . . . . . . . . . 1-8

1.3.3 Poor Voice Quality Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

1.4 Failover Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

1.4.1 Switch is Not Failing Over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

1.4.2 Switch is Failing Over Too Frequently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

1.5 Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

1.5.1 After Upgrade, Version Number Has Not Changed . . . . . . . . . . . . . . . . . . . . . 1-10

1.5.2 After Upgrade, Configuration Settings Revert to Defaults. . . . . . . . . . . . . . . . 1-10

1.6 Miscellaneous Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1.6.1 Excessive Fragmented Data or Excessive Broadcast . . . . . . . . . . . . . . . . . . . . 1-11

1.6.2 Excessive Memory Leak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1.6.3 Administrative Login Does Not Authenticate. . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1.7 System Logging Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Chapter 2. Service Mode CLI Commands

2.1 CLI Service Mode Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1.1 Logging into the Service Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.1.2 Basic Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2 SM-WS5000> Command Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2.1 ? or help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.2.2 logout or bye . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2.2.3 exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

2.2.4 capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2.2.5 check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.2.6 clear. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.2.7 configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.2.8 copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.2.9 debug. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

2.2.10 delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.2.11 description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.2.12 directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

2.2.13 emergencymode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

2.2.14 execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

2.2.15 install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

2.2.16 launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

2.2.17 name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

2.2.18 password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

2.2.19 ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

2.2.20 restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

2.2.21 save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

v

2.2.22 shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

2.2.23 show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

2.2.24 watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Chapter 3. Network Events

Chapter 4. MU Disassociation Codes

WS5000 Series Switch Troubleshooting Guide

vi

About this Guide

This preface introduces the WS5000 Series Switch Troubleshooting Guide and contains the following sections:

• Who Should Use this Guide

• How to Use this Guide

• Conventions Used in this Guide

• Service Information

Who Should Use this Guide

The WS5000 Series Switch Troubleshooting Guide is intended for system administrators maintaining and

troubleshooting issues encountered with the WS5000 Series Switch within the wireless local area network.

The administrator should be familiar with wireless technologies, network concepts, Ethernet concepts, as well

as IP addressing and SNMP concepts.

WS5000 Series Switch Troubleshooting Guide

viii

How to Use this Guide

This guide will help you troubleshoot issues encountered with the WS5000 Series Switch and associated

network elements. This guide is organized as follows.

Conventions Used in this Guide

This section describes the following topics:

• Annotated Symbols

• Notational Conventions

Annotated Symbols

Note This symbol signals recommended behavior or reference information that

might be important to consider. It may include tips or special requirements.

IMPORTANT! THIS SYMBOL SIGNALS INFORMATION ABOUT A PROCESS OR CONDITION

THAT COULD CAUSE DAMAGE TO EQUIPMENT, INTERRUPTION OF SERVICE, OR LOSS OF

DATA.

Warning! This symbol signals information about a process or condition

that could cause bodily injury. Before you work on any equipment, be

aware of physical and electrical hazards and follow standard practices for

preventing accidents.

Table 1 Quick Reference on How This Guide Is Organized

Chapter Description

Chapter 1, “System

Troubleshooting”

This chapter is organized categorically, like a “Frequently Asked Questions (FAQ)”

chapter, focussing on most common areas of concern.

Chapter 2, “Service Mode CLI

Commands”

This chapter provides a complete command reference for the Service Mode CLI of the

WS5000 Series Switch.

Chapter 3, “Network Events” This chapter provides a complete reference for the network events that can be

incurred on the WS5000 Series Switch, including descriptions and suggested actions,

for problem areas.

Chapter 4, “MU

Disassociation Codes”

This chapter provides a complete reference for 802.11 mobile unit disassociation

codes.

!

ix

Notational Conventions

The following notational conventions are used in this document:

• Italics are used to highlight specific items in the general text, and to identify chapters and sections in

this and related documents.

• Bullets (•) indicate:

• action items

• lists of alternatives

• lists of required steps that are not necessarily sequential

• Sequential lists (those describing step-by-step procedures) appear as numbered lists.

Service Information

If a problem is encountered with the WS5000 Series Switch, review the details within this guide to see if you

can resolve the problem yourself. If you are still having troubles, contact Symbol Customer Support. See

Symbol’s Web site (http://www.symbol.com) for Symbol Customer Support contact information and policies.

Note Before calling Symbol Customer Support, have the model number and serial

number for the WS5000 Series Switch on hand.

If the problem cannot be resolved over the phone, you may need to return your equipment for servicing. If that

is necessary, you will be given specific directions.

Symbol Technologies is not responsible for any damages incurred during shipment if the approved shipping

container is not used. Shipping the units improperly can also possibly void the warranty. If the original shipping

container was not kept, contact Symbol to have another sent to you.

WS5000 Series Switch Troubleshooting Guide

x

1

System Troubleshooting

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

WS5000 Series Switch Troubleshooting Guide

1-2

1.1 Wireless Switch Issues

This section describes various issues that may occur when working with the WS5000 Series 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 Telnet into the Switch

• GUI Applet is Sluggish, Does Not Refresh Properly, or Does Not Respond

• Console Port is Not Responding

• WS5000 CLI Prompt Displays DIAG>

1.1.1 Switch Does Not Boot Up

The WS5000 Series Switch does not boot up to a username prompt via CLI console or Telnet. Table 1.1 provides

suggestions to troubleshoot this issue.

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 WS5000 Series Switch requires a routable IP address for the administrator to manage it via Telnet or a

Web browser. By default, the switch boots up with a non-routable static IP address.

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 Symbol Support

center for further instructions.

All else... Contact Symbol Support.

System Troubleshooting

1-3

Table 1.2 provides suggestions to troubleshoot this issue.

1.1.4 Switch is Stuck in a Booting Loop

The WS5000 Series Switch continuously boots and does not change context to a user name prompt. Table 1.3

provides suggestions to troubleshoot this issue.

1.1.5 Unable to Telnet into the Switch

The WS5000 Series Switch is physically connected to the network, but telneting into the switch does not work.

Table 1.4 provides suggestions to troubleshoot this issue.

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 WS5000

Series Switch

• Verify that the configuration for the switch has DHCP enabled. By default, Ethernet

NIC 2 is DHCP enabled. Otherwise, use set dhcp enable command at the Ethernet

NIC 2 Instance prompt (

WS5000.(Cfg).Ethernet.[2]> set dhcp enable).

• Ensure that the WS5000 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

not managing the RF network (NIC 2)

• Verify that 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 Symbol Support.

Table 1.3 Switch is Stuck in a Booting Loop Troubleshooting Notes

Possible Issue Suggestions to Correct

Bad DOM (disk on memory)

module

Remove the DOM (disk on memory) and install it in a different switch.

DOM/switch not getting

enough ventilation

Verify that the CPU fan is operating properly.

All else... Contact the Symbol Support.

Table 1.4 Unable to Telnet into the Switch 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 WS5000 Series

Wireless 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 that Telnet is enabled and SSH is disabled by using the CLI or GUI (By default,

telnet is disabled.).

Use the show telnet command at the WS5000> prompt.

WS5000 Series Switch Troubleshooting Guide

1-4

1.1.6 GUI Applet 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 WS5000 Series Switch is providing the data to the browser. Occasionally, while using the Applet (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.

Max sessions have been

reached

Maximum allowed sessions is 8 concurrent users connected to a switch. Verify that the

threshold has not been reached.

Use the show users command at the WS5000> prompt.

Primary VLAN is not routed Verify Primary VLAN is routed.

Use the show VLAN command at the WS5000> prompt.

Primary LAN is not

receiving Telnet traffic

Verify that Telnet traffic is on the primary VLAN.

Use the show system command if you wish.

All else... Contact Symbol Support.

Table 1.5 GUI Applet 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 that the line between the switch and the host computer is functioning normally.

Slow transmission of data

packets

Verify that 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.

Use the set countrycode command at the Switch Policy Instance prompt (for example,

WS5000.(Cfg).SPolicy.[Default Wireless Switch Policy]>)

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.

SNMP trapping Turn SNMP off from the SNMP configuration context (especially if SNMP is not needed).

All else... Contact Symbol Support.

Table 1.4 Unable to Telnet into the Switch Troubleshooting Notes (Continued)

Possible Issue Suggestions to Correct

System Troubleshooting

1-5

1.1.7 Console Port is Not Responding

The WS5000 Series 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 WS5000 CLI Prompt Displays DIAG>

The WS5000 Series Switch changes into the diagnostics mode, displaying the DIAG> prompt, when it

encounters a critical internal failure, such as when the switch is unable to start. This is a fatal error that should

never happen.

From the DIAG> prompt, the following options are available:

•reset

• shutdown

• restore

Before contacting the Symbol Support Center, perform the following suggested corrective actions:

1. From the DIAG> prompt, invoke the reset command.

DIAG> reset

This command resets the system.

2. From the DIAG> prompt, invoke the restore default configuration command:

DIAG> restore <default config>.cfg

3. From the DIAG> prompt, invoke the restore system image command. Restore a known good image, not

the image used when the switch went into diagnostics mode.

DIAG> restore WS5000_x.x.x.0-00xx.sys.img

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 WS5000 console port to the

host computer’s serial port.

Not using a terminal

emulation program

Verify that 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 Symbol Support.

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

WS5000 Series Switch Troubleshooting Guide

1-6

4. If the switch comes up normally, return the switch to a normal operational readiness state. That is, check

Ethernet NIC 2 IP configuration, adopt access ports and associate an mobile unit.

If the switch continues to go into Diagnostics mode, call Symbol Support or log a Symbol Support Center

call.

1.2 Access Port Issues

This section describes various issues related to access ports within the WS5000 Series Switch network.

Possible issues include:

• Access Ports are Not Adopted

1.2.1 Access Ports are Not Adopted

Access ports are not being adopted. Table 1.7 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 that the access port key is entered into the switch prior to setting up any access

ports.

Country code for switch is

not set

Verify that 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.

Use the set countrycode command from the Switch Policy Instance prompt

(WS5000.(Cfg).SPolicy.[Name]>).

Access ports are off-

network

Verify that the access ports are connected to the network and powered on.

Switch is configured as

Standby switch

Verify that 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 “Startup”

state in order for it to adopt access ports.

The state is automatically determined by the failover system. From the CLI, use the show

command from the Standby prompt (WS5000.(Cfg).Standby>). In the returned output

from the command, StandBy mode should be “Primary”, and State should be “Startup”

Access ports are restricted

in configuration

Verify that the switch is not configured with an active switch policy that does not allow

access port adoption. In other words, verify that access port adoption is not set to

“deny”.

Access Port is on Exclude

List

Verify that the WS5000 Series Switch exclude adoption list does not include the access

ports that are not being adopted.

• To check the list, go to the Switch Policy instance and use the show command

(WS5000.(Cfg).SPolicy.[Name]>).

• To remove an access port from the exclusion list, go to the Switch Policy instance and

invoke the set adoptionlist exclude <MAC_address> remove

command

(

WS5000.(Cfg).SPolicy.[Name]>)

Miscellaneous other issues • Check the access port LEDs for “Loadme” message on start-up.

• With a packet sniffer, look for 8375 (broadcast) packets

All else... Contact Symbol Support.

System Troubleshooting

1-7

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. Table 1.8 provides suggestions to troubleshoot

this issue.

Table 1.8 Access Port Adopted, but MU is Not Being Associated Troubleshooting Notes

Possible Issue Suggestions to Correct

Unadopted access port Verify that the switch has adopted the access port with which the MU is trying to

associate.

WLAN is not authenticated Verify that the WLAN has been authenticated. Use the show command from the WLAN

Instance prompt (WS5000.(Cfg).WLAN.[WLAN_Name]>).

Incorrect ESSID applied to

the MU

Verify on the MU that the correct ESSID has been applied to the MU.

Encryption key(s) for the

MU is incorrect

• Verify that the encryption key(s) on the MU was entered correctly. The key on the

switch and the key on the MU must be identical (in a shared key authentication

system).

• Verify the encryption keys that the switch is using. Go to the Security Policy instance

(WS5000.(Cfg).SecurityPolicy.[Name]>) that was applied to the WLAN and verify that

the same encryption keys are being used at the MU.

Ethernet port configuration

issues

• Verify that the Ethernet port connected to the wired side of the network (sometimes

referred to as the RON NIC or rest of network NIC) 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. The Ethernet port is set and viewed in the active

Ethernet Policy (EtherPolicy) context. (WS5000.(Cfg).Ethernet.[1]>

)

Incorrect security settings Verify that the correct security settings are applied to a WLAN in which the MU is tryng

to associate.

All else... Contact Symbol Support.

WS5000 Series Switch Troubleshooting Guide

1-8

1.3.2 MUs Cannot Associate and/or Authenticate with Access Ports

MUs cannot associate and/or authenticate with access ports. Table 1.9 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. Table 1.10 provides

suggestions to troubleshoot this issue.

1.4 Failover Issues

This section describes various issues related to the failover capabilitie of the WS5000 Series Switch. Possible

issues include:

• Switch is Not Failing Over

• Switch is Failing Over Too Frequently

Table 1.9 MUs Cannot Associate and/or Authenticate with Access Ports Troubleshooting Notes

Possible Issue Suggestions to Correct

Preamble differences Verify that the Preamble matches between switch and MUs. Try a different setting.

Use the show command from the Access Port Policy Instance prompt

(WS5000.(Cfg).APPolicy.[Name]>)

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 that the device is not in the “do not adopt ACL”.

Keyguard not set on client Verify that Keyguard is set on the client if the Security/WLAN Policy calls for Keygaurd.

Table 1.10 Poor Voice Quality Issues Troubleshooting Notes

Possible Issue Suggestions to Correct

Traffic congestion with

data traffic

• Maintain voice and data traffic on separate WLANs.

• Use a 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.

System Troubleshooting

1-9

1.4.1 Switch is Not Failing Over

Switch is not failing over (Hot Standby) as appropriate. Table 1.11 provides suggestions to troubleshoot this

issue. Please verify the latest version of JRE is installed on your system.

1.4.2 Switch is Failing Over Too Frequently

Switch failing over too frequently (flapping). Table 1.12 provides suggestions to troubleshoot this issue.

Table 1.11 Switch is Not Failing Over Troubleshooting Notes

Possible Issues Suggestions to Correct

Primary and Standby

switches are not both

enabled

Verify that 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.

Use the show system command at the WS5000> prompt.

Primary and Standby

switches cannot

communicate with each

other

Verify that the Primary and Secondary switch are configured properly and attempt to

ping each switch (using the ping command) from each switch.

Symbol WS5000 Owner's manual

This manual is also suitable for

Symbol WS5000 Owner's manual

Related papers

Other documents