The procedures for managing Monitoring Point software depend on the type of Monitoring Point.

Managing software on physical and virtual Monitoring Points

There are a number of procedures that you can use to affect the software version, the network configuration, and the APM access configuration on a Monitoring Point:

The effects of these procedures are summarized in the following table:

Procedure Software change? Network config change? APM access config change?
Upgrade software Y (latest software) N N
Reflash (local image) Y (local image) N N
Reflash (USB image) Y (USB image) N N
Decommission N N Y (factory)(no APM access)
Reset to factory defaults (local image) Y (local image) Y (factory) Y (factory)(no APM access)
Reset to factory defaults (USB image) Y (USB image) Y (factory) Y (factory)(no APM access)

Upgrading EMP software

AppNeta recommends keeping your Enterprise Monitoring Point (EMP) software up to date to take advantage of the latest features and bug fixes. You will see the warning symbol 50x50_trans.png appear at various places in APM (including the Manage Monitoring Points page) when a Monitoring Point is no longer running the latest software version. You can configure APM to have a Monitoring Point upgraded automatically or you can upgrade it manually at any time. Note that the upgrade process can result in a gap of up to 15 minutes of monitoring history.

Configure upgrade automation

AppNeta recommends keeping your Enterprise Monitoring Point (EMP) software up to date to take advantage of the latest features and bug fixes. You will see the warning symbol 50x50_trans.png appear at various places in APM (including the Manage Monitoring Points page) when a Monitoring Point is no longer running the latest software version. You can configure APM to have a Monitoring Point upgraded automatically or you can upgrade it manually at any time. Note that the upgrade process can result in a gap of up to 15 minutes of monitoring history.

Configure upgrade automation

APM provides flexibility in scheduling Monitoring Point software upgrades to conform to your maintenance program. There are three upgrade automation settings:

  • Manual - Upgrades are to be performed manually (no automation).
  • Managed - Upgrades are to be performed automatically when new software is released. This enables you to have the latest software running at all times. The software upgrade schedule is listed on the AppNeta service status page: http://status.appneta.com/.
  • Scheduled - Upgrades are to be performed automatically on a regularly scheduled interval. This enables you to schedule upgrades during your regular network maintenance window. You also have the option of skipping the next upgrade.

To configure Monitoring Point upgrade automation:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to configure, select > Upgrade Settings.
  3. From the Upgrade Type drop-down, select the type of upgrade automation you want to use.
    • If you select Scheduled you will need to specify the upgrade schedule (Note: The upgrade schedule is based on the Monitoring Point time zone).
  4. Click Save.
    • The Monitoring Point upgrade automation is set.

The Upgrade Settings option is also available in the Bulk Action drop-down. Use this feature to configure upgrade automation on multiple Monitoring Points at the same time.

Manual upgrade

The upgrade process can be performed manually at any time to any model of Monitoring Point no matter which of the upgrade automation settings is selected.

To upgrade Monitoring Point software to the latest release:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to upgrade, select > Upgrade Now.
  3. Click OK.
    • The Monitoring Point software is upgraded to the latest release.

The Upgrade Now option is also available in the Bulk Action drop-down. Use this feature to upgrade multiple Monitoring Points at the same time.

Failed upgrade?

If an upgrade attempt fails, try the following:

  1. Retry the upgrade.
  2. Restart the Monitoring Point then retry the upgrade.
  3. Physically power the Monitoring Point off for 10 seconds then back on and retry the upgrade.
  4. Reflash the Monitoring Point using the latest image.

If you are still unsuccessful, contact AppNeta Support.

Reflashing an EMP - local image

Reflashing an Enterprise Monitoring Point (EMP) (local image) involves rewriting the Monitoring Point file system with a software image stored on the Monitoring Point. All configuration information is saved during a reflash. This procedure is typically only required when troubleshooting a problem on the Monitoring Point.

Reflash using the Admin API

To reflash a Monitoring Point with the local image using the Admin API:

  1. Access the Admin API.
  2. Navigate to Appliance > PUT /appliance/reflash/.
  3. Click Try it out.
  4. Click Execute.
    • The Server response section should show Code “200” to confirm that the reflash instruction was received by the Monitoring Point.
    • The Monitoring Point reflashes with the locally stored image. Connectivity to the Monitoring Point is lost during the reflash procedure.

Reflash using a USB stick

