Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

Keep IAP VC connected to airwave when master AP goes down

This thread has been viewed 0 times

  • 1.  Keep IAP VC connected to airwave when master AP goes down

    Posted Oct 04, 2018 09:14 AM

    Hi,

     

    We are setting up zero touch and uses DNS to connect to airwave when they initially boot up.

     

    I set up a couple of test 314 IAP's which connected to airwave via a DNS entry.  The first one became the master AP with the VC.

     

    When I disconnected the master AP (AP1) the second AP (AP2) was elected the master AP and had the VC but all both AP's and the VC we shown as down on airwave and wouldn't reconnect.  I have tried this with a static IP and without a static IP for the VC

     

    How can I configure the IAP/VC to stay connected to airwave when the master AP goes down?

     

    Thanks

    Sean



  • 2.  RE: Keep IAP VC connected to airwave when master AP goes down

    Posted Oct 04, 2018 11:48 AM

    Sounds kinda strange.

    Having 2 IAPs in a cluster would yield 3 entries in airwave (2 physical APs and a VC). Turning off the VC AP, should make AP2 VC and in extension only showing 1 entry in airwave as down (while AP2 and VC still up).

     

    Did you do any troubleshooting in AP2 when initial VC is offline?

    I'd recommend starting with 

    'show ap debug airwave'-commands and

    'show log system all'



  • 3.  RE: Keep IAP VC connected to airwave when master AP goes down

    Posted Oct 09, 2018 02:58 AM

    I did troubleshoot it.

     

    I've run the commands again and below is the output:

     

    Test-Ave-IAP2# show ap debug airwave

    Airwave Server List
    -------------------
    Domain/IP Address  Type  Mode  Config-only  Status
    -----------------  ----  ----  -----------  ------

    Test-Ave-IAP2#

     

     

    Test-Ave-IAP2# show log system

    Oct  9 03:00:58  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:05:58  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:06:00  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:11:00  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:11:02  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:16:02  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:16:04  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:21:04  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:21:06  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:26:06  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:26:08  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:31:08  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:31:10  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:36:10  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:36:12  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:41:12  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:41:14  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:46:14  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:46:16  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:51:16  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:51:18  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 03:56:18  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 03:56:21  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:01:20  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:01:23  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:06:23  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:06:25  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:11:25  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:11:27  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:16:27  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:16:29  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:21:29  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:21:31  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:26:31  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:26:33  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.

    Oct  9 04:31:33  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:31:35  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:36:35  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:36:37  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:41:37  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:41:39  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:46:39  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:46:41  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:51:41  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:51:43  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 04:56:43  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 04:56:45  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:01:45  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:01:47  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:06:47  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:06:49  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:11:49  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:11:51  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:16:51  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:16:54  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:21:53  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:21:55  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:26:55  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:26:57  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:31:57  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:32:00  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:36:59  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:37:01  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:42:01  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:42:04  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:47:04  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:47:06  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:52:06  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 05:52:08  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 05:57:08  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.

    r allowed: code: fail-prov-no-rule.
    Oct  9 06:02:10  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:02:12  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:07:12  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:07:14  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:12:14  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:12:16  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:17:16  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:17:18  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:22:18  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:22:20  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:27:20  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:27:22  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:32:22  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:32:24  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:37:24  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:37:26  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:42:26  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:42:28  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:47:28  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:47:30  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.
    Oct  9 06:52:30  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  provision try.
    Oct  9 06:52:33  cli[3831]: <341004> <WARN> |AP Test-Ave-IAP2@172.16.149.109 cli|  Set amp discover allowed: code: fail-prov-no-rule.



  • 4.  RE: Keep IAP VC connected to airwave when master AP goes down

    Posted Oct 09, 2018 04:45 AM

    Hi,

     

    I figured it out and got it working.  I needed to add the ams-ip/key commands. 

     

    When looking previously I didnt know what the commands were to to poin the IAP to airwave after it had initially connected.

     

    Thanks for you help.