Always Follow Cloud Configuration Follow
- ecCLOUD provides “Always Follow Cloud Configuration” feature which ignores configuration received from device local side.
- This feature is independent of device firmware version. Cloud administrator can simply enable on any devices.
- Once user enabled “Always Follow Cloud Configuration”, after first synchronization in cloud, cloud will ignore all configuration tasks received from the device, the cloud configuration will not be affected.
- If there is any dispute between cloud and the device, ecCLOUD will notify cloud administrator with the message of “The configuration between cloud and device is not matched”. The “Configuration status” will be marked as “Configuration is not matched”.
- Cloud administrator can choose to push the configuration manually or automatically by enabling “Auto follow cloud config” to resolve the status of “Configuration is not matched”.
How to enable "Always Follow Cloud Configuration"?
In "Register new devices" page, there is a toggle switch for "Always Follow Cloud Configuration".
Once you enable in this page, devices add it successfully will be enabled.
Note: "Always Follow cloud configuration" will automatically be disabled when device was added by QR code onboarding.
You can also enable/disable this feature for multiple devices in devices page.
User can check the status in Site level device management page.
Manage Follow Cloud Configuration
If user wants to enable/disable this feature to all devices of one site, please click "MANAGE FOLLOW CLOUD CONFIGURATION".
Configuration received
Once enable "Always Follow Cloud Configuration", ecCLOUD will not change anything to device.
However, if there's anything changed in device and ecCLOUD received config from device, The configuration stored in cloud side will not be updated.
Configuration is not matched
Once device configuration changed and cloud received it, the configuration stored in ecCLOUD will not be affected by device.
Due to configuration between ecCLOUD and device is different, eCLOUD will marked configuration state as "Configuration is not matched" when device changed configuration.
User can choose to push cloud configuration to device to synchronized.
Please be noted that ecCLOUD update the configuration states definition:
Configuration failed
- Result of:
- Configuration change task failed.
- Configuration change task timeout
“Configuration status” will be marked as “Configuration failed”, user needs to check if the failed reason is caused by wrong configuration or check the connection quality between ecCLOUD and device.
Configuration is not matched
- Result of:
- Configuration received and ignored by Lock configuration
- Configuration version mismatch
“Configuration status” will be marked as “Configuration is not matched”.
How to resolve it?
To resolve this configuration state, we have to push configuration into device again:
- You can click "SYNC NOW" in device level configuration.
- You can click force push configuration in Site level devices page.
- You can also enable "Auto follow cloud config" to push configuration automatically.
Limitation
- User cannot initiate firmware upgrade process on device enabled "Always follow cloud configuration", please disabled this feature before firmware upgrade.
- Due to "MSP mode with Local Configurable" allow user to configure in local web GUI, enable Always follow cloud configuration will cause device configuration cannot be updated to ecCLOUD properly.
Please do not enabled both features at the same time.
Comments
0 comments
Please sign in to leave a comment.