Network Management

last person joined: yesterday 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

PSK based authentication: swarm is not approved in Airwave.

This thread has been viewed 24 times
  • 1.  PSK based authentication: swarm is not approved in Airwave.

    Posted Apr 25, 2017 05:47 AM

    Hi Guys

    We upgraded our Airwave to version 8.2.3.1 , And we deleted all our DB in order to start with fresh config.

    We getting stange errors from our IAP's (that worked in the past)

    PSK based authentication: swarm is not approved in Airwave.

     

    Please advise.

    How do i enable swarm in Airwave?



  • 2.  RE: PSK based authentication: swarm is not approved in Airwave.

    EMPLOYEE
    Posted Apr 25, 2017 06:00 AM

    Hi,

    Are you seeing this messages in Airwave events log? Could you try edit the VC key and check the status.

     

    We see this issue , when we try to add an IAP to Airwave which is part of cluster previously, aiwave thinks it is old IAP which is already added to Airwave and it wont accept.Airwave recongnize each cluster based on GUID.

     

    1) # show running | include virtual

    2) copy the virtual-controller key

    3) # conf t

    4) # virtual-controller-key <paste copied kay>

    5) change th last 2 digit of the key
    sample key

    virtual-controller-key 1bc58c2c014f78440e92d71fec0bc72428de77cef98b92624c

    virtual-controller-key 1bc58c2c014f78440e92d71fec0bc72428de77cef98b92625d



    6) # commit apply.

     

    Regards,

    Pavan

    If my post address your query, give kudos:)



  • 3.  RE: PSK based authentication: swarm is not approved in Airwave.

    Posted Apr 25, 2017 06:25 AM
    Are you seeing this messages in Airwave events log? Could you try edit the VC key and check the status.

    Doing it right now... will update soon,
    But i have 200 diffrent VC'S with almost 1000 IAP's , I will need to do it one by one?!


  • 4.  RE: PSK based authentication: swarm is not approved in Airwave.

    EMPLOYEE
    Posted Apr 25, 2017 06:35 AM

    Yes, if we are seeing same error for all IAPs. How did you reset the database?

     

    We could reset the database by running below command

     

    #amp_disable

    #bootstrap_db

    #amp_enable -now

    #amp_version

    copy the old backup file to /tmp and restore

    #amp_restore -d /tmp/<backupfilename>

     

    Note: Make sure, restore same version backup file. We cannot restore lowerversion backup file on higher version.

     

    Regards

    Pavan



  • 5.  RE: PSK based authentication: swarm is not approved in Airwave.

    Posted Apr 27, 2017 12:58 PM

    Thanks,BUT,I dont want to restore , i want to start from nothing.

    *Even after running the bootstrap_db command , i still seeing the same errors on swarm is not approved in Airwave. *

     

    Please advise. :(



  • 6.  RE: PSK based authentication: swarm is not approved in Airwave.

    Posted Apr 27, 2017 01:29 PM

    2017-04-27_20-25-55.jpg

    Still same error:

    PSK based authentication: swarm is not approved in Airwave.

     

    :(



  • 7.  RE: PSK based authentication: swarm is not approved in Airwave.

    EMPLOYEE
    Posted Apr 28, 2017 01:47 AM

    If you still see the issue after bootstrap, try reset the VC key and check the status.

     

    Regards,

    Pavan



  • 8.  RE: PSK based authentication: swarm is not approved in Airwave.

    Posted Apr 28, 2017 05:05 AM
    It's multiple VC'S (Something like above 300 different branches )

    Is there any other way?


  • 9.  RE: PSK based authentication: swarm is not approved in Airwave.

    EMPLOYEE
    Posted Apr 28, 2017 05:28 AM

    Have you tried resetting the VC key and checked ? Try restore the same version backup on server, if you have. If not, resetting the VC key is only option.

     

    Make sure, you have valid Airwave license aswell.

     

    Regards,

    Pavan



  • 10.  RE: PSK based authentication: swarm is not approved in Airwave.

    Posted Apr 29, 2017 03:27 AM
    Thanks,I will try again resetting one of the VC's key (via command line like you mentioned before,even due i tried on one unit,and it still in the event log...)

    I'm now using the 90days trial license , should i install my official license? (the 90day license got limitations ? )


  • 11.  RE: PSK based authentication: swarm is not approved in Airwave.

    EMPLOYEE
    Posted Apr 30, 2017 09:21 AM

    Hi,

     

    If eval license is valid and not expired, it should work. Could you check the security method for adding new virtual controller setting in AMP Setup>Aruba Instant Option. Default it will set to PSK, if it is set to PSK+Certificate or Certificate only, make sure you have certifictae intalled in Airwave.

    Capture(1).PNG

     

    If you still have the issue, please open TAC ticket.

     

    Regards,

    Pavan



  • 12.  RE: PSK based authentication: swarm is not approved in Airwave.
    Best Answer

    Posted May 03, 2017 06:11 AM
    It was an issue on 8.2.3.1
    Even when i created a new VM from nothing , same issue.
    i created a new VM machine with 8.2.1.1 - everything works! no swarm warnings


  • 13.  RE: PSK based authentication: swarm is not approved in Airwave.

    EMPLOYEE
    Posted May 03, 2017 06:16 AM

    Hi,

     

    We do not have any issue related to adding IAPs to Airwave on  8.2.3.1 code, I believe you might doing something wrong. If you still have 8.2.3.1 server running, I would recommand to open TAC  case to troubleshoot the issue.

     

    Regards,

    Pavan



  • 14.  RE: PSK based authentication: swarm is not approved in Airwave.

    Posted May 03, 2017 06:40 AM
    Also do i, But above 200 iaps dont lie... On 8.2.3.1 new from the box , Swarm not allowed errors. ( Some of thr iaps do work ) , and on 8.2.1.1 new from the box no Swarm errors at any unit.
    I guess its 8.2.3.1 issue.


  • 15.  RE: PSK based authentication: swarm is not approved in Airwave.

    EMPLOYEE
    Posted May 03, 2017 06:52 AM

    Hi,

     

    I would recommand to open TAC ticket to look in to this issue. We need to check logs to confirm, whether issue really on Airwave server or not?

     

    Regards,

    Pavan