If you get a valid output like above, then the credentials are correct. If you're on older code - it might just be easier to go to the device's management page and updating the creds with the correct creds.

:: Check SNMP version ::

Go to Groups -> select group -> Basics page

Under the specific supported Device type breakout - check that SNMP version used to communicate with your device is set to the right version.

Running .1 is collecting the entire MIB table. You could also isolate to specific tables that are larger like the BSSID table (for Aruba controllers: wlsxWlanAPBssidTable) or client usage tables (for Aruba controllers: nUserName or nUser6Name). If you're seeing the timeout happening frequently even when at max setting, then open a support case for further debugging. Support may have to manually increase the timeout value beyond what the UI allows (but this makes the Device Communication page obsolete as any setting change would revert the timeout back to the max allowed).

:: Big Hammer - Restart of all AMP services ::

If you choose not to try to debug the cause and just want to see if the services are stalled, then you can go to System -> Status, at the bottom of the page is Restart AMP option.

AMPCLI also has a parallel option under the Advanced (8) -> Restart Application (1).