Monitoring Points

The AppNeta Windows NMP Enterprise Monitoring Point is software that runs on the native operating system of a host computer and is used for Delivery monitoring. As such, it is typically used to monitor network performance from the perspective of a work-from-home user. The Windows NMP can be licensed as either an n10 (using the “Workstation (n10)” license) or as an n35 (using a “Strategic (m50/c50) / Legacy Small Office” license).

Specifications

Host Requirements

Spec Sub-spec Value
Storage 2 hours stored locally in case disconnected from APM
Supported OS Windows
  • Windows 8.1 and newer (all variants) and Windows Server 2012 R2 and newer
Virtual environments Hypervisors
  • ESXi 5.5 or higher
Guest OS
  • 64-bit RHEL 7
  • Windows 10 (all variants) and Windows Server 2016
Hardware requirements Memory 512 MB
CPU 2.0 GHz
Disk space 10 MB

Limitations and issues

  • Delivery monitoring only (no Experience monitoring, Usage monitoring, or Packet Capture).
  • Does not support PathTest.
  • Does not support voice or video testing when installed on a virtual machine.
  • Windows prevents QoS settings from being configured for paths originating from the computer.
  • Scheduled access network links (for example, Fibre PON, DOCSIS Cable), typically provided by ISPs to residential customers, can show lower uplink capacity than expected.
  • Capacity measurements in either direction are problematic on Wifi networks.
  • Can be used at a maximum speed of 500 Mbps when the Windows NMP is either a path source or a path target.
  • TCP Traceroute and TCP Ping are not supported.
  • Usage monitoring is not supported.

A full list of features can be found on the Monitoring Point Feature Comparison page.

Setup

Monitoring Point setup

Use the following steps to install a Native Monitoring Point (NMP) on a Windows system on your network. After installation is complete, the NMP software connects to back APM. Once this is done, you need to license the Monitoring Point, set its location, and then set up monitoring.

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), only steps 1, 2, and 3 below (Download, Install, and Verify) are required. The existing Monitoring Point identity and settings are preserved.

Prerequisites

Download the software

  1. Log in to APM.
  2. Select an organization (if you belong to more than one).
  3. If you’re setting up your first Monitoring Point, you will be taken to the first step of the Add Monitoring Point wizard.
  4. If your organization already has Monitoring Points, navigate to > Manage Monitoring Points > Add Monitoring Points.
  5. In the Platform Type field, select Windows (native).
  6. Click Download.
    • The installer is downloaded to your computer.

Install the software

If you are using anti-virus software that requires that applications be included on an “allow” list, add the Windows NMP to that list. For example, for Malwarebytes, add the NMP software (C:\Program Files\AppNeta\NativeMonitoringPoint\appneta-nmp.exe) to the list using this procedure.

Note: As part of the installation procedure, rules are added to the Windows Firewall. If the NMP is to serve as a target for single-ended paths, another inbound rule must be added manually.

There are two ways to install the software:

This procedure is also available in other formats: Word, PDF

  1. Make sure that you’ve downloaded the installation package (e.g., appneta-nmp-for-<org>-windows-<version>.exe).
  2. In Windows, press the Windows Logo Key + E to open File Explorer.
  3. Select the Downloads folder.
  4. Double-click the downloaded file (e.g., appneta-nmp-for-<org>-windows-<version>.exe).
  5. Depending on your environment, you may receive messages prompting you to approve making changes on your system. You must approve all of these.
    • For example, click ​Yes​. Screenshot of dialog reading 'Do you want to allow this app from an unknown publisher to make changes to your device?'
  6. Read the license agreement. If you accept it, select I accept, and click Next. Screenshot of read the license agreement dialog.
  7. Click Install. Screenshot of install dialog.
  8. Click Close. Screenshot of install completion dialog.
    • The NMP software is installed.

To deploy to multiple PCs using a Configuration Management (CM) tool (for example, Microsoft Endpoint Manager (formerly SCCM)):

  1. Define an “Appneta NMP” application in the CM tool
  2. Add the downloaded installer (installer.exe) to the application and deploy to your Windows hosts

