Cloud Managed Networks

The customer  use Aruba SDWAN in all branches , and then they want to remove controller function  to save maintenance cost

Ideally New central, but it really is far from mature yet. I have been attempting to migrate a few of my customers and I have had the worst time of my life with 10+ tickets taking weeks, features not supported in New Central and having to roll several parts back to classic because it cannot be done on New Central.
It has a LOT of issues with corrupted object data rendering reporting useless (not updating) or devices keeping wrong settings perpetually.

It's not mature yet in my opinion.

It has many more issue than just that.  What use to take 30 seconds to configure now takes all day. And even when I get HPE on the phone, not even they can figure it out right away. I don't want a platform where I waste hours of my time with what use to take me 30 seconds.  If they don't scrap these rule-based policies in favor of the simplicity of the way it was done in Classic, I'll be throwing all my Aruba APs in the dumpster and switching to Ubiquiti.

Actually the new rule based policies are 100% what was needed. It may not seem straight forward at first and it is a bit confusing.  They work very similar to a top down approach on a firewall. A few of us posted to another link, you may find some use there. If you wish to pm me I am more then happy to explain my take on everything. 

When I had to manage 5-8 products with 20 roles and many acl's. Now its a simple update for an acl to be tagged to many roles and what would take hours now takes seconds. Its so easy to scale to other products instead of re-creating the wheel over and over. I have included the link below that may be helpful with some hints. You are welcome to PM me if you need a better understanding. 

https://airheads.hpe.com/discussion/new-central-client-assigned-roles

As I am still waiting for features to be added back. Its still a green product and orchestration/topology is not even in production yet. With a little bit of time on the product.. I find its so much easier to get data from CNX not only from the web although the API's as well. Any major project change and overhaul will create new challenges. It all takes time. 

Justin
ACMX #598, ACCX #638

It has many more issue than just that.  What use to take 30 seconds to configure now takes all day. And even when I get HPE on the phone, not even they can figure it out right away. I don't want a platform where I waste hours of my time with what use to take me 30 seconds.  If they don't scrap these rule-based policies in favor of the simplicity of the way it was done in Classic, I'll be throwing all my Aruba APs in the dumpster and switching to Ubiquiti.

I disagree about the need for role-based policies, especially when I have to call HPE every time I need to make a change, and even they take up hours of my time trying to figure it out themselves, on something that took me 30 seconds to accomplish with Classic.

There was nothing wrong with Classic and this new Central is a muddled mess.  I don't have the time it takes for this convoluted interface.  If they insist on keeping it, or at least make it to where their own techs can navigate it in a timely manner as well, I'm jumping ship.

Actually the new rule based policies are 100% what was needed. It may not seem straight forward at first and it is a bit confusing.  They work very similar to a top down approach on a firewall. A few of us posted to another link, you may find some use there. If you wish to pm me I am more then happy to explain my take on everything. 

When I had to manage 5-8 products with 20 roles and many acl's. Now its a simple update for an acl to be tagged to many roles and what would take hours now takes seconds. Its so easy to scale to other products instead of re-creating the wheel over and over. I have included the link below that may be helpful with some hints. You are welcome to PM me if you need a better understanding. 

https://airheads.hpe.com/discussion/new-central-client-assigned-roles

As I am still waiting for features to be added back. Its still a green product and orchestration/topology is not even in production yet. With a little bit of time on the product.. I find its so much easier to get data from CNX not only from the web although the API's as well. Any major project change and overhaul will create new challenges. It all takes time. 

Justin
ACMX #598, ACCX #638

It has many more issue than just that.  What use to take 30 seconds to configure now takes all day. And even when I get HPE on the phone, not even they can figure it out right away. I don't want a platform where I waste hours of my time with what use to take me 30 seconds.  If they don't scrap these rule-based policies in favor of the simplicity of the way it was done in Classic, I'll be throwing all my Aruba APs in the dumpster and switching to Ubiquiti.

Ideally New central, but it really is far from mature yet. I have been attempting to migrate a few of my customers and I have had the worst time of my life with 10+ tickets taking weeks, features not supported in New Central and having to roll several parts back to classic because it cannot be done on New Central.
It has a LOT of issues with corrupted object data rendering reporting useless (not updating) or devices keeping wrong settings perpetually.

It's not mature yet in my opinion.

There are options other then TAC. You can contact your SE or local VAR's for assistance. 

If you would like to learn about roles and policies. I am happy to assist. The others on the forum are actually asking for real feedback and assistance. I am more then happy to provide some tips or assistance to anyone that is willing to put in some effort. 

I disagree about the need for role-based policies, especially when I have to call HPE every time I need to make a change, and even they take up hours of my time trying to figure it out themselves, on something that took me 30 seconds to accomplish with Classic.

There was nothing wrong with Classic and this new Central is a muddled mess.  I don't have the time it takes for this convoluted interface.  If they insist on keeping it, or at least make it to where their own techs can navigate it in a timely manner as well, I'm jumping ship.

Actually the new rule based policies are 100% what was needed. It may not seem straight forward at first and it is a bit confusing.  They work very similar to a top down approach on a firewall. A few of us posted to another link, you may find some use there. If you wish to pm me I am more then happy to explain my take on everything. 

When I had to manage 5-8 products with 20 roles and many acl's. Now its a simple update for an acl to be tagged to many roles and what would take hours now takes seconds. Its so easy to scale to other products instead of re-creating the wheel over and over. I have included the link below that may be helpful with some hints. You are welcome to PM me if you need a better understanding. 

https://airheads.hpe.com/discussion/new-central-client-assigned-roles

As I am still waiting for features to be added back. Its still a green product and orchestration/topology is not even in production yet. With a little bit of time on the product.. I find its so much easier to get data from CNX not only from the web although the API's as well. Any major project change and overhaul will create new challenges. It all takes time. 

Justin
ACMX #598, ACCX #638

It has many more issue than just that.  What use to take 30 seconds to configure now takes all day. And even when I get HPE on the phone, not even they can figure it out right away. I don't want a platform where I waste hours of my time with what use to take me 30 seconds.  If they don't scrap these rule-based policies in favor of the simplicity of the way it was done in Classic, I'll be throwing all my Aruba APs in the dumpster and switching to Ubiquiti.