Hello,
I am using a Mikrotik Wireless Wire Cube 60G with a link distance of 652 m. The RSSI is consistently between -65 and -67 dB, with a deviation of 0.8° / 0.8°. After a reboot, the link reaches a PHY rate of 2500 Mbps. However, after rainfall, the PHY rate drops to 1250 Mbps and does not recover on its own.
Is there a parameter to trigger recalibration more frequently, or a recommended way to schedule an automatic reboot once per day?
Thank you in advance for your support.
No experience with that, but of course it is easy to schedule a "/system reboot" command at some time during the night when you wish to do so.
Given the ethernet port is Gb, what is actually the issue ?
Isn’t that the transmission rate of the 60 GHz link?
Why should the Ethernet interface first show 2.5 Gb and now 1.25 Gb?
Which ethernet interface are you talking about? CubeG-5ac60adpair has officially single 1Gbps RJ45 ethernet port. I've never seen such port to report speeds 1.25Gbps or 2.5Gbps.
Those PHY speeds most likely refer to radio interface speed ... and they should indeed be ideally as high as possible. Basing on experience with "usual" WiFi gear they might be lower than maximum if the traffic doesn't require them to get higher ... lower interface speeds mean more robust RF modulation and coding which in turn mean less errors on the link.
You might want to test throughputs via that wireless bridge ... first after things seem to be fine (PHY rate reported at 2.5Gbps) and then after link seems to be degraded. Does user throughput actually suffer? And if you push the link, does PHY rate change?
Well, these devices normally support 1Gbps full-duplex between the ethernet interfaces, but the radio link is only half-duplex. So to really support that you would need a radio link throughput that is well above 2Gbps (well above, because there is also other overhead on the radio link).
It could be difficult to test this, you would require a high-performance router at each end of the link, like a RB5009 or CCR2xxx, using the Tools->Bandwidth Test with direction "Both".
Running the test on the cubes itself is an indication but not sufficient to prove that the speed cannot be achieved, as the test itself may saturate the CPU on the cubes.
The parameter is located under the W60G interface, so it must refer to the wireless interface. Is there a command to restart/reinitialize just the 60G interface without having to reboot the whole system?
You could try disable/enable it. But of course be careful not to lock yourself out.
You can disable/enable the interface, but with the Cubes it has to be seen WHICH interface to cycle, as what is actually running is a bonding with the 60 GHz and the backup 5 Ghz interfaces as members, so it is very possible that you have to cycle the bonding interface or the 60 GHz (or both) and/or possibly also the 5 GHz one, in a given order.
You'll have to experiment to see which approach gives the expected result.
You should have a configuration loosely like this one:
/interface wireless
set [ find default-name=wlan1 ] band=5ghz-a/n/ac channel-width=\
20/40/80mhz-XXXX disabled=no frequency=auto installation=outdoor mode=\
bridge ssid=MikroTik-67ceee
/interface w60g
set [ find ] disabled=no mode=bridge name=wlan60-1 password=6a04-8480 ssid=\
MikroTik-67ceee
/interface w60g station
add comment=defconf mac-address=04:CE:14:F7:48:08 name=wlan60-station-1 \
parent=wlan60-1 remote-address=04:CE:14:F7:47:E7
/interface bonding
add comment=defconf mode=active-backup name=bond1 primary=wlan60-station-1 \
slaves=wlan60-station-1,wlan1
The actual commands would be something like:
/interface wireless
set [ find ] disabled=yes (no)
/interface w60g
set [ find ] disabled=yes (no)
/interface bonding
set [ find ] disabled=yes (no)
if you disable and then re-enable it, add a 10-15 seconds delay between the commands:
delay 15s
Thank you for the helpful advice, I will try that.
I would think the only thing you need to try is to disable/enable the 60g interface itself, as that is what keeps the wireless state. The bonding and wireless interfaces have nothing to do with that.
I would try to use this script:
/interface w60g
set disabled=yes [find]
:delay 5
set disabled=no [find]
Put that in a script, and run it to see if that helps. If so, put it in a schedule.