Hardware Lifecycle States

Oracle Enterprise Communications Platform (Oracle ECP) maintains a lifecycle state for each hardware object that it manages. After you onboard hardware, the Inventory and Request pages displays up-to-date information about each Cloud Connector and Device, including this lifecycle state, which can transition across all interactions with the platform.

Understanding the lifecycle states for devices and Cloud Connectors helps ensure equipment can exchange data with the Oracle ECP platform and be managed effectively. While devices and Cloud Connector share several lifecycle states, some are hardware specific. The actions available on individual devices and Cloud Connectors in inventory depend on their current lifecycle state. Cloud Connectors and Devices share the three essential lifecycle states. The following table adds valid actions available on a Cloud Connector.

Lifecycle State	Description	Valid Actions
Onboarded	The onboarding request from Oracle ECP has completed successfully, and the platform is waiting for the device or Cloud Connector to connect to ECP cloud.	Edit Move Edge Nodes Decommission Change APN (MNO) Change Data Plan (MNO) Change Service Plan (Satellite)
Inactive	The initial state when onboarding to Oracle ECP has started for a device or Cloud Connector. Onboarding is not complete at this phase, and the equipment cannot send data or communicate with the cloud. The Inactive lifecycle state can also indicate that equipment is not functioning – for example, due to an issue or because of a manual action a local user performs (for example, as part of troubleshooting). An administrator controlling a device or Cloud Connector from the cloud can also change the lifecycle state to Inactive.	Edit Move Edge Nodes Decommission Change APN (MNO) Change Data Plan (MNO) Change Service Plan (Satellite)
Active	The device or Cloud Connector has connected with Oracle ECP and has been Authenticated. The hardware can communicate with Oracle ECP and is ready for functionality or monitoring tasks.	Edit Reboot^Foot 1 Move Edge Nodes Manage Application^Foot 1 Manage Platform^Foot 1 Get Platform Logs^Foot 1 Decommission Change APN (MNO) Change Data Plan (MNO) Change Service Plan (Satellite)

Lifecycle State

Description

Valid Actions

Onboarded

The onboarding request from Oracle ECP has completed successfully, and the platform is waiting for the device or Cloud Connector to connect to ECP cloud.

Edit
Move Edge Nodes
Decommission
Change APN (MNO)
Change Data Plan (MNO)
Change Service Plan (Satellite)

Inactive

The initial state when onboarding to Oracle ECP has started for a device or Cloud Connector. Onboarding is not complete at this phase, and the equipment cannot send data or communicate with the cloud.

The Inactive lifecycle state can also indicate that equipment is not functioning – for example, due to an issue or because of a manual action a local user performs (for example, as part of troubleshooting).

An administrator controlling a device or Cloud Connector from the cloud can also change the lifecycle state to Inactive.

Edit
Move Edge Nodes
Decommission
Change APN (MNO)
Change Data Plan (MNO)
Change Service Plan (Satellite)

Active

The device or Cloud Connector has connected with Oracle ECP and has been Authenticated. The hardware can communicate with Oracle ECP and is ready for functionality or monitoring tasks.

Edit
Reboot^Foot 1
Move Edge Nodes
Manage Application^Foot 1
Manage Platform^Foot 1
Get Platform Logs^Foot 1
Decommission
Change APN (MNO)
Change Data Plan (MNO)
Change Service Plan (Satellite)

^Foot 1

ECP tracks additional transient lifecycle states with the following states on the Requests page to indicate the progress of onboarding and offboarding:

Submitted: The initial state of Device or Cloud Connector submitted to be onboarded on ECP cloud.
Pending SIM: The state of cellular equipment waiting for the assignment of a SIM card.
Onboarding: The state of a Device or Cloud Connector for which the onboarding request has been submitted for processing by downstream systems.
Failed: The state of a Device or Cloud Connector that could not be onboarded due to some internal error or for which SIM assignment was rejected due to unavailability of the requested SIM.

Additional Cloud Connector Lifecycle States and Updates

Each Cloud Connector runs a tightly controlled OS and system container stack. To maintain security, feature availability, and compatibility with your Oracle ECP environment, Cloud Connectors must be kept up to date. Cloud Connector upgrades are managed centrally, ensuring they all stay in sync with ECP’s latest capabilities and compliance requirements.

