We have Airwave running in a VM on Windows Server 2012 R2 as the host.
A day ago, early in the morning when nobody was touching the config (that would only be me) it stopped responding to pings.
The CLI is still available, I can login and check the settings and still looks good.
When rebooting the machine, it being responding to ping until it loads Centos and just before it hits the airwave login, it stops responding again.
Anyone had this happen before? Running 8.2.6
Did you change the network adapter to 'Legacy' for the VM in Hyper-V, as described in the Airwave Installation Guide?
There are some known issues with network adapters, Linux (which is the underlying base of Airwave) and Hyper-V; which should be circumvented by selecting a Legacy Network adapter.
If you followed that direction already, and still have issues, please contact Aruba TAC as they might be able to optimize some other things via the backend.
Please work with Aruba TAC to get this investigated.
Restored from backup to fix issue.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.