Controllerless Networks

last person joined: an hour ago 

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

Add IAP to existing VC

Jump to Best Answer
  • 1.  Add IAP to existing VC

    Posted Jan 16, 2015 07:56 AM

    Hello, this is my first post in the forum.

     

    I have a little problem with Aruba APs.

     

    I had a VC cluster with a IAP 103 and IAP 105 devices. I delete the 103 devie to make some tests.

     

    Now I want to add to VC the 103 device to have better signal. How coulad I add it?

     

    I try to access to the VC IP address, and in the Access Point section click in the Add, add the MAC but nothing happens.

     

    I reset the 103 device before add to the VC. Both devices has same software version.

     

    I will appreciate any help.

     

    Regards.



  • 2.  RE: Add IAP to existing VC

    Posted Jan 16, 2015 08:01 AM
    It should join automatically as long is these are on the same segment and with the same IAP OS , make sure auto join is enabled under the system tab


  • 3.  RE: Add IAP to existing VC

    Posted Jan 16, 2015 08:06 AM

    Thanks for the reply,

     

    both devices are in the same segment.

     

    This is what I have in the System Tab in the VC:

     

    aruba_problem.png

     

    Regards.



  • 4.  RE: Add IAP to existing VC

    Posted Jan 16, 2015 08:17 AM
    Click on the show advanced and should show you that option


  • 5.  RE: Add IAP to existing VC

    Posted Jan 16, 2015 09:21 AM
    What OS are each of them on? Be sure they match.


  • 6.  RE: Add IAP to existing VC

    Posted Jan 19, 2015 02:58 AM

    Hello,

     

    I activate the "Auto join mode": aruba_advanced.png

     

    But nothing, I activa in both devices. This is the OS version of both devices:

     

    Name: Aruba Operating System Software
    Type: 105
    Build Time: 2014-11-05 10:00:49 PST
    Version: 6.4.2.0-4.1.1.1_46936

     

    Name: Aruba Operating System Software
    Type: 103
    Build Time: 2014-11-05 10:44:10 PST
    Version: 6.4.2.0-4.1.1.1_46936

     

    Regards.



  • 7.  RE: Add IAP to existing VC

    Posted Jan 20, 2015 06:30 AM

    Hi friend,

     

    Please check the following also,

     

    1. Console IAP 103 and ensure that , it is getting IP address from the same subnet as IAP 105

     

    2. Check the country code also both should have the same country code.

     

    3. To pin point the issue, console the IAP 103 and run " show log system"

     

    Please feel free for any further help on this.



  • 8.  RE: Add IAP to existing VC

    Posted Jan 20, 2015 07:12 AM

    Thanks for the reply.

     

    They can see each other:

     

    From the IAP 103:

     

    # ping 192.168.2.232 (IAP 105)
    Press 'q' to abort.
    PING 192.168.2.232 (192.168.2.232): 56 data bytes
    64 bytes from 192.168.2.232: icmp_seq=0 ttl=64 time=1.0 ms
    64 bytes from 192.168.2.232: icmp_seq=1 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=2 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=3 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=4 ttl=64 time=0.5 ms

    --- 192.168.2.232 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.5/0.6/1.0 ms

     

    # ping 192.168.2.239 (VC)
    Press 'q' to abort.
    PING 192.168.2.239 (192.168.2.239): 56 data bytes
    64 bytes from 192.168.2.239: icmp_seq=0 ttl=64 time=0.2 ms
    64 bytes from 192.168.2.239: icmp_seq=1 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=2 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=3 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=4 ttl=64 time=0.1 ms
    
    --- 192.168.2.239 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.1/0.1/0.2 ms

     

    The country region is same in both.

     

    This is the "show log system" in the IAP 103:

     

    # show log system
    
    Jan 20 07:50:41  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 07:50:45  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 07:55:43  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 07:55:49  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:00:45  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:00:49  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:05:48  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:05:52  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:10:50  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:10:54  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:15:52  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:15:56  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:20:54  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:20:58  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:25:57  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:26:01  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:30:59  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:31:03  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:36:01  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:36:05  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:41:03  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:41:08  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:46:06  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:46:10  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:51:08  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:51:12  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:56:10  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:56:14  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:01:12  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:01:17  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:06:15  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:06:19  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:11:17  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:11:21  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    
    Jan 20 09:16:19  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:16:23  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:21:22  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:21:26  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:26:24  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:26:28  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:31:26  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:31:30  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:36:29  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:36:33  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:41:31  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:41:35  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:46:33  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:46:37  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:51:35  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:51:39  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:56:38  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:56:42  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:01:40  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:01:44  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:06:42  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:06:46  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:11:45  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:11:49  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:16:47  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:16:55  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:21:49  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:21:53  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:26:52  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:26:56  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:31:54  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:31:58  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:36:56  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:37:00  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    
    Jan 20 10:42:04  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:47:01  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:47:05  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:52:03  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:52:07  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:57:05  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:57:10  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:02:07  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:02:15  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:07:10  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:07:14  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:12:12  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:12:16  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:17:14  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:17:18  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:22:17  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:22:24  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:27:19  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:27:23  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:32:21  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:32:29  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:37:29  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:37:33  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:42:37  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:42:41  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:47:39  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:47:43  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule

     I try to configure the "auto join" in both 103 and 105 (master), in wich must I configure it?

     

    Kind regards.



  • 9.  RE: Add IAP to existing VC

    Posted Jan 20, 2015 07:14 AM

    Thanks for the reply.

     

    They can see each other:

     

    From the IAP 103:

     

    # ping 192.168.2.232 (IAP 105)
    Press 'q' to abort.
    PING 192.168.2.232 (192.168.2.232): 56 data bytes
    64 bytes from 192.168.2.232: icmp_seq=0 ttl=64 time=1.0 ms
    64 bytes from 192.168.2.232: icmp_seq=1 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=2 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=3 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=4 ttl=64 time=0.5 ms

    --- 192.168.2.232 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.5/0.6/1.0 ms

     

    # ping 192.168.2.239 (VC)
    Press 'q' to abort.
    PING 192.168.2.239 (192.168.2.239): 56 data bytes
    64 bytes from 192.168.2.239: icmp_seq=0 ttl=64 time=0.2 ms
    64 bytes from 192.168.2.239: icmp_seq=1 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=2 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=3 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=4 ttl=64 time=0.1 ms
    
    --- 192.168.2.239 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.1/0.1/0.2 ms

     

    The country region is same in both.

     

    This is the "show log system" in the IAP 103:

     

    # show log system
    
    Jan 20 07:50:41  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 07:50:45  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 07:55:43  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 07:55:49  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:00:45  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:00:49  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:05:48  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:05:52  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:10:50  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:10:54  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:15:52  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:15:56  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:20:54  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:20:58  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:25:57  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:26:01  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:30:59  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:31:03  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:36:01  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:36:05  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:41:03  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:41:08  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:46:06  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:46:10  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:51:08  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:51:12  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 08:56:10  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 08:56:14  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:01:12  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:01:17  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:06:15  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:06:19  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:11:17  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:11:21  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    
    Jan 20 09:16:19  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:16:23  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:21:22  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:21:26  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:26:24  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:26:28  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:31:26  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:31:30  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:36:29  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:36:33  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:41:31  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:41:35  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:46:33  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:46:37  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:51:35  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:51:39  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 09:56:38  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 09:56:42  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:01:40  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:01:44  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:06:42  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:06:46  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:11:45  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:11:49  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:16:47  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:16:55  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:21:49  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:21:53  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:26:52  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:26:56  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:31:54  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:31:58  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:36:56  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:37:00  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    
    Jan 20 10:42:04  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:47:01  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:47:05  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:52:03  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:52:07  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 10:57:05  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 10:57:10  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:02:07  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:02:15  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:07:10  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:07:14  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:12:12  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:12:16  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:17:14  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:17:18  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:22:17  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:22:24  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:27:19  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:27:23  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:32:21  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:32:29  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:37:29  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:37:33  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:42:37  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:42:41  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule
    Jan 20 11:47:39  cli[1424]: <341004> <WARN> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  Isc_send_request
    Jan 20 11:47:43  cli[1424]: <341005> <ERRS> |AP 9c:1c:12:xx:xx:xx@192.168.2.108 cli|  APAS provision failed, code: fail-prov-no-rule

     I try to configure the "auto join" in both 103 and 105 (master), in wich device must I configure it?

     

    Kind regards.



  • 10.  RE: Add IAP to existing VC

    Posted Jan 20, 2015 09:41 AM

    Thanks for the reply.

    They can see each other:

    From the IAP 103:

    # ping 192.168.2.232 (IAP 105)
    Press 'q' to abort.
    PING 192.168.2.232 (192.168.2.232): 56 data bytes
    64 bytes from 192.168.2.232: icmp_seq=0 ttl=64 time=1.0 ms
    64 bytes from 192.168.2.232: icmp_seq=1 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=2 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=3 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=4 ttl=64 time=0.5 ms

    --- 192.168.2.232 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.5/0.6/1.0 ms

    # ping 192.168.2.239 (VC)
    Press 'q' to abort.
    PING 192.168.2.239 (192.168.2.239): 56 data bytes
    64 bytes from 192.168.2.239: icmp_seq=0 ttl=64 time=0.2 ms
    64 bytes from 192.168.2.239: icmp_seq=1 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=2 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=3 ttl=64 time=0.1 ms
    64 bytes from 192.168.2.239: icmp_seq=4 ttl=64 time=0.1 ms

    --- 192.168.2.239 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.1/0.1/0.2 ms

    The country region is same in both.

    This is the "show log system" in the IAP 103:

    # show log system -> http://paste.debian.net/plain/141389

     

    I try to configure the "auto join" in both 103 and 105 (master), in wich device must I configure it?

    Kind regards.



  • 11.  RE: Add IAP to existing VC

    Posted Jan 20, 2015 10:43 AM

    Hi friend,

     

    Let me get some clarity on this.

     

    do you have IAP 105 as a master already ? or trying to bring up both IAPs ?

     

    If you have Master already, please enable Auto join in the master.

     

    please share the output of the following, run these commands on IAP 103

     

    1. show election

    2. debug-master-beacon

     

    we can fix this issue once we go through the above out puts



  • 12.  RE: Add IAP to existing VC

    Posted Jan 20, 2015 11:05 AM

    Hello,

     

    Thanks for your help.

     

    The IAP 105 is set as Master and it is configured as Enabled in "System -> Auto join mode".

    I just reset the IAP 103 device.

     

    Access to the "instant" SSID, change the Country Code (same as the IAP 105).

     

    I see the IP address that it takes from DHCP (same range as the IAP 105).

     

    Connect again to the IAP 105 (master) SSID and access to the IAP 103 from console:

     

    # show election
    State        : Master
    
    master_beacon   : sent=492 rcvd=0
    hierarchy_beacon: sent=0 rcvd=0
    hierarchy_ack   : sent=0 rcvd=0
    beacon_req      : sent=0 rcvd=0
    beacon_resp     : sent=0 rcvd=0
    
    election wait   : 0
    timer slow      : 0
    master high cpu : 0
    ap cpu usage    : 0
    Slave->Pot-Master : 0 time
    Pot-master->Master: 0 time
    Pot-master->Slave : 0 time
    
    last spoof arp rcvd: 0
    last spoof mac: 00:00:00:00:00:00
    last beacon received ticks: 0
    uplink flap count         : 0
    max beacon miss ticks     : 0
    
    hierarchy mode            : 0
    last hierarchy beacon received ticks: 0
    provisioned master denied : 0

     

    # debug-master-beacon
    (nothin in the output)

     The IAP 103 can ping to IAP 105:

     

    # ping 192.168.2.232
    Press 'q' to abort.
    PING 192.168.2.232 (192.168.2.232): 56 data bytes
    64 bytes from 192.168.2.232: icmp_seq=0 ttl=64 time=2.0 ms
    64 bytes from 192.168.2.232: icmp_seq=1 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=2 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=3 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.232: icmp_seq=4 ttl=64 time=0.5 ms
    
    --- 192.168.2.232 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.5/0.8/2.0 ms

     And to the VC:

     

    # ping 192.168.2.239
    Press 'q' to abort.
    PING 192.168.2.239 (192.168.2.239): 56 data bytes
    64 bytes from 192.168.2.239: icmp_seq=0 ttl=64 time=2.1 ms
    64 bytes from 192.168.2.239: icmp_seq=1 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.239: icmp_seq=2 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.239: icmp_seq=3 ttl=64 time=0.5 ms
    64 bytes from 192.168.2.239: icmp_seq=4 ttl=64 time=0.5 ms
    
    --- 192.168.2.239 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max = 0.5/0.8/2.1 ms

     

    Need I configure something else?

     

    Thanks and best regards.



  • 13.  RE: Add IAP to existing VC

    Posted Jan 20, 2015 01:20 PM

    Hi,

     

    The output clearly saying that. IAP 103 is not receiving Master beacons hence it is assuming itself as the Master. we have figure out why it is not able to receive the Master beacon from IAP 105.

     

    Master beacon traffic is L2 traffic hence we have to find the reason why L2 traffic is not getting exchanged.

     

    Console IAP 105 (MAster) and run the same commands and see if you get some hint.

     

    If not, please open a case with TAC.

     

     



  • 14.  RE: Add IAP to existing VC

    Posted Jan 21, 2015 02:32 AM

    Thanks again,

     

    This is the commands in the IAP 105:

     

    # show election
    State        : Master
    
    master_beacon   : sent=0 rcvd=542220
    hierarchy_beacon: sent=0 rcvd=0
    hierarchy_ack   : sent=0 rcvd=0
    beacon_req      : sent=0 rcvd=0
    beacon_resp     : sent=0 rcvd=0
    
    election wait   : 0
    timer slow      : 0
    master high cpu : 0
    ap cpu usage    : 9
    Slave->Pot-Master : 0 time
    Pot-master->Master: 0 time
    Pot-master->Slave : 0 time
    
    last spoof arp rcvd: 0
    last spoof mac: 00:00:00:00:00:00
    last beacon received ticks: 0
    uplink flap count         : 0
    max beacon miss ticks     : 0
    
    hierarchy mode            : 0
    last hierarchy beacon received ticks: 0
    provisioned master denied : 0

     

    # debug-master-beacon
    (nothin in the output)

    Need I force the IAP 103 to be slave device?

     

    Thansk for you help.

     

    Regards.



  • 15.  RE: Add IAP to existing VC
    Best Answer

    Posted Jan 31, 2015 07:21 AM

    in principle you should have to.

     

    if you can i would save the config, reset both devices to factory default and start from there.

     

    if you can't then again go over the basics, firmware version, l2 connectivity, auto add members, no fixed master, ...



  • 16.  RE: Add IAP to existing VC

    Posted Feb 02, 2015 02:27 AM

    Thanks!

     

    I did it and it works.

     

    I reset the IAP105 device, configure the IAP 103 as master, and when I connect the reseted 105 it join automatically.

     

    Thanks for your help.

     

    Regards.



  • 17.  RE: Add IAP to existing VC

    Posted Feb 02, 2015 02:30 AM

    What is the version running on the 105?