topic Re: Wireless bridge between two C9124AXE in Wireless

Wireless bridge between two C9124AXE

B A — Fri, 02 Jun 2023 07:41:17 GMT

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!

Re: Wireless bridge between two C9124AXE

pieterh — Fri, 02 Jun 2023 13:57:31 GMT

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

Re: Wireless bridge between two C9124AXE

B A — Mon, 05 Jun 2023 06:04:11 GMT

Any other suggestions?

Re: Wireless bridge between two C9124AXE

B A — Mon, 05 Jun 2023 06:02:56 GMT

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

Re: Wireless bridge between two C9124AXE

pieterh — Mon, 05 Jun 2023 07:23:31 GMT

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.

Re: Wireless bridge between two C9124AXE

B A — Mon, 05 Jun 2023 11:21:57 GMT

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?

Re: Wireless bridge between two C9124AXE

pieterh — Mon, 05 Jun 2023 11:49:35 GMT

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

Re: Wireless bridge between two C9124AXE

B A — Mon, 05 Jun 2023 12:07:14 GMT

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.

Re: Wireless bridge between two C9124AXE

pieterh — Mon, 05 Jun 2023 12:52:20 GMT

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

Re: Wireless bridge between two C9124AXE

B A — Mon, 05 Jun 2023 13:14:26 GMT

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

Re: Wireless bridge between two C9124AXE

B A — Tue, 13 Jun 2023 10:12:26 GMT

Does this output tell anything?

Re: Wireless bridge between two C9124AXE

pieterh — Tue, 13 Jun 2023 11:17:01 GMT

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?

Re: Wireless bridge between two C9124AXE

B A — Wed, 14 Jun 2023 08:22:31 GMT

Yes, 192.168.1.203 is the IP address of EWC.

Re: Wireless bridge between two C9124AXE

B A — Wed, 14 Jun 2023 08:22:07 GMT

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.

Re: Wireless bridge between two C9124AXE

pieterh — Wed, 14 Jun 2023 10:55:45 GMT

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

Re: Wireless bridge between two C9124AXE

B A — Mon, 19 Jun 2023 05:17:39 GMT

...

Re: Wireless bridge between two C9124AXE

B A — Mon, 19 Jun 2023 05:17:19 GMT

Thank you! Where can I configure it?

Re: Wireless bridge between two C9124AXE

S. K. — Tue, 17 Oct 2023 14:26:46 GMT

Hi B A,

Could you solve the issue? I'm right now at the same point with my 2 x 9124. In Version 17.6.6 it was not possible to change the AP mode, then I did the upgrade to 17.9.4 which solved the issue.

Which documentation did you use for the mesh config on the EWC?

Greetings

Re: Wireless bridge between two C9124AXE

cmcclinton — Mon, 20 Nov 2023 23:03:20 GMT

Hi BA and SK

Did you get your 9124s works as Mesh Bridge?
I have also tried to set this up and had quite a few frustrating problems, but I did get it working in the end.

Definitely had the problem of not being able to select set the mode to Flex+Bridge as mentioned above in version 17.9.4 this works as expected.

My other tips would be to only work on the base eWLC 9124 and get that working as a RAP first before plugging in the MAP as there are a number of reboots required and with both 9124 connected to the same switch the intended MAP was being converted to an eWLC and becoming the controller when the RAP and eWLC where rebooting.

So start with just the one 9124 use the wizard to get initial WLC up and running, add the MAC addresses and AAA authentication and authorization and Mesh profile up as per the guides. (or if this is purely a two AP bridge just use the default profiles and edit the default AP join profile to support Mesh).

Once the eWLC has rebooted confirm that the RAP mesh config has taken the mode and role etc.
Look under Monitoring/Mesh and it should confirm 1 RAP and 1 sector is up and running.
The fact that eWLC is running on the RAP and mode chnages require a reboot does mean that the config can look OK but things arent running yet until the host AP reboots.

Next plug the intended MAP into the same switch as the RAP so it can register as a normal AP and begin the conversion by changing the mode to Flex+Bridge and setting the role as Mesh. If you save the config at this point the AP should reboot to take on the mode change. Good idea to have a console cable connected so you can see where it is in the process.

Keep it connected to the same network as the RAP and let it register again.
Then again under the AP Mesh tab configure the mode to trunk, set the native VLAN to the VLAN back on the RAP side of the network that you want to manage the AP from. Then configured the allowed VLANs that you want to pass from the MAP side switch to the RAP side switch.

Save the config again and you should be ready to move the MAP AP to the remote switch.
Let it boot and it under Monitoring/Mesh you should see it as a child of the RAP and have 1 RAP and 1 MAP.

Re: Wireless bridge between two C9124AXE

S. K. — Tue, 21 Nov 2023 08:03:08 GMT

Hi CMC....

Thanks a lot for your explanation.

I got it only working in version 17.9.4 with the most deafault config --> default AP join profile to support Mesh

I took the config if someone needs a proper default config.

S.K.