On 11 Jan 2010, at 17:56, [email protected] wrote:
Dear Opsviewers!
Currently I'm integrating all SNMP capable hosts into Opsview 3.5.1.
Of
course I also tried the "Host Interfaces" view. And I'm not under-
standing it, or it's just a bug:
If an interface's Links status is down and the admin status is also
down, the Opsview status is critical. But I'd consider the down/down
situation as a intended one, so the Opsview status should be OK.
I see what you mean, but why are you monitoring it? Should it be a
warning or unknown instead so you can disable monitoring of it?
From my point of view you should be able to check and monitor all
Interfaces of a switch/router and get notified if any admin-enabled
port
goes down, or vice-versa, any admin-disabled port goes up. But I don't
want to be notified if a port, that's not connected and therefore was
set to down by the admin, is (really) not connected.
It further looks like I have to reconfigure the host in Opsview if any
new port gets connected.
At the moment, you have to "tick" that you want that interface
monitored. This is because we need the extra services created at
Nagios to store the performance data and provide the alerting.
We have been thinking that you could have a single service which has a
dynamic list of interface performance data returned, but then that
starts to hit the NSCA packet limits in a distributed environment.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
