Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Orion Platform > Orion Documentation > Orion Platform Administrator Guide > Poll devices with SolarWinds Orion agents

Poll devices with SolarWinds Orion agents

Table of contents
No headers
Created by Caroline Juszczak, last modified by Magdalena.Markova on Sep 14, 2017

Views: 2,301 Votes: 0 Revisions: 5

Updated: June 11, 2018

This topic applies to all Orion Platform products except for the following products:

EOCIPAMUDT

An agent is a software that provides a communication channel between the Orion server and a Windows or Linux/Unix computer. Products install plugins on agents to collect the data that the agents send back. This can be beneficial in situations such as:

  • Polling hosts and applications behind firewall NAT or proxies.
  • Polling nodes and applications across multiple discrete networks that have overlapping IP address space.
  • Secure, encrypted polling over a single port.
  • Support for low bandwidth, high latency connections.
  • Polling nodes across domains where no domain trusts have been established.
  • Full, end-to-end encryption between the monitored host and the main polling engine.

You can monitor servers hosted by cloud-based services such as Amazon EC2, Rackspace, Microsoft Azure, and other Infrastructure as a Service (IaaS).

After deployment, all communication between the Orion server and the agent occurs over a fixed port. This communication is fully encrypted using 3072-bit TLS encryption. The agent protocol supports NAT traversal and passing through proxy servers that require authentication.

Learn more:
Last modified

Tags

Classifications

Public