Wireless bridge between two C9124AXE

[B A]

Hello all,

we recently received 2x Cisco C9124AXE and we need to use them for a point-to-point wireless bridge between two buildings as shown in the image. How can we configure them? They are brand new, I didn't convert them to any mode or EWC... I am just asking for the correct steps. I would be glad for any suggestions. C9124AXE firmware version: 17.6.2.43

We have only these two APs and don't have a C9800 controller so we plan to convert one C9124 to EWC. This is our idea:

1. Convert C9124_A to EWC
2. Join C9124_B to this C9124_A EWC
3. Configure mesh according to documentation
4. Switch C9124_B to Flex+Bridge mode
5. Switch C9124_A to Flex+Bridge mode. But this C9124_A is EWC at the same time. Will this work? Or do I need a third device - C9800 WLC or AP that will server as EWC?

Or do you have any other suggestions on how to make it work?

Thank you!

[pieterh]

5.>>> will this work <<<
yes it should, the EWC enables a virtual wireless controller running on the access point hardware
at the same time the access point runs on this hardware (each has it's own ip-adress)
for the design you can consider this as separate devices 

[B A]

Thank you for confirmation. I attempted to set it up and now I have C9124_A and C9124_B in Flex+Bridge mode but something is incorrect because it is not working. These APs do not communicate with each other. Can you give some tips on where to look at or how to configure it properly?

Here are screenshots of the config... https://www.mediafire.com/file/95pp8aqj2q4yj4q/screenshots.rar/file

Anyway, I didn't find a way to bind Mesh profile with the APs. I followed this Cisco manual but I am stuck at step 5. I don't see the AP tab on EWC (I believe this is because EWC doesn't have all features?) So is there any other way to make it work?

https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/215100-join-mesh-aps-to-catalyst-9800-wireless.html

[B A]

Any other suggestions?

[pieterh]

here  is the document/chapter for EWC using CLI
Cisco Embedded Wireless Controller on Catalyst Access Points Configuration Guide, IOS XE Amsterdam 17.3.x - Workgroup Bridges [Cisco Embedded Wireless Controller on Catalyst Access Points] - Cisco

check your settings match this note and the other prerequisites:
Central authentication is supported on Wave 1 and Wave 2 APs, whereas local switching is supported only on Wave 2 APs.

You need to connect the remote AP to your local LAN to associate to the controller
after configuration you can move it to the destination location.

[B A]

Central authentication is supported on Wave 1 and Wave 2 APs, whereas local switching is supported only on Wave 2 APs.
We have C9124AXE. I believe there is no issue with that.

You need to connect the remote AP to your local LAN to associate to the controller
after configuration you can move it to the destination location.
That's what we do. I have connected both APs on my desk and trying to figure it out.

How can we configure it or troubleshoot it?

[pieterh]

start by giving more information

you mention you did not convert them to EWC, bot at leas one should have the EWC image

is the switchport connected to the EWC AP configured as an access port ?
is the switchport of the second AP configured as an access port on the same vlan
is there a DHCP server on this vlan ?
do both AP's get a DHCP address ?
both AP should be able to locate the EWC using broadcast on this vlan , check by connecting a console cable and inspect the output

[B A]

To sum it up (and cover all your questions above), EWC is installed, both APs are connected to the EWC and both are configured in a Flex-Bridge mode, I configured EWC for mesh (please see my comments above + screenshots here: https://www.mediafire.com/file/95pp8aqj2q4yj4q/screenshots.rar/file), however, it is not working. The thing is that both APs didn't build AP bridge for some reason.

[pieterh]

connect a serial console to the remote access point and collect some output

[B A]

Do you have specific commands in mind?

This is what I get from the console:

[*06/02/2023 12:29:20.2558] AP is in fair condition, BLE is off
[*06/02/2023 12:29:20.2558] Set radio wifi0 power 6 antenna chain 2 3 23
[*06/02/2023 12:29:20.2558] Set radio wifi1 power 6 antenna chain 2 3 23
[*06/02/2023 12:29:20.2558] Set radio wifi2 power 6 antenna chain 2 3 22
[*06/02/2023 12:29:20.2559] set_sfp disable
[*06/02/2023 12:29:20.2559] set_gbe_phy enable
[*06/02/2023 12:29:20.2559] set_poe_out disable
[*06/02/2023 12:29:20.2559] set_fem_voltage 5V
[*06/02/2023 12:29:20.2559] set_sys_cond_state: condition fair state 2
[*06/02/2023 12:29:24.5774] CRIT-MeshControl: Starting Mesh with last known state:(0,0)
[*06/02/2023 12:29:25.6090] AP IPv4 Address updated from 0.0.0.0 to 192.168.1.252
[*06/02/2023 12:29:25.6199] send CAPWAP ctrl msg to the socket: Socket operation on non-socket
[*06/02/2023 12:29:44.7896] CRIT-MeshControl: Mesh restart in 5s for Could not seek last known uplink
[*06/02/2023 12:29:49.7897] CRIT-MeshControl: Stopping Mesh
[*06/02/2023 12:29:49.7917] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (mon0) is down
[*06/02/2023 12:29:49.7930] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (apbhr0) is down
[*06/02/2023 12:29:49.8067] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (apbhr0) is up
[*06/02/2023 12:29:49.8071] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (mon0) is up
[*06/02/2023 12:29:49.8214] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (mon1) is down
[*06/02/2023 12:29:49.8227] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (apbhr1) is down
[*06/02/2023 12:29:49.8392] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (apbhr1) is up
[*06/02/2023 12:29:49.8395] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (mon1) is up
[*06/02/2023 12:29:49.8682] CRIT-MeshControl: Starting Mesh
[*06/02/2023 12:29:49.8781] vendor_set_range: Radio 0 set range: 27000ft rx_ack_timeout: 106us pre_rx_ack_timeout: 93us result: PASS
[*06/02/2023 12:29:49.8877] vendor_set_range: Radio 1 set range: 27000ft rx_ack_timeout: 106us pre_rx_ack_timeout: 93us result: PASS
[*06/02/2023 12:29:49.8969] vendor_set_range: Radio 2 set range: 27000ft rx_ack_timeout: 106us pre_rx_ack_timeout: 93us result: PASS
[*06/02/2023 12:29:49.9919] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (mon1) is down
[*06/02/2023 12:29:49.9933] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (apbhr1) is down
[*06/02/2023 12:29:50.0733] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (apbhr1) is down
[*06/02/2023 12:29:50.0735] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (mon1) is down
[*06/02/2023 12:29:50.0860] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (apbhr1) is up
[*06/02/2023 12:29:50.0862] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (mon1) is up
[*06/02/2023 12:29:56.0038] DOT11_DRV[0]: Channel set to 2

[*06/02/2023 12:32:26.6375] CAPWAP State: Init
[*06/02/2023 12:32:26.6379] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (mon0) is down
[*06/02/2023 12:32:26.6395] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (apbhr0) is down
[*06/02/2023 12:32:26.6748] CAPWAP State: Discovery
[*06/02/2023 12:32:26.6848] Discovery Request sent to 192.168.1.203, discovery type STATIC_CONFIG(1)
[*06/02/2023 12:32:26.6867] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*06/02/2023 12:32:26.6942] CAPWAP State: Discovery
[*06/02/2023 12:32:26.6995] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*06/02/2023 12:32:26.7247] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (apbhr0) is up
[*06/02/2023 12:32:26.7301] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (mon0) is up
[*06/02/2023 12:32:26.7338] DOT11_DRV[1]: Channel set to 136
[*06/02/2023 12:32:26.7420] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (mon1) is down
[*06/02/2023 12:32:26.7437] wlan: [0:I:CMN_MLME] mlme_ext_vap_down: VAP (apbhr1) is down
[*06/02/2023 12:32:26.7694] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (apbhr1) is up
[*06/02/2023 12:32:26.7703] wlan: [0:I:CMN_MLME] mlme_ext_vap_up: VAP (mon1) is up
[*06/02/2023 12:32:27.4254] Start: RPC thread 2115416976 created.
[*06/02/2023 12:32:28.6689] DOT11_DRV[0]: Channel set to 12

[B A]

Does this output tell anything?

[pieterh]

from this part of the log, it looks like the access point cannot find the EWC
not by broadcast 255.255.255.255, and not the primed controller 192.168.1.203
it remains in "discovery" state and does not send join request

[*06/02/2023 12:32:26.6848] Discovery Request sent to 192.168.1.203, discovery type STATIC_CONFIG(1)
[*06/02/2023 12:32:26.6867] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*06/02/2023 12:32:26.6942] CAPWAP State: Discovery
[*06/02/2023 12:32:26.6995] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).

can you confirm 192.168.1.203 should be the EWC ?
or does the EWC is configured for DHCP and has retrieved another address?

[B A]

Yes, 192.168.1.203 is the IP address of EWC.

[B A]

The problem is that when I disconnect C9124_B from the ethernet, I cannot reach the AP over the bridge. These APs do not see each other as mesh neighbors. 

[pieterh]

i see AP_Bridge_01 is using channels 100,104
but the log of the AP_Bridge_02 shows: 
     *06/02/2023 12:29:56.0038] DOT11_DRV[0]: Channel set to 2
     [*06/02/2023 12:32:28.6689] DOT11_DRV[0]: Channel set to 12
for 2.4 GHz band. and 
     [*06/02/2023 12:32:26.7338] DOT11_DRV[1]: Channel set to 136
for 5GHz band

=> configure matching channels