Searching...
Gateway Configuration States
Some AMM screens (e.g. Configuration Control screen) include a field that indicates a device’s configuration state.
The following table lists the possible states:
| State | Description | Available Functions/State Transitions |
| In Sync | The configuration of the gateway is synchronized with the AMM, which means that the repositories of the gateway and AMM are an exact copy of each other. | ▪ Revert: the gateway’s configuration state will transition to Pending (sync from device). |
| Pending (sync to device) | The configuration between the device and AMM is pending synchronization due to one of the following reasons: ▪ Changes have been made on the AMM but are waiting for a user to review and apply them before they will be pushed out to the gateway. Therefore the gateway and AMM are not in sync. ▪ Changes were detected in the AMM’s configuration repository. The changes will be automatically pushed to the gateway. ▪ The configuration is waiting to be rolled forward to that on the AMM. | ▪ Revert: the gateway’s configuration state will transition to Pending (sync from device). ▪ Apply: applies the selected configuration(s) from the AMM. The gateway’s configuration state will transition to Pending (sync to device) |
| Pending (sync from device) | The configuration between the device and AMM is pending synchronization due to one of the following reasons: ▪ Changes were detected on the gateway. The changes will be automatically pulled from the gateway by the AMM. ▪ The configuration is waiting to be rolled back from that on the AMM. ▪ A file needs to be updated. ▪ A file is being generated. | ▪ Revert: the gateway’s configuration state will transition to Pending (sync from device). |
| Pending (device registration) | The AMM is waiting for the device to check in for the very first time. | |
| Pending (firmware update) | The AMM is waiting for a firmware update operation to complete on the device before starting the configuration deployment. | |
| Error | A configuration template validation error or configuration template deployment error occurred during configuration (e.g., the remote configuration is not set up, there was a failure to generate a file, etc.). | |
| Error (configuration being reset) / Error (configuration has been reset) | The device is currently resetting its software back to the factory default configuration, or has successfully completed this process. This state may also occur after an MG90 gateway is upgraded to 4.3.1. If this happens, use Revert to transition back to Pending (sync from device). | ▪ Revert: the gateway’s configuration state will transition to Pending (sync from device). |
| Conflict (user action required) | The configurations on both the AMM and on the gateway have been modified. To resolve this, choose the desired configuration to use, and overwrite the other configuration with it. | ▪ Revert: the gateway’s configuration state will transition to Pending (sync from device). ▪ Apply: applies the selected configuration(s) from the AMM. The gateway’s configuration state will transition to Pending (sync to device) |
| Confirmed (applicable to ALEOS devices only) | A configuration change was sent to an ALEOS device and the device confirmed the change at the time indicated. | ▪ Revert: the gateway’s configuration state will transition to Pending (sync from device). ▪ Apply: applies the selected configuration(s) from the AMM. The gateway’s configuration state will transition to Pending (sync to device) |
| Confirmed with warnings (applicable to ALEOS devices only) | A configuration change was sent to an ALEOS device or the configuration was partially synchronized, and the device confirmed the change at the time indicated, along with warnings. | ▪ Revert: the gateway’s configuration state will transition to Pending (sync from device). ▪ Apply: applies the selected configuration(s) from the AMM. The gateway’s configuration state will transition to Pending (sync to device) |