"Cannot edit this label Unknown"

[russellhltn]

Another problem I've noticed - some APs drop off the list. The system knows they're there, but can retrieve the status. The status line looks like this:

192.168.108.51 AP4c4e.35b3.e8cd Cannot edit this label Unknown 4c:4e:35:b3:e8:cd Not found

Looks like some more bugs they need to hammer out. I think it safe to say that if you attempted to deactivate the APs (for a conference) those APs wouldn't deactivate. At least not right away. When they do come back on-line, I'm not sure as they'd get the command or not.

[CleggGP]

I've noticed - some APs drop off the list.

Normally a wireless network controller (e.g., field-wlc-2.ldschurch.org) is listed next to each AP in TM. However, an AP may have a problem finding (or staying connected to) a controller. If an AP is not connected to a controller then the AP cannot be disabled/enabled (nor can the AP label be changed) through TM; instead TM displays an error.

In ... buildings that have ... the new Maraki firewalls, the usage statistics are blank. Is there a time frame when this will return?

There is a specific thing that TM developers need from Meraki before they can provide network "usage statistics," but there is not firm timeframe yet.

[russellhltn]

I've noticed - some APs drop off the list.

Normally a wireless network controller (e.g., field-wlc-2.ldschurch.org) is listed next to each AP in TM. However, an AP may have a problem finding (or staying connected to) a controller. If an AP is not connected to a controller then the AP cannot be disabled/enabled (nor can the AP label be changed) through TM; instead TM displays an error.

That provides more information, but doesn't tell me why. It doesn't seem to be the same APs each time.

[CleggGP]

That provides more information, but doesn't tell me why. It doesn't seem to be the same APs each time.

It's difficult to know exactly why. Local network issues such as network/ISP, latency, VPN, hardware, etc. may be factors, but usually the issue is temporary.

[lajackson]

. . . usually the issue is temporary.

There is not a fix, then? It just repairs itself? I am asking so I will know whether to pull wires for our next stake conference or just wait a few minutes and try again remotely.

[russellhltn]

That provides more information, but doesn't tell me why. It doesn't seem to be the same APs each time.

It's difficult to know exactly why. Local network issues such as network/ISP, latency, VPN, hardware, etc. may be factors, but usually the issue is temporary.

Yes, it's temporary. Unfortunately, so is the fix. It's not stable. This might have been present before the firewall switch out because I haven't look at the list in a long time, but it wasn't always this way. Back when the ability to apply labels to the APs came out, it was rock solid.

Edit: In fact, in the last few minutes, I did a refresh and the one that was out came back, but then another AP fritzed out.

[russellhltn]

Trying to do a trend analysis, I'm not seeing anything. I have a suspicion that the problem may be a reporting error - perhaps something like the process that gathers the information isn't waiting long enough for everyone to "report in".