cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 12

Auto Connect Links don't show in NPM

For various reasons we are still very much using Atlas and will likely do so for a while until Solarwinds get the mapping tool capable of doing what we need (if ever) ...

Anyway - I've noticed today that some of our maps where we have used "ConnectNow" are not showing the details of those links in NPM. Any clues on where to start looking to fix this please as I really don't want to have to manually check and then re-draw / re-link "missing" details.

Labels (1)
0 Kudos
9 Replies
Level 12

As an aside, I have now responded to the map update question linked above as I was told, this morning, that we upgarded last night so have had a play.

Saw it Stuart.  It was perfect feedback and very much appreciated!

Level 12

As an update... If I delete and "re-connect" one of these links and then save it shows up in NPM.

As above though, I don't want to have to re-check every map

0 Kudos

You will still likely need to check the Network Atlas maps to verify if the connections exist.

What would get the web based Orion Maps capable of doing what you need?  What is it missing?

0 Kudos

Hi - thanks for replying but not sure I follow... but letme try.

>> need to check the Network Atlas maps to verify if the connections exist

The maps and connections were / are created in Network Atlas and the connections exist. By that, I mean, there is a physical line that connects the device and when 'hovered' over it shows details of those links. Originally, when saved, these details also showed up in NPM. As per my update, if I then delete a link and re-create it via autoconnect, then the details "re-appear" in NPM.

>> What would get the web based Orion Maps capable of doing what you need?  What is it missing?

This is another thread altogether but short answer is we haven't instaleld the latest version - I believe we are doing so this / next week - so for now I can't really advise. Last I was aware you couldn't add your own links and you couldn't do customeicons - though I note that both are said to be possible now. Until we get a chance to test it, I can't say what may or may not be missing / not working but would address as and when we do.

0 Kudos

stuartd  You stated the following -

I've noticed today that some of our maps where we have used "ConnectNow" are not showing the details of those links in NPM.

What does this mean?  Are you indicating the link is no longer visible and is no longer showing metrics on the map while others are still working?  Are you indicating the popover/ hover no longer works?  Some screenshots would likely help but I would recommend opening a support case if something is disappearing where you would expect to see specific data. 

All of these ConnectNow links are built based on identified topology connections.  Anything that is showing in the NPM Network Topology Widget should automatically be mapped as long as we have an interface monitored on either side of the link.  This is all info you are already likely aware of but, the only way you could validate this would be to compare whats in the widget to what is on your map.  There is also a Core Topology Widget that can show connections also.  Now you could potentially find an example that has "disappeared" and double-check the topology tables in the database too.   

pastedImage_2.png

>> What would get the web based Orion Maps capable of doing what you need?  What is it missing?

"This is another thread altogether but short answer is we haven't installed the latest version" 

Right - which is why I asked - you stated you would be using Atlas, "until Solarwinds get the mapping tool capable of doing what we need (if ever)"

This sounds like you lack confidence that this will be accomplished or it is missing a specific piece of functionality.  So I am looking for what are you missing which would allow you to transition to the web based map tool beyond the obvious that you would need to upgrade to that version of course. As you mentioned above, the latest release does allow for auto connections to be seen on the map or custom connections. -  Orion Platform 2019.4 - Orion Maps is Now Available

0 Kudos

OK, so my apologies, I realise I ought to have been more precise...

What does this mean?  Are you indicating the link is no longer visible and is no longer showing metrics on the map while others are still working?  Are you indicating the popover/ hover no longer works?  Some screenshots would likely help but I would recommend opening a support case if something is disappearing where you would expect to see specific data.

I am saying that the popover / hover no longer shows the expected details.

This is an NPM screenshot with names blanked out.

pastedImage_2.png


And then the same thing from Atlas.

pastedImage_4.png

If I delete this link, then allow 'ConnectNow' to rediscover it and save then NPM starts showing the info.

So, the info exists in the topology tables but I will do as you suggest and raise a case, as I'm not confident of knowing what I'm looking for in the database.

This sounds like you lack confidence that this will be accomplished or it is missing a specific piece of functionality. 

I would say it's more cynicism than a lack of confidence. However, let me not get into that here as until we get the new version installed I can't realistically answer that as all experience is based on older versions.

0 Kudos

No worries Stuart - I love the feedback and conversation.  Curious about why the popover/ hover is important to you in this case?  I know that is a very broad question but I am interested in the importance of this interaction for you and why.  Thank you for helping provide all this info that helps us make our product better!

Curious about why the popover/ hover is important to you in this case?  I know that is a very broad question but I am interested in the importance of this interaction for you and why. 

It's a matter of making life for our engineers as straightforward as possible and in trying not to let the shock of having to use an entirely different product be too much of a culture shock to them. Aside from this they also need to still jump between Solarwinds and our old product (which technically is still current) in certain of our support environments.

For me, personally speaking I'd say this info is important to know / see as, from a map perspective, it is an immediate clue as to where a problem might lie if the link is down.

Secondly, we are also using Solarwinds as a repository for network maps so need them to be as flexible and as configurable as possible to account for the unusual - and boy do we do unusual.

Next, the Atlas maps don't show the interfaces on (our "old" product does) so its helpful in understanding the physical if not the logical or traffic flow layout - again, at a glance. I realise one can click through to the dynamic map, etc, but in a lot of our support environments these don't work to client requirements to not enable CDP, etc

Which leads me to the last reason I like the popovers - in that I could be in the depths of a highly complicated, convoluted secure environment and tehn have to jump out to a plain Jane setup and back again depending on chases, calls, SLA's, OLA's etc and it just helps reset the brain to the environment you are looking at.

Personally I love that the popover shows the interface names, their ifindex and STP which you don't get with manually crafted links.