Administrators have full management capabilities through the Oracle ECP cloud UI — everything from configuration to monitoring and updates is available with no special user action. Most users will find that Cloud Connectors remain “Active” and require no manual intervention.

Unattended Upgrades

To simplify device management and security, all Cloud Connectors are set to upgrade themselves automatically when a new platform release becomes available. This process is unattended, meaning the Cloud Connector will detect its own version (“Active,” “Restricted,” or “Outdated”) and perform any needed updates in the background. Administrators do not need to initiate or manage these upgrades—Oracle ECP orchestrates the process centrally, making sure all Cloud Connectors are kept up-to-date with the latest capabilities and compliance standards.

Note:

You still can perform discretionary upgrades. See the Update the Cloud Connector Platform section.

Behavioral Exceptions: Transitory States

During certain periods, particularly after cloud upgrades or if a Cloud Connector has not been connected for some time, it might be running an older version. To manage compatibility and feature differences, ECP uses two additional lifecycle states—these are temporary and only occur during the automated upgrade window:

Restricted: If a Cloud Connector is 1 or 2 major/minor versions behind the up-to-date version, it enters the “Restricted” state. In Restricted, basic and existing features remain available, but new features introduced in later releases will not function until the Cloud Connector completes its upgrade. The UI may display a banner or warning, but the system will update the Cloud Connector as soon as possible—no user action is necessary. You will also observe a corresponding incident of appropriate severity in the issues Tab.
Outdated: If a Cloud Connector is running 1 version ahead of the cloud, which is rare, but can occur in staggered updates, or is 3 or more versions behind, it moves to the “Outdated” state. In this case, only fundamental operations such as upgrade and reboot are permitted, and all other local management actions are locked. You will see a corresponding incident with the appropriate severity listed in the Issues tab, and a red banner indicating that the Cloud Connector is in an outdated state will appear on that Cloud Connector’s details page. When in the Outdated state:
- The only allowed actions on a Cloud Connector are
  - Reboot^Foot 1
  - Move Edge Nodes
  - Manage Platform^Foot 1
  - Decommission
  - Change APN (MNO)
  - Change Data Plan (MNO)
  - Change Service Plan (Satellite)
- The right panel content is hidden and an error banner indicates outdated software is running.
- Previously activated Cloud Connectors in this state must be manually updated with the Manage Platform function.

Both Restricted and Outdated are designed to be temporary, self-correcting states. Oracle ECP works to resolve these conditions automatically through its unattended upgrade process. Once complete, the Cloud Connector returns to Active state, regaining full functionality and management capabilities.

Note:

Lifecycle states are managed based on major and minor software release versions; new patches do not prompt auto upgrades.

MDM Device Lifecycle and Connectivity States

Devices managed by MDM have dependencies on the MDM platform.

MDM-Enabled Devices progress through the three standard Oracle ECP lifecycle states. When an MDM-enabled device is onboarded to Oracle ECP, the lifecycle state changes to Onboarded. At the point when an MDM-enabled device is registered on Ivanti Neurons for MDM, and ECP is alerted of this, the lifecycle state in Oracle ECP changes from Onboarded to Active. The Wipe action for an MDM-enabled device provides two actions. First you can just Wipe the device which will leave it reset to the factory settings, but Active in Oracle ECP. You can also choose to Wipe and Deactivate the device, and this will leave it set to Inactive.

Connectivity States based on Connectivity Type

The connectivity type an MDM-managed device uses plays a part in determining that Device's connectivity state. For both Customer Managed Connectivity and WiFi/Ethernet connectivity, if the device has not communicated with the MDM service for more than 65 minutes, it is considered disconnected at the MDM level. Refer to the following tables:

Table 3-1 Customer Managed Connectivity

MDM Connectivity	ECP Device Connectivity State
Connected	Connected
Disconnected	Disconnected

Table 3-2 WiFi/Ethernet Connectivity

MDM Connectivity	ECP Device Connectivity STate
Connected	Connected
Disconnected	Disconnected

Table 3-3 Cellular Connectivity

Connectivity per Connection	ECP Device Connectivity State
MDM - Connected Cellular - Connected	Connected
MDM - Connected Cellular - Disconnected	Connected
MDM - Disconnected Cellular - Connected	Connected
MDM - Disconnected Cellular - Disconnected	Disconnected

Footnote Legend

Footnote 1: These actions are not available if the Cloud Connector is in a Disconnected connectivity state.