What's the point of the restriction though. Restrictions should come in the form of features, layer 3 etc, like all other vendors. This 22 network and 50 device limit seems pointless, a device limit I could understand on a free cloud platform, but the network limit makes no sense. The fact is, what I need these high-end switches to do can be done by the lesser competitors (even TP Links cloud switches...). The switches do in fact do everything I need when managed locally. I'm just trying to raise my voice and hope Aruba/HP hears.
I was sold the Aruba solution by a major vendor, it was a competing bit against a Meraki solution, I worked with Aruba engineers on it, waited nearly a year to get my 1960 switches. My deployment is at a sporting venue, 17 48port PoE switches, 30 VLANs. If I knew about the limitation, I would never have went with the solution. The client has waited nearly a year and has its season starting in a couple months, the switches do work managed locally, so we kept them.
------------------------------
Dru DuBay
------------------------------
Original Message:
Sent: 01-11-2023 07:07 PM
From: JM52
Subject: Why is there a 22 "wired" network limit?
Yes, 22 Wired networks and 50 devices per site are the limits in cloud mode. The restriction is because of SMB networks which generally are small in size and this should suffice.
Can you please share your deployment and the use case?
------------------------------
Aruba Instant On Communications
Original Message:
Sent: 12-27-2022 04:51 PM
From: DD83
Subject: Why is there a 22 "wired" network limit?
Why, just... why...
Maybe it's fringe, but all of Aruba's competition allows for more than 22 VLAN's on a switch. I've been forced to manage all 16 of my new 1960 switches in local mode because of this one, silly limitation. Where do I have to post about this to get some real feedback.
------------------------------
Dru DuBay
------------------------------