Wireless Access

AOS 8.6.0.5

10 MCs in cluster

MM and standy MM

 

Hello,

 

We realised this morning that our cluster has been running in L3-Connected state. We're not sure for how long, but it could have been at least a week. It is fixed now (though I cannot explain how it ended up in L3 in the first place).

 

My question is what kinds of issues would end users experience with the cluster in this state? We have the usual start of term noise with people having problems, but would like to get a feel for which kinds of problems we can put down as probably being caused by the cluster issue.

 

Thank you,

 

Guy

This typically happens when a VLAN or VLANs is not properly defined on the controller(s) or the VLAN is not properly defined on the uplink switch

All cluster members will probe each VLAN for connectivity. If they do not see each other on every VLAN, except those configured here, they will only form a L3 cluster

You can run the “ show lc-cluster vlan-probe status”



Thank you

Victor Fabian

Pardon typos sent from Mobile

Thanks Victor,

 

Actually we've already fixed the issue. My query was more about what kinds of issues it would have caused clients while in the L3 state. We have had a fair number of reports of poor wireless experience recently (though this isn't unusual at the start of term!) but what we wanted was to know what kinds of problems clients might have experienced as a result of the L3-Connected cluster issues (which have probably been going on for at least a week)?

 

Thanks for your help with this,

 

Guy

In an L3 state your cluster will not be capable of doing hitless failover



Thank you

Victor Fabian

Pardon typos sent from Mobile

Ah ok, so is this the only side-effect? ie clients shouldn't be affected in normal usage (outside of a failover)?