Renamed network interfaces not monitored
Renamed network interfaces not monitored
Deploying one of my first agents on a test server and when adding in XI through the wizard it only adds the three inactive network interfaces with default names Local area connection 2,3,4 and is not showing the interfaces I have renamed on the server for the Vlans they operate on.
Re: Renamed network interfaces not monitored
Did you add/rename them after the agent was installed? If so, try restarting the ncpa_listener service on the Windows system.
If you go to https://YOURNCPAHOST:5693/ in a web browser:
- Type in your token
- Click API
- Select interfaces from the dropdown, do you see them listed there?
What version of the NCPA agent is it running?
What version of Windows is it running?
Are they any special kind of interface or anything?
If you go to https://YOURNCPAHOST:5693/ in a web browser:
- Type in your token
- Click API
- Select interfaces from the dropdown, do you see them listed there?
What version of the NCPA agent is it running?
What version of Windows is it running?
Are they any special kind of interface or anything?
Re: Renamed network interfaces not monitored
They were present before the agent was installed, I went as far as to remove the device from Nagios and add it back in fresh and the only interfaces it listed were teh ones that are not currently in use.
When I went to the host direct under interfaces they weren't listed.
NCPA is 2.3.0
Windows version is 2008R2 - testing on a decom IT server before deploying on anything production
Not special interface, standard built in HP 1gb 366i adapter the other is a a HP561T 10gb adapter
When I went to the host direct under interfaces they weren't listed.
NCPA is 2.3.0
Windows version is 2008R2 - testing on a decom IT server before deploying on anything production
Not special interface, standard built in HP 1gb 366i adapter the other is a a HP561T 10gb adapter
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Renamed network interfaces not monitored
Hi,
For this system, let's set the loglevel to debug, then try to run the wizard or query the interfaces from the API, and post the output. Be sure to re-start the NCPA listener after changing the config file.
The default config file location:
Thanks,
Benjamin
We ran some quick tests here and we're not able to replicate it, but it could be an issue with the older Windows server version. Do you have any other systems to test this against in your lab environment?NCPA is 2.3.0
Windows version is 2008R2 - testing on a decom IT server before deploying on anything production.
For this system, let's set the loglevel to debug, then try to run the wizard or query the interfaces from the API, and post the output. Be sure to re-start the NCPA listener after changing the config file.
The default config file location:
Code: Select all
C:\Program Files (x86)\Nagios\NCPA\etc\
For more details on configuration options, please see this doc: https://www.nagios.org/ncpa/help/2.0/configuration.htmlloglevel info The level of message that will be logged to the log file. Valid log levels are info, error, warning, and debug.
Thanks,
Benjamin
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!