Field Replacement of a Provider Connectivity Assurance Sensor Control

Software Specifications

This appendix explains how to replace a broken endpoint (hardware) in a running supervision case. All endpoints are assigned a unique node identifier (NodeId). The Node ID is initially set to the same value as the unit identifier (UnitId) during the boot up phase of the endpoint. The Node ID can later be configured in the endpoint CLI.

The new endpoint, which will replace the old endpoint, must be configured with the old endpoint’s Node ID before it can be used in the supervision case. The following section explains the steps required to replace an endpoint.

Procedure Steps for Field Replacement

To replace a Provider Connectivity Assurance Sensor Control with the same IP

1. Log in to the mgr-command of the Legacy orchestrator via the app_mon to find the node ID of the failed Assurance Sensor Control.

2. From the Managed Elements tab in Legacy orchestrator, update the entry for the failed Assurance Sensor Control to the IP address of the replacement instance.

3. Establish connectivity.

4. Restore the last configuration backup to the replacement Assurance Sensor Control via the Devices ▶ Backup & Restore tab.

5. Once the new Assurance Sensor Control has started with the restored configuration, log into the CLI interface and update the node ID to match the node ID of the instance being replaced.

6. In the orchestrator GUI, stop and then restart all sessions associated with this Assurance Sensor Control.

To replace a Assurance Sensor Control with a different IP

1. Log in to the mgr-command of the Legacy orchestrator via the app_mon to find the node ID of the failed Assurance Sensor Control.

2. From the Managed Elements tab in Legacy orchestrator, update the entry for the failed Assurance Sensor Control to the IP address of the replacement instance.

3. Establish connectivity.

4. Restore the last configuration backup to the replacement Assurance Sensor Control via the Devices ▶ Backup & Restore tab.
   

   ---

   Note: Skip step 5 if the failed device has enabled DHCP.

   ---

5. Once the new Assurance Sensor Control has started with the restored configuration, log into the CLI interface and update the node ID to match the node ID of the instance being replaced.

   ---

   Note: Skip step 6 if DHCP is enabled on old device and new device.

   ---

6. From the Managed Elements tab in Legacy orchestrator, update the entry for the new Assurance Sensor Control with the changed IP address.

7. In the orchestrator GUI, stop and then restart all sessions associated with this Assurance Sensor Control.