How does site-level configuration inheritance work?

How does site-level configuration inheritance work?

When site-level configuration inheritance is enabled for a device, your device's final configuration will be made of merging two different sets of configurations: 
  1. The common site level configuration for that product type, and

  2. The device's individual configuration, which includes settings not configurable at the site level, such as advanced radio settings, features unique to a single product, and more importantly, any device-level configuration overrides.  
There are configurable common settings at the site level available for each product type: Wi-Fi devices (this includes all standard Wi-Fi products like Spark, SunSpot, Spark Wave 2, etc), MetroLinq, MeshLinq, Switches, etc*.   

At the time of device registration, you will choose whether or not you want your device to inherit from the site level config, but this behavior can be changed at any time by selecting the appropriate menu option from the device's main menu.


Here's a screenshot of the common site-level configuration settings for our Irvine office.  You can see below that the 5 Ghz radio has one SSID attached to it:

Any other SSIDs you add here will be inherited by all Wi-Fi devices in the site that have site-level config inheritance enabled.

If you navigate to the config page of one of these device's, you'll see:

The "ATCW 5 GHz" SSID was inherited from the site-level config, as indicated by the green site-level origin indicator.

If we modify this SSID from the device-level config, we'd see that an override is created:

Any changes to the site-level SSID will no longer be reflected in this device's configuration since it's being overriden.  Overrides can always be reversed by pressing the purple button near the overriden setting.

Confused about which inheritance policy to choose?

1. Inherit site-level settings
Select this inheritance behavior if you want to manage the devices in your site like a single unit with a common configuration.

This is the most popular way to configure Wi-Fi access devices as well as MetroLinq Omnis.  You might choose this for a hotel, business, or other similar application where enterprise Wi-Fi is deployed.

Even though devices will inherit most of their settings from the site-level, you can always override any site-level settings at the device-level by making changes on the device-level configuration pages.

2. Don't inherit site-level settings
Select this inheritance behavior if you don't want your device to inherit any settings from the site level. 

You might choose this if your device will be used for infrastructure, backhaul, or will be configured independently from the other devices in your site.  This is the typical choice for MetroLinq PtP links.

What if I don't see an option to change my device's inheritance behavior?

If you don't see an site inheritance registration option at device registration, this means we do not yet have site-level inheritance support for your product type.


Prior to February 2018, site-level configuration settings were only available for Wi-Fi access types of IgniteNet Devices. 

The inheritance behavior was also referred to as "Configuration policy", and there were two options, "Enterprise" or "Individually configured".  Devices that were "Individually configured" still inherited a subset of site-level system and service settings, such as local logins and timezone and such.  This was changed after January 2018.

* = Common site level settings are still in development for certain product types, so check back soon if you don't see an option for your product type!

FAQ - Cloud

  1. How does site-level configuration inheritance work?
  2. What happens if I mistakenly send a bad configuration to my devices?
  3. Can I be a member of multiple clouds?
  4. How do I undo disabling a device? I can't find my device anymore!
  5. Can I turn off the LEDs on my SunSpot?
  6. Can I use my APs without having an IgniteNet cloud account?
  7. What do the LED colors on my SunSpot indicate?
  8. How do I start a remote packet capture from the cloud?
  9. How do I blink the LEDs on my device from the Ignite Cloud?
  10. What ports do I need to open on my firewall to connect my IgniteNet device to the cloud?
  11. Can I still configure my devices locally in the web GUI if I have them set up in the cloud?
  12. What is the difference between the owner and administrator user?
  13. How do I assign devices to the cloud?
  14. What happens when one of the cloud controlled devices is reset to factory defaults?
  15. Can I visually confirm if my device has connected to the cloud?
  16. Can I restrict a cloud user to a specific network?
  17. How do I physically highlight one of my installed devices from the cloud?
  18. How many devices can I manage from the cloud?
  19. What is the bandwidth required between my device and the cloud?
  20. How long are my devices' statistics stored in the cloud?
  21. How long does it take my device to connect and get its configuration from the cloud?
  22. What is the polling interval between the cloud and my devices?
  23. Is the traffic between my devices and the cloud encrypted?
  24. Can I export my statistics from the cloud?
  25. Can I reset my device to factory default settings from the cloud?

Feedback and Knowledge Base