Open for Voting

Simplify Additional Poller Communication Model

I would like to see the communication model for the Additional Polling engine significantly reduced.  Currently are using a remote poller in a secure environment and the communication requirements for that to work are complicated, unclear and undocumented.  The additional poller should communicate on one single port back to the master system across which all traffic should be both compressed and encrypted and that should be it.

I am certainly open to feedback on this.

byrona

  • Correct me if I'm wrong, please, but an additional poller only requires 4 ports (all of which are encrypted) to communicate back to the Orion Primary Poller/Orion Database Server. At least, that is what page 555 of the SAM administrators guide says. Which my personal experience seems to support.

    pastedImage_1.png

    Communication complexity within the network that the additional poller is actually polling is going to depend on what you are polling and your method of polling. That said, there are ways to decrease your port footprint and unencrypted packet exposure.

    Yes I realize I just commented on a 2 year old post.

  • I couldn't agree with this more.  The communication on this seems crazy over complicated.

  • our corp sec guys are looking at me like deers in truck's lights when I ask them to poke the firewall like a swiss cheese. We have an APE per network Zone and it is not so easy to maintain.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.