To reflash a Monitoring Point with the local image using a USB stick:

  1. Download the reflash file.
  2. Copy usb-config.yaml to the root of an empty, FAT32-formatted USB stick.
  3. Edit the file with a text editor.
    1. Set the “reset:” line to reset: false.
      • This preserves the network and APM access configuration.
    2. Save the file.
  4. Make sure the Monitoring Point is powered on and ready to accept a USB stick.
  5. Insert the USB stick into the device.
  6. The device indicates that the USB stick is inserted.
  7. Wait until the device indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The Monitoring Point reflashes with the locally stored image. Connectivity to the Monitoring Point is lost during the reflash procedure.

Reflashing an EMP - USB image

Reflashing an Enterprise Monitoring Point (EMP) (USB image) involves rewriting the Monitoring Point file system with a software image downloaded to a USB stick. All configuration information is saved during a reflash. Also, the locally stored image is replaced by the downloaded image. This procedure is typically only required when upgrading the local system image or troubleshooting a problem on the Monitoring Point.

Reflashing using a USB stick

To reflash a Monitoring Point with a downloaded image using a USB stick:

  1. Download the System image file.
  2. Extract the contents to the root of an empty, FAT32-formatted USB stick.
  3. Edit the usb-config.yaml file with a text editor.
  4. Set the “reset:” line to reset: false.
    • This preserves the network and APM access configuration.
  5. Save the file.
  6. Make sure the Monitoring Point is powered on and ready to accept a USB stick.
  7. Insert the USB stick into the device.
  8. The device indicates that the USB stick is inserted.
  9. Wait until the device indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The Monitoring Point reflashes with the downloaded image. Connectivity to the Monitoring Point is lost during the reflash procedure.

Reflashing using a USB stick

To reflash a Monitoring Point with a downloaded image using a USB stick:

  1. Download the System image file for your Monitoring Point:
  2. Extract the contents to the root of an empty, FAT32-formatted USB stick.
    • There should be no folders. All files must be at the root level.
  3. Edit the autorun.sh file with a text editor.
  4. Remove the “#” from the beginning of the RESTORE_SETTINGS="yes" line.
    • This preserves the network and APM access configuration.
  5. Save the file.
  6. Make sure the Monitoring Point is powered on and ready to accept a USB stick.
  7. Insert the USB stick into the device.
  8. The device indicates that the USB stick is inserted.
  9. Wait until the device indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The Monitoring Point reflashes with the downloaded image. Connectivity to the Monitoring Point is lost during the reflash procedure.

Decommissioning an EMP

Decommissioning a Monitoring Point resets its APM access configurations but does not affect its network configuration (for example, its hostname, IP address, and any static routes) or the software it is running.

After decommissioning, the Monitoring Point is not accessible on the network. Its status will show as disconnected. Any paths and monitoring data are not removed from your organization until you delete the Monitoring Point.

To use the Monitoring Point again, you should follow the Migrating Monitoring Between EMPs procedure if you are replacing a failed Monitoring Point or the Getting Started procedure to set up the Monitoring Point as a new device within APM.

Decommission using Web Admin

To decommission a Monitoring Point using Web Admin:

  1. Log in to Web Admin.
  2. Click > Decommission.
  3. Click Confirm.
    • The Monitoring Point restarts with a factory APM access configuration.

Decommission using the Admin API

To decommission a Monitoring Point using the Admin API:

  1. Access the Admin API.
  2. Navigate to Appliance > PUT /appliance/.
  3. Click Try it out.
  4. In the Parameters section, for the action parameter, select decommission.
  5. Click Execute.
    • The Server response section should show Code “202”.
    • The Monitoring Point restarts with a factory APM access configuration.

Decommission using Web Admin

To decommission a Monitoring Point using Web Admin:

  1. Log in to Web Admin.
  2. Click Appliance Configuration.
  3. Click Decommission PathView Appliance.
  4. Click OK.
    • The Monitoring Point restarts with a factory APM access configuration.

Resetting an EMP to factory defaults - local image

Resetting to factory defaults using a local image resets both the network and APM access configurations and reflashes the Monitoring Point using a software image stored locally on the device.

After resetting to factory defaults, the Monitoring Point is not accessible on the network. Its status will show as disconnected.

To use the Monitoring Point again, you should follow the Migrating Monitoring Between EMPs procedure if you are replacing a failed Monitoring Point or the Getting Started procedure to set up the Monitoring Point as a new device within APM.

Reset to factory defaults using Web Admin

