Rehoming the Sensor Control

This article explains how to move a Cisco® Assurance Module from one Cisco® Crosswork Assurance Sensor Control to another, referred to as rehoming.

About Rehoming

This Sensor Control rehoming process ensures the following moves along with the module:

• Port and interface configurations
• VCE configurations
• Flowmeter sessions
• Sessions going through the VCEs of the module
• Flow broker Capture and Data configurations
• Policies, regulators and classification profiles
• Encryption keys (if activated)
• Licenses if acquired need to be released.

When rehoming an older Sensor Control release to a newer Sensor Control release, a module upgrade is performed if the automatic upgrade parameter is enabled. The module upgrade must be factored into the link timeout wait period, which is up to one hour.

Requirements and Procedure

Before rehoming the Sensor Control, ensure that you meet the following requirements:

A. Software version of the module can be supported on the destination Sensor Control.

B. The module can be reached or pinged on the destination Sensor Control when online (offline is left unchecked).

C. The module can be discovered by the Discovery setting on the destination Sensor Control.

D. The devices are backed up before rehoming.

E. Moving the module over to the destination Sensor Control will not exceed the target Sensor Control engineering limits (for any of the objects being moved above).

To rehome an Sensor Control

1. Log in to Legacy Orchestrator.
2. Access Devices ► Managed Elements page to view the Sensor Controls required for rehoming.

3. Log in to the source Sensor Control.

4. Access Remote Devices ▶ Configuration to view Assurance Sensor Module(s).

5. Log in to destination Sensor Control.

6. Access Remote Devices ▶ Configuration.
   The Assurance Sensor Module(s) in step 4 will not be displayed yet.

7. Return to Legacy Orchestrator.

8. Access Devices ▶ Device Configuration to view the state of the PM streaming. There are two scenarios:
   a. State of source PM streaming is disabled; therefore, no changes are applied on the destination Sensor Control. Skip to PM collect global settings migration below.
   b. State of the source PM streaming is enabled. In this instance, Legacy Orchestrator will check the PM type one by one and update the active state on the destination Sensor Control.

9. Access Commission ▶ Jobs from Legacy Orchestrator.
   The Job configuration dialog is displayed.
   a. Click the Add button to add a new configuration job.
   b. Set all common configuration job settings, as described in Creating Configuration Jobs in GUI Mode and in Creating Configuration Jobs Using Data Sets.
   c. Select Rehoming in the left pane. The Rehoming tab is displayed.
   d. Choose Migrate unlinked option.
   e. Click the Name field, then click to display the Select Name dialog.
   f. Select an Sensor Control destination and click OK.
   g. Click Apply, then click Close.

10. Access Commission ▶ Jobs Executors.
    a. Click the Add button to add a new executor. The Job execution configuration window is displayed.
    b. Set all common job executor settings, as described in "Executing Configuration Jobs" (Adding a Job Executor).
    c. Drag the jobs that you want to execute from the left pane to the right pane in the Jobs tab.
    d. Click the Device Selection ▶ Modules & SFPs subtab, drag and drop to the right pane, titled Target devices, the module that you are rehoming.
    e. Click Apply.
    f. Select the Status tab and click the Start Job Executor ▶ button. Job executor is now being started. Wait a few minutes for the information to update.
    g. Click the Refresh button to refresh the user interface.

11. After the executor is completed, access the Devices ▶ Managed Elements page in Legacy Orchestrator.

12. Select the source Sensor Control and the destination Sensor Control, then click the Resynch button.
    A pop-up confirmation window will appear, confirming the resynchronization of all selected devices.

13. Click OK.
    After the resynchronization of both Sensor Controls is complete, access Device Selection ▶ Modules & SFPs page and click the Refresh button.
    The modules are now being managed by not only the source Sensor Control but also the destination Sensor Control.

14. Verify in the destination Sensor Control that all modules have been imported.

If there is an issue, the user can unlock the module on the source Sensor Control and delete the constructs on the destination Sensor Control, to return the module to operation on the original Sensor Control.

IMPORTANT: After the rehoming, the module will still remain on the source Sensor Control.

• If the rehoming fails for any reason, the module will be reconnected on the source Sensor Control.
• If the rehoming is successful, the module will be in disconnected state on the source Sensor Control.

PM collect global settings migration

If the PM streaming is enabled on the source Sensor Control, the Legacy Orchestrator will automatically activate PM streaming on the destination Sensor Control and check the PM types one by one:

• If the PM mode is not enabled on the source Sensor Control, then no changes are applied for this PM mode on the destination Sensor Control.
• If the PM mode is enabled on the source and destination Sensor Controls, then no changes are applied on the destination Sensor Control.
• If the PM mode is enabled on the source Sensor Control but the PM mode is not enabled on the destination Sensor Control, the Legacy Orchestrator will activate this PM mode on the destination Sensor Control and give the period of the source Sensor Control.

In the case of multiple source Sensor Controls, the same rules apply. It is a merge where all activated modes amongst different source Sensor Controls will be activated in the final destination Sensor Control.

Restoring the Sensor Control

Note that if rehoming was unsuccessful, the Sensor Control will need to be restored to previous settings. However, if rehoming was successful, the Sensor Control must not be restored to previous settings. Otherwise, certain configurations will be lost.

To restore the Sensor Control to previous settings, refer to "Restoring the Configuration of a Device from Backup".

Known Limitations

This section explains known limitations related to the module rehoming feature.

Resyncing the Managed Elements

Before the user performs a rehoming procedure on any device, a resynch of the managed elements to be rehomed should be performed. If the forced resynch is disabled, then a manual resynch is recommended after rehoming the device; otherwise the user can expect to wait up to 15 minutes for the scheduled resynch.

Before the user attempts rehoming a module to another Sensor Control, ensure there is a discoverer configured and enabled on the endpoint where the discovery inventory contains the module.

Job Executor and Multiple Steps

The rehoming step cannot be executed at the same time as other steps, otherwise the job executor fails and the module cannot move to the destination Sensor Control.

Flow Executors

The rehoming process cannot be performed alongside other steps; flow executors cannot be used with a rehoming step.

Session Relocation

If several commission configuration jobs are executed in parallel, i.e by selecting more than one module at a time in the job executor, there is no validation on the aggregate of these jobs' resulting number of sessions on the target endpoint. This will leave sessions exceeding the limit not moved to the target endpoint, and they will not be restarted. The "Last update status“ will be “ERROR“ for such sessions. The module rehoming is not rolled back.

Rehoming the module successfully and moving up to 2,000 sessions per module requires several minutes. Therefore, it is good practice to check that the rehoming process is complete prior to performing the next. This can be accomplished with a search in the Sessions view or by simply searching for Last update status; the status will be INPROGRESS during rehoming and then COMPLETED.