Monitoring, Management & Location Tracking

How to change the VC key on IAP, which is used for IAP to Airwave or Aruba central communication
Requirement:

IAP Cluster, being monitored or managed on Airwave or Aruba Central.

If we want to change the VC key on IAP, which is a unique attribute of a cluster, used to communicate with Airwave or Aruba central. We might required to change the key if it is matching with some other Cluster already present in Airwave. That might happen because of multiple reasons, if we switch the IAP from different cluster and it becomes Master on the new Cluster or if we import the backup from one cluster to the other etc.



Solution:

We could check the VC key by running the below command on the IAP (VC or Master) CLI:

IAP Master 225# show running-config | include virtual*
virtual-controller-country IN
virtual-controller-key 797ceb400158cf69b78bbd572087d7d5ec5f4af2da50efbeed

and compare with already added IAP cluster. If it matches,  for the above mentioned reasons or some other reasons, we should change the key for IAP to Airwave smooth communication.

 

 



Configuration:

since this key is unique, all we need to do is, change the last one or two letters/numbers of the key as shown below, in the below example am changing the last two letters:

IAP Master 225# config t
We now support CLI commit model, please type "commit apply" for configuration to take effect.
IAP Master 225 (config) # virtual-controller-key 797ceb400158cf69b78bbd572087d7d5ec5f4af2da50efbefh
IAP Master 225 (config) # exit
IAP Master 225# commit apply
committing configuration...
configuration committed.

once changed a reload is mandatory, for IAP cluster to start using the new key, we would need to do the following:

IAP Master 225# Reload

 

 



Verification

we could verify if the key is changed, by running the command:

IAP Master 225# show running-config | include virtual*
virtual-controller-country IN
virtual-controller-key 797ceb400158cf69b78bbd572087d7d5ec5f4af2da50efbef

and also we could see the IAP logs, where we could verify its using the new key to communicate with Airwave:

IAP Master 225# show log ap-debug

Jan  1 00:03:39  awc[3039]: awc_init_connection: 2039: connected to 10.17.164.203:443
Jan  1 00:03:39  awc[3039]: awc_init_connection: 2173: Connected
Jan  1 00:03:39  awc[3039]: Sent header(len=312) 'POST /swarm HTTP/1.1^M Host: 10.17.164.203^M Content-Length: 0^M X-Type: login^M X-Guid: 797ceb400158cf69b78bbd572087d7d5ec5f4af2da50efbef^M X-Name: instant-C8:21:F8^M X-Organization: sita^MX-Shared-Secret: admin^M X-OEM-Tag: Aruba^M X-Accept-Authentication: PSK,CERT^MX-Ap-Info: CT0201852, 18:64:72:cd:76:96, AP-225^M ^M '
Jan  1 00:03:39  awc[3039]: Message over SSL from 10.17.164.203, SSL_read() returned 67, errstr=Success, Message is "HTTP/1.1 401 Unauthorized^M Connection: close^M Content-Length: 0^M ^M ", AWC response: (null)

Version History
Revision #:
2 of 2
Last update:
4 weeks ago
Updated by:
 
Labels (2)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.