nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Additional unleashed mesh AP shows as "Configure.Me" after powered up, Why?

unknown

I now have 5 working T300 Unleashed APs.
2 wired (master\reserve) and 3 mesh.
Today I added a 6th AP.

Dashboard AP settings are "join automatically when discovered"

The 6th AP still shows as "Configure.Me" SSID 45 minutes after powering up.

The same thing happened with the 5th AP but suddenly one day, after powering up\down\trying wire it suddenly started working.

This would not be an issue trying on this AP if it werent for it being mounted on top of a flagpole and therefor is hard to access physically.

I can access the main wifi with 2 bars from AP 6' location so it should be able to connect to it.

When adding new mesh AP, do I need to connect it with wire first before I "mesh" it ?
Because I have not done that in this case.

Can I still hope for it to come online\join the mesh or should I just start taking it down again to do a factory reset?

Thanks for any tips\help

Find more posts tagged with

Accepted answers

All comments

unknown

You need to connect the access point via Ethernet to the network first for it to provision before disconnecting and moving the AP to a different physical location in order for it to form mesh.

unknown

Thanks.
Was hoping I wouldnt have to but ive arranged to take it down and try.

unknown

It just happened to me with a T300.

It was first connected, provisionned then unplugged and moved, mounted to a distant hard to access place.

And now just showing "configure.me" SSID.

Is there a special procedure to ensure the provisionning is saved somehow?

unknown

You do need to "test" it after provisioning it via ethernet. I suggest that to plug it in, get it joined. Update all the firmware, wait 10 minutes after a reboot and then disconnect the ethernet and plug in the WAP with a power supply and then check the dashboard to see if the WAP is working via mesh. THEN move it to the final location.

unknown

I did exactly that. Except the reboot. This one happened while moving away from the switch to the wall !

It got configured and was working in mesh (AIR led on). Only powered (POE but without any LAN connected) with a POE adapter.

That's why I suppose there is a "save the settings" somewhere in the console which was not checked... 😞

unknown

I've never done mesh with a PoE injector.... I wonder if the WAP is confused and doesn't switch to mesh. I've always done local power adaptor. That's a good test for me to try. Do you have a power adaptor?