To reset a Monitoring Point to factory defaults and the local image using Web Admin:

  1. Log in to Web Admin.
  2. Click > Reset to Factory Defaults.
  3. Click Confirm.
    • The Monitoring Point restarts using the local system image and factory configurations. Access to the Monitoring Point is lost.

Reset to factory defaults using the Admin API

To reset a Monitoring Point to factory defaults and the local image using the Admin API:

  1. Access the Admin API.
  2. Navigate to Appliance > PUT /appliance/reflash/.
  3. Click Try it out.
  4. In the body field, change the “reset” property from “false” to “true”.
  5. Click Execute.
    • The Server response section should show Code “200”.
    • The Monitoring Point restarts using the local system image and factory configurations. Access to the Monitoring Point is lost.

Reset to factory defaults using a USB stick

To reset a Monitoring Point to factory defaults and the local image using a USB stick:

  1. Download the reflash file.
  2. Copy usb-config.yaml to the root of an empty, FAT32-formatted USB stick.
  3. Edit the file with a text editor.
    1. Set the “reset:” line to reset: true.
      • This resets the network and APM access configuration.
    2. Save the file.
  4. Make sure the Monitoring Point is powered on and ready to accept a USB stick.
  5. Insert the USB stick into the device.
  6. The device indicates that the USB stick is inserted.
  7. Wait until the device indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The Monitoring Point restarts using the local system image and factory configurations. Access to the Monitoring Point is lost.

Reset to factory defaults using Web Admin

To reset a Monitoring Point to factory defaults and the local image using Web Admin:

  1. Log in to Web Admin.
  2. Click System Configuration.
  3. Click Reset to Factory Defaults.
  4. Click OK.
    • The Monitoring Point restarts using the local system image and factory configurations. Access to the Monitoring Point is lost.

Reset to factory defaults using the reset button

Most Monitoring Points provide a way to reset to factory defaults via a reset button.

To reset to a Monitoring Point to factory defaults and the local image using a reset button, follow the procedure below for your Monitoring Point model:

Device Reset procedure
m22 Press and hold the reset button for 2 seconds. Then immediately press and hold the reset button again until all LEDs start flashing, which should be in about 25 seconds. The device is ready when the blue status LED returns to heartbeat. This should take 15 to 20 minutes.
m25 Press and hold the reset button until the heartbeat LED starts to do a green slow flash (usually about one minute).
m30 Press and hold the full datawipe (F/D) button on the back of the device until it starts beeping, which should take about 20 seconds. You’ll hear four short beeps, then one long one. The device is ready when it beeps twice. This should take 5 to 15 minutes.
m35 Press and hold the reset button until the heartbeat LED starts to do a green slow flash (usually about one minute).
m50 Press and hold the reset button until the heartbeat LED starts to do a green slow flash (usually about one minute).
m70 Press and hold the reset button until the heartbeat LED starts to do a green slow flash (usually about one minute).
r40 Press the F/D button for 15 seconds. Follow the prompts on the LCD.
r45 Reboot the unit by power-cycling. While it’s rebooting, press the F/D button. The LCD will update in < 1 minute when re-flashing begins.
r90 Press and hold the reset button until the heartbeat LED starts to do a green slow flash (usually about one minute).
r400 Using the end of a paper clip, press the F/D button (located in a small hole to the left of the Ethernet ports on the front panel) for 15 seconds. Follow the prompts on the LCD.
r1000 Cannot be hard reset physically. Reset via USB stick instead.

Resetting an EMP to factory defaults - USB image

Resetting to factory defaults using a downloaded image resets both the network and APM access configurations and reflashes the Monitoring Point using a software image downloaded onto a USB stick. It also updates the local system image.

After resetting to factory defaults, the Monitoring Point is not accessible on the network. Its status will show as disconnected.

To use the Monitoring Point again, you should follow the Migrating Monitoring Between EMPs procedure if you are replacing a failed Monitoring Point or the Getting Started procedure to set up the Monitoring Point as a new device within APM.

Reset to factory defaults using a USB stick

To reset a Monitoring Point to factory defaults and a downloaded image using a USB stick:

  1. Download the System image file.
  2. Extract the contents to the root of an empty, FAT32-formatted USB stick.
  3. Make sure the Monitoring Point is powered on and ready to accept a USB stick.
  4. Insert the USB stick into the device.
  5. The device indicates that the USB stick is inserted.
  6. Wait until the device indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The Monitoring Point restarts using the downloaded system image and factory configurations. Access to the Monitoring Point is lost.

Reset to factory defaults using a USB stick

