Airwave Snmp; Pushing Configs From Master To Local Controllers; Disable Debugging Utilizing Arubaos Cli - Dell PowerConnect W-Airwave Manual

(Controller-Name) (config) # write mem
This command creates the AirWave server as an SNMPv3 Trap Host in the controller's running configuration.
This command also creates an SNMPv3 user on the controller with authentication protocol configured to SHA
and privacy protocol DES. The user and password must be at least eight characters, because the Net-SNMP
package in AirWave adheres to this IETF recommendation. ArubaOS automatically creates Auth and Privacy
passwords from this single password. If mobility-manager is already using a preconfigured SNMPv3 user, ensure
the privacy and authentication passwords are the same.
Example:
mobility-manager 10.2.32.1 user airwave123 airwave123

AirWave SNMP

Log in into the AirWave server with proper administrative access and issue the following command for all
controllers (master and locals):
[root@AMP ~]# snmpwalk -v3 -a SHA -l AuthPriv -u <MMS-USER> -A <MMS-SNMP-PASSWORD> -X
<MMS-SNMP-PASSWORD> <Controller-IP> wlsxSystemExtGroup
WLSX-SYSTEMEXT-MIB::wlsxSysExtSwitchIp.0 = IpAddress: 10.51.5.222
WLSX-SYSTEMEXT-MIB::wlsxSysExtHostname.0 = STRING: dell-3600-2
.
..
WLSX-SYSTEMEXT-MIB::wlsxSysExtSwitchLastReload.0 = STRING: User reboot.
WLSX-SYSTEMEXT-MIB::wlsxSysExtLastStatsReset.0 = Timeticks: (0) 0:00:00.00 response
[root@AMP ~]#
Unless this SNMP walk command is issued properly on all of the controllers, they will not properly populate client
and rogue statistics. Ensure the user and passwords match exactly to those entered in above sections.
Example:
snmpwalk -v3 -a SHA -l AuthPriv -u airwave123 -A airwave123 -X airwave123 10.51.3.222
wlsxSystemExtGroup
If you do not use the AirWave WebUI to offload WMS, you must add a cronjob on the AirWave server to ensure
continued statistical population. Because the MIB walk/touch does not persist through a controller reboot, a
cronjob is required to continually walk and touch the MIB.

Pushing Configs from Master to Local Controllers

Use the following ArubaOS CLI commands to ensure that the master controller is properly pushing configuration
settings from the master controller to local controllers. This command ensures configuration changes made on
the master controller will propagate to all local controllers.
NOTE: Do not use these commands if you use the AirWave GUI to monitor APs and clients.
(Controller-Name) (config) # cfgm mms config disable
(Controller-Name) (config) # write mem

Disable Debugging Utilizing ArubaOS CLI

If you are experiencing performance issues on the master controller, ensure that debugging is disabled. It should
be disabled by default. Debugging coupled with gathering the enhanced statistics can put a strain on the
controllers CPU, so it is highly recommended to disable debugging.
32 | ArubaOS and AirWave CLI Commands Dell PowerConnect W-AirWave 7.5 | Best Practices Guide