Contents
Introduction
When a network device fails, replacing it manually can require re-adoption, credential configuration, and recreation of existing settings, resulting in increased downtime and operational overhead. To simplify device replacement, Omada Controller provides the Replace with Spare feature, which allows a spare device to automatically inherit the configuration and logical relationships of a failed AP or switch.
Omada Controller v6.4 introduces a new Pending Device replacement method, enabling administrators to select a controller-discovered device directly without entering a Device Key. Unlike the traditional Device Key method, the Pending Device method does not require Cloud Access or Device Management Access, providing a simpler replacement workflow for local controller deployments.
This article explains how to configure and use both replacement methods in Omada Controller v6.3 and above.
Requirements
- Omada Controller v6.3 and above (Software / Hardware / Cloud-Based)
What's new in Omada Controller v6.4
The Replace with Spare feature now supports a new Pending Device method.
Compared with the Device Key method, the Pending Device method:
- Allows controller-discovered devices to be selected directly
- Eliminates the need to manually enter a Device Key
- Does not require Cloud Access or Device Management Access
- Simplifies replacement workflows in Local Controller and Cloud-Based Controller deployments.
Note:
- Only APs and switches support the Replace with Spare feature.
- The replacement device must belong to the same model family as the original device (for example, SG3428 v2.3 and SG3428 v2.4 are considered the same model family).
- The replacement device must not already be assigned as a spare device for another device.
- Configuration differences caused by hardware inconsistencies may be shown during device replacement. Upgrading to the latest firmware version is recommended before replacement.
- Cloud Access and Device Management Access are required only when using the Device Key method because Device Key resolution relies on cloud services. The Pending Device method introduced in Omada Controller v6.4 does not require Cloud Access.
- If the original device is bound to a device template, the template must be unbound or the replacement device must match the same model and version.
- Mesh AP is supported. Switch stacking and MLAG are not supported.
- Country code validation applies to AP devices.
Configuration
Cloud Access (Settings > Cloud Access) and Device Management Access (Settings > System Settings > Device Management Access) are required only when using the Device Key method. They are not required when using the Pending Device method introduced in Omada Controller v6.4, because the controller can directly select a discovered device from the Pending Device list.
Step 1. Go to the Sites > Devices page in the Omada Controller, select the device that needs to be replaced, and navigate to its details page. Click the Replace with Spare option to open the replacement configuration window.
Step 2. Select an Import Method for the spare device.
Device Key Method
- Select Device Key.
- Enter the Spare Device Key found on the replacement device packaging.
- Optionally configure Username and Password.
Pending Device Method (New in Omada Controller v6.4)
- Select Pending Device.
- Choose a device with status Pending or Managed by Other from the drop-down list.
- Optionally configure Username and Password if required.
Click Apply to save the replacement configuration.
New in Omada Controller v6.4: The Pending Device method allows administrators to directly select a controller-discovered device as the spare device without entering a Device Key.
Note: Only devices with status Pending or Managed by Other can be selected when using the Pending Device method.
Step 3. Verify Replacement Status.
After applying the configuration, a replacement icon will appear next to the device name in both the Devices list and the device details page. This indicates that the device has been successfully configured for replacement and is currently in a pending replacement state.
Step 4. Execute Device Replacement. Once the spare device is powered on and connected to the network, and the original (faulty) device is offline or disconnected, the controller will automatically adopt it using the provided or default credentials.
For the Pending Device method, the spare device must already be discovered by the controller and appear in the Pending Device list before it can be selected for replacement.
If the replacement is successful, the new device will inherit all of the configuration and logical associations of the original device, allowing the network to be restored without manual reconfiguration.
A success notification popup will be displayed on the frontend, and an Event Log entry will be recorded. The original device will be automatically forgotten (removed), and the new device will appear as Connected, inheriting the original device’s configuration and logical relationships.
If the replacement fails, a failure popup will be shown and an Alert Log will be recorded. The original device will be retained, and the new device will not inherit its configuration. The new device may show as Adoption Failed or Adopted; if it appears as Adopted, it usually means the replacement workflow failed and the device entered the default adoption flow instead.
Common causes include incorrect Device Key or credentials, the original device not being fully offline, network issues, or the spare device being in an unexpected state. The popup will include an error code and message, which should be used for troubleshooting.
To retry, do not click the Retry button on the new device (this triggers normal adoption).
Instead, re-initiate replacement via Replace with Spare. Before retrying, ensure the original device is offline, credentials are correct, the spare device is reachable, and check logs or the error code for guidance.
Step 5. Modify or Cancel Replacement (Optional). If needed, you can revisit the replacement configuration by clicking the replacement icon or the Replace with Spare entry again on the device details page. From there, you can update the Device Key or credentials, or click Cancel Replacement to remove the current replacement configuration.
If a replacement attempt fails, the replacement icon will disappear. In this case, you need to click Replace with Spare to re-enter and modify the replacement configuration.
Conclusion
The Replace with Spare feature helps reduce service disruption by allowing replacement APs and switches to automatically inherit the configuration of failed devices. In addition to the original Device Key method, Omada Controller v6.4 adds support for the Pending Device method, allowing controller-discovered devices to be selected directly without requiring a Device Key, Cloud Access, or Device Management Access. By choosing the appropriate replacement method, administrators can simplify device recovery, reduce deployment effort, and restore network services more efficiently.
To learn more about each function and configuration, please visit Support Home to download or check the manual for your product.
