User's Guide

Table Of Contents

assigned to the device group, but this setting can be overridden from the AP Override settings for each

AP. Dierentiate the AP Root behavior setting one of two ways:

• (Best Practice) Conﬁgure two device groups: One device group for the root AP, one device group

for the non-root APs. Conﬁgure separate Proﬁles with the appropriate Root behavior setting for

each device group. For ease of conﬁguration, you can copy conﬁguration Proﬁles and make the

necessary Root behavior changes.

• Conﬁgure one device group: From the conﬁguration Proﬁle, conﬁgure the Root behavior as non-

root. Non-root is the correct conﬁguration for all APs in the device group except for the one root AP.

Then, override the Root behavior setting on that one root AP, conﬁguring the designated AP as the

root.

Before you conﬁgure Mesh Point conﬁguration Proﬁle settings, verify Advanced conﬁguration Proﬁle

settings or individual AP Override settings:

• A single mesh point is supported on multiple radios for a single AP. You can use dierent channels

for each hop of a multiple hop mesh network. This can improve air time utilization and possibly

increase throughput. However, multiple hops do not improve latency, so a best practice is to keep

the number of hops less than two.

• The AP4000 6 GHz radio is supported in a mesh network.

• Radio settings for the root-AP and non-root APs must match.

• When you add or remove a mesh point from a radio, the AP will reboot.

• Dual-band support is available with Mesh Point. When one radio is conﬁgured for Mesh Point, both

radios can provide service.

• The recommended Poll Timeout setting for non-root APs is 60 seconds.

Note

Conﬁguration parameters you set from the conﬁguration Proﬁle apply to all APs in a device

group. To override settings for speciﬁc AP, go to the AP radio properties. For more

information, see Advanced Setting Overrides on page 196.

Note

When a single interface AP is conﬁgured as a Mesh non-root AP, the single interface is used as

a client port, not as an uplink. When a single interface AP is conﬁgured as a Mesh root, the

single interface is used as an uplink, not as a client port.