-
Re: IMPORTING OF DEVICES' INTERFACE DESCRIPTIONS
chris.lapoint Dec 12, 2008 6:08 PM (in response to blizejr)There isn't currently, but I'll add it as an enhancement request for this one. If there are others interested in this feature, please speak up to help us prioritize.
-
Re: IMPORTING OF DEVICES' INTERFACE DESCRIPTIONS
simonpt Dec 16, 2008 3:27 PM (in response to chris.lapoint)Hi Chris
This would be a useful feature, but I recommend that it be implemented as optional. That is, when you do a scan you should be able to specify whether you want ipMonitor to use the interface name or the alias as the monitor name. Then each customer can choose which naming convention works best for them. You were probably thinking along these lines anyway, but I thought I better mention it.
I got caught out with this when using another monitoring product that added ifAlias naming support but didn't make it discretionary. When we did a rescan of a core switch, all the interface names changed and made our network map far less helpful. The connecting links ended up having the same names as the end nodes (eg. link: SERVER1, node: SERVER1) whereas previously we could easily identify the physical port from the map (eg. link: Gi1/0/1, node: SERVER1), which made fault resolution much easier.
This scenario obviously isn't applicable to ipMonitor today, but it highlights that there may be downsides to using ifAlias that people may not be aware of. I, for one, was looking forward to ifAlias support in the other product but quickly changed my mind when I saw what it did to the maps.
HTH
Rgds, Simon
-
Re: IMPORTING OF DEVICES' INTERFACE DESCRIPTIONS
chris.lapoint Dec 16, 2008 3:46 PM (in response to simonpt)Simon, thanks for the thoughtful feedback based on your experiences. I was actually thinking something more along these lines:
- Update Bandwidth monitor so that it includes a property field for interface description. This field should be populated during discovery and rediscovery operations
- Update all dashboard resources that display Bandwidth monitors to include the interface description field as a displayed column
Let me know what you think of this approach.
-
Re: IMPORTING OF DEVICES' INTERFACE DESCRIPTIONS
simonpt Dec 16, 2008 4:00 PM (in response to chris.lapoint)Chris
Thats sounds good too.
Will be interesting to hear if that meets blizejr's requirements or if ipMonitor needs to go a step further and offer for the alias to be used when generating the monitor name.
Rgds, Simon
-
Re: IMPORTING OF DEVICES' INTERFACE DESCRIPTIONS
blizejr Dec 17, 2008 8:44 AM (in response to simonpt)Chris' suggestion sounds great...as long as we also have the OPTION to utilize the interface description as part of the monitor name.
When we receive alerts on our monitors, it would be nice if we immediately knew what was affected instead of having to dig in to find out. Thanks guys, this would make a wonderful enhancement.
-
Re: IMPORTING OF DEVICES' INTERFACE DESCRIPTIONS
mwelker Apr 30, 2010 10:23 AM (in response to blizejr)Back from the dead...has this feature ever been added? I recently upgraded to IPMonitor 10 from 8.5, and I'm reorganizing our monitors/ devices. This would be a huge time saver for me, rather than having to go through each monitor on a switch/ router and edit the name in order to know what it is.
-
Re: IMPORTING OF DEVICES' INTERFACE DESCRIPTIONS
MarieB May 12, 2010 4:38 PM (in response to mwelker)Hi mwelker--
Since this is a resurrection, I'm going to mark this for the PM. Also, IpMonitor: What We're Working On what development is currently working on for IPMonitor 10. Take a look--it might help.
M
-
-
-
-
-