Controllerless Networks

last person joined: 2 days ago 

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
Expand all | Collapse all

Instant AP Mismatch in Airwave, not VC

This thread has been viewed 3 times
  • 1.  Instant AP Mismatch in Airwave, not VC

    Posted Nov 01, 2015 08:14 PM

    Have 3 Instant clusters deployed with 10-30 APs in each.  AMP discovered APs and they're now all in AMP.  Each cluster is in its own Folder and Group.  Fetching the VC config and creating the template changed VC state to Good.  Auditing the remaining Instants leaves them in Mismatch state, with the difference shown below:

    Device Settings
    Template:
            
            per-ap-settings ac:a3:1e:c5:d3:a4
              a-channel 0 0
              a-external-antenna 0
              g-channel 0 0
              g-external-antenna 0
    Actual    hostname AP109_SA115_ac:a3:1e:c5:d3:a4
    Desired   hostname ac:a3:1e:c5:d3:a4
              ip-address 10.4.2.109 255.255.248.0 10.4.0.1 0.0.0.0 ""
              swarm-mode cluster
              uplink-vlan 0
              wifi0-mode access
              wifi1-mode access

    Thanks in advance



  • 2.  RE: Instant AP Mismatch in Airwave, not VC

    EMPLOYEE
    Posted Nov 02, 2015 05:12 PM

    In the AP/Devices tab, you can select multiple entries by clicking on "modify devices" just above the table. Select all mismatched IAP then select Import Settings...as an option under the drop down list...then click Import Settings button.  Does that clear it up?

     

    Screen Shot 2015-11-02 at 5.11.20 PM.png



  • 3.  RE: Instant AP Mismatch in Airwave, not VC

    Posted Nov 03, 2015 03:24 PM

    Hi Seth,

    Thanks for the reply.  I had done exactly what you replied with already, which has worked for me in the past.

    Oddly enough, some of the IAPs changed to Good status, while others stayed Mismatched.

    I ended up rebooting and rerunning the procedure, and the remaining IAPs changed to Good.  Not sure why.

    Thanks again for the response,

    Andrew