The installer contains the following command line options:

Option Description
/S                      Silent mode. Install and uninstall with no end-user interaction. Useful for mass deployment through configuration management tools.
/JustUnpack=1          Unpack the files but do not register, start the service, or change firewall rules.
/ModifyFirewallRules=0 Installs and starts the Monitoring Point but skips configuration of firewall rules. Use this option if you wish to manage host firewall rules by other means (for example, a configuration management tool).  
/D=<SomePath>        Install the program at a specific path. The default path is C:\ProgramFiles\AppNeta\NativeMonitoringPoint.
/SIP=<SomePort> Sets the voice signalling port for voice tests. For example, /SIP=5060. The Windows NMP can only be used for voice tests when the port is set.
/VideoSignalling=<SomePort> Sets the video signalling port for video tests. For example, /VideoSignalling=1720. The Windows NMP can only be used for video tests when the port is set.

Verify the software is running

To check that the AppNeta Native Monitoring Point service is running:

  1. In the Windows search box (lower left), type “services”.
  2. Click Services. Screenshot of search for and selecting Services app.
  3. If you receive a message prompting you to approve making changes on your system, click Yes. Screenshot of prompt reading 'Do you want to allow this app to make changes to your device?'
  4. Confirm that the “AppNeta Native Monitoring Point” appears in the list and its Status is Running. Screenshot of Services app showing AppNeta Native Monitoring Point with Status of 'Running'.

Assign a base license

Every Windows NMP is sold with a base license that must be assigned to it in APM before it can be used.

  1. Within APM, navigate to > Manage Monitoring Points.
  2. Wait for the new Windows NMP to show up in the list (you may need to refresh your screen).
    • The Windows NMP’s status should show “Connection Established” (Green circle with white check mark).
    • If it doesn’t appear after a few minutes, you’ll need to troubleshoot the problem.
  3. To assign it a base license, navigate to > Manage Licenses.
  4. In the Parent Organization drop-down (if visible), select the parent organization containing the Windows NMP.
  5. In the Organization drop-down, select the child organization containing the Windows NMP.
  6. Click the APM Monitoring Points tab in the bottom table.
  7. For the Windows NMP you want to add the license to, select > Assign Licenses.
  8. In the Base License section, select a base license.
  9. Click Submit. The Windows NMP is ready to use.

Optional - Assign add-on licenses

In addition to a base license, you can add Standard Enterprise Application licenses, voice licenses, and video licenses to the Windows NMP. Before they can be assigned, you need to purchase them. Once purchased, they will be added to your organization and available for assignment.

To assign an add-on license to the Windows NMP:

  1. Navigate to > Manage Licenses.
  2. In the Parent Organization drop-down, select the parent organization containing the Windows NMP.
  3. In the Organization drop-down, select the child organization containing the Windows NMP.
  4. Click the APM Monitoring Points tab in the bottom table.
  5. For the Windows NMP you want to add the license to, select > Assign Licenses.
  6. In the Add-on Licenses section, specify the types and quantities of licenses you want to add.
  7. Click Submit.
    • The new capabilities are ready to use.

Set the location

When adding a new Windows NMP to APM, you need to specify its location. This setting provides essential geographical context for the data that the Windows NMP collects. Typically, you specify its location during the setup procedure.

If you are outside the setup procedure, you’ll need to edit its location:

  1. Navigate to > Manage Monitoring Points
  2. For the Windows NMP you want to edit, select > Edit Location.
  3. Specify the location of the Windows NMP.
  4. Click OK.
    • The location is set.

Set up monitoring

At this point the Monitoring Point setup is complete. Continue the APM setup procedure at Set up performance monitoring. Note that the NMP only supports Delivery monitoring. It does not support Experience or Usage monitoring.

Troubleshooting connectivity to AppNeta

Your Windows NMP is properly connected to AppNeta Performance Manager (APM) when the status icon in > Manage Monitoring Points shows Green circle with white check mark.

If this is not the case, use the troubleshooting procedure below to help determine why it is not connecting.

