Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Topology Mapper (NTM) > NTM - Knowledgebase Articles > Automatically shortening interface names in maps

Automatically shortening interface names in maps

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 698 Votes: 0 Revisions: 7

Issue

In scanning your netork, NTM records the names of discovered interfaces based on the relevant OIDs polled. If all interface names are mapped as named, the result can be a very cluttered map display.

Solution

NTM maintains a configuration file at \ProgramData\SolarWinds\Network Topology Mapper\Configs\NTM.cfg

In this file are a group of regular expression properties that you can define to truncate common strings that NTM sees in the interface names it finds.

<root/>
  <group name="RegexesForIfName">  // default group name--do not change this value</group>
    <item name="regex1">    //  these names can be changed</item>
      <property key="pattern" value="Gigabit"> // Gigabit - that is what will be replaced with</property>
      <property key="replaceValue" value="Gi"> // Gi - something on what will it be replaced</property>

    <item name="regex2"/>
      <property key="pattern" value="FastEthernet"/>
      <property key="replaceValue" value="Fa"/>

In these configurations, there are two regular expressions, "regex1" and "regex2".
"regex1" tells NTM to look for the string "Gigabit" and to replace it with "Gi".

So for example, if NTM discovers an interface named "Gigabit1/8g," NTM will change the name to "Gi1/8g" in the maps you create. Similarly, NTM changes"GigabitEthernet1/8g" to "GiEthernet1/8g".

You can create as many "regex[#]" as you need to shorten or otherwise manage common strings in the interface nams you expect to appear on NTM maps.
Keep in mind that NTM applies regular expressions you define in the configuration file in a descending order based on the pattern length of strings, and NTM only applies one expression per interface name.

So, for example, let's say you define these two regular expressions:

  <item name="regex1"/>
      <property key="pattern" value="Ethernet"/>
      <property key="replaceValue" value="Eth"/>

 <item name="regex2"/>
      <property key="pattern" value="FastEthernet"/>
      <property key="replaceValue" value="Fa"/>

Based on these expressions, if NTM finds an interface name "SomeFastEthernet1/8g," then it transforms the string to "SomeFa1/8g". This is because, of the two patterns NTM considers, "FastEthernet" is longer than "Ethernet", and so NTM uses the replacement value of "Fa".

Last modified

Tags

Classifications

Public