Omada has come a long way since we first started using it in our organization. It's almost to the point that it could replace our Aruba equipment in a lot of situations. One of the major issues for us is the limitation on the amount of VLAN interfaces allowed to be configured in the GUI (16). Note that I am not talking about VLANs themselves; you can have up to the maximum 4096 like normal. Instead, I'm talking about routable-interfaces assigned to VLANs (think default gateway for each VLAN).

I am evaluating an SG6428X for sites that are connected with layer 2 using a MAN. It's a great unit, but the problem is that we have about <30 standard VLANs we use for device segmentation. The SG6428X hardware itself supports 256 VLAN interfaces, and I have gotten all the VLAN interfaces I needed working when it's in standalone mode; however, when I adopt it into the Omada controller the 17th VLAN always has the error "The number of VLAN Interface entries has reached the limit." I confirmed with sales representatives at TP-Link that this is a limitation of the controller: "As of right now there is a limitation of 16 via the controller. Currently the best practice recommended with TP-Link at this time is to run a core L3 switch in standalone mode allowing you to have more IP interfaces."

I'm not sure what the technical reason for this limitation is. The only thing I can think of is that the hardware controller has limited resources which somehow effects how many VLAN interfaces can be propagated from it. If that is the case, TP-Link should come out with a more powerful hardware controller or, at the very least, remove this limitation for software controllers.

Please remove this limitation, TP-Link!