Reading this:
https://help.mikrotik.com/docs/display/ROS/Fail-over+PtP+CLIexample
It suggests to add primary=wlan60-station-1 slaves=wlan60-station-1,wlan1 to a bond interface.
What should I do when there is more than one station [ie, PtMP]? Surely can’t have wlan60-station1 as primary in the bond if wlan60-station2 is going to be in there as well, right?
No, bonding is only appropriate for PtP links. Either RSTP for L2 bridged or OSPF for L3 routed connections, examples of PtMP failover in the documentation would be most helpful.
We tried some configurations with WDS on AP to have “physical” interfaces on 5Ghz available for backup to bonding. Also some routing and other types, but the best and easiest solution is to NOT have bonding on AP. You just make bonding only on other, client side and thats it. On AP you just put 60Ghz station interfaces in same bridge as 5Ghz interface. This wont make loopback with client side, thanks to active backup in that bonding. We are using this style of client backup for 4 months without any problems.
Thanks Gu457v, that’s basically where I got to, pretty much because I couldn’t work out what to do next. Sounds like it’s going to be fine. Seemed OK on the test bench, although we know test bench != the real world.
This helped me so much just now. I was under the impression the AP side needed to be bonded as well.
To get around this issue in the past, I had to put things on layer 3 and use OSPF.
Yeah, about that…now it’s installed my CubeSA 60Pro ac has rebooted 7 times so far today, max uptime is 33 minutes. It seems like weak stations will cause repeated reboots. Going to try 7.10rc!
How is this working out , I am trying to accomplish the same thing, and just like this.. I got it to work in the office.. 60ghz with 5ghz failover with just the stations in bonded interface.. Did it not survive out in the wild . ?
Ended up switching off the 60G radio. Simply couldn’t find a firmware version that was stable.
nooooooo… lol damn im really trying to get this 60 with 5ghz failover to work.. so what happened.. they would just reboot over and over throughout the day.. ?
Did you try RouterOS v7.11 or higher? According to the changelog there were some changes in v7.11 to improve system stability for these devices:
What's new in 7.11 (2023-Aug-15 09:33):
*) w60g - improved stability for Cube 60Pro ac and CubeSA 60Pro ac devices;
I use these in PTMP deployments as well, with OmniTik 5AC’s as the 5GHz AP and its POE out powering a couple of wAP60’s at half of my MikroTik-based sites. The rest are 60GHz-only to wAP60’s.
The bond on the CPE side is active/passive, with the 60GHz as primary, and all of the AP’s (5GHz + 60GHz) in the same Layer 2 VLAN. (For a 60GHz-only AP, I disable the 5GHz radio.) It works very well, and I’ve had no complaints.
The majority of my CPE are the old Cube 60G’s (CubeG5ac60ad), but I have some the newer Cube 60 Pro’s as well. All of them work fine on 60GHz, with 6.49 or 7.12.
Of course it works, the air is so pure in UTAH 
I really appreciate your insight.. I hate to push you to another post, but I posted the config that worked for me on the bench.. but I have yet to try it out in the wild yet.. but have a few events coming up and im planning on using the same solution for multiple locations.. id love to know if im barking up the right tree..
Thank you so much..
http://forum.mikrotik.com/t/60ghz-ptmp-with-5gz-failover-sanity-check/172868/1
Yeah, it didn’t make any difference. Mikrotik support couldn’t replicate and suggested changing it from bridged to routed instead but I simply can’t justify the time/expense of reconfiguring the network to test this 
I’m not the only one with this problem either:
http://forum.mikrotik.com/t/cubesa-60pro-ac-60ghz-clients-flapping/160291/1
I guess I got lucky first try, I set up the cube 60s as station bridge for the 60gz and made sure they were in the bridge with the ethernet in winbox, firmware was updated to 7.14.xx. I then set up the 60Ghz on the as ap bridge on the sa cube. I also set up the wifi 5ghz also except I think I had to manually add it to the bridge. I set it up just like the ptp example on youtube (https://www.youtube.com/watch?v=CCbVzl6WtF0), except only one would work at a time, then I changed the bridge to ap-bridge on the cube sa 60ghz interface and the 5ghz…then they both worked and were stable.
However, though both connected simultaneously but it tended to favor the 5gz wifi link. I then manually set the path cost in the bridge to 5 on the 60G and left the path cost of the 5ghz to 10. 60Ghz links became preferred and stayed stable. I disabled the 60Ghz on cube sa and the 5ghz took over, reenabled and 60ghz took it back. I then held a 2x10 board in front of the 60sa and the 5ghz took over again until I removed the board and the 60ghz took back over. I called it good and went home…checked the next day and the 60ghz links were still up and stable. No complaints from the customers 30 or so users that were then using it. The further client station is 600 feet, the closer one is 300 feet. I tested the links for about an hour two different days from my laptop in my truck and when it was sunny client to sa speed tests show about 1.9Gbit/sec for udp transfer and I think 1.5 on tcp, during moderate rain it was 1.2Gbit/sec on udp and 980Mbit/sec on tcp speed test (client to ap). I had these attached ethernet side to some Grandstream GWN7664LR outdoor aps at the two cube 60 stations and a third one at the main incoming fiber where they cube 60 sa was. The users are some happy campers…literally…it is wifi access for a new camper park and I got a complement from a camper on the farthest ap saying it was the best wifi in a camper park they had ever used so I am guessing it’s all good.
I am happy to report that since the AP was updated to 7.20.4, I have enabled the 60G interface on the AP and it has stayed up for more than three days so far without a reboot.
For the sake of completeness:
Stations are 2x Cube 60G ac running 6.49.19. Reported distances are 60m and 220m.