Controllerless Networks

With central being split out to be a basic license then Guest and Analystics as paid for options, what does JW451AAE - Aruba Central Cloud Services for 1 Instant AP, 3 Yr Subscription actually include?

 

Same question!

The device management license will allow you able to manage the device of course and also 24/7 TAC support and AppRF

Get Outlook for iOS

So, what the difference between

JW450AAE	Aruba Central Cloud Services for 1 Instant AP 1-year Subscription E-STU
JW455AAE	Aruba SUB1-WE-IAP-1 Cloud Web Policy Enforcement for 1 Instant AP 1-year Subscription E-STU
JY925AAE	Aruba Central DM 1 Token 1y Sub E-STU
JY928AAE	Aruba Central Svc 1 Token 1y Sub E-STU

---

@Betancourt wrote:

So, what the difference between

JW450AAE	Aruba Central Cloud Services for 1 Instant AP 1-year Subscription E-STU
JW455AAE	Aruba SUB1-WE-IAP-1 Cloud Web Policy Enforcement for 1 Instant AP 1-year Subscription E-STU
JY925AAE	Aruba Central DM 1 Token 1y Sub E-STU
JY928AAE	Aruba Central Svc 1 Token 1y Sub E-STU

---

The first option, JW450AAE, from my understanding, is the original Central SKU from before the split and shouldn't be used going forward (but can techncially still work) - if this is incorrect someone please feel free to correct me (trust me, i'd like to be wrong here as it's much harder to position the split than one whole subscription) 

The second, JW455AAE, is basically web filtering  but I don't believe that is techincally part of Central (just a seperate cloud service)

The last 2, JY925AAE & JY928AA, are the SKU's needed going forward when purchasing/positioning/quoting Central.

 

JY925AAE, the Device Management token, lets you add 1 Device (IAP, switch, & hopefully soon, the 7000 series controllers) to be monitored in Central. So think of that one as your base subscription.  

 

JY928AA is the Service Token SKU and only applies to AP's (at the moment).  This gives the ability to add one of the available services (Guest Wifi / Presence & Analytics) to any given AP.  

 

So, for example, if you wanted 10 IAP's and wanted them all to be monitored and wanted both Services you'd need qty 10 of JY925AAE and qty20 JY928AA 

 

If, on the other hand, you only wanted 1 Service and Device Monitoring for those 10 IAP's, you'd get qty.10 JY925AAE and qty10 JY928AA. 

 

And, lastly, you could just do monitoring and neither of the Services for your 10 IAP's and just get qty. 10 JY925AAE

 

Not a fan on the split, the old SKU worked just fine and was easy to explain.

 

Can we expand on what the services cover, what exactly is defined by "Guest WiFi". Are you telling me with out a license then you can't connect to a guest network? What if you have multiple guest networks? How is the distintion made on what a "Guest Network" is.

 

Secondly, isn't analytics the whole point of central?  What analytics are we giving up by not buying these seats.

 

If we don't understand HP's logic, I can't explain it to our clients.

Hey EHanson,

 

   While the old SKU's were easier to explain, the new method achieved 2 things:

 

1. Competitive Pricing Structure

2. Flexibility

 

Both of those things are big struggles for Cisco/Meraki.

 

Guest Wi-Fi is pretty much a full functioned Captive Portal with several login options including Social/Facebook login. It's not that you can't create a "Guest" network by creating a "Guest" SSID and applying certain rules to it but you won't have a fully featured Captive Portal option.

 

I don't know what Meraki offers off the bat but every company is going to plan features around cost and flexibility - with Cisco, for instance, Presence Analytics is technically a whole other product that you can kind of tie in to Meraki; with Central it's just a service option you can use or not and you can choose which AP's you want it/can afford it on and which ones you can't or don't.

Speaking of Presence Analytics, that's a very specific function - this isn't just network analytics this is RF Analytics specifically regarding Client traffic patterns. That's in HUGE demand in the retail markets because it even sees people that don't connect to the network. 

 

And they just recently added Clarity which is a MASSIVELY effective product for network admin's/engineers/analysts because it really takes the most common network failures into account and gives you visibility there that you don't get on any other product out there.

 

Lastly, the Services options can, at any given time, within the timeframe of your subscription, be swapped out  with other services- you aren't locked in to the first one you choose or to the architecture you chose.

 

So while the first method was much more simple, it was also more costly and rigid and was going to inhibit future development on the Cetral roadmap

Thanks for the reply, this community is great. HPe could have done a better explaining the changes to their partners.

 

Do you need more than one service token if you have more than one captive portal? 1 Captive Portal = 1 token?

 

So the analytics token, is more in like with the beacons? Or is the standard that everyone is deploying the presence analytics tokens regardless of size.

 

Thanks again

Happy to help!

 

And, yeah, I think even HP would agree that some of the things in transition with Aruba could've been comumunicated better but they've apologized for a lot of that and have tried to smooth out those issues in the recent months.

 

With the Service Tokens, they are assigned on a per AP basis and you choose which service you want to use.  If you want 2 services (let's say Guest WiFi and Clarity) on 2 of your 5 AP's, that'd cost 4 Service Tokens (you'd basically just assign Guest WiFi and Clarity to each AP and it would consume 2 service tokens per AP).

 

 That said, once those services are assigned to the AP, Guest Wifi Capabilities and Clarity capabilities are enabled for that AP.  To get 2 Captive Portals you'd create 2 SSID's and point them to 2 different Captive Portal profiles (configured in the Guest Management portion of Central).but it wouldn't cost you an extra token to do so since it's only on a per AP (not per network/SSID) basis.

 

And with Presence Analytics, it's actually just using the AP's (no beacons required) and it also just consumes 1 Service token so you'd treat it just like above, assigning it on a per-desired-AP basis.  This one isn't used as much across verticals but it is very popular in Retail markets and things like Museums and Art Galleries and Stadiums where traffic pattern analytics are a huge business driver

 

---