To reset a Monitoring Point to factory defaults and a downloaded image using a USB stick:

  1. Download the System image file for your Monitoring Point:
  2. Extract the contents to the root of an empty, FAT32-formatted USB stick.
  3. Make sure the Monitoring Point is powered on and ready to accept a USB stick.
  4. Insert the USB stick into the device.
  5. The device indicates that the USB stick is inserted.
  6. Wait until the device indicates that it is ready and the USB stick can be removed. This should be less than 15 minutes.
    • The Monitoring Point restarts using the downloaded system image and factory configurations. Access to the Monitoring Point is lost.

Managing software on a CMP deployed using AKS

For a Container-based Monitoring Point (CMP) deployed using AKS, you can upgrade the software, roll it back to the previous version, or uninstall it. You can also remove all resources associated with the deployment.

Upgrade CMP software - AKS

To upgrade the software on a CMP deployed using AKS:

  1. Sign in to the Azure Cloud Shell.
  2. Perform the upgrade.

    helm repo update
    helm upgrade <monitoring-point-name> cmp-charts/c50
    

Other useful helm commands include:

  • helm list - lists installed CMP releases. Useful to show release version before and after an upgrade.
  • help search repo - lists the most recent chart.
  • helm repo ls - lists helm repositories.

Roll back CMP software - AKS

To roll back the software version on a CMP deployed using AKS:

  1. Sign in to the Azure Cloud Shell.
  2. Perform the rollback.

    helm rollback <monitoring-point-name>
    

Uninstall CMP software - AKS

To uninstall the software on a CMP deployed using AKS:

  1. Sign in to the Azure Cloud Shell.
  2. Perform the uninstall.

    helm uninstall <monitoring-point-name>
    

Remove all resources associated with a CMP - AKS

To remove all resources associated with a CMP deployed using AKS:

  1. Sign in to the Azure Cloud Shell.
  2. Determine the resource group name.

    terraform output
    
  3. Perform the resource group removal.

    az group delete -n <resource group name>
    
  4. Remove the contents of the directory containing the CMP software.

    rm -r <hostname>
    

Managing software on a CMP deployed using Docker Compose

For a Container-based Monitoring Point (CMP) deployed using Docker Compose, you can recreate the Monitoring Point if the host fails, upgrade the software or uninstall it.

Recreate a CMP - Docker Compose

In a Docker Compose environment there is no automatic failover, so if the host fails and needs to be reinstalled, the CMP needs to be reinstalled as well. In order to keep all its monitoring history, you can recreate the failed CMP point with the same identity as the old one rather than creating a new one.

Note: To avoid monitoring problems, you should only recreate a single instance of a CMP.

To can recreate a failed CMP deployed using Docker Compose:

  1. Log in to APM.
  2. Select the organization of the failed CMP (if you belong to more than one).
  3. Navigate to > Manage Monitoring Points.
  4. For the CMP you need to recreate, select > Re-create.
  5. Follow the instructions provided.
    • The replacement CMP is created and running.

Upgrade CMP software - Docker Compose

To upgrade the software on a CMP deployed using Docker Compose:

  1. Login to the host the Monitoring Point is deployed on.
  2. Navigate to the directory the Monitoring Point was deployed from.
  3. Perform the upgrade.
Linux hosts
   docker-compose -f mp-compose.yaml down
   docker-compose -f mp-compose.yaml pull && docker-compose -f mp-compose.yaml up -d
  • Note: You may need to run sudo docker-compose -f mp-compose.yaml down and sudo docker-compose -f mp-compose.yaml pull && sudo docker-compose -f mp-compose.yaml up -d for these commands to execute successfully.
Windows hosts

Run the following in Windows PowerShell:

   docker-compose -f mp-compose.yaml down
   docker-compose -f mp-compose.yaml pull
   docker-compose -f mp-compose.yaml up -d

Note: For automated upgrades, Watchtower is available.

Uninstall CMP software - Docker Compose

To uninstall the software on a CMP deployed using Docker Compose:

  1. Login to the host the Monitoring Point is deployed on.
  2. Navigate to the directory the Monitoring Point was deployed from.
  3. Perform the uninstall.

    docker-compose -f mp-compose.yaml down
    
    • Note: On Linux hosts, you may need to run sudo docker-compose -f mp-compose.yaml down for this to execute successfully.
    • If necessary, you can use docker ps and docker kill to find and stop the two containers used by the Monitoring Point. Their names end in “sequencer_1” and “talos-001_1”.
  4. Remove the contents of the directory containing the CMP software.
