Hi there,
I will try to sum-up a very nice network in a few words : we have 11 x AP6562 in a mesh network, running 5.5, controlled by one of them as a virtual-controler.
We did a meshconnex configuration, that is working fine on 5ghz radios (smartrf), through a wide outside area. The 2.4ghz radios are used for clients (mobile clients on vehicules mostly, third-party as hirschmann or such)
Here are my concerns, for which I got a few answers from level 2 support, but that do not satisfy me 100%, and would love some feedback from fellow moto users who could have been using such solutions :
- we want to make sure not to have any network disruption, especially in case of a meshpoint failure, or a radar detection. The problem is that with the automatic channel selection, we saw that half of APs connect to "mesh-root 1" (let's call it like that) on, let's say channel 140, and the other ones, who are more likely to be close to "mesh-root 2" all communicate through channel 100. When a radar is detected, even though we chosed the channel list according to the shortest CAC (1 minute) applicable in europe, all APs connected to "mesh-root 1" for example, would lose network if mesh-root 1 is out (radar detection, failure, etc.). they all start a new radar scan before connecting to the other neighbours on channel 140. Anyone knows how to prevent that ? any configuration I would have missed that allow us to say "ok, please make sure what channels do your neighbours use and please be ready in any case to connect to them without making a new DFS scan" ?
- does anyone have a fine-tuned example for such config, especially for optimizing available bandwidth for each root mesh, in our case mesh-root 2 is connected through a wireless backhaul (not motorola) that is only 300 meg, not 1 gig as the AP6562 might think.
Thanks for your help, below is a few relevant extracts from my conf :
meshpoint MESH
description meshconnex policy
meshid MESH
beacon-format mesh-point
control-vlan 4000
allowed-vlans 1
neighbor inactivity-timeout 60
security-mode psk
wpa2 psk 0 hellomoto
no root
!
smart-rf-policy default
assignable-power 5GHz min 10
assignable-power 2.4GHz min 8
channel-list 5GHz 100,104,108,112,116,136,140
!
profile ap6562 root-ap6562
ip default-gateway H.E.L.O
no autoinstall configuration
no autoinstall firmware
crypto ikev1 policy ikev1-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ikev2 policy ikev2-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ipsec transform-set default esp-aes-256 esp-sha-hmac
crypto ikev1 remote-vpn
crypto ikev2 remote-vpn
crypto auto-ipsec-secure
crypto load-management
crypto remote-vpn-client
interface radio1
placement outdoor
wlan CLIENTSIDE bss 1 primary
aggregation ampdu none
no dynamic-chain-selection
interface radio2
data-rates an
rate-selection opportunistic
placement outdoor
meshpoint apmesh bss 1
antenna-gain 2.0
aggregation ampdu none
no dynamic-chain-selection
interface ge1
ip dhcp trust
qos trust dscp
qos trust 802.1p
interface vlan1
ip address zeroconf secondary
interface pppoe1
use firewall-policy default
ntp server NTP
rf-domain-manager capable
service pm sys-restart
router ospf
meshpoint-device MESH
root
monitor primary-port-link action no-root
acs channel-width 5GHz 40MHz
!
rf-domain default
timezone Europe/Paris
country-code fr
use smart-rf-policy default
!
ap6562 ROOT1
use profile root-ap6562
use rf-domain default
hostname ROOT1
device-upgrade auto
interface radio1
channel 1
placement outdoor
antenna-gain 3.0
interface radio2
placement outdoor
interface vlan1
ip address ROOT1-IP/24
use auto-provisioning-policy meshpoint
virtual-controller
rf-domain-manager capable
logging on
logging console warnings
logging buffered debugging
configuration-persistence
!
ap6562 meshpoint-sample
use profile root-ap6562
use rf-domain default
hostname meshpoint-sample
interface radio1
channel 11
placement outdoor
interface radio2
placement outdoor
interface vlan1
ip address meshpoint-sample-ip/24
!
ap6562 sample-bridge
use profile root-ap6562
use rf-domain default
hostname sample-bridge
interface radio1
channel 6
placement outdoor
interface radio2
placement outdoor
interface vlan1
ip address sample-bridge-ip/24
meshpoint-device apmesh
no root
no monitor primary-port-link action no-root
!! we say that we don't want to turn route, even though ge1 is up, which means that the switch behind ge1 gets vlan1 data
Thanks a lot guys, if anyone could help, that's fantastic !
Romain