Gui Applet Is Sluggish, Does Not Refresh Properly, Or Does Not Respond - Symbol WS5000 Troubleshooting Manual

1-4
WS5000 Series Switch Troubleshooting Guide
Table 1.4 Unable to Telnet into the Switch Troubleshooting Notes (Continued)
Possible Issue Suggestions to Correct
Max sessions have been
reached
Primary VLAN is not routed
Primary LAN is not
receiving Telnet traffic
All else...

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 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
Slow transmission of data
packets
Access ports may try to
adopt while country code is
not set
Packet storm
Overburdened with a large
number of access ports
SNMP trapping
All else...
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.
Verify Primary VLAN is routed.
Use the show VLAN command at the WS5000> prompt.
Verify that Telnet traffic is on the primary VLAN.
Use the show system command if you wish.
Contact Symbol Support.
Table 1.5 provides suggestions to troubleshoot this issue.
Verify that the line between the switch and the host computer is functioning normally.
Verify that the data packets are being sent to and from the switch using a sniffer tool.
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]>)
Check Syslog for any type of a packet storm.
With large numbers of access ports, changing the configuration quickly may cause the
switch to not refresh properly, at least immediately following configuration.
Turn SNMP off from the SNMP configuration context (especially if SNMP is not needed).
Contact Symbol Support.