Nis.config is the configured key within hardware and software monitoring points which tell the Appneta servers which organization a monitoring points belongs to. In some situations, we might need a nis.config file to apply to monitoring points that are missing the configuration, are moving in between organizations etc.
Auth.config is required now starting from version 14.1.
This article will walk you through generating both.
Your browser will download a Zip file. Once you extract the ZIP files, you should see the following contents:
If your monitoring point is using 14.0 or older, use the nis.config file. If the monitoring point is running 14.1 or newer, use the the .yaml file.
Instructions for using these files can be found here:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/appneta/GA/appliance-overview/managing-monitoring-points/connect-to-appneta-server.html
See Additional Information below.
NIS.Config's are identical for all monitoring points within the same Organization, though every Child organization has its own unique site key and thus NIS.Config.
See also:
How to Provisioning AppNeta monitoring point with a NIS.CONFIG file
https://knowledge.broadcom.com/external/article/242839
See also checking the NIS.config:
https://knowledge.broadcom.com/external/article/258323/