Operations

The Operations panel provides an overview of operations launched on the AMM. This feature is only available for AMM 2.17.1+.

An operation is a single action derived from a workflow. It is based on a single target.

A workflow is an AMM user action procedure that can target one or more gateways or the AMM itself. It can start immediately or in a scheduled time range.

A workflow can trigger multiple operations. For example, you want to deploy a template to two gateways. This workflow would create two operations, which can be executed concurrently.

deploy template to first gateway
deploy template to second gateway

Sometimes operations cannot be executed concurrently. The AMM will build up the operations in a series of steps to ensure that they are executed sequentially. For example, a user deploys a MG90 4.3 template to one 4.3 gateway (A) and one 4.1.0 gateway (B). The AMM will create the following operations.

deploy template to gateway A running 4.3
upgrade 4.1.0 gateway B to 4.1.2.1
- upgrade 4.1.2.1 gateway B to 4.3
  - deploy template to upgraded gateway B

For gateway B, the second and third operation will stay in the Pending/Initialized state until the upgrade to 4.1.2.1 is completed/cancelled. If for whatever reason the upgrade becomes stuck, the user will need to cancel the workflow/operation, so that the next planned operation can be started.

Information can be filtered by text, time and date, operation state and/or workflow/gateway.

The text box will search for the specific text in the report.
The time period can be set to : Created Time, Modified Time, Expired Time.
To select a time period, select one of the following : Last Hours (Default), Previous Days, Previous Months and Range.
The operation state is displayed as a selection of colour coded toggle buttons. By default the buttons are all set to be selected, as indicated by the grey background of the button. The states available are Initialized , Pending , In Progress , Cancelling , Canceled , Completed , Completed with failure , Failed , Expired .

Note: From AMM 2.17.2, additional information is displayed under the State column to assist the user.

By default Group by workflow is set. Alternatively the user can set to Group by gateway.

Note: For AMM 2.17.2 and higher, the AMM has had an expiration function and a purge function added, to manage the operations. By default at midnight after 10 full days, the AMM will set any unfinished operations to the Expired state. By default after 90 days, the AMM will purge the operations that have a state of Expired, Completed, Failed, or Cancelled. The default time is configurable and set at the server level and requires a reboot of the system. Please speak to Sierra Wireless support if you wish to change this on your appliance.

Group by workflow

Viewing Workflow Progress

The workflow progress is displayed as a progress bar , which shows the distribution of operation states.

When hovering over the progress bar, an information balloon will appear displaying the total number of operations in each state.

When hovering over an Operation, an information balloon will appear showing more detail.

If any template used for deployment has since been deleted, it will be marked with [Deleted].

Note: The Software update operation state will change to Completed when the updated SoftwareVersion event is received after the reboot. In comparison, on the Software Distibution page, the Last Updated Status will change to Success when a Startup event is received. Therefore there will be a delay when comparing the two statuses.

Cancelling a Workflow

To cancel a workflow, select the workflow(s) and then click on the Cancel button. The AMM will display a confirmation dialog with the affected and unaffected workflows. The reasons for each operation for unaffected and affected workflows are shown by selecting the appropriate header. If the operation is already In Progress, it may not be possible to cancel, however the AMM will attempt to do so. Press the Submit button when ready to continue.

Note: If the workflow consists of a software upgrade that is In Progress and a template deployment that is Pending, then the AMM may fail to cancel the workflow because it is already installing the upgrade. The Software Distribution screen will show the latest version in the Current version column after the gateway finishes upgrading and reports back into the AMM. The template deployment can be cancelled by changing the view to Group by gateway, selecting the template deployment operation and then cancelling.

Deleting a Workflow

A workflow cannot be deleted until all workflows are either in a Cancelled state or a Completed state. To delete a workflow, select the workflow(s) and then click on the Delete button. The AMM will display a confirmation dialog with affected and unaffected workflows. The reasons for each operation for unaffected and affected workflows are shown by selecting the appropriate header. Press the Submit button when ready to continue.

Group by gateway

Viewing Gateway Progress

Using Group by gateway, allows the user to see what operations are applicable on a per gateway basis.

All the functions available on Group by workflow are similiarly available using Group by gateway.

Cancelling an Operation

To cancel an operation, select the operation(s) and then click on the Cancel button. The AMM will display a confirmation dialog with the affected and unaffected operations. The reasons for unaffected and affected operations are shown by selecting the appropriate header.

Note: If the operation is a software upgrade that is already In Progress, it may not be possible to cancel. If the upgrade operation fails to be cancelled, then the Software Distribution screen will show the latest version in the Current version column after the gateway finishes upgrading and reports back into the AMM.

Press the Submit button when ready to continue.