One change that is casuing me some issues is that with one interface down on a map the status upper level map is now down and red. Before the upgrade the status was yellow on the upper map not red? Is there a setting to fix this?
This change was by design. We are now bubbling up the worst status. This was a long-standing request. Is this a problem? If so, can you give me details?
Yes on the traning side, we will need to retrain our NOC staff. An example of why we liked it the old way is that we have many interfaces we are monitoring at our locations. There are times that things are off line for periods of time like an AP taken down for construction, and that in the past had shown yellow on the map not red.
If it's something on a sub-map, you can control how things on a submap are rolled up.
I personally think this is a bad decision without giving the option of choosing which behavior is allowed. In my network we monitor devices at over 140 sites across the globe, so obviously it is very likely that a minor switch will be down at any given point. What good is a geographical map with all red at the highest level when upper management walks in the door of the NOC?
All I can find is that you can choose what percentage of items have to be up to be considered "green."
Are there other options?
That is what I found also, by adjusting the percentage on the submap you can keep the upper level map green with a small red flasher. That is wnat I have done on all my submaps, it is okay, but it may not work for every event. If there is something I am missing would love to know about it.
Another point is that there aren't any global sliders either, so even if I wanted to do that, I would have to edit well over 100 submaps, and that will only let me turn it green.
It should have been a global override option to allow worst state inheritance. I'm actually considering restoring these servers from tape now, and going back to 9.0 because our NOC is upset.
This is a fine option for a small shop, but we use this for monitoring >100 sites in a Fortune 500 company. Not having a global setting or workaround is ridiculous, because the smallest switch outage causes the icon for North America to be red.
OK. Our bad (my bad, specifically, to be completely honest). We should have made it configurable. We will do so in an upcoming patch.
Would it be possible to allow the weighing of nodes differently?It's a matter of perspective but not all nodes have the same importance: routers, switches, print servers, domain controllers, mail servers, etc are not the same to an organization.
Would it be possible to allow the weighing of nodes differently?
We can make it configurable to show mixed=yellow vs. rollup worst, but you're asking for a completely new feature, which is not an option in a service pack.
Let's not get cute we need this as fast as possible, and please when you implement the patch please make the default configuration be the old way (yellow).
The change will be in the first SP, and we are working on it as fast as possible. As for making surprise changes, we had an unfortunate and unusual lack of communication (which, again, was my fault) so that this change to All Nodes is mentioned in the RNs, but the change to maps got left out.
Next time we make a change, we'll make it configurable, and we'll document the change better. Our apologies.
Sounds like a good attitude. Personally I love it when "Release Notes" are just that, a dump of all the little changes that went on in a release, maybe not the technical details, but at least what the effects are. Hate to say it, but your release-notes are more of a marketing hype at times.
I used to feel pretty comfortable upgrading to the latest release right away with SW products, but I have to say lately I'm waiting on feedback like this and usually the first or second SP before upgrading. I've had quite a few tickets in for 9.2, both upgrade problems and in production problems, and I waited for SP2 to come out before upgrading to 9.0!!
I was very tempted to upgrade to 9.1 to try and fix some of the problems right away, but I'm glad I came to the forums first - otherwise I'd have my NOC hollering at me too...
Has anybody tried polling the cisco devices in NPM9.1 on SNMPv3
Whenever i upgrade to 9.1 my CPU and memory stops polling when i downgrade to 9.0 SP2 everything works fine.
Is this an issue or what ???
I even have a ticket logged for this, the team has been really helpful but the reason for this issue is still not clear.
can solarwinds team test this on their lab setup?? can someone share the SNMPv3 commands they used for the setup. The TAC team is saying i am not polling all the required MIBs but it was working on 9.0 and 8.5 too i am polling on SNMPv3 since feb without any issues with the same settings. Even if i downgrade back to 9.0 it starts working.
I upgraded from 9.0 to 9.2 with SQL std 2005 DB on a seperate server
Is it possible that till the time the issue is not fixed i can use the webconsole of 9.1 and pollers on 9.0 SP2 ????
