AppNeta - Checking a NIS.config on a monitoring point

Products

• AppNeta

Issue/Introduction

Issue: My AppNeta monitoring point is not connecting to the portal.

 

Cause

In some scenarios the monitoring point may be unable to connect to the server, and you can run Server Reachability tests to verify why.  
However for these test to function, the AppNeta monitoring point needs to be provisioned for the correct AppNeta Server, where you log in. 

 

Resolution

The AppNeta server settings can be found in the Web UI.  Click on Monitoring Point Settings >  AppNeta Server  and verify the settings:

 

NIS Address;  this is the specific AppNeta server where you log into to the portal to check your fleet of monitoring points.
Site Key:  This is essentially the location of the Parent or Child Organization within the AppNeta portal.  Each Parent or Child have a unique Site Key.  

If either of these values are missing, or incorrect, your monitoring point will not be able to connect into your organization.

Alternatively, you could also perform a factory reset and then performing the original setup procedure to add a monitoring point.
See also the Getting Started guide and review the details. 


**Note:  You can also check this setting from Console or Command Line using the following:

cat /opt/pathview/config/nis.config

Additional Information

You can fix this by getting a copy of your NIS.config which can be used to apply to your monitoring points:
https://knowledge.broadcom.com/external/article/240444 

You can also uploading the file into the monitoring point which will configure the device for the new organization:
https://knowledge.broadcom.com/external/article/242839