Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Parent Map shows wrong status

I have 2 levels of map nesting, the parent map always shows a yellow node even though both levels below are fully green. Why would this be?

Find more posts tagged with

Accepted answers

All comments

Isaac

Hi Dave,

Welcome to the dark and lonely world of Orion.

I have experienced a similar problem with several of my nested maps. By removing one of the nested maps from a parent map and then re-adding it I have solved this problem on several occasions. However, it has not always worked.

It would be nice to know if someone else has a solution to this problem. Someone like SW support.

FormerMember

Hi,

I had the same problem and it was caused by a network link that was missing it's interface. As soon as I associated the link to the corresponding interface the map came back to green.

Hope this helps

GR

JohnM

I spent about a week with this, and I finally figured out why this was happening for us.

There was:

1) An 'unknown node' that was put on a child map in the size of 1x1. I used the "select all nodes" ability from the menu bar, and after deselecting all the ones I wanted, it was selected, its properties were there... so I killed it with my all mighty delete button. Fixed that problem.

2) We had a parent map that depended upon "NameofMap" for its status, which had unknown, downed, etc. type of nodes on it. Well, "NameofMap" wasn't the correct map to figure out the parent's status, it was "NameofMap USA", yet via the website the link would go to "NameofMap USA" so that was hard to find. Simple mistake. To find out if this is the case, go to Map Maker, and check out your maps, and if your child maps are the correct ones to be looking at. If they aren't, I believe it's just a matter of associating/linking to the map you want.

3) Someone installed a different interface between two switches, so it showed that the line/link between the switches was down. So, that was easy to see where it was, but we had to do port searching to figure out what exactly the new interface's name was, and associate that to the line on the map.

If any of those weren't explained well, or you'd like more info on any of them, let me know.

John M

Bandag - World Leader in Retread