I agree, but a potential good value-added is the ability to detect
potential configuration mistakes. We rely here on a lot of automation
tools, one of which is InterMapper, to check our work.
Perhaps the best compromise is to have a global or per-map server
configuration checkbox, "Call out possible device configuration
errors." Or a more fine-grained list of checkboxes, one each for a
set of areas Intermapper might check on.
Boy, if IM could pick up the duplex setting of a port (which is
possible but usually buried in a vendor-specific MIB so I'm not
hopeful), it'd be able to save a lot of teeth-gnashing if it pointed
out duplex mismatches on opposite ends of a link!
/cvk
On Mar 7, 2007, at 9:12a, Quezada, Pedro wrote:
Intermapper should just display what ever mask an administrator
configures.
Intermapper job is to display what is on the router.No exceptions
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
