photoshas.blogg.se

What ports must be opne to use the orion solarwinds api
What ports must be opne to use the orion solarwinds api







what ports must be opne to use the orion solarwinds api

Simply adding 17778 to this ACL should permit the agent to communicate: acl SSL_ports port 443 8140 17778 On RedHat-based systems Squid comes preconfigured with an SSL_ports ACL. This is not permitted in the default configuration, though the following modification should allow this. On a Squid proxy, HTTPS clients must have CONNECT privileges to the Orion SDK port. Hostname or IP address of an HTTPS-capable proxy server. Note: Unlike targetpw and proxypw, the shared secret will not be hashed for storage in swi.ini.

what ports must be opne to use the orion solarwinds api

This parameter is mandatory when agentpush is set to false.

what ports must be opne to use the orion solarwinds api

Sets a shared secret for use in server-initiated communication mode. In this situation, I'd be strongly inclined to push the agent install from the Orion console, though there may be use-cases I've not thought of. Note: Server-initiated communication mode will require manual intervention in Solarwinds, and as such probably negates many of the advantages of using this module. On setting this parameter to false, agentsecret becomes mandatory. When set to true, the agent will operate in agent-initiated communication mode. Used to control the agent communication mode of swiagentd. This is an unfortunate (security-wise) neccessity as swagent must be given the plaintext password. Note: The password will be SHA1 hashed for permanent storage in the swi.ini file, though it will be briefly exist in plaintext form in a (mode 600, root-owned) temporary file whilst Puppet is piping the information to swagent. Valid password for the user specified in targetuser. Username of an Orion user with sufficient privileges to create nodes within NPM on the server specified in targethost. Hostname or IP address of your Orion server.ĭefault value: targetport Below is the same configuration written directly into a manifest. swiagent::targethost : '192.168.0.1' swiagent::targetuser : 'orionuser' swiagent::targetpw : 'SuperSecretPassword' swiagent::proxyhost : '192.168.0.2' swiagent::proxyport : '8080'Īlthough iesmith-swgagent was written with the intent of configuring the module via Hiera, it may be equally well configured via a class declaration. Setup puppet module install iesmith-swiagentīelow is a relatively simple installation of an (already installed) swiagent, followed by configuration of the agent to talk to the Orion server 192.168.0.1, via a proxy at 192.168.0.2:8080. One, which led to the development of this module, is the possiblity that the monitored hosts reside within a secure network, such as a DMZ in which only limited inbound and outbound connections are possible. While agents can be deployed from the Solarwinds console itself, there are many use case in which this isn't simply possible.

what ports must be opne to use the orion solarwinds api

The swiagent module can be used to control and deploy the Solarwinds Linux agent in ways not possible via the Solarwinds Orion interface.









What ports must be opne to use the orion solarwinds api