Between sharing your Network Atlas maps and Worldwide maps, you've all helped us out as we continue to improve the Orion maps. Which is why we want MORE! Show us your Orion Maps (or at least the ones you cannot live without) OR email it directly to me at firstname.lastname@example.org AND answer the following questions, then we'll award you 500 thwack points. (You must answer the questions as well as share your maps to get points)
Please submit your maps by December 31, 2019 to receive 500 THWACK points.
I love maps for reports and for training new Network Analysts about our sites. Maps--when kept current--are a visual shortcut to seeing what may be impacted by losing any piece of hardware or circuit.
I need to have fewer places to reference, to keep current, to use as my sources of truth. Towards that goal, I need maps to be able to display and filter information from Network Atlas so that I don't need to open/use Network Atlas at all any more. I'm thinking of things like:
Maps and Atlas are important for keeping uptime at five or six 9's. When we have accurate maps, we know what's supposed to be connected. If we didn't have maps and atlas, we'd have to buy something to do the discoveries for us, or do the work manually. I'd done both and ended up more satisfied with the output of the manual discovery and tracking. But it leaves human error as a factor for making the maps stale. If someone removes or adds a new device to the network and doesn't add it to the map, the information is unavailable for use when planning and troubleshooting. If someone makes an error when doing manual map modification, your mileage will vary.
Better still would be having NPM do all the mapping AND automatically learning nodes in the map based on CDP or LLDP information, and then automatically adding them to NCM and NPM monitoring while simultaneously updating the map. When the map changes due to a node being down, if it had been correctly autodiscovered by the mapping process and added to NPM and NCM, it should stand out like a red light on the front page of NPM, and at the highest level of a map.
Maps should be nested:
What we are looking for is clarity around what is necessary to improve your experience with the tool. If you are still using Network Atlas over the web based Orion Maps, why? You indicated that you use the tool to show the network but it gets too busy, what would improve that? It is hard to tell from that screenshot but it appears you are mapping out a ton of interfaces in that example.
I emailed 2 maps to Kristin both of the same devices and links. One was in Atlas the other Orion Maps. Orion Maps can get cluttered very quickly in a small space as nato has indicated.
Here's a small snippet. Custom labels in Atlas, I can also choose to have custom labels/description for the links which I can move around (I have none though in the example). These can show me utilization, bandwidth speed etc. Also port channel shows red in atlas but not in orion maps (it was already down before I created the orion map)
Sorry I have not emailed you since our previous messages on this subject. My 2019.4 upgrade (just for the new Orion Maps features) was a bit of a disaster.
2) I think the main things I still use in Atlas that I couldn't do in the new maps are custom labels, custom tooltips, and being able to select and delete connections that I don't want the map to display. Would be good to just have some kind of "hide this connection" at least.
3) I find that the main value add in building these maps is it provides a way for someone who knows how everything comes together to document that and make it accessible to the rest of the team. I may know all the critical interfaces for my WAN topology but the new hire hasn't learned them yet and it's a lot easier to point them to a WAN dashboard in Orion than to actually sit down and explain all the bits every time. Similar problems apply to application architectures.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.