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

VC Status "No matching template could be found for this device."

This thread has been viewed 9 times
  • 1.  VC Status "No matching template could be found for this device."

    Posted Jul 28, 2015 02:23 PM

    Hi!

     

    We´re deploying new IAP-205 clusters to an existing Airwave group. All the clusters will have the same configuration. When we deploy a new cluster, it gets provisioned to its Airwave and the correct group, automatically upgrades to the group enforced firmware and gets its configuration from the golden config. Everything works fine and the status of the APs and the VC is "good".

     

    Then, nightly maintenance happens. After the first night, the cluster changes configuration status to: Configuration: Error (No matching template could be found for this device. See the templates page.)

     

    Everything still works fine, but the error is kind of annoying. In the AP Events tab in Airwave for the cluster, we can see the below error messages every night.

     

    Tue Jul 28 00:39:14 2015 Configuration status changed to 'No matching template could be found for this device. See the templates page.' System
    Mon Jul 27 00:38:38 2015 Configuration status changed to 'No matching template could be found for this device. See the templates page.' System
    Sun Jul 26 00:38:23 2015 Configuration status changed to 'No matching template could be found for this device. See the templates page.' System
    Sat Jul 25 00:38:49 2015 Configuration status changed to 'No matching template could be found for this device. See the templates page.' System
    Fri Jul 24 00:38:33 2015 Configuration status changed to 'No matching template could be found for this device. See the templates page.' System

     

    Anyone have any idea why this is happening? We have another customer in a separate Airwave server with the exact same Airwave version, IAP model and IAP version and they don´t see this issue.

     

    The versions we´re running:

    Airwave: 8.0.7.1

    Instant: 4.1.1.4

    Model: IAP-205

     

    Cheers,