Linux hosts
	   rm -r <hostname>
Windows hosts

In Windows PowerShell):

	   rm -r <hostname>

Managing software on a Windows NMP

For a Windows based Native Monitoring Point (NMP), you can upgrade the software or uninstall it.

Upgrade NMP software - Windows

Upgrading from a Windows Software Sequencer to a Windows NMP: If you are upgrading a Windows Software Sequencer (EMP 8.4 or earlier) to Windows NMP (EMP 12.8.0 or later), you need to reinstall the software. The existing Monitoring Point identity and settings are preserved. Upgrades to a Windows NMP running EMP 12.8.0 or later software can be done remotely using the upgrade procedures that follow.

AppNeta recommends keeping your Enterprise Monitoring Point (EMP) software up to date to take advantage of the latest features and bug fixes. You will see the warning symbol 50x50_trans.png appear at various places in APM (including the Manage Monitoring Points page) when a Monitoring Point is no longer running the latest software version. You can configure APM to have a Monitoring Point upgraded automatically or you can upgrade it manually at any time. Note that the upgrade process can result in a gap of up to 15 minutes of monitoring history.

Configure upgrade automation

APM provides flexibility in scheduling Monitoring Point software upgrades to conform to your maintenance program. There are three upgrade automation settings:

  • Manual - Upgrades are to be performed manually (no automation).
  • Managed - Upgrades are to be performed automatically when new software is released. This enables you to have the latest software running at all times. The software upgrade schedule is listed on the AppNeta service status page: http://status.appneta.com/.
  • Scheduled - Upgrades are to be performed automatically on a regularly scheduled interval. This enables you to schedule upgrades during your regular network maintenance window. You also have the option of skipping the next upgrade.

To configure Monitoring Point upgrade automation:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to configure, select > Upgrade Settings.
  3. From the Upgrade Type drop-down, select the type of upgrade automation you want to use.
    • If you select Scheduled you will need to specify the upgrade schedule (Note: The upgrade schedule is based on the Monitoring Point time zone).
  4. Click Save.
    • The Monitoring Point upgrade automation is set.

The Upgrade Settings option is also available in the Bulk Action drop-down. Use this feature to configure upgrade automation on multiple Monitoring Points at the same time.

Manual upgrade

The upgrade process can be performed manually at any time to any model of Monitoring Point no matter which of the upgrade automation settings is selected.

To upgrade Monitoring Point software to the latest release:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to upgrade, select > Upgrade Now.
  3. Click OK.
    • The Monitoring Point software is upgraded to the latest release.

The Upgrade Now option is also available in the Bulk Action drop-down. Use this feature to upgrade multiple Monitoring Points at the same time.

Uninstall NMP software - Windows

Prior to removing the NMP software, delete the Monitoring Point in APM.

To uninstall the Windows NMP software:

  1. In the Windows search box (lower left), type “add or remove programs”.
  2. Click Add or remove programs.
    Screenshot of search for and Add or remove programs.
  3. Select AppNeta Monitoring Point.
  4. Click Uninstall.
    Screenshot of Apps & features dialog with 1 next to AppNeta Native Monitoring Point and 2 next to Uninstall button.
  5. Click Uninstall.
    Screenshot of dialog reading 'The app and its related info will be uninstalled'
  6. If you see the following message, click Yes.
    Screenshot of dialog reading 'Do you want to allow this app from an unknown publisher to make changes to your device?'
  7. Click Yes.
    Screenshot of dialog reading 'The AppNeta Monitoring Point is installed on your machine. Do you want to completely remove it and all of its components?'
  8. Click Uninstall.
    Screenshot of Uninstall AppNetaNMP dialog asking whether to uninstall the AppNeta NMP software.
  9. Click Close.
    Screenshot of the Uninstall completion dialog.

Managing software on a macOS NMP

For a macOS based Native Monitoring Point (NMP), you can upgrade the software or uninstall it.

Upgrade NMP software - macOS

AppNeta recommends keeping your Enterprise Monitoring Point (EMP) software up to date to take advantage of the latest features and bug fixes. You will see the warning symbol 50x50_trans.png appear at various places in APM (including the Manage Monitoring Points page) when a Monitoring Point is no longer running the latest software version. You can configure APM to have a Monitoring Point upgraded automatically or you can upgrade it manually at any time. Note that the upgrade process can result in a gap of up to 15 minutes of monitoring history.

Configure upgrade automation

