Introduction :
When Airwave server communicates to controller over natted IP address then default method to offload WMS would not help.
prerequisite:
Please make sure the natted IP address of Airwave is static.
Environment :
To offload WMS on the Aruba controllers using AMP:
1. In AMP Setup > General, locate the Device Configuration section and enable Allow WMS Offload Configuration in Monitor-Only Mode to Yes
2. Select Save and Apply. This will push a set of commands via SSH to all Aruba master controllers. If the controller does not have an SNMPv3 user that matches the AMP database it will automatically create a new SNMPv3 user. AMP must have read/write access to the controllers in order to push these commands
3. Navigate to Groups > Basic and locate the Aruba section.
4. Set the Offload WMS Database field to Yes
When we enable WMS offload using the above instruction, Airwave construct the command that needs to enable the WMS offload however it will includes its local IP address Airwave and push it to controller over SSH.
Telnet_cmd log from Airwave:
Tue Apr 29 08:33:02 2014:
>> configure terminal
<< Enter Configuration commands, one per line. End with CNTL/Z
Tue Apr 29 08:33:03 2014:
>> mobility-manager 10.17.164.92 user airwave airwave123 trap-version 2c
The controller will accept the configuration however the WMS offload will not initiate since the Airwave IP that was included in the configuration command that was pushed by Airwave cannot help to establish session between the controller and Airwave to initiate the offload sequence.
Audit trail from controller command line:
Apr 29 09:51:52 fpcli: USER:admin@115.30.27.12 COMMAND:<no paging > -- command executed successfully
Apr 29 09:51:52 fpcli: USER:admin@115.30.27.12 COMMAND:<mobility-manager 10.17.164.92 user "airwave" ****** trap-version "2c" > -- command executed successfully
Apr 29 09:51:55 fpcli: USER:admin@115.30.27.12 COMMAND:<write memory > -- command executed successfully
Apr 29 09:51:57 fpcli: USER:admin@115.30.27.12 COMMAND:<no paging > -- command executed successfully
Apr 29 09:51:57 fpcli: USER:admin@115.30.27.12 COMMAND:<encrypt disable > -- command executed successfully
[Note: Here the IP address in green is natted IP and yellow is local IP address of Airwave.]
Mobility manager is added but not activated:
#show mobility-managers
MMS SERVERS
-----------
HOST USER NAME PORT INTERVAL RETRY RTLS-PORT ACTIVE
------- -------------- ------ ------------- -------- -------------- ---------
10.17.164.92 airwave 162 60 3 8000
Until we see an asterisk '
*' under "
Active" the WMS is not offloaded.]
Configuration Steps :
Run the following command from the Master controller's/ Standalone controller's command line to modify the Airwave's Natted IP address.
# configuration terminal
# Show running-config | include mobility
mobility-manager
<local IP address> user <username> <password> trap-version 2c
# no mobility-manager
<local IP address> user <username> <password> trap-version 2c
# mobility-manager
<natter ip address> user <username> <password> trap-version 2c
Example:
# configuration terminal
# Show running-config | include mobility
mobility-manager 10.17.164.92 user airwave airwave123 trap-version 2c
# no mobility-manager 10.17.164.92 user airwave airwave123 trap-version 2c
# mobility-manager 115.30.27.12 user airwave airwave123 trap-version 2c
Verification :
Once the above task is completed run the following command from Master controller's/ Standalone controller's command line to verify the completion of WMS offload when we see an asterisk '*' under "Active" as show marked in yellow.
#show mobility-managers
MMS SERVERS
-----------
HOST USER NAME PORT INTERVAL RETRY RTLS-PORT ACTIVE
------- -------------- ------ ------------- -------- -------------- ---------
<natter ip address> airwave 162 60 3 8000
* Example:
#show mobility-managers
MMS SERVERS
-----------
HOST USER NAME PORT INTERVAL RETRY RTLS-PORT ACTIVE
------- -------------- ------ ------------- -------- -------------- ---------
115.30.27.12 airwave 162 60 3 8000 *