Hello.
I was wondering if there is anyway for my Solarwinds server to pull node information from another SolarWinds server I have administrative access to. Is there anyway to do that?
Good call - I hadn't tried this out yet, but it does sound like it might solve the problem.
Here's the link: http://www.solarwinds.com/products/orion/eoc/index.aspx
This should work pretty well, considering you basically have two standalone Solarwinds installations in separate sites.
What type of information are you trying to pull? Can you be a little more specific?
I just want to use the other sever as a polling agent. We can connect to the SW server just fine, but not some of the core routers we need to monitor on the other end that are already using two community strings (one for the firewall and one for the SW server). That and we think ICMP is being blocked somewhere, but that's another, non-Orion related issue.
I would think that I could use another SW server I can reach to monitor nodes I can't reach on my SW server. If this is not the case, I can find another solution to my problem.
It sounds like you're wanting to rollup data from another polling engine.
Although Solarwinds doesn't support a polling engine connecting to a SQL Server across a WAN link, it could have it's own SQL Server and rollup the data. Then again, if you're not going across a WAN link you won't have this problem anyways. :-)
This post might be of some help:
I think you may end up having to call Solarwinds support to get the exact information you need, and to verify you'll have it setup properly. I can't seem to locate any information in the administration guide, though others might have some more exact processes for you.
Mark, any ideas?
Okay, I finally found out what they want us to do. I'm at the hub site. I've got the enterprise domain and exchange servers, primary SW/SQL, etc etc. At our remote site (it either goes through a radio or sat shot), they're maintaining a completely separate SW/Sql sever. Because of the distance between the two sites, we cannot monitor some of the core switches or routers: ICMP packets run out of TTL and SNMP packets get lost somewhere, even if I use the right community strings. The remote SW suite, being much, MUCH closer, both logically and geographically, doesn't have this problem. The question is, can we make the remote SW server report to the primary SW server on the status of those nodes, preferably without mucking around in out DB? Or, as it was put to me: "Hi, remote site. I'm primary site. What's up with NFR11? Oh, it's up? It's passing x amount of data? Thanks, that's what I needed."
Hope that clears it up
-Cpl Wallace
I may be wrong but what you are describing is what the new EOC is supposed to be doing for us. It is for geographically distributed networks. that helps unify remote npm servers. check it out on the sw website. there is even a trial that may work for you.
That looks like EXACTLY what we're looking for. I'm waiting for authorization to install the trial and we'll see how it works. Thanks, gents
