Hello all. I am wondering if we can configure a remote SAM poller to look to the SQL DB on a different port than 1433? We are running this in the cloud and I need to connect back to SQL.
I believe your question is answered by the following KB article.
SolarWinds Knowledge Base :: How do I connect Orion to a named instance of SQL Server 2005 on a non-standard port?
One other question. What ports are required for a remote poller? I know that it needs to reach MSSQL on 1443 (or whatever port we have listening), and the main needs to reach 17777 on the SAM server, and then the SAM server needs to reach 17777 on the remote poller. SW support is telling me that I also need 17778 to be reachable between the poller and main sam server, both directions. Is this the case?
Port 17778 is the Agent port. This port is only required to be open between the Orion server and any machine where the agent is installed. If you have an agent installed on your Additional Poller, then yes you will need to have that port open. If you don't have an Agent installed on the Additional Poller itself, then this port being opened between the main Orion server and Additional Polling Engine is unnecessary.
Hey thanks for the info here. I cannot get a node added to point to my remote poller. It adds and shows up fine in SAM except I cannot choose any resources to monitor. It seems that the agent gets installed but no plugins actually get put on this node. Any advice?
How was the agent deployed? Is the server where the Agent was deployed pending a reboot from some recently installed Windows Updates? The Agent requires .NET Framework 4.0 before 'List Resources' will function properly. The .NET Framework 4.0 will not however install if the server has Windows Updates that have been downloaded and installed but not yet applied until the server is rebooted.
