SolarWinds Nodes initiating te Discovery instead of the Polling Engine

bootneck1111

Hi Guys

This is one I have not come across before so reaching out to you guys.

Layout: Active & Standby Polling Engines hosted in AWS (US) monitoring elements to multiple sites (US)

Question: One of the sites only want to monitor their Domain Controllers (3 DCs), Security Conscious site and have said that the Domain Controllers used to be in SolarWinds but no longer. I have said "provide me with the IP addresses and I'll run the discovery, I have the IP addresses and the discovery finds nothing..."

I have said that commonly this is down to boundary restrictions such as a firewall and Access Rules may need adjusting/applying to allow the 2 x SW Pollers to see the Domain Controllers on site.

Problem: The site only wants to allow Outbound communication from the site to the Pollers in AWS, and they believe that the 3 x DCs were discovered previously without having the firewall allowing inbound traffic from the AWS Pollers.

I have not come across end points or client nodes running/completing the Node discovery and would like to know how this is done, if in fact it can be donw.

In advance thank you for your support.

stevenstadel

If they only want outbound communications, using the agent in agent-initiated mode will work. You can not discover the network if they do not allow inbound. The agent needs to be configured on their side. (Or you preconfigure it and download/send a golden image to them)

Agent communication modes (solarwinds.com)

Have them open port 17778 to your pollers and allow outbound access. They can check the agent configuration on the servers to ensure it is running and that they are pointing to the HA VIP, or to the proxy that sends to your VIP for your HA config. They can test that they can get through with Powershell to that VIP using test-netconnection to port 17778 to your HA VIP.