IPSEC VPN Topology

james.zhang22

Hi there,

We're trying to monitor the IPSEC VPN connections in Solarwinds; but neither Atlas nor Orion Map could discover the topology of mentioned tunnels automatically.

Is there any efficient way of mapping those without manually configuring such OID one by one?

Kind REgards,

James

jblankjblank

james.zhang22​ - Have you reviewed - Orion Platform 2019.4 - Orion Maps is Now Available  and more specifically the section on manually defining connections.  You wouldn't have to mess with OIDs or anything like that.  Below is the excerpt from that post:

Manually Define Connections!

As you are likely aware, the Network Performance Monitor module is responsible for collecting and calculating massive amounts of data from network gear. This includes topology data from which maps derive the network connections. However, topology data can be tricky to calculate across complex environments for a variety of reasons. Whether this is due to missing SNMP data, inability to access certain protocols, or something else entirely, at times we may not have everything required in order to stitch together a complete picture.

While there is no substitution for automatic discovery, having flexibility within the designer can present massive amounts of options and has certainly been a highly requested topic. Starting with this release, you will now be able to select any two entities and see a new button activated on the tool bar.  This button will grant users the ability to Connect Objects and define a custom connection within the map editor. Continuing with the map we have constructed to this point, I will walk through creating a number of topology connections between some of my network devices which are not currently connected and even to the ESX host.

Click to Enlarge

This example highlights a simple workflow, and once completed, these connections will function just like any other topology connection on the map, adhering to thresholds defined at the interface level from NPM. Taking a closer look, I want to emphasize two additional important options. In the image below, you can see I have the ability to create the connection "for this map only", which should hopefully be pretty self explanatory, or a secondary option, creating a connection "for all maps..."

What this means, is that anywhere in the platform where these two objects exist, including other maps, this connection will be visible. This custom connection will also appear in the Core or NPM Topology Widgets. Below is a screenshot of what that will look like. This moves Orion Maps beyond a simple editor, allowing you to define topology directly from the map, and alleviates the overhead of having to create this connection over and over again. This is an exciting improvement we think many of you will find quite useful.

Hopefully this helps!  You are still manually configuring these changes, but if the topology engine is not automatically detecting those connections and displaying them in the topology widget, this would be the best route to ensure that data is captured and displayed moving forward.