Orion Maps 2.0 - Need help linking objects

jamieinbox​ are you monitoring both sides of the interface?

No, didn't even consider-- I will give that a try and let you know. Thank you christopher.t.jones123​

Is there a way to pull in the interfaces without re-discovering the device? I'm hoping so- or any suggestions?

Thanks,

Jamie

Do you mean not doing a new "Network Discovery"? If so, then you don't need to run a whole new discovery job, you can just go to the node in question from the "Manage Nodes" page, select it and hit the "List Resources" button

Appears you are getting some assistance here and it would be important to monitor the interface on both sides in order to see the automatic connections.  Here are some posts that walk through the different phases of Orion Maps project to date.  The Maps are simply visualizing data already polled from your modules like NPM.  If you go to the details page of a network device, and look for the NPM Topology resource, we will map the links in which we are seeing the interface on either side of the connection.  

Orion Platform 2018.2 Improvements - Chapter Two - Intelligent Mapping

Orion Platform 2018.4 Improvements - Intelligent Mapping Enhancements

Orion Platform 2019.2 - Orion Maps 2.0!

Let kbongi​ and I know what would be critical for you to see in the next release.  We would love to see any screenshots of your maps/ dashboards too!

Thank you very much for the help. I appreciate it greatly.

I looks like we need licenses for interfaces (we needed them anyway for UDT).

-Am I on track with that statement?

Time to go unlimited.

Thanks again.
Jamie

Keep in mind that interfaces and ports, while obviously may be similar in real life, are a bit different in the SolarWinds World.  Interfaces as monitored by NPM should typically be links you care to see performance statistics on or in this case understand topology.  So very often in NPM you are monitoring critical trunks and up-links but not things like individual access ports.  Now every environment and need is different so take this for what its worth.  In UDT, you are really after understanding what is connected to each port.  So in this situation it is the more the merrier.  With your UDT license you need to ensure you have enough to cover all you ports, and making sure those are monitored.  I would suggest when discussing with your Sales Rep to ask to have a Engineer join and walk through what you want to accomplish.  You may be able to save some money. 

Not trying to be dense- I'm gathering that I *should have everything I need in NPM? No matter what license amount I have? I need to go into NPM and check out what I'm monitoring?

Thanks again. I'll check out the links, too.

Thinking about this, it looks like I need enough NMP licenses for the links I need. If I tried to monitor two pieces of equipment, would it have to be the individual port connecting to the individual port-- so I cannot use a virtual Vlan 80 (per say) and expect that it will connect to a neighboring device on Vlan port 80, too? I need the switch 1 gi1/0/1 connected to the switch 2 gi 1/0/1 for instance, right?

Correct - if you are looking to visualize particular connections, we need to have each end monitored.  So if currently you have Switch 1 gi1/0/1 monitored and in the NPM topology widget, you see that it is connected to Switch 2 but the interface is "Unknown" we can't really draw that connection for you.  If you monitor the gi 1/0/1 on Switch 2 as well...  the link we subsequently added to the map.

You do have an option where you can access Centralized Settings.

http://Your Orion IP Here/Orion/Admin/AdvancedConfiguration/Global.aspx

Here you could enable Layer 2 Unknowns - which would show you that we detect the connection, but are not showing them by default as one side of the equation is unknown.