Use this page to help determine why your AppNeta Monitoring Point is not connecting to AppNeta Performance Manager (APM). The Monitoring Point is properly connected to APM when the status icon in > Manage Monitoring Points shows Green circle with white check mark.

Troubleshooting is slightly different for physical Monitoring Points, container-based Monitoring Points, virtual Monitoring Points and native Monitoring Points.

Physical Monitoring Points

The following table shows the requirements for the Monitoring Point to connect to APM and things to check if it is not connecting.

Requirements Things to check
The Monitoring Point must be powered on (the power LED will indicate this). Check that power button has been turned on.
  Check that power cable/adapter is plugged in to device and to a surge protected power source.
  Check that the power source is providing power.
The Monitoring Point must be connected to the network (by default, use the Primary network connection port) Check that LEDs on the Monitoring Point port are on or blinking.
  Check that the cable is plugged into the correct Monitoring Point port.
  Check that the cable is connected to an L2 switch on the network.
The Monitoring Point must be configured to access APM and its system time must be correct. Check the Monitoring Point configuration (via USB) and verify that the following are as expected:
- Time On System - time and timezone must be correct.
- Address Assignment - should be “Dynamic” (for DHCP) or “Static”
- IP address
- Subnet Mask
- Default gateway
- DNS servers
- Sequencer Status - should be “Operational”
- Internet Connection - should be “Available”
- Server Connection Status - should be “Connection OK”
If a proxy is being used, the Monitoring Point must be configured to connect through it. Check the proxy configuration on the Monitoring Point (via Web Admin).
  Verify that the proxy is reachable from the network the Monitoring Point is on.
  Verify that the APM servers have been allowed in any access controls which may exist on the proxy.
Your firewall must be configured to allow the Monitoring Point to connect to APM. Check the firewall configuration.

If you are still unable to resolve the issue, read the Monitoring Point configuration then contact AppNeta Support.

Container-based Monitoring Points

The procedure to use for troubleshooting CMP deployments depends on how the Monitoring Point was deployed. Deployment options include AKS and Docker Compose.

Troubleshoot AKS deployments

The following table shows the requirements for the CMP deployed using AKS to connect to APM and things to check if it is not connecting.

Requirements Things to check
The Monitoring Point must be running. Check that the containers are running.
Your firewall must be configured to allow the Monitoring Point to connect to APM. Check the firewall configuration.

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

Troubleshoot Docker Compose deployments

The following table shows the requirements for the CMP deployed using Docker Compose to connect to APM and things to check if it is not connecting.

Requirements Things to check
The Monitoring Point must be running. Check that the containers are running.
   
If a proxy is being used, the Monitoring Point must be configured to connect through it. Check the proxy configuration of the deployment host.
  Verify that the proxy is reachable from the network the Monitoring Point is on.
  Verify that the APM servers have been allowed in any access controls which may exist on the proxy.
Your firewall must be configured to allow the Monitoring Point to connect to APM. Check the firewall configuration.

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

Virtual Monitoring Points

The following table shows the requirements for the Monitoring Point to connect to APM and things to check if it is not connecting.

Requirements Things to check
The Monitoring Point must be running. Check that the virtual machine is running.
The Monitoring Point must be connected to the network (by default, use the Primary network connection port) Check that LEDs on the port used by the Monitoring Point are on or blinking.
  Check that the cable is plugged into the correct port.
  Check that the cable is connected to an L2 switch on the network.
The Monitoring Point must be configured to access APM and its system time must be correct. Log in to Web Admin and verify that the following are as expected:
- General > Monitoring Point Connected - should be “Yes”.
- System Status > System Time - time and timezone must be correct.
- System Status > NTP Synchronized - should be “Yes”.
- Network State > eth0 - Status should be “Up” and IP Address and prefix should be as expected.
If a proxy is being used, the Monitoring Point must be configured to connect through it. Check the proxy configuration on the Monitoring Point (via Web Admin).
  Verify that the proxy is reachable from the network the Monitoring Point is on.
  Verify that the APM servers have been allowed in any access controls which may exist on the proxy.
Your firewall must be configured to allow the Monitoring Point to connect to APM. Check the firewall configuration.

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

Native Monitoring Points

The following table shows the requirements for the NMP to connect to APM and things to check if it is not connecting.

Requirements Things to check
Your firewall must be configured to allow the NMP to connect to APM. Check the firewall configuration.
- Windows
- macOS
- Linux
The NMP must be installed and running. Check that the NMP is properly installed and running.
- Windows
- macOS
- Linux
The NMP must be connected to the network (by default, use the Primary network connection port) Check that LEDs on the port used by the NMP are on or blinking.
  Check that the cable is plugged into the correct port.
  Check that the cable is connected to an L2 switch on the network.
The system time must be correct. Check the system time and timezone.
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 still unable to resolve the issue, contact AppNeta Support.

Verify installation on Windows

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.
    

Verify installation on macOS

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

  1. Verify that the NMP is running.

    hostname:~ username$ ps -ef | grep netseq-mac
    798102476 97641 81200   0 12:13pm ttys002    0:00.00 grep netseq-mac
    
  2. Verify that the “nis.config” file exists.

    hostname:~ username$ find /Library/PreferencePanes -name 'nis.config'
    /Library/PreferencePanes/AppNetaSequencer.prefPane/Contents/Resources/config/nis.config
    
  3. Check for errors in the “Sequencer.log” file.

    hostname:~ username$ cat /Library/PreferencePanes/AppNetaSequencer.prefPane/Contents/Resources/log/Sequencer.log | grep ERR
    ERR (34326|4551471104|2018-02-19 18:15:09.979341 Could not connect to NIS at pvc-st2.pathviewcloud.com.
    

Verify installation on Linux

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

  1. Verify that the NMP is running.

    [root@hostname ~]# ps -ef | grep netseq-linux
    root     25660     1  0 Jan29 ?        00:03:25 ./netseq-linux -b
    root     32522 32465  0 10:55 pts/1    00:00:00 grep netseq-linux
    
  2. Verify that the “nis.config” file exists.

    [root@hostname opt]# pwd
    /opt
    [root@hostname opt]# find . -name 'nis.config'
    ./pathview/config/nis.config
    
  3. Check for errors in the “Sequencer.log” file.

    [root@hostname opt]# cat pathview/log/Sequencer.log | grep ERR
    ERR (15103|3080215440|2018-01-28 14:01:23.669926 Could not connect to NIS at pca05.