We have come to learn about an issue in 3.0 which could be quite severe, depending on your deployment. Release 3.0 software incorrectly caps the SM and PTP mode EIRPs to the APs EIRP in FCC regions. The FCC requires the AP's EIRP to be capped to lower values (ex: 36 for the 5.8 band) while the SMs and PTP radios are allowed much higher EIRPs. Due to this EIRP cap, SMs with high gain antennas (ex: Force 200) will not be able to turn up thier TX powers beyond 11 dBm (25dBi antenna gain + 11 dBm Tx power = 36 EIRP). Therefore SMs that are at longer distances or in a tough link may see thier performance degrade significantly when running Release 3.0.
This issue has been fixed in 3.0.1 which is a maintenance release. We expect a 3.0.1 beta release early next week.
We apologize for the trouble caused due to this defect.
I'm still seeing an issue when setting the EIRP limit on 3.0.1-RC9 in the web GUI that I believe was supposed to fixed. We have two PTP links that have the TX power set to 20dbm in the 5.2 band with antenna gain of 25 ( 45 EIRP). Moving from 3.0 to 3.0.1-rc9 resolved the issue for one link with AP hardware of "5 GHz Connectorized Radio with Sync (Lite)", but the other link we have is a "5 GHz Connectorized Radio with Sync" (non-Lite version), and although it is being used for PTP, the web GUI still doesn't allow the TX power to be set above 11 without showing an error. Because the value was previously set before the upgrade however, TX output power is showing 20, but there's a red exclamation point on the radio configuration tab. Wondering if maybe the Web GUI needs to fixed for the non-lite connectorized radio with sync?
I'm in the US, using 5190. I looked at the same radio this morning however, and i'm not seeing the issue any more. I think it might've just had something to do with the browser cache, as it's no longer showing the red exclamation point. Oddly enough, it now shows "Version 3.0.1-RC9" along the bottom page footer, while immediately after the update it still showed 2.6.2 for a while. .... more reasons I suspsect it was a browser cacheing issue. (Using firefox on mac os).