Unfavourable MAp changes after upgrading to NPM version 9.1 sp3

Question

We recently upgraded our Orion NPM from version 9.0 sp2 to version 9.1 sp3. A few changes have occured in Map maker which we would hope there is a quick fix for. Our Map overview has been designed using orion network objects and then these objects are linked to visio diagrams(with their respective interfaces and nodes) which have been imported into the map maker. Now whenever an interface or node goes down in a site, the sites(network object) in the Map overview turns red even though the site is still reachable. This never used to be the case. Is there a global setting to fix this?

Oristilli · Answer

I was able to resolve my problem by right clicking on the map in orion map maker , selecting properties and  there are two options there one for adjusting the zoom level and the other one to adjust the MAP status on the Parent map. This defines when it should go in a warning, down or unknown state. It's a bit tricky, for me I had to take into consideration the number of critical objects in the site before adjusting it. Even though I had to do it for all the individual sites that are displayed on the parent MAP, whenever I now create a new Map it accepts the last setting defined on the last new MAP so I don't have to keep adjusting it everytime.

bshopp · Answer

Did you change the setting in the Admin page as referenced in the thread? Admin -> Web Console -> Status Rollup Mode

Mike_C · Answer

Wondering if this appliees to something we have had a question on.  Our network maop shows the entire US (we have multiple sites in every state.  State maps are nested in the US view.  Currently, if 1 node goes down in a state, the state map status shows red, someone mentioned that this used to cause the state map to show yellow unless ALL sites were down in a state.  Is this possible to do, to show a yellow status if 1 or more, but less than all sites down?