Know issues an bugs
This list is updated with all know issues and bugs.
Each product series has its own section in the list.
If you encounter a problem with any of our products please report to repeatit by email.
In the report be as specific as possible.
Include:
- Product name
- Serial number
- SW version used on the product.
RCS Software:
Some versions of the "IcedTea" JVM on Ubuntu causes BS-200 series basestations to fail to connect to the RCS.
1: The warning when replacing between BS200-series of BS5400-series are there for a reason!
Reported:
2011-01-18 SW version 2.7.1.1 - 2.7.1.3
Status:
2011-01-18: Problem is identified and solution has been chosen. Currently being implemented.
Description:
When an old BS type is replaced by an newer BS200-Series BS and the "Replace BS" button functionality does not migrate settings.
Result:
Settings needs to be imported from the BS before the BS can be configured. Press the "Use unit settings" button on the "RCS" tab of the settings.
Solution:
The RCS will automatically import the BS settings if settings are missing.
Is available in RCS version 2.7.2.1.
This is not a complete solution to the replace BS feature but will limit the problem.
It will still be necessary to check and adjust the configuration manually.
2. Statistics is sometimes shown wrong on a SU100-Series CPE
Reported:
2011-01-18 SW version 2.7.7.3 and earlier
Status:
2011-01-18: Problem is under investigation.
Description:
The statistics show in the online statistics window is sometimes showing negative values for different counters. This is only valid for SU100-Series SUs.
Result:
The number of packets and/or bytes can be wrong.
Workaround:
There is no workaround.
Soultion:
Solution will be available in SW upgrade.
BS200-Series
5: Error message in RCS when using BS with RCS,
Reported:
2011-07-18 SW version 1.5.3.0
Status:
2011-07-18: SW version 1.5.3.0 needs to be run with the latest version of the RCS version 2.8.2.0.
4. Flood unknown enabled causes BS to reboot.
Reported:
2011-05-04 SW version 1.5.2.9 and earlier
Status:
2011-05-04: A fix is under implementation.
Description:
Enabling the "Flood Unknown" parameter can cause the BS to reboot. This can happend if the "Flood Unknow" is enabled and there is at least one Client that is constantly loging on and off on the BS.
Result:
Reboot of BS.
Workaround:
Currently no workaround indentified.
Soultion:
A fix for the problem will be available in next version of software, 1.5.2.10.
3. Short disruptions on the link between BS and Clients
Reported:
2011-04-21 SW version 1.5.2.9 and earlier
Status:
2011-05-04: A fix is under implementation.
2011-05-03: Possible cause found.
2011-04-21: Problem is under investigation.
Description:
Sometimes clients to the BS can disconnect/reconnect eaven if traffic is flowing over the link. During theese short disruptions no traffic is going over the link.
Possible cause: In noisy environments the radio calibration can take longer time then expected this causes the beacons not to be sent properly. If more than 10 consecutive beacons is missed the clients assumes that the BS is gone and will try to reconnect. This involves a scan of all channels.
Result:
Disruptions of the traffic.
Workaround:
Currently no workaround indentified.
Soultion:
Solution will be available in next version of software, 1.5.2.10.
2. RESOLVED: When BS is used in Client mode and connects to a Legacy 11A BS, only antenna A is used
Reported:
2011-01-10 SW version 1.5.2.4 and earlier
Status:
2011-04-18: New SW version released with a fix.
2011-01-18: Problem has been identified, solution is under test.
2011-01-10: Problem is under investigation.
Description:
When a BS radio interface is used in Client mode and it connects to a Legacy 11A radio interface the radio only uses antenna connector A. If the used antenna has been connected to antenna port B the BS will have very poor signal values.
Result:
The BS radio interface will not be able to connect to the other BS.
Workaround:
Always use antenna port A for the main Antenna, normally vertical polarization.
Soultion:
Solution will be available in SW upgrade.
1. RESOLVED: Reading network information with SNMP halts traffic to Clients.
Reported:
2011-01-10 SW version 1.5.2.3 and earlier
Status:
2011-01-16: Problem has been solved new SW version 1.5.2.4 is released.
2011-01-10: Problem is under investigation.
Description:
If a SNMP is used to read information about network interfaces on the BS the BS halts all transmission to clients.
Result:
No traffic is sent to clients.
Workaround:
There is no workaround.
Soultion:
Solution will be available in SW upgrade.
BS52/51-Series
2: Error message in RCS when using BS with RCS,
Reported:
2011-07-18 SW version 1.5.3.0
Status:
2011-07-18: SW version 1.5.3.0 needs to be run with the latest version of the RCS version 2.8.2.0.
Workaround:
There is no work around.
Solution:
Uppgrade to RCS version 2.8.2.0.
1: SiteSurvey is sometimes causing a reboot of the BS.
Reported:
2011-01-18 SW version 1.5.2.4 and 1.4.4.4
Status:
2011-01-18: Problem is under investigation.
Description:
When performing a Sitesurvey or Spectrum scan the BS reboots. This does not happened on all BS it has been reported on aprox. 3 installed BSs.
Result:
The BS software hangs when the SiteSurvey is performed, the BS then reboots automatically. Causes a disruption of the radio traffic to and from the clients.
Workaround:
There is no work around.
Solution:
No solution yet, problem still under investigation.
SU55XX-Series
3: Connection problems with firmware version 1.5.3.0
The apply button on the network tab does not always work.
2011-07-18: Problem reported and identified.
Workaround:
There is no work around,
Solution:
Will be available with a SW upgrade.
3: Connection problems with firmware version 1.5.2.4
In some situation the SU refuses to reconnect after upgrading to this firmware version, only downgrade to previous version solves the problem.
Cause unknown.
Firmware version recalled.
2: RESOLVED: External antenna on SU5511-R4 can not be used when connecting to a legacy 11A Radio.
Reported:
2011-01-18 SW version 1.5.2.4
Status:
2011-04-18: New SW version 1.5.2.8 released with a fix for this problem.
2011-01-18: Problem has been identified, solution is under test.
Description:
The Radio in the SU locks to the internal antenna when connecting to a legacy 11A radio.
Result:
SU uses the integrated antenna and poor signal levels can be the result since the external antenna is not used..
Workaround:
There is no work around,
Solution:
Will be available with a SW upgrade.
1. SiteSurvey wile scanning causes the Scan to halt on R4 SUs.
Reported:
2011-01-02 This issue is only affecting R4 SUs.
Status:
2011-01-05: The cause of the problem is under investigation.
Description:
If the user performs an SiteSurvey on the web interface of the SU while the SU is scanning for the configured SSID the scan for that SSID will halt after the SiteSurvey is complete..
Result:
The SU might not connect to the configured SSID.
Workaround:
If a SiteSurvey is performed during the scan phase and the above problem appears press Apply button in webinterface. This will cause the SU to restart the scan for the configured SSID.
Solution:
Will be available with a SW upgrade.
SU100-Series
2. Measured roundtrip times is sometimes very high.
Reported:
2011-01-16 SW version 1.5.2.4
Status:
2011-01-18: Problem is under investigation.
Description:
There has been reports that the measured roundtrip times with ping is sometimes very high..
Result:
High latency is mainly affecting gaming experience and VoIP applications. The result can be poor speech quality on VoIP connections. Gaming experience can be affected.
Workaround:
There is no work around,
Solution:
No solution yet, problem still under investigation.
1. SiteSurvey wile scanning causes the Scan to halt.
Reported:
2011-01-02 This issue affects all SU100-Series SUs.
Status:
2011-01-05: The cause of the problem is under investigation.
Description:
If the user performs an SiteSurvey on the web interface of the SU while the SU is scanning for the configured SSID the scan for that SSID will halt after the SiteSurvey is complete..
Result:
The SU might not connect to the configured SSID.
Workaround:
If a SiteSurvey is performed during the scan phase and the above problem appears press Apply button in webinterface. This will cause the SU to restart the scan for the configured SSID.
Solution:
Will be available with a SW upgrade.
Trinity-Series
The 10MHz channel Bandwidth option is giving to much throughput, more than the indicated bitrate.
The 10 MHz option does not set the radio into 10MHz, the bandwidth becomes smaller than 20MHz but not half.
Wil be resolved with an FW upgrade.