Requirements Things to check
NMP 12.8.0 or later. See Offline Legacy Monitoring Points for issues with older Monitoring Points.
Your firewall must be configured to allow the NMP to connect to APM. Check the general firewall configuration.
Check the Windows specific firewall configuration.
The NMP must be installed and running. Check that the NMP is properly installed and running.
The NMP must be connected to the network Use a browser to confirm that you can connect to the internet.
The system time must be correct. Check the system time and time zone.
If a proxy is being used, the NMP must be configured to connect through it. Check the proxy configuration on the NMP.
  Verify that the proxy is reachable from the network the NMP is on.
  Verify that the APM servers have been allowed in any access controls which may exist on the proxy.
If you are using anti-virus software that requires that applications be included on an “allow”” list, confirm that the Windows NMP software is on that list. For example, for Malwarebytes, add the NMP software (C:\Program Files\AppNeta\NativeMonitoringPoint\appneta-nmp.exe) to the list using this procedure.

If you are still unable to resolve the issue, contact AppNeta Support.

Verify installation

To check that the NMP is installed and running on a Windows machine:

  1. Verify that the NMP is running.

    C:\>sc query "AppNeta Native Monitoring Point" | FindStr STATE
            STATE              : 4  RUNNING
    
  2. Verify that the “nis.config” file exists.

    C:\>dir "C:\Program Files\AppNeta\NativeMonitoringPoint\config\nis.config"
     Volume in drive C has no label.
     Volume Serial Number is A215-BFE5
    
     Directory of C:\Program Files\AppNeta\NativeMonitoringPoint\config
    
    08/06/2020  09:31 AM               272 nis.config
                   1 File(s)            272 bytes
                   0 Dir(s)  53,975,257,088 bytes free
    
  3. Confirm that an exception is added to the Windows firewall for the NMP.
  4. Check for errors in the “Sequencer.log” file.

    C:\>FindStr "ERR" "C:\Program Files\AppNeta\NativeMonitoringPoint\log\Sequencer.log"
    ERR (6400|5880|2020-08-11 15:43:39.741000 Could not connect to NIS at pvc.pathviewcloud.com.
    

Access

View Monitoring Point status

To view a Monitoring Point’s status in APM:

  • Within APM, navigate to > Manage Monitoring Points.
    • The Monitoring Point status is indicated by the icon in the left column.
Icon Status Description
Green circle with white check mark OK The Monitoring Point is connected to APM.
Black circle with white minus sign Connection Lost The Monitoring Point is not connected to APM. Troubleshoot the issue.

Additional statuses can be found in the Additional Status columns. Hover over the icons for details and/or actions to take.

Icon Status Description
Shared The Monitoring Point is shared between organizations.
Unlicensed The Monitoring Point is unlicensed.
Monitoring Point Error There is a Monitoring Point error.
Upgrade Available There is a software upgrade available for the Monitoring Point.

Determine the Monitoring Point hostname or IP address

Once the Windows NMP has connected to APM, you can view its hostname and IP address.

  1. Log in to APM.
  2. Make sure you are using the correct organization
  3. Navigate to > Manage Monitoring Points.
  4. Click the Windows NMP you want to connect to. In the right pane:
    • the Host Name field contains the hostname.
    • the Public IP field contains the public IP address. Use this if you are connecting to the Windows NMP across the internet.
    • the Host Networking Details section contains the active Windows NMP interfaces and the local IP address of each. Use this if you are connecting to the Windows NMP locally.

Access the Monitoring Point

Configure

Methods

Management and configuration capabilities are accessed from within APM via > Manage Monitoring Points. For example, changing Monitoring Point location or renaming the Monitoring Point.

Basic settings

There are a few settings that should be configured on the Windows NMP including Time zone, Location, and Name.

Time zone

There are two time zones that must be configured - your local time zone and the Monitoring Point time zone.

The Monitoring Point time zone must be configured on the host the Windows NMP is running on.

Having the correct time zone on the Windows NMP is important for a number of reasons:

  • In conjunction with the Windows NMP’s system time, it is required in order for the Windows NMP to connect to APM. If the time is not correct, then there could be an issue with certificate validity checks when connecting.
  • It is required for monitoring results to be timestamped correctly.
  • It is required in order to display the correct time in path performance charts when Source Monitoring Point Time Zone is set.
  • It is required for alert conditions to be applied at the right time according to alert time ranges you have set.

Location

The location specified for the Windows NMP is necessary for a variety of reports and charts.

The Windows NMP’s location is specified during the setup procedure but it can be edited at any time.

  1. Navigate to > Manage Monitoring Points
  2. For the Monitoring Point you want to edit, select > Edit Location.
  3. Specify the location of your Monitoring Point.
  4. Click OK.
    • The Monitoring Point’s location is set.

APM name and hostname

All Enterprise Monitoring Points (EMP) have two names: a hostname and an APM name. The hostname is used to identify the Monitoring Point on the network. The APM name is used to identify the Monitoring Point within APM. By default, both of these names are the same and match the computer name of the computer the Windows NMP is installed on.

If you manually change the APM name, the hostname is not affected. If you change the hostname, the APM name is changed automatically unless the APM name was changed manually. In this case, changing the hostname does not affect the APM name.

Rename a Monitoring Point

To change the Windows NMP’s APM name:

  1. Navigate to > Manage Monitoring Points.
  2. For the Windows NMP you want to rename, navigate to > Rename.
  3. Either select the default or specify a new name.
  4. Click Confirm.
    • The Windows NMP’s APM name is changed.
Change the hostname

When you change the Windows NMP’s hostname, the APM name is changed automatically unless the APM name was changed manually. In this case, changing the hostname does not affect the APM name.

To change the Windows NMP’s hostname, rename your Windows PC.

Networking

The following networking-related features can be configured on the Windows NMP.

Hostname

See APM Name and Hostname

Web proxy

For networks that require internet traffic to be forwarded by a web proxy, the Native Monitoring Point (NMP) - Windows must be configured to connect to your proxy server so that it can communicate with APM.

The proxy settings on the Windows NMP only affect how it connects and reports data back to APM. These settings are not used for performance monitoring. If you are using Experience monitoring, you will also need to configure access to the proxy either when you create a web app group or after the web app group is created.

  1. Find seq.config.sample in C:\Program Files (x86)\AppNeta\Sequencer\config
  2. Save a copy and rename it seq.config.
  3. Edit seq.config.
  4. Uncomment the proxy config lines and fill in your proxy details:
    • Proxy Address - the IP address of the proxy server.
    • Proxy Port - the port the proxy server is listening on.
    • Proxy Username - a valid user name on the proxy server (if authentication/authorization is required). Only basic and digest authentication protocols are supported. NTLM and Kerberos are not supported.
    • Proxy Password - the password for the username specified (if authentication/authorization is required).
  5. Save your changes.
  6. Restart the Windows NMP:
    1. Navigate to Control Panel > All Control Panel Items > Administrative Tools > Services
    2. Right-click AppNeta Sequencer Service and select Stop.
    3. Right-click AppNeta Sequencer Service and select Start.

Manage

Restart

Restarting the Windows NMP will disrupt its connection to APM but it does not affect its software or its configuration.

Administrative privileges are required to stop or start the Monitoring Point.

To restart the Windows NMP:

  1. Login to the host the Windows NMP is deployed on.
  2. Open a Command Prompt window and Run as Administrator.
  3. Shut down the Windows NMP.

    net stop "AppNeta Native Monitoring Point"
    
  4. Start the Windows NMP.

    net start "AppNeta Native Monitoring Point"
    
  5. Confirm that the Windows NMP restarted successfully.

    sc query "AppNeta Native Monitoring Point" | findstr "RUNNING"
    
    • You should see “STATE : 4 RUNNING”.

Note: You can also use the Windows Services app to restart the NMP.

Shutdown

Administrative privileges are required to stop or start the Monitoring Point.

To shut down the Windows NMP:

  1. Login to the host the Windows NMP is deployed on.
  2. Open a Command Prompt window and Run as Administrator.
  3. Perform the shutdown.

    net stop "AppNeta Native Monitoring Point"
    
  4. Confirm that the Windows NMP stopped successfully.

    sc query "AppNeta Native Monitoring Point" | findstr "STOPPED"
    
    • You should see: “STATE : 1 STOPPED”.
  5. To start it back up again:

    net start "AppNeta Native Monitoring Point"
    
  6. Confirm that the Windows NMP restarted successfully.

    sc query "AppNeta Native Monitoring Point" | findstr "RUNNING"
    
    • You should see: “STATE : 4 RUNNING”.

Note: You can also use the Windows Services app to shut down the Windows NMP.

Delete

Deleting the Windows NMP from an organization is typically done when you are moving it to another organization or freeing up its base license so it can be used by another Monitoring Point.

Deleting the Windows NMP has the following effects:

  • All paths where the Windows NMP is the source (and the monitoring history related to those paths) are deleted (though they can be moved to another Monitoring Point during the delete process).
  • Tests and assessments are not deleted.
  • The base license and any add-on licenses that were assigned to the Windows NMP become available again.
  • The Windows NMP can no longer be seen from APM and will be decommissioned if it is online during the delete process.

To delete the Windows NMP from your organization:

  1. Navigate to > Manage Monitoring Points.
  2. For the Windows NMP you want to delete, select > Delete.
    • You will be prompted to confirm this action, and optionally to move all affected paths to another Monitoring Point.
  3. You should also remove resources on the deployment host.

Manage software

For the Windows NMP, you can upgrade the software or uninstall it.

Upgrade software

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 Windows NMP software up to date to take advantage of the latest features and bug fixes. You will see the Upgrade Available symbol () appear on the Monitoring Points page when the Windows NMP is no longer running the latest software version.

You can configure APM to upgrade the Windows NMP automatically or you can upgrade it manually from APM at any time.

Note that the upgrade process can result in a gap of up to 15 minutes of monitoring history. Also note that the Windows NMP must be connected to APM in order for an upgrade to complete successfully.

Upgrade type

You can see which upgrade options are available on the Monitoring Points page.

To see the Upgrade Type currently assigned to your Windows NMP:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. The Upgrade Type column shows the upgrade type. These include:
    • 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.
Configure upgrade automation

To configure Monitoring Point upgrade automation:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. To configure a single Monitoring Point, select > Upgrade Settings next to the Monitoring Point you want to configure.
  3. To configure multiple Monitoring Points:
    1. Use the check boxes on the left to select the Monitoring Points to configure.
    2. In the Action drop-down, select Upgrade Settings.
  4. 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).
    • Start Date - The first day of the upgrade schedule.
    • Start Time - The start of the upgrade window.
    • Duration - The length of the upgrade window. Upgrades can only occur during the upgrade window.
    • Repeat - The period between the start of each upgrade window.
    • Skip next upgrade - Skip the next upgrade.
  5. Click Confirm. The Monitoring Point upgrade automation is set.
Manual upgrade

The upgrade process can be performed manually at any time to the Monitoring Point model 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 Action drop-down. Use this feature to upgrade multiple Monitoring Points at the same time.

Uninstall software

Prior to removing the Windows NMP software, delete it in APM.

To uninstall the Windows NMP software manually:

  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.
    • The Windows NMP software is uninstalled.

To uninstall Windows NMP software from multiple PCs using a Configuration Management (CM) tool (for example, Microsoft Endpoint Manager (formerly SCCM)) run uninstall.exe (located in C:\ProgramFiles\AppNeta\NativeMonitoringPoint by default):

C:\ProgramFiles\AppNeta\NativeMonitoringPoint\uninstall.exe

Use the /S option to uninstall silently.

Migrate monitoring

See Migrate Monitoring between Monitoring Points.

Share

See Sharing a Monitoring Point.

Move between orgs

Windows NMPs and the data they have collected cannot be moved to another organization. If you need to move a Windows NMP to another organization you must first delete it then reinstall/re-deploy it in the new organization.

  1. Delete the Windows NMP.
  2. Reinstall the Windows NMP in the new organization.