We have a PTP link with 2 LHG 60G radios. Everything worked fine on v7 for about a year until around 2 months ago. The far side would stop responding to pings, Romon and the link would stop forwarding DHCP traffic. All other traffic would work normally. Toggling client isolation on or off on the AP would fix the issue temporarily, sometimes for a couple days, sometimes for 5 minutes. We updated the radios to v7.14.2 and did not see any improvement. We created a ticket SUP-155542 and was notified that we need to downgrade to v6 before they could troubleshoot. Is there issues with v7 on the 60G radios?
AP
/interface bridge
add admin-mac=XX:XX:XX:XX:XX:33 auto-mac=no name=bridge port-cost-mode=short protocol-mode=none
/interface w60g
set [ find ] disabled=no mode=bridge name=wlan60-1 put-stations-in-bridge=bridge region=usa ssid=60G
/interface w60g station
add mac-address=XX:XX:XX:XX:XX:34 name=wlan60-station-2 parent=wlan60-1 remote-address=XX:XX:XX:XX:XX:39
/interface bridge port
add bridge=bridge ingress-filtering=no interface=ether1 internal-path-cost=10 path-cost=10
/ip address
add address=X.X.X.4/22 interface=bridge network=X.X.X.0
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=X.X.X.1
/tool romon
set enabled=yes
CPE
/interface bridge
add admin-mac=XX:XX:XX:XX:XX:38 auto-mac=no name=bridge port-cost-mode=short protocol-mode=none
/interface w60g
set [ find ] disabled=no isolate-stations=no mode=station-bridge name=wlan60-1 put-stations-in-bridge=bridge region=usa ssid=60G
/interface w60g station
add mac-address=XX:XX:XX:XX:XX:39 name=wlan60-station-1 parent=wlan60-1 remote-address=XX:XX:XX:XX:XX:34
/interface bridge port
add bridge=bridge ingress-filtering=no interface=ether1 internal-path-cost=10 path-cost=10
add bridge=bridge interface=wlan60-1
/ip address
add address=X.X.X.5/22 interface=bridge network=X.X.X.0
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=X.X.X.1
/tool romon
set enabled=yes
We have a PTP link with 2 LHG 60G radios. Everything worked fine on v7 for about a year until around 2 months ago. The far side would stop responding to pings, Romon and the link would stop forwarding DHCP traffic. All other traffic would work normally. Toggling client isolation on or off on the AP would fix the issue temporarily, sometimes for a couple days, sometimes for 5 minutes. We updated the radios to v7.14.2 and did not see any improvement. We created a ticket SUP-155542 and was notified that we need to downgrade to v6 before they could troubleshoot. Is there issues with v7 on the 60G radios?
Hi
Try removing put-stations-in-bridge=bridge on AP and CPE and manually adding interfaces to the bridge
P.S I’m using Cube 60Pro + Ros 7.15.1
Same, took about 2 min to drop out.
My conf
Master
# 2024-06-20 14:34:21 by RouterOS 7.15.1
#
# model = CubeG-5ac60ay
/interface bridge
add admin-mac=XX:XX:XX:XX:XX:39 auto-mac=no name=bridge port-cost-mode=short
/interface w60g
set [ find ] disabled=no frequency=62640 isolate-stations=no mode=bridge \
password="TesT" name=wlan60-1 ssid=60GHz
/interface w60g station
add mac-address=XX:XX:XX:XX:XX:B5 name=wlan60-station-1 parent=wlan60-1 \
remote-address=XX:XX:XX:XX:XX:CF
/interface bridge port
add bridge=bridge interface=ether1 internal-path-cost=10 path-cost=10
add bridge=bridge interface=wlan60-station-1 internal-path-cost=10 path-cost=10
Slave
# 2024-06-20 14:35:04 by RouterOS 7.15.1
#
# model = CubeG-5ac60ay
/interface bridge
add admin-mac=XX:XX:XX:XX:XX:03 auto-mac=no name=bridge port-cost-mode=short
/interface w60g
set [ find ] disabled=no mode=station-bridge name=wlan60-1 password=\
"TesT" scan-list=62640 ssid=60GHz
/interface bridge port
add bridge=bridge interface=ether1 internal-path-cost=10 path-cost=10
add bridge=bridge interface=wlan60-1 internal-path-cost=10 path-cost=10
P.S Some version of ROS had a problem with port-cost
The new config is pretty much identical to yours now with the exception of the port costs. It’s weird that we have several (over 30) other 60GHz links that have no issues, just this one. I think we are going to swap this one out with another set to rule out a possible hardware failure and run a netinstall on this set. Thanks for the help, fully appreciated.
The new config is pretty much identical to yours now with the exception of the port costs. It’s weird that we have several (over 30) other 60GHz links that have no issues, just this one. I think we are going to swap this one out with another set to rule out a possible hardware failure and run a netinstall on this set. Thanks for the help, fully appreciated.
The LHG may need to be adjusted (Alignment)
http://forum.mikrotik.com/t/ptp-bridge-alignment-60-ghz-cubeg-5ac60ay/169604/1