Typically, if I want to monitor a device (computer, printer, etc...) I'll
have that device on the map, and be monitoring it. This means it seems
pointless to alarm on the interface going down if that computer/printer
goes down, as its a double outage. The issue with auto-ack of the network
port is that because of the vantage point, a device could become ignored on
failure because the port was auto-acked, and since the device is behind
that port, it too does not notify, because it gets greyed.
Which is mainly the reason for my vote of having people monitor the devices
they need to monitor, instead of monitoring the ports they are connected
to. But there ARE indeed some (hopefully rare) cases where people need to
monitor devices they dont have access to, such as a far-end
router. They're only means of monitoring sometimes is to see if the local
interface goes down. But making the option selectable per device would
alleviate this issue.
The other way to "fix" this would be to allow for custom probes to look at,
and draw interfaces. Currently, this can only be done using intermapper
built in probes. But if this could change, I could just write my own
custom probe that looked at switches, plotted the interfaces, and didnt
return an alarm when an interface went down. This probe would also open up
a world of possibilities, such as allowing me to change the label of a
device on error, or even show (as a single interface) the number of
associations a particular wireless AP has. How cool would that be!? It
would also help with this next part about the "fix" to bug 41432.. :P
And if you are going to remind them of this request a few years ago, dont
forget to remind them to fix what they broke when they fixed bug #41432, so
we can possibly do a {ifAlias | "Text"} option if there is no interface
alias, but the label wants it.
At 11:51 AM 7/13/2007, you wrote:
Hi All,
OK, I see, and thanks for sharing.
I don't have any solutions, but would like to remind Dartware of a
feature request I added some time ago, maybe even 2-3 yesr back, when
this discussion started.. (feel free to re-post it, if it's gone in
to /dev/null... )
1: Auto-Ack interface on device Down.
It would be very helpful, if an interface that goes 'link down' could
be auto-ack'ed if the direct connected device goes down. This would
be useful for situations like those mentioned below, or if you have
printers or other non-mission-critical devices attached.
It could even be made a general setting, server-wide, that if 'Ignore
Outages' is checked on a device, the directly connected peer- interface
auto-ack's as well.
2: Auto-Ack interface on down, if nothing connected.
As above, it would be usefull to auto ack an interface if there are
nothing attached to it (on the map)
That would make it possible to keep maps with all ports visible, but
not get any alarms when individual interfaces go down. Connect
something, and fallback to #1 rule.
This would make sense to me, what do others think?
Jakob Peterhänsel
"Be a part of the Love Generation - carry a smile, not a gun."
- JP, May 2006
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
