Cloud Managed Networks

I have a TAC case open for a client, anytime we attempt to set the VC name for any new or existing VC, we receive an error stating "VC name cannot be empty". The VC Name is definitley not empty, simply renaming from SetMeUp-xx:xx:xx to SetMeUp-xx:xx:xx1 or setting to VC1, etc, replicates the error.

Initially we thought it was just chrome, we tried IE and it was fine, but now IE and firefox are doing the same, even tried it from my phone, same deal. I have tried on on numerous machines, customer domain joined, my domain joined, personal, phone, vm, etc and can replicate it.

Initially support tried to tell me it was my issue (even though we could replicate on different machines that have never touched the same network...), but now the seem to finally taking it seriously.

Anyone else have this issue? I have had to add workarounds in ClearPass to get them by, but this is annoying, i have a major site coming up in a week...

Hi Brett,

I also experienced the same problem. I thought I could be a missconfiguration but now I see it is serious.

I hope Aruba Central guys could solve the problem soon.

Regards

Same issue here, hope this gets resolved quickly.

We have the same issue as well. Started out with Chrome then went through other browsers. Any word on a fix?

I had the same issue, opened up Central in MS Edge (yeah...i know!) and it worked without issues.

Yeah it worked with Edge for awhile for us but then it stopped although for a select few it is still working with Edge

Same issue here on a new Instant deployment with IAP-315s.  I'm assuming there's no word yet on a fix?

This should already be fixed (at least it is in my account). Can you try again?

Thanks

Nope, still not working. Engineering "fixed" it a few weeks ago but it never worked, engineering still working on a fix.

Still not fixed for me either. In fact it has gotten worse. I can update it from any browser now. 

Same problem here to. 

Please Try with Edge Browser. (Endlich I found the tempory solution!)

It did work on Edge for awhile for me but then that browser stopped working as well. Have tried on multiple PC's with same issue

Aruba did an upgrade Friday night to fix this issue. As of now it is working for me using Chrome again. Hopefully that continues. 

Yes, since the last update is seems to be fixed. Many times we were told it should be fixed, this time though it is true.