MESH network not working

[Support Wifi]

Hello to the Community,

I'm facing a problem trying to establish a wireless mesh between two APs. The BGN is identical between this two APs, backhaul is on the same radio (5GHz), and channel is identical (140).

The root AP receives update from its child but the Wireless bridge betweeb both does not work. Any advice is very welcome.

Thanks!

Theo

ps: attached to this discussion is the debug from the root AP. (Child is 0008.32f2.1aff as 2c5a.0fa0.d05c)

[Support Wifi]

The MESH bridge went up for a while, but went down few minutes later:

*Mar 28 13:57:18.003: ADJPKT:Using config BGN to respond to 0008.32f2.1aff
*Mar 28 13:57:18.003: ADJPKT:Tx ADJ rsp of type and version 34 to 0008.32f2.1aff on ant 0, channel 140
*Mar 28 13:57:18.003: ADJ:Processing child adjacency from 0008.32f2.1aff channel 140, hw Dot11Radio1
*Mar 28 13:57:18.003: ADJ_NEIGH:Completed processing child 0008.32f2.1aff channel 140 hw Dot11Radio1
*Mar 28 13:57:18.007: ADJPKT:Using config BGN to respond to 0008.32f2.1aff
*Mar 28 13:57:18.007: ADJPKT:Tx ADJ rsp of type and version 34 to 0008.32f2.1aff on ant 0, channel 140
*Mar 28 13:57:18.007: ADJ:Processing child adjacency from 0008.32f2.1aff channel 140, hw Dot11Radio1
*Mar 28 13:57:18.007: ADJ_NEIGH:Completed processing child 0008.32f2.1aff channel 140 hw Dot11Radio1
*Mar 28 13:57:20.103: adj_ischild_mac(1371):0008.32f2.1aff is a child
*Mar 28 13:57:20.103: mesh_security_send(1497):mesh_security_send sending on backhaul Dot11Radio1 , vhwidb Dot11Radio1

*Mar 28 13:57:21.003: ADJPKT:Using config BGN to respond to 0008.32f2.1aff
*Mar 28 13:57:21.003: ADJPKT:Tx ADJ rsp of type and version 34 to 0008.32f2.1aff on ant 0, channel 140
*Mar 28 13:57:21.003: ADJ:Processing child adjacency from 0008.32f2.1aff channel 140, hw Dot11Radio1
*Mar 28 13:57:21.003: ADJ_NEIGH:Completed processing child 0008.32f2.1aff channel 140 hw Dot11Radio1
*Mar 28 13:57:21.007: ADJPKT:Using config BGN to respond to 0008.32f2.1aff
*Mar 28 13:57:21.007: ADJPKT:Tx ADJ rsp of type and version 34 to 0008.32f2.1aff on ant 0, channel 140
*Mar 28 13:57:21.007: ADJ:Processing child adjacency from 0008.32f2.1aff channel 140, hw Dot11Radio1
*Mar 28 13:57:21.007: ADJ_NEIGH:Completed processing child 0008.32f2.1aff channel 140 hw Dot11Radio1
*Mar 28 13:57:24.003: ADJEVENT:Request to new parent 0000.0000.0000 from child 0008.32f2.1aff
*Mar 28 13:57:24.003: ADJEVENT:Clearing 0008.32f2.1aff CHILD status, hw Dot11Radio1
*Mar 28 13:57:24.003: %MESH-6-LINK_UPDOWN: Mesh station 0008.32f2.1aff link Down
*Mar 28 13:57:24.003: ADJPKT:Using config BGN to respond to 0008.32f2.1aff
*Mar 28 13:57:24.003: ADJPKT:Tx ADJ rsp of type and version 34 to 0008.32f2.1aff on ant 0, channel 140
*Mar 28 13:57:24.003: ADJ:Processing child adjacency from 0008.32f2.1aff channel 140, hw Dot11Radio1
*Mar 28 13:57:24.003: ADJ_NEIGH: Ignoring request, it's for another parent
*Mar 28 13:57:24.207: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor 0008.32f2.1aff VIDB Virtual-Dot11Radio0 going down

[Ric Beeching]

Have you added the non-root's MAC address under the mac filter so it will authorise the AP?

I can't remember which one you need so you can do it via GUI: Security -> Mac Filtering, click New and fill out two separate entries 00:08:32:f2:1a:ff and 2c:5a.0f:a0:d0:5c with Any WLAN and Management interface selected.

Or via CLI: 

config macfilter add 00:08:32:f2:1a:ff  0
config macfilter add 2c:5a.0f:a0:d0:5c 0

Let me know if that works..

Cheers,

Ric

[Ric Beeching]

Also I've had this occur and a full reboot of the child AP works for some reason.. guessing you've tried that already?

[Support Wifi]

Hi Ric,

Yes, the MAC was already added. So I try to remove it and add it another time but the behaviour is strange:

(Cisco Controller) >config macfilter add 2c:5a:0f:a0:d0:5c 0
MAC filter already exists - entry not created.

(Cisco Controller) >config macfilter delete 2c:5a:0f:a0:d0:5c

MAC Filter provided is unrecognized.

The MAC address is already known but no way to remove it...!

Yes i tried to reboot the child too with no effect.

[Scott Fella]

Look in the GUI.  You have two spots where you can add a MAC address. There is the macfilter list or under AP authorization.  From the output you show, the MAC address was entered under AP authorization. 

[Support Wifi]

Hi Scott,

Where do i need to put the MAC address? Under AP Auth or macfilter? Do you know also how to remove it from the AP Auth? I did not fond the command.

Thanks

[Support Wifi]

i just found how to remove, sorry!

[Scott Fella]

I have always used the AP authorization, but you can use either. Just stick to one so that you are not managing two lists.

When your testing this, are the AP’s already mounted? If not, make sure you have the antennas on and place them on opposite ends of the room. You don’t want to place them next to each other. If they are mounted, is there clear line of site between the RAP and MAP and what is the distance.

[Support Wifi]

yes the APs are already mounted, antenna alignement is OK, and the distance between them is approx 15 meters (1530E mounted outside). The fact is sometime the child AP connects successfully after a longgggggg time and from what i've seen the Mesh bridge is not stable at all.

[Support Wifi · Accepted solution]

The problem is solved. The antenna configuration was not correct (single vs dual). The Root AP has a directionnal antenna (dual mode) but the AP configuration on the Wlc was setup as single. One thing to remember when configuring Mesh and Antenna!

Have a nice day

Theophile