You can move an Enterprise Monitoring Point (EMP) from one organization to another but any paths and monitoring history associated with the monitoring point are not moved. These can, however, be moved to another monitoring point in the old organization. You need to be an Organization Admin or Advanced user in the old and new organizations in order to move a monitoring point between them.

To move a monitoring point between organizations:

  1. Download the nis.config file for the new organization.
  2. Update the monitoring point with the new nis.config settings.
  3. Finalize the move to the new organization.
  4. Clean up the monitoring point from the old organization.

Download the nis.config file for the new organization

The nis.config file is used to associate a monitoring point with an organization. It is normally configured as part of a monitoring point setup but it can be obtained independent of the setup procedure in order to associate a monitoring point with a different organization.

To download the nis.config file for the new organization:

  1. Change organization to the new organization.
  2. Navigate to > Manage Monitoring Points > + Add Monitoring Points > Physical Monitoring Point > Direct Connect.
  3. Click Download File.
    • The nis.config file is downloaded to your computer.

Update the monitoring point with the new nis.config settings

The procedure used to update the monitoring point with the new nis.config settings depends on the monitoring point model.

Update with new nis.config

  1. Change organization to the old organization.
  2. Log in to Web Admin on the monitoring point.
  3. Decommission the monitoring point.
    • When the monitoring point is decommissioned you can no longer access it via APM. You need to use it’s hostname or IP address to access it.
  4. Log in to Web Admin on the monitoring point using its hostname or IP address.
  5. Navigate to Appliance Configuration > PathView Cloud Configuration.
  6. Click Choose File.
  7. Select the downloaded “<org-name>_nis.config” file.
  8. Click Save.
  9. Click OK.
    • The monitoring point restarts. Once restarted, it will be associated with the new organization.

Update with new nis.config

  1. Change organization to the old organization.
  2. Log in to Web Admin on the monitoring point.
  3. Decommission the monitoring point.
    • The monitoring point will take a while to restart.
    • When the monitoring point is decommissioned you can no longer access it via APM. You need to use it’s hostname or IP address to access it.
  4. Log in to Web Admin on the monitoring point using its hostname or IP address.
  5. Navigate to Monitoring Point Settings > APM Connection.
  6. Open the downloaded “<org-name>_nis.config” file in a text editor.
  7. Update the settings on the Connect to APM page to match those in the nis.config file.
  8. Click Submit.
    • The nis.config settings on the monitoring point are updated and the monitoring point connects to APM under the new organization.

Update with new nis.config (via Admin API)

  1. Rename the downloaded file to “nis.config” (i.e., remove “<org-name>_” from the filename).
  2. In APM, Change organization to the old organization.
  3. Decommission the monitoring point.
    • The monitoring point will take a while to restart.
    • When the monitoring point is decommissioned you can no longer access it via APM. You need to use it’s hostname or IP address to access it.
  4. Log in to Web Admin on the monitoring point using its hostname or IP address.
  5. Access the Admin API on the monitoring point.
  6. Navigate to NIS confirguration > POST /nis/file/.
  7. In the Parameters section, in the nis_config_file parameter, click Choose File and select the “nis.config” file.
  8. Click Submit.
    • The nis.config settings on the monitoring point are updated and the monitoring point connects to APM under the new organization.

Finalize the move to the new organization

When a new monitoring point initially connects to an organization in APM it needs to be licensed and have its location specified. At that point the monitoring point is available in the new organization and new paths can be created or existing paths can be moved to the monitoring point.

To finalize the monitoring point’s move to a new organization:

  1. In APM, change organization to the new organization.
  2. If prompted, specify the monitoring point licensing. Otherwise, assign a base license and any add-on licenses required.
  3. If prompted, specify the monitoring point location. Otherwise, set the location directly.

Clean up the monitoring point from the old organization

Moving a monitoring point to a new organization does not remove it from the old organization. From the perspective of the old organization, the monitoring point is simply disconnected. All paths and monitoring history are still available in the old organization.

To clean up the monitoring point from the old organization:

  1. Change organization to the old organization.
  2. If you want to preserve the paths and the associated monitoring history:
    1. Move old paths to another monitoring point.
  3. Once there are no more paths associated with the monitoring point (or you don’t care if they are deleted), delete the monitoring point from the old organization.