Page 1 of 1

Local Area Connection Bandwidth - Inbound/Outbound is UNKNOWN

Posted: Thu Jan 15, 2026 11:58 am
by LACMAIS
We're testing Nagios and periodically, the servers we're testing with get the following warnings
Local Area Connection Bandwidth - Outbound is UNKNOWN
Local Area Connection Bandwidth - Inbound is UNKNOWN

How is Nagios testing bandwidth? Is there some external destination we would need to allow at our firewall?

Thank you!

Re: Local Area Connection Bandwidth - Inbound/Outbound is UNKNOWN

Posted: Thu Jan 15, 2026 12:14 pm
by browan
Hey @LACMAIS,

I am wondering a couple of things,

1. I assume this is through one of our wizards that uses NCPA for checks, if so, what version of NCPA are you running?
2. What kind of process did you go through to create these service checks?
3. Once you setup the checks, did you modify the systems you are checking in such a way that the network interface name could have changed?

Thank you!
~ Ben Rowan

Re: Local Area Connection Bandwidth - Inbound/Outbound is UNKNOWN

Posted: Thu Jan 15, 2026 2:48 pm
by kg2857
You may want to look at the service details and then the command definition to see what's actually being checked.

Re: Local Area Connection Bandwidth - Inbound/Outbound is UNKNOWN

Posted: Fri Jan 16, 2026 3:00 pm
by LACMAIS
browan wrote: Thu Jan 15, 2026 12:14 pm Hey @LACMAIS,

I am wondering a couple of things,

1. I assume this is through one of our wizards that uses NCPA for checks, if so, what version of NCPA are you running?
2. What kind of process did you go through to create these service checks?
3. Once you setup the checks, did you modify the systems you are checking in such a way that the network interface name could have changed?

Thank you!
~ Ben Rowan
#1 - version 3.1.3
#2 - as you mentioned the wizard - Select a Wizard, Windows Server
#3 - yes, now that you mention it. The VM was converted from Hyper-V to VMware, but since the alert clears out, but then eventually comes back, that did not occur to me...

I'll uninstall the current NCPA agent and reinstall, perhaps with an updated one, and update the thread. Thank you for your insight.