NCPA is listenable on all IP's

[ITOMB_IMT]

Hi,

We have Nagios installed on Development and Staging environment. We configured windows server monitoring using NCPA in staging environment. while configuring, we provided Bind IP as "staging IP address" which means windows server has to communicate with staging Nagios. while testing we configured windows server monitoring in development too, and we have not added development IP address in BIND IP. but windows server is being monitored from development and staging.

Is it a expected behavior? as BIND IP has only staging IP address but being monitored from both environments.

See the attached NCPA config of windows server.

[ssax]

Changing the ncpa.cfg IP address just changes the interface that NCPA listens on.

If they are active checks the XI servers are still going to use the IP address that is defined in the CCM configuration when reaching out. What do you have the IP address set to for that host on both the prod/stage systems? If it's a DNS address, what does this command output on both?

Code: Select all

nslookup the_dns_name_from_address_field

EDIT: To stop prod from being able to query the system, you would set this in the ncpa.cfg and restart the ncpa_listener service:

Code: Select all

allowed_hosts = STAGING_IP_ADDRESS