APM provides flexibility in scheduling Monitoring Point software upgrades to conform to your maintenance program. There are three upgrade automation settings:

  • Manual - Upgrades are to be performed manually (no automation).
  • Managed - Upgrades are to be performed automatically when new software is released. This enables you to have the latest software running at all times. The software upgrade schedule is listed on the AppNeta service status page: http://status.appneta.com/.
  • Scheduled - Upgrades are to be performed automatically on a regularly scheduled interval. This enables you to schedule upgrades during your regular network maintenance window. You also have the option of skipping the next upgrade.

To configure Monitoring Point upgrade automation:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to configure, select > Upgrade Settings.
  3. From the Upgrade Type drop-down, select the type of upgrade automation you want to use.
    • If you select Scheduled you will need to specify the upgrade schedule (Note: The upgrade schedule is based on the Monitoring Point time zone).
  4. Click Save.
    • The Monitoring Point upgrade automation is set.

The Upgrade Settings option is also available in the Bulk Action drop-down. Use this feature to configure upgrade automation on multiple Monitoring Points at the same time.

Manual upgrade

The upgrade process can be performed manually at any time to any model of Monitoring Point no matter which of the upgrade automation settings is selected.

To upgrade Monitoring Point software to the latest release:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to upgrade, select > Upgrade Now.
  3. Click OK.
    • The Monitoring Point software is upgraded to the latest release.

The Upgrade Now option is also available in the Bulk Action drop-down. Use this feature to upgrade multiple Monitoring Points at the same time.

Uninstall NMP software - macOS

Prior to removing the NMP software, delete the Monitoring Point in APM.

To uninstall the macOS NMP software:

  1. On your Mac, click the Apple icon (top left) and select ​System Preferences​.
    Screenshot of selecting the Apple icon then System Preferences.
  2. Click AppNeta Sequencer.
    Screenshot of the System Preferences dialog with AppNeta Sequencer highlighted.
  3. Enter your password if prompted, and click ​OK​.
  4. Click Uninstall.
    Screenshot of the AppNeta Sequencer dialog with Uninstall highlighted.
    • The macOS NMP software is uninstalled.

Managing software on a Linux NMP

For a Linux based Native Monitoring Point (NMP), you can upgrade the software or uninstall it.

Upgrade NMP software - Linux

AppNeta recommends keeping your Enterprise Monitoring Point (EMP) software up to date to take advantage of the latest features and bug fixes. You will see the warning symbol 50x50_trans.png appear at various places in APM (including the Manage Monitoring Points page) when a Monitoring Point is no longer running the latest software version. You can configure APM to have a Monitoring Point upgraded automatically or you can upgrade it manually at any time. Note that the upgrade process can result in a gap of up to 15 minutes of monitoring history.

Configure upgrade automation

APM provides flexibility in scheduling Monitoring Point software upgrades to conform to your maintenance program. There are three upgrade automation settings:

  • Manual - Upgrades are to be performed manually (no automation).
  • Managed - Upgrades are to be performed automatically when new software is released. This enables you to have the latest software running at all times. The software upgrade schedule is listed on the AppNeta service status page: http://status.appneta.com/.
  • Scheduled - Upgrades are to be performed automatically on a regularly scheduled interval. This enables you to schedule upgrades during your regular network maintenance window. You also have the option of skipping the next upgrade.

To configure Monitoring Point upgrade automation:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to configure, select > Upgrade Settings.
  3. From the Upgrade Type drop-down, select the type of upgrade automation you want to use.
    • If you select Scheduled you will need to specify the upgrade schedule (Note: The upgrade schedule is based on the Monitoring Point time zone).
  4. Click Save.
    • The Monitoring Point upgrade automation is set.

The Upgrade Settings option is also available in the Bulk Action drop-down. Use this feature to configure upgrade automation on multiple Monitoring Points at the same time.

Manual upgrade

The upgrade process can be performed manually at any time to any model of Monitoring Point no matter which of the upgrade automation settings is selected.

To upgrade Monitoring Point software to the latest release:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. For the Monitoring Point you want to upgrade, select > Upgrade Now.
  3. Click OK.
    • The Monitoring Point software is upgraded to the latest release.

The Upgrade Now option is also available in the Bulk Action drop-down. Use this feature to upgrade multiple Monitoring Points at the same time.

Uninstall NMP software - Linux

Prior to removing the NMP software, delete the Monitoring Point in APM.

To uninstall the Linux NMP software:

  1. Remove all files that were installed.

    [root@hostname ~]# rm -rf /opt/pathview