Nagios Support Forum

Hi,

Is there any way to filter? services that are currently "unknown" so they don't show up under "unhandled" in the Server Status Summary?

We're monitoring some switches, and ports that don't have clients connected show up as "unknown" which creates a lot of noise in "unhandled" column.


Thanks,

If you "acknowledge" the service problem, it will be removed from the unhandled list.

Yeah, I know that.
There are over 100 "unknown" status ports on this host.

Is there a way to mass "acknowledge" all services on a host?

Thanks,

Unfortunately there is not an clean way to do this without some impact. One method though is to schedule the host for downtime (maybe during offpeak), the downside being that any problematic services under this host will also be here.

Alright,

Well, maybe there is a different resolution to my problem.
I'm using the "Network Switch/ Router" wizard to add a switch. Now in the past ( I thought only a couple of versions ago ) I thought it was only importing ports that were active (ie: has something connected to it ) at the time, is this correct?
Now when I add a switch it's adding ALL of the ports, which really is ideal, but ports that don't have something connected to it give an status as "unknown" with an error of "/var/lib/mrtg/host_port.rrd does not exist."

So maybe the issue I need to resolve is this. Any ideas?

Thanks,

Well, maybe there is a different resolution to my problem.
I'm using the "Network Switch/ Router" wizard to add a switch. Now in the past ( I thought only a couple of versions ago ) I thought it was only importing ports that were active (ie: has something connected to it ) at the time, is this correct?

yes, this is correct.

Now when I add a switch it's adding ALL of the ports, which really is ideal, but ports that don't have something connected to it give an status as "unknown" with an error of "/var/lib/mrtg/host_port.rrd does not exist."

So maybe the issue I need to resolve is this. Any ideas?

I haven't ever hunted down why the rrd file doesn't get created for this service, it gets into the messing with mrtg and cfgmaker, which I'm less familiar with. However, a temporary workaround it to run a 'touch host_port.rrd' in that directory and the 'unknown' state goes away. At some point we need to track down why the file isn't being made in the first place, but it could simply be because of a lack of performance data...

Touching the files resolved the problem, FYI.

Thanks.

Thanks for the heads up!