AP 125 Unreachable out of nowhere

KimNeumannKimNeumann
edited March 28 in WiFi - Firebox Managed

we are using AP 125 for our wifi and for some time our APs are unreachable. they got the 11.0.0.36-4 firmware around november last year and after that we changed our M440 for a M590. for a few months everything was fine, but out of nowhere all of them are unreachable. there was no new firmware for the APs and no new firmware for the M590. if i reset one AP it can connect to the M590 just fine and will be Not Trusted. after marking it as trusted, it starts authentication and then its online for a few seconds, until it starts to Update Configuration. after that its unreachable again.
any1 got an idea what could cause this? i tried to disable Auto-Deploy so there is no configuration to update, but that step still happens and the AP goes back to unreachable

the APs themselve work fine, they are still broadcasting all SSIDs they should and everyone can work just fine. but we need to add new devices to the MAC Filter List which wont get pushed to the APs, as they are unreachable for the firebox

Comments

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @KimNeumann

    I'm not sure what might be happening there. If you haven't already done so I'd suggest opening a support case. You can do this via the support center link at the top right of the page.

    -James Carson
    WatchGuard Customer Support

  • IThelpdesk123IThelpdesk123

    Hi, have you any feedback.
    I have same issues.

  • VelosoVeloso

    Same her - 3 AP 320 with M270 12.11.2 - stays with status discovered.

  • KimNeumannKimNeumann

    i dont know if this is helpful, but i found a solution for my problem.

    somehow we activated "communication VLAN tagging" for the access points, sending them into a VLAN that was not known to the Switches or the Firebox. Next Problem, default VLAN is 4094, which is an internal VLAN for our switches, which means we cant use that.
    we had a free port on the firebox and set is a VLAN 4094 and directly put an access point on that port. now the firebox can communicate with the access point. we then removed the VLAN tagging from the access point and for this 1 access point, everything is fine again.
    putting it back on the wall behind the switches again, the access point was stuck on "Discovered". as long as my VLAN port exists, the access point is stuck on "Discovered". after disabling that port, the access point is now back online.

    i dont really now how we set that option and the default VLAN id is like one of the worst ids to use, many switches cant use that id, because its internal or stops way before that (ubiquiti only allowes up to vlan 4018, dell uses 4094 internaly), but shit happens. the solution to get them back is pretty bad with lots of running around, there should be a way to remove the VLAN tag for communication without all this, as the access points still have a connection to the firebox and work just fine, they just didnt accept any new configurations.

  • IThelpdesk123IThelpdesk123
    edited April 4

    Same her - AP 125 with M390 12.11.2 - stays with status discovered.
    And AP 120 same problem 12.11.1 status- unreachable

  • Bruce_BriggsBruce_Briggs

    There seem to be 2 classes of comments here:
    . AP120 & AP125 - Wifi 5 units, which can be managed by GWC or the older cloud managed wifi method.
    . AP320 - a wifi 6 model, only managed by the new wifi cloud method

    My AP330 (wifi 6 cloud managed) connected to a T20 running V12.11.2 is showing the correct status, showing usage graphs & connected clients as expected.

    A support incident is the best way to go here.

    Should anyone find a resolution, please post it for others to find.

Sign In to comment.