This article aims to describe the process to replace an existing device in Juniper Apstra. 

It's important to note that a single Juniper Apstra Agent cannot be used for two distinct hardware devices. Prior complete device decommissioning is mandatory.

The replacement process in Juniper Apstra is split into two main phases:

1. Device Decommissioning: This involves removing the existing device from the Blueprint and Managed Devices.
2. Device Onboarding: This phase is about installing the device's agent and re-onboarding the new hardware to the blueprint.

Please follow the steps below:

Device decommissioning

1. Select the Device:
   • Navigate to the Juniper Apstra Blueprint where the device is assigned
   • Go to the Staged tab, select Physical > Topology, and choose the device you want to replace.

2. Undeploy the Device:
   • In the right side panel, click on the 'Device' tab
   • Edit the 'Deploy Mode' and select 'Undeploy'

3. Remove the Serial Number:
   • From the same tab, edit the 'S/N' option and click the red delete button to remove the device S/N.
   • Ensure the S/N is removed and the Deploy Mode is set to 'Undeploy'.
   • Move to the 'Uncommitted' tab and commit the change.

4. Decommission the Device:
   • Go to Devices > Managed Devices from the left menu.
   • Find the device, click on the three dots option in its row (last button on the right side), in the Device menu, click on the edit button, set the Admin State to 'DECOMM' and Update.

5. Remove the Agent:
   •  Please follow the instructions based on your scenario: 
     • If the device has communication with your Apstra Controller. Click on the three dots button in its row, click on the 'Uninstall' option from the Agent's column and once done, click 'Delete' in the same Agent's menu.

• If the device is disconnected or lacks connectivity: 
  • For Juniper Apstra > 4.1.1:  Click on the three dots button in its row, click on the 'Uninstall' button on the Agent's column, the job state will be 'Failed', click on the 'Delete' button on the Agent's column and select 'Force delete?', confirm. 
  • For Juniper Apstra <= 4.1.1: Click on the three dots button in its row (In Juniper Apstra < 4.1.0, you can find this option from Devices > Agents), in the Agent's column, click on the edit button and set the 'Operation Mode' from 'Full Control' to 'Telemetry Only', update. Click on the 'Uninstall' option from the Agent's column, followed by 'Delete'.

6. Delete the Device:
   •  Click on the three dots button, choose 'Delete' in the Device's menu. You should no longer see the device in Managed Devices.

Device Onboarding

1. Configure the new Device with pristine config
   • Configure the new device with recommended minimum configuration (pristine)
   • A minimum configuration example can be seen in the Juniper Apstra User Guide's Agent section: offbox or onbox
2. Install the Agent:
   • Navigate to Devices > Managed Devices.
   • Click 'Create Onbox Agent' or 'Create Offbox Agent' (Junos supports only the Offbox Agent). Provide the IP address, platform and credentials or Agent Profile.
3. Acknowledge the new Device:
   • Once the agent is installed, a new entry for the device will appear in Managed Devices with the state 'OOS-QUARANTINED.'
   • Select the device in the first column, and from the top menu, click 'Acknowledge selected systems' in the Device's options, this will make the device available in the Blueprint and the state will change to OOS-READY.
     
4.    Re-assign the Device in Blueprint:
   • In your Blueprint, navigate to Staged > Physical > Topology.
   • Click on the replacement device, and in the right panel, set 'Deployment Mode' to 'Deploy' and update the 'S/N' with the new device's Serial Number.
   • Confirm these fields, move to the 'Uncommitted' tab, and commit the change.
     
5. Final Check:
   • Verify any anomalies with the device. Some probes might take up to 120 seconds to update details.
   • The device should now be 'IS-ACTIVE' in Managed Devices and associated with the blueprint.

19/09/2023 - Initial version

Apr 8, 2025 - Device Onboarding section updated based on the customer feedback - case 2025-0407-662475 [NTHRIVE, INC.]