If cable is not an option

Wireless MESH Networks are often used, if network cabling, to an area where Wireless Coverage are wanted, is not an option (usely because it will be too expensive).

I have installed Cisco MESH Network in Harbors, Oil rigs, parks etc. Here are some writings from a project with 9800 and 1540 AP’s

1540 APs have been used, as the 9800 does not currently support Mesh/Bridge in 9100 APs

1540 AP will, unless otherwise ordered, be delivered in bridge mode. If the AP is to remain in bridge mode, “base ethernet MAC” must be added under “configuration->Security->AAA – AAA advanced-Device Authentication.
The AP is then configured for ROOT/MESH, name, tags etc.
Base ethernet MAC is on the AP, packaging and under sh ver
The above only works because it is configured in “default-mesh-profile” under Configuration->Wireless->Mesh

Here it points to an Authentication Profile ”Mesh_Authentication” and an Authorization Profile ”Mesh_Authz” created under Configuration->Security->AAA – AAA Method List

At the same time, “default-ap-profile” points to “default-mesh-profile”

For locations that use MESH APs, a MESH profile has been created:

If the AP is to be in local mode and you have console access, write: capwap ap mode local

To have FlexConnect for client on MESH AP’s (RAP/MAP) Which so far has their own sitetag with no FlexConnect.

• Make sure “normal” Site-tag with FlexConnect have configures Mesh-profile: