Configuration synchronization changes
We've changed the way we handle incoming configurations (from the device) at the cloud level, to make it more clear what the state of your device's actual configuration is, and to help re-apply configuration settings in the event that the device is running a different configuration than the cloud.
This mainly affects cases where a "bad" configuration is pushed down to a device, causing the device to revert and resend its old configuration back up to the cloud.
Before this change, the device's out-of-date set of config settings would be merged in with the cloud's version of the configuration, creating a lot of device-level overrides, and making it a pain for you to re-configure your device.
Now what will happen is that the device will be put into a "Warning" health state, you will receive a "Received Config" task failure email, and an alert will be created letting you know that the device's configuration is not in sync with what's on the cloud.
It will also be quite obvious from the device's configuration page that configuration is out of sync with the cloud:
If your device gets in this state, you can choose to go ahead and try to resend the same configuration (this works if the configuration doesn't break the network settings - and is useful in cases like a power outage), or you can figure out why the device was rejecting the config, fix it, and then push down new settings.
Other notable changes
Device-to-cloud communication is now allowed over port 443 in addition to the standard 5222. This is useful when installing devices behind a firewall that blocks the default XMPP ports.
Your devices will automatically figure out which port works best for them, so you won't have to do anything.
Note: Your devices must be running firmware v1.1.3+, which we'll be updating for beta/badge-of-courage users very soon.
Remote syslog configuration settings have been added to the Services configuration tab.
Client OS type is now recorded for your wireless clients and can be viewed on any of the clients pages. NOTE: Your devices must be running v1.1.3+ firmware in order for this feature to work.
- VPC (Virtual Private Cloud) is in the beta testing phase
- The same goes for MetroLinq - a few bugs have already been reported and fixed.