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
Email: [EMAIL PROTECTED]
AIM: Marook
Phone: +45 29687104
On 13/07/2007, at 16.05, Jon Myers wrote:
We need to show these interfaces for the integrity of the network.
If I have a high usage link between two switches, it'll glow yellow
or orange. If I'm not showing computer interfaces, how do I see
what computer/port is a major contributor to the high usage?
Yes, we most likely do have students using p2p illegally, and
although we try to block all p2p at the packetshaper, it would be
nice to just see from a bandwidth point which students are still
using high bandwidth apps, and figure out if they are p2p programs
getting around the blockage.
We do have two (huge) maps that are our backbone, and only show
ports going to other switches, and these ones for the most part
should stay green. But we also have about 20 other maps (showing
devices in various buildings) that we like to see all the ports on,
to see what computers are using what bandwidth, to see at a glance
what ports are not being used (show status of a down port, and if
it says that port has been down for 5 months, chances are, thats an
available port, and if something is plugged into it, it can be
unplugged, as we don't normally keep live empty ports in some
buildings).
This functionality (along with the "IfAlias not available" issue)
will be something that we look for in whatever we're going to use
to replace intermapper.
At 09:41 AM 7/12/2007, you wrote:
Not that I should deside what you do with your setup, but I am a bit
curious why in the world you like to show interfaces that is not
mission critical..
Do your users use illegal software like Limewire or Kazaa or
something (that show as bandwidth usage) or do you have other issues?
On the maps I use, it's just clutter and makes the important stuff
fade into the void...
Could you elaborate a bit on why you need to see those interfaces?
Best,
Jakob Peterhänsel
"Be a part of the Love Generation - carry a smile, not a gun."
- JP, May 2006
Email: [EMAIL PROTECTED]
AIM: Marook
Phone: +45 29687104
On 11/07/2007, at 19.59, Jon Myers wrote:
After waiting about 3 years, I've just come to the realization that
all my maps will be in constant alarm state because of interfaces
being down when people turn computers off.
This could also be fixed via custom probe that allowed for ports
coming off from the device being probed.. I think I requested this
a few years ago as well, but no luck there either. The only time
you can show ports on a device is if its probed with a built in
intermapper probe.
At 05:01 AM 7/11/2007, you wrote:
Hi "Dartware"
Anything new about this feature?
I'm waiting badly for this.
J. Brändle
Am 13.10.2006 um 14:52 schrieb Christopher L. Sweeney:
At 8:54 AM +0200 10/13/06, Jürgen Brändle wrote:
I need to acknowledge all the interfaces on a switch on which
"endusers" connect and disconnect all day long.
These interface are not interesting for my network health.
But I don't want to acknowledge some interfaces with servers or
uplinks behind.
I also need the "standard" acknowledgement feature like timed or
indefininite for the interfaces.
We have had a couple of enhancement requests along this line, and
we can certainly add yours to them.
At the moment, the acknowledge for an interface is just the
equivalent of the "basic" acknowledge for a device.
-- Christopher
--
================================================
Christopher L. Sweeney
[EMAIL PROTECTED]
http://www.dartware.com/
__________________________________________________________________
__
List archives: http://www.mail-archive.com/intermapper-talk%
40list.dartware.com/
To unsubscribe: send email to: InterMapper-Talk-
[EMAIL PROTECTED]
___________________________________________________________________
_
List archives: http://www.mail-archive.com/intermapper-talk%
40list.dartware.com/
To unsubscribe: send email to: InterMapper-Talk-
[EMAIL PROTECTED]
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: InterMapper-Talk-
[EMAIL PROTECTED]
____________________________________________________________________
List archives: http://www.mail-archive.com/intermapper-talk%
40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
