Understanding Template Status on ALEOS Devices

To effectively manage changes on an ALEOS device, you need to know how it was configured, and when it was configured. The ALEOS status page and the AMM dashboard are able to easily identify this information about the ALEOS device.

ALEOS devices can be configured using three methods.

1. template deploy from the AMM
   
2. template apply from ACEmanager
3. manual changes using ACEmanager

On the AMM, there are several stats that can be setup as thresholds on the dashboard to easily identify configuration changes. For more information on how to setup a threshold, refer to Adding a New Threshold

Template Deploy from AMM

When a template is deployed from the AMM to an ALEOS device, the management template stats will show the name of the last template uploaded, the date and time when it happened, and if the ALEOS device is in sync with the template on the AMM. The stats used on the AMM to report this are :

• ConfigTemplate : the name of the template on the AMM that is uploaded to the ALEOS device.
• ConfigTemplateChange : the date/time when the template on the AMM was uploaded to the ALEOS device.
• ConfigTemplateInSync : if the configuration on the ALEOS device is In Sync with the last template uploaded via the AMM.

Template Apply from ACEmanager

When a template is applied from ACEmanager to an ALEOS device, it will show the name of the template uploaded, the date and time it happened, and if the ALEOS device is in sync with the template. The stats used on the AMM to report this are :

• ACEmanagerTemplate : the name of the template on the ACEmanager that was last uploaded to the ALEOS device.
• ACEmanagerTemplateChange : the date/time when the template on the ACEmanager was last uploaded to the ALEOS device.
• ACEmanagerTemplateInSync : if the configuration on the ALEOS device is In Sync with the last template uploaded via the ACEmanager.

Manual Change using ACEmanager

If the ACEmanager is used for a manual change, then the stat LastConfigurationChange is updated with the date/time and ConfigTemplateInSync and ACEmanagerTemplateInSync are updated to No.

In the above figure, a template was applied from ACEmanager on Aug 6, 2:25:11PM. However it is not In Sync, so the ALEOS device is not using that template.
On Aug 18 8:34:12AM, the AMM deployed a template to the device. It is In Sync, so the ALEOS device is using the AMM template.

The ALEOS device records the time stamp for applying the template first. Then changes are made as per the template. The LastConfigChange stat is updated after the last configuration change is completed.

From the LastConfigChange field, the last recorded configuration change was at Aug 24 11:13:56AM.

Additional Information:

• ALEOS devices must be running ALEOS minimum software version 4.14.0.006 to display template information on the device’s login page when connected directly to the device. This information is not displayed by default, and can be enabled and configured on the device in the Services->Device Status Screen.
• The AMM server version must be 2.17.1 or higher to support the template status feature.
• The date/time stats on the AMM are automatically converted to the timezone of the user logged in.