What is our primary use case?
In general, I use it for scanning IT and OT devices for networks and laying out their topology mapping.
The industry I use it for is manufacturing.
We specifically don't use it as our network management tool at my company; it's another utility tool that we use in the engineering department to study OT networks. This is specifically for OT, not for IT, and it helps us gather data from OT networks, running Ethernet over IP with SIP communication protocols.
What is most valuable?
One of the best features is that it is quick and easy to utilize for our network.
We utilize the network discovery and mapping features of SolarWinds Network Topology Mapper. We go in and connect with the database, scan the infrastructure, and help to identify nodes on an existing network so we can make recommendations for future upgrades.
It helps reduce manual workload by pinpointing devices, so we get an idea of where those devices are located, allowing us to avoid spending a longer time trying to trace them out independently. It helps somewhat with manual reduction of load to identify devices on the network.
The generated network diagrams and topology maps work as a very general overview. It's a very simple utility tool for the most part, helping generate a Visio file, and from that Visio file, I can create more in-depth mapping that fits the needs for the clients that we serve.
The real-time analytics and reports provided by SolarWinds Network Topology Mapper give us data so we can start making recommendations, allowing us to identify the topologies, the mapping, and the infrastructure. It helps us gain initial insight before we dive deeper into the application.
The benefit I've seen from using the Topology Mapper is that we haven't really had a comparison option in terms of Lansweeper or OT-BASE, which would be the comparison options in the manufacturing sector for scanning topologies. It has helped identify nodes, which is what we're after. Identifying the nodes, identifying the mapping of the nodes, and identifying some of the core structures of what we need for basic use in the Engineer's ToolBox.
One of the best features of SolarWinds Network Topology Mapper is that it has over 60 utility tools to utilize, so it offers a lot of different features, more than I have time to discuss at this moment, making it a good extra set of utility tools that we can incorporate onto our network.
What needs improvement?
I can't really articulate any areas that could be improved with the product right offhand. Just as long as they keep it around, since I know things are going into subscription models. One thing we do appreciate about the tool is that it's essentially a perpetual tool. Once you purchase it and the Engineer's ToolBox, it's been beneficial, serving as another utility tool on the network.
I can't think of anything specific offhand for how SolarWinds Network Topology Mapper could improve, because I treat it as a simple utility tool that serves those needs. It scans the network for SNMP and ICMP echoes to map the topologies of the existing network. It's a small utility tool that's very helpful and beneficial, another option for us to utilize, and while there's always room for more features, that typically comes with a cost that we have to weigh.
For how long have I used the solution?
I have dealt with the Topology Mapper for about three to four years now.
What do I think about the stability of the solution?
I would say it's a stable solution, as I have not experienced any problems with crashes or complaints about utilizing the software, either personally or from other team members.
What do I think about the scalability of the solution?
While it's not scalable in the sense of advancing to other SolarWinds products at this time, it works as a software solution that is scalable in that I can deploy it at one site and have another license deployed at another site. If I need to take that license away, I can do so, and once it's installed on a system, I can scan whatever network I want. What's nice about this utility tool is that it's not regulated, so I can use it at multiple sites once installed.
How was the initial setup?
The setup is straightforward; there are no real issues that we had setting up servers to support SolarWinds Network Topology Mapper, whether they are on virtual machines or not.
What other advice do I have?
The Engineer's Toolset is something I use hand-in-hand with the Topology Mapper, and it complements it well.
Regarding pricing and licensing with SolarWinds Network Topology Mapper, I haven't faced any issues there.
They have decent documentation, with everything that I found available on their website, so no issues there.
I rate SolarWinds Network Topology Mapper a 10 out of 10.