Network Management

Hi,

I forgot Airwave shared key.

Can i see existing shared key or do i need reset.

Kindly suggest how can i do that

Thank you

You should contact TAC.  I am not sure that the end-user can recover it.

AirWave Shared key for what? Can you give more details?

To join an IAP cluster for example?

If it's the shared key for IAP, then you can open TAC case and they can assist in helping you retrieve it.

If it's a different shared key, they can assist as well, just need to flesh out which key it is.  Depending on the key, it might require additional decrypting.

Hi,

Yes. to join IAP cluster with Airwave i need to insert correct shared key.

Thank you

Hi Nik,

Are you trying to add new IAP cluster to Airwave, if Yes then you could use any random shared key to add the device to Airwave, it is just use to authorize.

If you already have exisiting IAPs been added to Airwave and want to use same shared key to authorize this new cluster aswell then we could pull the information from database.

Try run below command to get shared sceret key

#dbc "select password from ap where id = 'xx'";

Replace xx with VCs id number, we could get this id from APs/Devices>monitor URL page in Airwave.

sample output from my server.

[root@Aruba-Airwave mercury]# dbc "select password from ap where id = '66'";
 password
----------
 test
(1 row)

Regards,

Pavan,

If my post address your query, give kudos:)

@Pavan

Please keep in mind that dbc commands won't work in the future as the AMP CLI will be locked down from running commands like you suggested.

---------------

The benefit of remembering the shared secret is that when a new IAP is detected with the same shared secret / organization string pairing, it will get automatically approved into AirWave if another device with that pairing is already present / approved as a monitored device.

With the above in mind, it'd be okay to create a new shared secret.  This would mean that the 1st device with the new shared secret would go into the new devices bin until approved.  Once you manually approve 1 entry with the new shared secret, additional IAPs with the new pairing will be automatically approved.  Ideally you would setup 1 IAP with the new shared key first to approve before enabling the other IAPs.  If they all go live at the same time, you can simply delete the extras from new devices and then they will be automatically authorized the next time they are discovered.

The shared secret is no longer displayed in clear text after 8.2.10.0 .