Have many SolarWinds Network Atlas Maps and do not want to have to recreate each on into Orion Maps. We need a tool to migrate existing Network Atlas Maps in Orion Maps.
https://documentation.solarwinds.com/en/success_center/orionplatform/Content/Release_Notes/Orion_Pla...
Network Atlas is deprecated as of this release and will be removed in a future release. SolarWinds recommends that you start using Orion Maps in the Orion Web Console to display maps of physical and logical relationships between entities monitored by the Orion Platform products you have installed.
Network Atlas and Orion Maps are structurally different, this would prevent a migration tool from offering 100% migration as there are constructs that only exist in each map type. I am curious what would you consider as required from a tool like this, for example, if there were a tool available which would do the following, would that meet your needs?
This has been discussed a few times and I have even had a phone chat about it with @jblankjblank so have tagged him in.More and more of us want/need the updates but don't want the pain of converting old world stuff to new.
Also, I'll add and point out that it is a HUGE, for us, caveat with the new world offering.
This bit you probably know, is that you can currently configure groups and sub-groups in NPM to show group specific maps. So when you name a map in Atlas, with the same name as a group, then that map shows up only in that group.
You can't (unless Solarwinds have provided a patch that I haven't seen), as yet, have that same functionality with Orion Maps.
I think that the migration tool would not convert NA Map into Orion Map to satisfy the users. Both kind of maps are too different and Orion Map has too little features to make the conversion succesfull - I mean without additional effort to make it readable and sensible. I'm pretty sure that it would be wasting time to build up perfect converter.
My suggestion is to keep NA and NA Maps for a loger time to allow users to transit from NA MAPs to Orion Maps step by step, for at least a year yet. At the same time SW should present information that NA Maps are deprecated and will not be supported from - let say 2022 Platform. There is a question to SW Team, if displaying NA Maps would be possible even without NA application?
I asked my users to resign from NA and NA Maps months ago already.
So Orion has to create some kind of conversion tool for Network Atlas, you guys have to give us some kind of pathway to convert all these maps we have created in Network Atlas for YEARS that most our support teams and leadership relies on daily. I mean Network Atlas is not a small insignificant application, a lot of companies decide to purchase SW NPM in part because of Network Atlas and a lot of us have built and hosting close to hundred maps in our system. Do you understand the all the overhead and man hours that incredible expense that will cause companies to recreate all our maps manually? There are companies with huge worldwide networks with their entire network infrastructure mapped out in Network Atlas. So you mean to tell me companies like Boeing, Lockhead Martin and Department of Veterans Affairs are going to just accept that all their maps are just "poof" up in smoke because SolarWinds say so? Is Orion really this disconnected?
Actually @jdbramwell we do not expect everyone to switch over at the drop of the hat, which is why Network Atlas-based maps will continue to be supported on the platform for some time. The deprecation statement isn't giving a drop dead date - it's just saying that we're investing more time and development on Orion Maps.
There's also zero chance that we can build an "everything" converter tool because the underlying architecture is just so inherently different. This is why @tony.johnson was asking what are the most important things from the Network Atlas Maps that you'd like to be converted to Orion Maps.
It sounds like you are very interested in a tool like this, so please provide us a list of things that would be required in the tool, sorted by most important needs first. Tony's provided an excellent starter list, but I'm sure there are things that he's omitting.
BTW - If you just need the icons/backgrounds, then there's already a solution for that in Export Network Atlas Map Files from Orion [PowerShell].
@KMSigma.SWI Well if Network Atlas-based maps will continue to be supported on the 2020.2 platform for some time then why did we lose our maps after migrating to 2020.2 from 2019.4 HF5
We now get the following message of
“Unexpected error: An error occurred while generating map 338bc0b4-b69a-451e-9aeb-3b8c6d03dbd2.OrionMap”I can create custom maps and auto-generated maps but really don't want to re-create a bunch of maps.
@rcaballero Network Atlas maps are still supported as previously mentioned. The error you are sharing represents that you had an issue with Orion Maps however correct? It sounds like you can generate new maps but the existing maps you had built prior to the upgrade are no longer allowing you to make changes? Is that accurate?
There was a bug found in 2020.2 that was addressed. If you are upgrading from 2019.4 HF5 you should be able to upgrade to 2020.2.1 HF2 which would be recommended path.
@jblankjblank
The issue was ultimately directory permission issues. For some reason Solarwinds update/install changed the permissions on several directories.
We have lots of maps and would like to see a migration tool.
Tony,
Can or will SolarWinds Network Topology Mapper (NTM) be integrated with NPM and or HCO?
The Shadow node feature isnt working despite being set in global settings. The nodes arent appearing, sometimes the background appears other times it doesnt, the connections are also not as they used to be and sometimes missing .
@lynchnigel Go ahead and open a ticket for that. We probably need to gather some diags and let the team do some investigating.
