Classic examples are all the user devices that auto-discovery can turn up - or everything that gets turned when people go home...
fwiw, Charlie.
On 19/06/2004, at 04:17, Ian Struckhoff wrote:
Dennis,
I wanted you to know that some of your ideas are already possible, and that I will pass the rest of them on as ERs (enhancement requests) to the developer gang. See my comments below.
On Jun 18, 2004, at 12:42 PM, [EMAIL PROTECTED] wrote:
Here is a list of simple to implement Intermapper enhancements for the wish list:
(1) When you paste a device or a network onto a map it should go where you last clicked on the map rather than always going in the centre of the map. (eg, this is how Filemaker works when you paste objects into layouts.)
This sounds like an ER.
(2) Provide a way to hide all interfaces that are down. This would be a real time saver when creating complex maps.
This is already possible, if I understand what you mean. You can choose "DOWN Interfaces" from the "Select Other" hierarchal menu in the edit menu. Then choose "Hide Selection". Does this do what you are looking for?
(3) Provide a global preference to default new interfaces to Full Duplex. Half Duplex is almost a thing of the past.
This also sounds like an ER.
(4) For all of the built in application probes (ie, not Ping and SNMP probes) there should be a radio button in the probe configuration window that causes the device to go DOWN rather than into ALARM when the application probe fails. As things stand if the application probe fails but the server is still pingable, the device only goes into ALARM. In 99% of the cases with application probes this is not what people want. We have missed important application level outages because of this. As networks get bigger it is common to always have many devices that are in alarm, and so alarms tend to go unnoticed.
We have received a few suggestions along these same lines. I will submit your comments as an ER. The detail you have considered could be helpful, as could seeing how much interest there is for such a change.
(5) In the Device List devices that are in ALARM should come before devices that have been acknowledged. On our Device List we have two dozen devices that are acknowledged (due to construction projects) and so our NOC can't see the devices that are in alarm.
I know that a lot of thought went into the details of acknowledgments in 4.2, but I can see how what we do now could be inconvenient in some circumstances. I am passing this on as another ER.
(6) Provide a global preference that causes "Ignore Appletalk port information" to disappear from the device info window. I'll be the majority of sites don't use Appletalk any more.
I will pass this on as an ER as well.
Thanks, Ian
____________________________________________________________________
List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
--
C. C. Winchcombe Systems Heretic
ICQ: 4203990 -- AIM: [EMAIL PROTECTED] Mobile: 0418-384-838 -- Home: 03 9636-3397 PGP Fingerprint: 9880 18EA 5960 E164 283B� F927 2C75 A2D9 B472 84C2
"... so why would you bet YOUR company on a product that falls over more often than a drunken lemming?"
- on Microsoft in mission-critical situations
____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
