34 Replies Latest reply on Nov 27, 2017 4:23 AM by pratikmehta003

    Linux Agent Deployment

    aLTeReGo

      Linux Agent Deployment

       

       

      Add Node Wizard - Push 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.

       

      Agent Deployment Add Node.png

       

      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 PromptInstalling Agent Progress IndicatorList Resources
      Install Agent Software.pngInstalling Agent Software.pngList Resources.png

       

       

      Manual - Pull Deployment

       

      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 TypeSelect Deployment MethodChoose Agent Settings & Distribution
      Select Agent Type.pngAgent Deployement Type.pngAgent Distribution.png

       

      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.

       

      Copy Install Command.png

      Paste the generated command into your Linux terminal session and press 'enter' to start the download and install process.

      Console Session Install Agent.pngThe 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.

      Agent Download and Install.pngOnce 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.

      Choose Resources.png

       

      Mass Deployment - Repository

       

      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)'.

       

      yum.pngBased 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
      Linux Repository.png

       

      SSH Add Repository.png

      Install AgentConfigure Agent

      CopyPaste Command From Step #3 Above

      yum install.png

      IP/Hostname, Username & Password

      Configure Agent.png

       

      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 WizardPull Deployment
      Deployment via Repository Manual Installation
        • Re: Linux Agent Deployment
          cbunge

          So odd question.  If we install the Linux Agent on a machine, do you think it will communicate back to the 6.2 SAM as well?

          • Re: Linux Agent Deployment
            cbunge

            Unfortunately trying to convince our Linux admins to turn on SNMP and configure has been an uphill battle. They are used to using a shareware software that has had an easy to configure agent installed.  It would be nice to get a large range of OS's as a lot of OVA's seem to come with CentOS or Debian.  To give you an idea of what we have out our vCenter alone (gotta love the Fedora 7 :-|

             

            Linux.PNG

            • Re: Linux Agent Deployment
              bluefunelemental

              So we have some cloud linux instances which will not be able to download the agent from our on-prem Orion server.

              Will you plan to host any agent installers in public-facing repos or is that up to us?

              Any reason that would not work?

              • Re: Linux Agent Deployment
                xpowels

                Tried to push to Redhat 6.5: Failed.

                Pulled agent install fromRedhat 6.5: Install correctly as best I can tell.

                Back in Orion, it shows up as a running an connected agent. However, when i click the checkbox next to the server, Choose Resources stays grey. What next?

                  • Re: Linux Agent Deployment
                    aLTeReGo

                    It may take a moment for the plugins to deploy and the agent to be fully operational. If the agent is still not operating normally please gather a Diagnostic from the Orion server and zip the contents of '/opt/SolarWinds/Agent/bin/appdata/Logs' on the machine where the agent is installed. Then reply to the Beta email you received, attaching these log files. We will take a look through the logs.

                      • Re: Linux Agent Deployment
                        xpowels

                        My diags are 29MB and the logs are 4MB.....not going to fit in an email. Can you suggest an alternate method?

                          • Re: Linux Agent Deployment
                            aLTeReGo
                            1. Navigate to solarwinds.leapfile.com.
                            2. Click Secure Upload.
                            3. Enter support@solarwinds.net in the Recipient Email field.
                            4. Click Start.
                            5. Complete the Secure Upload form and click Select files to send (Regular Upload).
                            6. Click Choose File and select the Diagnostics file to be uploaded.
                            7. Click Open.
                            8. If you have finished selecting files, click Upload & Send.
                              Note: Please reply to the beta invite email you received to let me know that you've successfully uploaded these files.
                              • Re: Linux Agent Deployment
                                xpowels

                                Uploaded

                                  • Re: Linux Agent Deployment
                                    aLTeReGo

                                    Thanks xpowels. I have retrieved the logs and have created case OA-972 internally for investigation.

                                    • Re: Linux Agent Deployment
                                      Petr Vilem

                                      From provided diagnostics it seems that communication between agent and orion is established and even plugins are deployed correctly. Missing piece is that this agent is not yet managed as orion node. Node record will not be created automatically because this agent was originally deployed via add node wizard that was not fully finished.

                                       

                                      In agent management grid, next to grayed "Choose resources", there should be also "Manage as node" button that will take you back to add node wizard which needs to be completed first. If this wizard does not work (e.g. hangs on list resources step for some reason), please try following steps:

                                       

                                      1) stop agent on target linux box: service swagent.service stop

                                      2) go to orion web console / manage agents and delete record for this particular agent (it may warn you that agent is not connected so it will not be uninstalled, but that's reason why we stopped it in previous step)

                                      3) make sure that agent record is gone from orion (you may need to refresh agent grid manually)

                                      4) perform agent re-provisioning to make new registration in orion: service swagent.service init

                                      5) once provisioning is completed agent should automatically start and connect to orion

                                      6) agent record should be recreated and become visible on orion side and this time node record should be created automatically unless it is disabled by global agent configuration (by default it is enabled)

                                      1 of 1 people found this helpful
                                        • Re: Linux Agent Deployment
                                          aaguilar

                                          Let's say that you need to Uninstall the agent some other way: based on distro

                                           

                                          rpm -e swiagent or if the agent is connected you can delete using the ui

                                          yum remove swiagent

                                          apt-get remove swiagent ( or  apt-get remove purge --auto-remove swiagent) (or say snmp)

                                          rm /tmp/taskProperties.*

                                          1 of 1 people found this helpful
                              • Re: Linux Agent Deployment
                                joedissmeyer

                                My first attempt with installing the Linux agent.

                                *** NOTE: Linux is new for our organization and many of us are not yet at the 'intermediate' level of expertise but we are learning quickly - by force I, myself, am definitely a beginner. RHEL v6.7 and v7 will be our standard.

                                 

                                Details:

                                • Machine OS is RHEL v6.7, managed by Satellite.
                                • I have full admin access to the machine via SUDO. I do not know what the ROOT password is and it will not be shared with me.
                                • Was unable to deploy the agent automatically from the Orion web console since the root user was required. Instead, followed instructions and generated the command below:

                                 

                                bash -c "$($(if which wget &>/dev/null; then echo 'wget -O -'; elif which curl &>/dev/null; then echo curl; fi) http://USO12QSLRWND02:8787/Orion/AgentManagement/DownloadLinuxOnlineInstallScript.ashx?requestId=baf7119d-ca6c-42ea-9941-f0a44f71ce86)"

                                 

                                Ran this locally on the RHEL server and was presented with an error:

                                 

                                bash: line 10: [: -v: unary operator expected

                                 

                                Screenshot:

                                2016-03-03 09_14_55-Inbox - Dissmeyer, Joseph  (NBCUniversal, Orlando) - Outlook.png

                                In the shell you can see the package attempted to download and failed.

                                  • Re: Linux Agent Deployment
                                    toby.burton

                                    Just ignore the following line as it doesn't hurt anything and will be fixed in the next beta.

                                    bash: line 10: [: -v: unary operator expected

                                    Since you only have sudo access to your RHEL box, I would suggest you see if you can manually download the rpm and install with the following steps:

                                    1. Confirm the distro and architecture
                                      1. cat /etc/redhat-release
                                      2. uname -m
                                    2. Download the rpm file from the Orion to your RHEL box (there will be an easier way in the future for this)
                                      1. For RedHat 6.x -32 bit use
                                        1. curl http://ip_address_of_orion/Orion/AgentManagement/DownloadLinuxPackage.ashx?packageId=rhel-6.0-x86 > rhel.rpm
                                      2. For RedHat 6.x -64 bit use
                                        1. curl http://ip_address_of_orion/Orion/AgentManagement/DownloadLinuxPackage.ashx?packageId=rhel-6.0-x64 > rhel.rpm
                                    3. Install the rpm using sudo.  The beta currently does not provide an automated way of installing using sudo, but you can manually install the rpm once you have the rpm file.
                                      1. sudo rpm -Uvh rhel.rpm
                                      2. If this doesnt work, make sure you have the right package (ie 32 versus 64 bit)
                                    4. Now that the agent is installed, we need to start the manual configuration of the installed agent to use the appropriate SAM Beta Orion Server/Poller
                                      1. sudo service swagent.service init
                                        1. Press '2' to set ip_address_of_orion
                                        2. Press '4' to set Orion admin.  Normally this is 'admin'
                                        3. Press '5' to set Orion admin password if required.
                                        4. manual-config.png
                                        5. Then just press <enter> to provision the agent with the orion server.
                                        6. You should see something like this:

                                     

                                    Agent is initiating provisioning. Please wait until it finishes.

                                     

                                    Agent device ID [675C7678-1B0C-483C-A536-B15F88772EE5], Provisioned by [lab-apm-demo], device ID [22DF091B-CA01-4FD4-B833-DAAF7DB80F4D]

                                    Press ENTER to continue...

                                    2 of 2 people found this helpful
                                      • Re: Linux Agent Deployment
                                        joedissmeyer

                                        Thank you for these instructions toby.burton I was able to successfully provision the Linux agent to my RHEL 6 machine.

                                        I initially had a problem with downloading the rpm because I forgot to include the 8787 port in the url .

                                         

                                        Provisioning was good and the agent shows up in the console. However it has been more than 10 mins and the node still displays as "unknown" status.

                                        2016-03-07 07_24_44-.png

                                         

                                        It is running in agent initiated mode.

                                        When I attempt to list resources it never finishes.

                                        2016-03-07 07_27_05.png

                                         

                                        Do you know where I can find the Linux agent logs?

                                          • Re: Linux Agent Deployment
                                            joedissmeyer

                                            toby.burton --- I figured it out. The problem was that in my beta install I never set a password for the admin account (it was 'blank'). I create a password for the user in the Orion console, ran through the agent configuration again on the RHEL server (sudo service swagent.service init) and now it appears that agent polling is working.

                                             

                                            2016-03-07 07_38_16-Manage Agents.png

                                            Drilling into the node details of this server shows that the server's vital stats and data is flowing in as expected.

                                            1 of 1 people found this helpful
                                      • Re: Linux Agent Deployment
                                        fredrikolausson

                                        Hi,

                                         

                                        One of our technician has found that a cron job has been created when i installed the Orion agent on a Linux machine where it tried to start up the agent every minute, why is this job created?

                                        • Re: Linux Agent Deployment
                                          cory.chandler@boystown.org

                                          I'm seeing this error in RHEL7 when trying to use the repo process -" [Errno 14] curl#60 - "Certificate key usage inadequate for attempted operation."  I have a ticket open but no help yet - Case # 1347278

                                            • Re: Linux Agent Deployment
                                              aLTeReGo

                                              Is your Orion website configured to use HTTPS?

                                                • Re: Linux Agent Deployment
                                                  cory.chandler@boystown.org

                                                  yes and we are using an internal cert

                                                    • Re: Linux Agent Deployment
                                                      aLTeReGo

                                                      Using repository from Orion accessible only via https with not trusted certificate

                                                      When the Orion web interface is configured to use HTTPS, it uses some certificate. This certificate can be quite often be self-signed, and therefore not trusted. The recommended method to fix this is by adding Orion's web certificate to the trusted certificates on target linux agent machine.

                                                      Getting certificate from web browser

                                                      In Firefox you can export this certificate in the following way:

                                                      • Open the Orion web interface in Firefox
                                                      • Click on icon left of the URL
                                                      • Click on the Details button:

                                                       

                                                      • Click 'More Information':

                                                       

                                                       

                                                      • Click 'View Certificate':

                                                       

                                                      • On 'Details' page click 'Export':

                                                       

                                                      • Save it to your local file system:

                                                       

                                                      Note: Above steps were taken from Firefox 47.0.1, they may be different in other versions or browsers.

                                                       

                                                      Content of export file should look like:

                                                      -----BEGIN CERTIFICATE-----

                                                      MIIC3DCCAcSgAwIBAgIQL6ACeH92/LBI/9FG+WBRXjANBgkqhkiG9w0BAQUFADAX

                                                      MRUwEwYDVQQDEwxkZXYtb2hvbC13b3IwHhcNMTYwODAzMDgwMjE1WhcNMTcwODAz

                                                      MDAwMDAwWjAXMRUwEwYDVQQDEwxkZXYtb2hvbC13b3IwggEiMA0GCSqGSIb3DQEB

                                                      AQUAA4IBDwAwggEKAoIBAQDPRUzLiC4uQBWrTS3BpOOOBBJT2BrkxhkNLj2O8zDd

                                                      MDeP7L/4NvkqdIn5IxCIO62csfWgYXQOXTShJs9W0HZijVrrII7YnvE5Ovkt48rB

                                                      z3XqFnGYDO8PXdJdO3fp6yPS8GQXhicY4Ki86seWzS7ZSFdftVV6Uzz5+W+RaTOG

                                                      4TZZ3F8hocFHXKME3JtBTIKXX7Gsx2lMgtBIcJtM3Fw8cHm0taVUaEsEjnmPSl3A

                                                      D4uKwIFXHWmfIzU38KP8l4qUHFlfay+ImRZ5RunZwe/iess65pSiQKpnkWWiGdEi

                                                      2AqOF3welEXSnZUYpSQtovIc9FxL9JWssW8FDnMB9lcJAgMBAAGjJDAiMAsGA1Ud

                                                      DwQEAwIEMDATBgNVHSUEDDAKBggrBgEFBQcDATANBgkqhkiG9w0BAQUFAAOCAQEA

                                                      amOYyMTorN/bNOxkOVNimJRprefnbycBWgwAw2QW3cEZwE3/JICfFNSRKbU+jrPC

                                                      jgKRToajf1mJOwSaa/Jqo1sG6mUj4FYastG2U2rWw6Rd16LM6i31V1H6rgCTMmnv

                                                      gfo5+P1OQYhf3yEagZCR/sR8bzpxJUsSlvupTwCla/euBQ70ZKVpX/Mz2kdBCaST

                                                      FCD+oT7e5bP9WarouGhAF4vwQXBAfedW5YKGcREbgXRBCcLKeHBTsFodm0CyqEVR

                                                      Z1kGztjNe0nGpdtwtMYBQVFW/DhliVnBZKqyYD7xcL9/5nJ32tdDqSGZnPCVHAnE

                                                      z1QQVkCl8i/t2qKGCSf8mQ==

                                                      -----END CERTIFICATE-----

                                                       

                                                      Importing certificate to target Linux machine

                                                       

                                                      Ubuntu 14.04

                                                      • Switch to root
                                                      sudo su

                                                       

                                                      • Review the content of file '/etc/ssl/certs/ca-certificates.crt':
                                                      cat /etc/ssl/certs/ca-certificates.crt

                                                       

                                                      • It should contain list of trusted certificates and look similar to the following:

                                                      -----BEGIN CERTIFICATE-----

                                                      MIIEKjCCAxKgAwIBAgIQYAGXt0an6rS0mtZLL/eQ+zANBgkqhkiG9w0BAQsFADCB

                                                      rjELMAkGA1UEBhMCVVMxFTATBgNVBAoTDHRoYXd0ZSwgSW5jLjEoMCYGA1UECxMf

                                                      Q2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjE4MDYGA1UECxMvKGMpIDIw

                                                      MDggdGhhd3RlLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxJDAiBgNV

                                                      BAMTG3RoYXd0ZSBQcmltYXJ5IFJvb3QgQ0EgLSBHMzAeFw0wODA0MDIwMDAwMDBa

                                                      Fw0zNzEyMDEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMdGhhd3Rl

                                                      LCBJbmMuMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9u

                                                      MTgwNgYDVQQLEy8oYykgMjAwOCB0aGF3dGUsIEluYy4gLSBGb3IgYXV0aG9yaXpl

                                                      ZCB1c2Ugb25seTEkMCIGA1UEAxMbdGhhd3RlIFByaW1hcnkgUm9vdCBDQSAtIEcz

                                                      MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsr8nLPvb2FvdeHsbnndm

                                                      gcs+vHyu86YnmjSjaDFxODNi5PNxZnmxqWWjpYvVj2AtP0LMqmsywCPLLEHd5N/8

                                                      YZzic7IilRFDGF/Eth9XbAoFWCLINkw6fKXRz4aviKdEAhN0cXMKQlkC+BsUa0Lf

                                                      b1+6a4KinVvnSr0eAXLbS3ToO39/fR8EtCab4LRarEc9VbjXsCZSKAExQGbY2SS9

                                                      9irY7CFJXJv2eul/VTV+lmuNk5Mny5K76qxAwJ/C+IDPXfRa3M50hqY+bAtTyr2S

                                                      zhkGcuYMXDhpxwTWvGzOW/b3aJzcJRVIiKHpqfiYnODz1TEoYRFsZ5aNOZnLwkUk

                                                      OQIDAQABo0IwQDAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB/wQEAwIBBjAdBgNV

                                                      HQ4EFgQUrWyqlGCc7eT/+j4KdCtjA/e2Wb8wDQYJKoZIhvcNAQELBQADggEBABpA

                                                      2JVlrAmSicY59BDlqQ5mU1143vokkbvnRFHfxhY0Cu9qRFHqKweKA3rD6z8KLFIW

                                                      oCtDuSWQP3CpMyVtRRooOyfPqsMpQhvfO0zAMzRbQYi/aytlryjvsvXDqmbOe1bu

                                                      t8jLZ8HJnBoYuMTDSQPxYA5QzUbF83d597YV4Djbxy8ooAw/dyZ02SUS2jHaGh7c

                                                      KUGRIjxpp7sC8rZcJwOJ9Abqm+RyguOhCcHpABnTPtRwa7pxpqpYrvS76Wy274fM

                                                      m7v/OeZWYdMKp8RcTGB7BXcmer/YB1IsYvdwY9k5vG8cwnncdimvzsUsZAReiDZu

                                                      MdRAGmI0Nj81Aa6sY6A=

                                                      -----END CERTIFICATE-----

                                                      -----BEGIN CERTIFICATE-----

                                                      MIIC3DCCAcSgAwIBAgIQL6ACeH92/LBI/9FG+WBRXjANBgkqhkiG9w0BAQUFADAX

                                                      MRUwEwYDVQQDEwxkZXYtb2hvbC13b3IwHhcNMTYwODAzMDgwMjE1WhcNMTcwODAz

                                                      MDAwMDAwWjAXMRUwEwYDVQQDEwxkZXYtb2hvbC13b3IwggEiMA0GCSqGSIb3DQEB

                                                      AQUAA4IBDwAwggEKAoIBAQDPRUzLiC4uQBWrTS3BpOOOBBJT2BrkxhkNLj2O8zDd

                                                      MDeP7L/4NvkqdIn5IxCIO62csfWgYXQOXTShJs9W0HZijVrrII7YnvE5Ovkt48rB

                                                      z3XqFnGYDO8PXdJdO3fp6yPS8GQXhicY4Ki86seWzS7ZSFdftVV6Uzz5+W+RaTOG

                                                      4TZZ3F8hocFHXKME3JtBTIKXX7Gsx2lMgtBIcJtM3Fw8cHm0taVUaEsEjnmPSl3A

                                                      D4uKwIFXHWmfIzU38KP8l4qUHFlfay+ImRZ5RunZwe/iess65pSiQKpnkWWiGdEi

                                                      2AqOF3welEXSnZUYpSQtovIc9FxL9JWssW8FDnMB9lcJAgMBAAGjJDAiMAsGA1Ud

                                                      DwQEAwIEMDATBgNVHSUEDDAKBggrBgEFBQcDATANBgkqhkiG9w0BAQUFAAOCAQEA

                                                      amOYyMTorN/bNOxkOVNimJRprefnbycBWgwAw2QW3cEZwE3/JICfFNSRKbU+jrPC

                                                      jgKRToajf1mJOwSaa/Jqo1sG6mUj4FYastG2U2rWw6Rd16LM6i31V1H6rgCTMmnv

                                                      gfo5+P1OQYhf3yEagZCR/sR8bzpxJUsSlvupTwCla/euBQ70ZKVpX/Mz2kdBCaST

                                                      FCD+oT7e5bP9WarouGhAF4vwQXBAfedW5YKGcREbgXRBCcLKeHBTsFodm0CyqEVR

                                                      Z1kGztjNe0nGpdtwtMYBQVFW/DhliVnBZKqyYD7xcL9/5nJ32tdDqSGZnPCVHAnE

                                                      z1QQVkCl8i/t2qKGCSf8mQ==

                                                      -----END CERTIFICATE-----

                                                       

                                                      • Append (NOT copy!) content from your exported Orion certificate to the end of this file. Your certificate should now be trusted by apt-get.
                                                • Re: Linux Agent Deployment
                                                  pratikmehta003

                                                  Hi aLTeReGo

                                                  One query...

                                                  1. If we poll through agent for the Linux flavors then we will still be able to get the hardware information?

                                                  2. Secondly how is the calculation of memory parameter done when we poll via agent? Can you break this up in terms of whether its done overall or excluding free, cache etc...