Proxim Wireless Corporation XB92WFR ユーザーズマニュアル
Troubleshooting
Tsunami
®
800 & 8000 Series - Software Management Guide
272
8.5 Application Specific Troubleshooting
8.6 Wireless Link Issues
Given below are the possible reasons for a wireless link not getting established and the relevant observations.
Problem
Solution
RADIUS
Authentication Server
Services unavailable
Authentication Server
Services unavailable
If RADIUS Authentication is enabled on the device, then make sure that your network’s
RADIUS servers are operational. Otherwise, clients will not be able to log on to the device.
RADIUS servers are operational. Otherwise, clients will not be able to log on to the device.
There are several reasons for the authentication server‘s services to be unavailable. To
make it available,
make it available,
•
Make sure you have the proper RADIUS authentication server information setup
configured on the device. Check the RADIUS Authentication Server’s Shared Secret
and Destination Port number (default is 1812; for RADIUS Accounting, the default is
1813).
configured on the device. Check the RADIUS Authentication Server’s Shared Secret
and Destination Port number (default is 1812; for RADIUS Accounting, the default is
1813).
•
Make sure the RADIUS authentication server RAS setup matches the device.
TFTP Server
If a TFTP server is not configured and running, you will not be able to download and
upload images and configuration files to or from the device. Remember that the TFTP
server need not be local, as long as you have a valid TFTP IP address. Note that you do not
need a TFTP server running unless you want to transfer files to or from the device.
upload images and configuration files to or from the device. Remember that the TFTP
server need not be local, as long as you have a valid TFTP IP address. Note that you do not
need a TFTP server running unless you want to transfer files to or from the device.
After the TFTP server is installed:
•
Check to see that TFTP is configured to point to the directory containing the
device Image.
device Image.
•
Make sure you have the proper TFTP server IP Address, the proper device image
file name, and that the TFTP server is connected.
file name, and that the TFTP server is connected.
•
Make sure the TFTP server is configured to both Transmit and Receive files (on
the TFTP server’s Security tab), with no automatic shutdown or time-out (on
the Auto Close tab).
the TFTP server’s Security tab), with no automatic shutdown or time-out (on
the Auto Close tab).
Reason(s)
Observation
Mismatch in network
name
name
•
The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in
BSU/End Point A and SU/End Point B.
BSU/End Point A and SU/End Point B.
•
The WORP counters are not affected.
•
The remote device is not listed in the Site Survey.
Incorrect or invalid
configured BSU/End
Point A name
configured BSU/End
Point A name
•
The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in
SU/End Point B.
SU/End Point B.
•
The WORP counters are not affected.
•
The remote device is not listed in the Site Survey.
Mismatch in network
secret
secret
•
The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in
BSU/End Point A and SU/End Point B.
BSU/End Point A and SU/End Point B.
•
The WORP counters are incremented (Req for Serv, Reg Req, Auth Req, Reg
Attempts, Reg LastReason: Incorrect Parameter) on both ends.
Attempts, Reg LastReason: Incorrect Parameter) on both ends.