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
Store

Can anyone answer these issues?

We have
multiple engineers that work on our SolarWinds
environment. Since there is not a desktop version of the System Manager we have
to login to the servers themselves to access the System Manager console. Does
multiple people logging into the SolarWinds
servers and opening the consoles cause a problem? I do have the ability to
monitor connections to a server but currently we are not monitoring
connections. When we originally opened this issue as the hot standby
server continues to activate unexpectedly. I believe this case has changed
somewhat. It appears the hot standby problem we were seeing before is a cause
of a user logging into the SW poller. When that happens the poller gets behind
and then the standby activates. But when we get this far the only way to clear
up this situation is to restart the polling engine.

I
had asked before if my pollers are over taxed. Could this still be the case? Is
there any algorithm you could provide to me to show that they are not over
taxed?

Yesterday
in the lab one of our engineers logged into the primary polling engine at
4:01PM. The engineer then logged off at 7:01PM. Why is the SNMP polling
engine off and not up to date?

We
have been over and over this issue and really need to resolve this very
soon. There are several tickets open with SW; I hope you can provide some
insight to all of this.

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Since there is not a desktop version of the System Manager we have to login to the servers themselves to access the System Manager console

If your administrators need access to system manager remotely you should consider the "Orion Remote Administration Package". This allows you to run the System Manager, Map Maker, and etc.. from your workstation to manage the Orion NPM Server. All without terminal services.

FormerMember

Unfortunately, we don't have sell the remote admin pack any longer. Changes to Windows' security model with XP SP2 broke our method for using the RAP. We are looking into building something for Maps and Reports.

FormerMember

Does multiple people logging into the SolarWinds servers and opening the consoles cause a problem? I

Opening System Manager will typically have a negative impact on polling performance.

In Orion 9.0, you will be able to add/delete/edit nodes from the web console. If you could do that, would you still need to access System Manager as much?

wvitalec

Even 1 person logging on causes a problem.

wvitalec

I don't know if that will solve the issue. If 1 person logs on to the manager and the data comes up missing in spots, would the web console really fix that?

FormerMember

Yes, any time the System Manager is opened, it will have a negative impact on polling because they are using the same thread. If your server is right on the edge, then opening SM can push it over the edge. Web-based node management gets around the problem because it is not using the same thread as the poller.

FormerMember

Does multiple people logging into the SolarWinds servers and opening the consoles cause a problem?

I'm not sure if this is your situation but SM should only be run from the primary system (which runs the website). If you run SM from the primary and from an additional poller at the same time you will at some point cause a conflict and the netperfmonservice will hang and polling will stop. The workaround is to disable orionnetperfmon.exe on all additional pollers and have all engineers use the SM on the primary system. Multiple engineers can be remoted into the primary system and run concurrent copies of SM without a problem. We have not had any further incidents since disabling SM on the additional poller.

What is the fail-over set to for hot-standby? I believe 5 min is the default. If you have it set too low, you may experience HS activate/deactivate unexpectedly. If your SQL system is congested or Orion has trouble communicating with SQL, Orion's queues will grow. It is my understanding from SW Support and I hope I say this right, once the number of queued SQL requests reaches 900 (SQL limit), SQL will terminate the remote connection (Orion). This will result in a netperfmonservice hang and polling to stop.

wvitalec

Yes, it is because the software is single threaded and cannot handle someone making administrative changes in the System Manager and keep up with Polling a large number of elements. Any word on possible enhancing or fixing this issue? The SolarWinds developers would make my life 100% better if this single threaded issue was resolved.

FormerMember

In 9.0, you can make most admin changes from the web console, so there's no need to open System Manager.