deploying controller on azure

[avdheshkumar]

Hi All,

trying to deploy vWLC in azure, when the VM is deployed it show error "vm agent not ready".

WLC is reachable on network and am able to have CLI access. not getting access via webui though the public IP is reachable (i can ping the public IP). i have allowed HTTP and SSH incoming in NSG.

just wanted to know if anyone has faced this issue and how it was resolved.

[marce1000]

             - Make sure the software version being used is 17.7.1 or higher,

 M.

[avdheshkumar]

This is the only version available on azure

[Scott Fella]

I have a few in Azure and also have that "vm agent not ready". This is due to some of the diagnostic features you have enabled on your subscription or resource that is trying to load.  It will not affect anything.  I have someone whom manages the features in Azure and she is looking at it for me.  I will post what she did if she is able to fix that.

[avdheshkumar]

Great... I will wait or update if i get the solution first.

[Rich R]

When you say vWLC - do you mean 9800-CL controller?
AireOS vWLC product is not supported in Azure.

[Scott Fella]

Rich,

I think a lot of people still use the vWLC for anything virtualized:) Easier to say than 9800-CL, but I don't use the vWLC term because that was such a bad experience on AireOS.

[avdheshkumar]

9800-CL it is..

[Rich R]

Agreed @Scott Fella but good to confirm of course, just in case ...

[avdheshkumar]

Hi All ,

thanks for the suggestions and support, as of now the "VM agent not ready" notification is gone.

[Scott Fella]

Interesting. All of mine still show that when I click on the VM. It’s an agent for Windows and Linux machines so don’t know why a Cisco appliance would get flagged. Might be because of the underlying Linux OS.

[avdheshkumar]

to add, we didn't do any changes.