Flexible Interface Name Construction

kjspgd

I would love the flexibility to choose how interface names are constructed based on SNMP values.

As I understand it, interface names are currently constructed by a concatenation of IfDescr · ifName.

The ifDescr for our switches is excessively long - which makes the readability of interface lists on nodes with many interfaces awkward.

i.e.:

Enterasys Networks, Inc. 1000BASE-SX Mini GBIC w/LC connector · Link to Building 2

When I have switches with many interfaces, it becomes increasingly difficult to find the interface I am most interested.  We also share view access and would like the experience to be a little more viewable.

I understand that I can change the Caption for the interface manually in NPM but it will then never auto-update.  If I need to update a port description on my switch, I then *also* need to go update NPM.

I would love the flexibility to choose the SNMP elements (or limit it to just use ifName) used when automatically constructing the interface name.

solarview

In principle a good idea. But what is causing a lot of misunderstanding is the fact that a interfacename, constructed by a concatenation of IfDescr · ifName, is static, and does not change when the ifName of the monitored interfaces changes on the device.

Sometimes the description of a interface, that is carrying the name of a private line, or bundle, has to be changed. In Solarwinds NPM, the name of the interface does NOT change automatically then, and has to be adapted manually, or deleted, and reinserted in monitoring.

I think it would help a lot of people when the interfacename would be dynamic!