Linux Agent Deployment
Deploying the Linux Agent to an individual machine is as simple as adding the node to Orion via the Add Node Wizard. To begin, navigate to [Settings -> All Settings -> Add Node], enter the IP address or fully qualified host name of the Linux host you'd like managed in the "Polling Hostname or IP Address" field, and select the "Windows Servers: Agent" radio button from the available "Polling Method" options. Next, enter the credentials that will be used to both connect to the Linux host and install the agent software. The credentials provided here should have 'root' or equivalent level permissions. Note that the credentials provided here are used only for initial deployment of the agent. Future password changes of the account credentials provided here will have no impact on the agent once it is deployed.
The Agent is deployed to the Linux host using a combination of SSH and SFTP requiring TCP port 22 be open from the Orion server (or additional polling engine) to the Linux endpoint you wish to manage for push deployment to function properly.
Once credentials are provided click "Next" at the bottom of the page. You will then be prompted to start the installation of the Linux Agent. Click "Start Install" and the progress indicator will appear. When finished, you will be taken through the rest of the Add Node Wizard flow where you can select which resources you wish to monitoring on the host.
|Install Agent Prompt||Installing Agent Progress Indicator||List Resources|
In some scenarios it may not be possible for the Orion server to push the agent to the Linux host over SSH. This is not uncommon when the host you wish to manage resides behind a NAT or is hosted in the cloud. While firewall policy changes, port forwarding, or one-to-one address translations could be made to facilitate push deployment of the agent, in many cases it may be far easier to perform a manual deployment of the agent to those hosts.
The Linux Agent can be downloaded from the Orion web interface to the Linux host by going to [Settings -> All Settings -> Agent Settings -> Download Agent Software] and selecting "Linux" from the options provided and clicking "Next". In the following step of the Wizard select "Manual Install" and click "Next". Finally, In the third and final step of the wizard is where you will select the Linux distribution you will be installing the Agent on, as well as bitness of the OS (32 or 64bit). Here you can also configure any advanced options the agent will use when it is installed, such as which polling engine the Agent should be associated with in Agent Initiated (Active) mode, or the listening port the Agent will use when running in Server Initiated (Passive) mode.
|Select Agent Type||Select Deployment Method||Choose Agent Settings & Distribution|
Once selecting all the appropriate configuration options, click the "Generate Command" button at the bottom of the page. This will generate a dynamic installation command based upon the the settings chosen above, which can then be copied and pasted into an SSH or X-Windows session on the Linux host. The Linux machine will then download and install the appropriate agent software from the Orion server using those pre-configured options.
Paste the generated command into your Linux terminal session and press 'enter' to start the download and install process.
The command will begin downloading, then installing the Agent onto the machine. When complete, the agent service will automatically start on the Linux host registering with the Orion server, and becoming a managed node.
Once registered select your newly added agent node and click "Choose Resources" from the 'Manage Agents' view to select items on the node you would like to monitor.
With the introduction of the Linux Agent in SAM 6.3 Beta 3, the Orion server and Additional Web Servers are now also Linux repositories for the Agent. This method can be utilized for mass Agent deployment using automation and orchestration tools such as Puppet and Chef. It also means you can use the same native built-in package management tools for the Agent, as you would any other package on the Linux operating system. Now you can install the Linux Agent the same way you might install or update BIND or Apache, using 'yum', 'apt-get', or 'zypper' depending upon your distribution. To utilize 'yum', 'apt-get', or 'zypper' for installing the agent you must first register the Orion repository with your operating system. To do so, navigate to [Settings -> All Settings -> Agent Settings -> Download Agent Software -> Linux] and select 'Install via Package Management Tool (e.g. yum, apt)'.
Based upon the distribution selected in the drop down (1), a command line string is dynamically generated. Simply click the 'Copy' button (2), then paste this string into an SSH session for the Linux host you want to add the repository to and press 'Enter'. Once the repository is added to the host, you can use the appropriate 'yum', 'apt-get', or 'zypper' command to install the agent from the repository. Simply click the 'Copy' button (3) and once again, paste this command into the SSH session to install the Agent. The Agent will then be downloaded from the Orion repository and installed on the host.
|Select Distribution||Add Repository to Host|
|Install Agent||Configure Agent|
CopyPaste Command From Step #3 Above
IP/Hostname, Username & Password
When installation is complete, all that remains is to configure the agent by typing 'service swiagentd init'. This will bring up the Linux Agent configuration settings where you will need to provide the IP, hostname, or FQDN of the Orion server or Additional Polling Engine (option #2). Then enter your Orion 'admin' or equivalent credentials used to login to the Orion web interface (Options 4 & 5). When complete, save your changes and exit (Option 7). This will then register the agent with the Orion server and begin managing it as a node.
|Add Node Wizard||Pull Deployment|
|Deployment via Repository||Manual Installation|
How does the Agent appear under Manage Agents? Is it in a healthy state? How is availability configured on the node? Are you using the Agent for availability calculations or ICMP? What happens when you change it? The behavior you're describing is very unusual, and perhaps a bit too complex to delve into on a forum such as Thwack. Have you opened a case with support regarding these issues?
@aLTeReGo agent does appear but with error stating not successfull. I m using ICMP option only under List resources.
When i change the polling back to ICMP, there is no packet loss observed... Yes i have raised the case yesterday.. waiting for support to revert...
So....after going back and forth with support for a week or so, we all stepped back and...oh yeah....the agent selects the first adapter in a list to ping, not the adapter that it is installed across. So, if your primary adapter is eth0 but shows up second, eth1 (nonrouted) will be the interface it attempts to ping, and will fail. But statistics for the server itself will continue to feed fine, as these are coming over your primary adapter.
So, now I know what to look for in the GUI to get it straightened out. Liking the agent so far--fixes the disk space issue with LInux real nice.
One basic question when monitoring Linux device via agents...we get 2 options when we list resources right- one is ICMP-Fast Ping and other Status & Response time Agent...
I would like to know when will the device show as down if Status & Response time Agent option is selected...
The two options function essentially identically. Agent status will report ‘down’ when a AMS message goes unreplied to by the Agent. The ICMP option reports a node being down when the node fails to reply to an ICMP echo request. The ‘faster’ in this case is really about payload size. ICMP packets are super tiny, where as AMS messages are full size HTTP requests which are a bit larger
Sent from my iPhone
What is the database field for using ICMP (Ping) - Fastest vs Status & Response Time Agent? We would like to setup different alerts depending on which is selected for Agent monitored nodes.
This is kind of hidden, but the answer is Pollers table, so when ICMP set (left) ICMP pollers are enabled and agent disabled for node, when Agent set (right) it is vice versa.
I want to install the agent via repository.
What is the syntax for configuration if you want to specify the parameters in the shell command?
In the swiagentaid.sh file i found this:
There are no parameters you need to pass to the 'swiagentaid.sh init' command. If you are wanting to configure the Agent as part of the provisioning process in an automated fashion, you will want to create an answer file and pipe it through with the swiagentaid.sh init' command. For example.
Create a file called 'driver.ini' that configures the agent to connect to the poller and use a specific Orion credential. For example.
Then pipe your answer file into the agent init command. E.G.
'cat /opt/SolarWinds/Agent/bin/driver.ini | service swiagentd init'
To register the Agent with Orion some form of authentication is required. Whether that's a user keying this into a terminal, or you use an automated mechanism like the one described above, some type of credential must be provided. You could certainly encrypt your answer file and then decrypt it as part of the output, such as using gpg in place of 'cat', but
We were able to automate the deploy and registration with the server _but_ it shows up in the UI under "unknown". Are there additional parameters we can pass to the 'init' or something to drop new agents into the correct group?
That is correct. These Linux nodes do not have the 'City' Custom Property assigned to them, which is why they are under the 'Unknown' grouping. This can be added by editing the node or going to the Custom Property Editor and populating this value.
Is there any way I can automate this?
cat templatedanswerfile | service swiagend init --City=ATL
Note: I'm passing an answer file to the service init to configure it. I'd like to be able to configure the "City" as well.
Can we automate Linux Agent Installation on Thousands of Devices using Linux Satellite system? if yes then please let us know what we need to do from our side.
We dont want to setup the Orion IP Address on individual Agent server.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.