Using SSL Communication with Linux-Based Agent

You can secure communication between the up.time monitoring station and the up.time Linux agent by enabling SSL encryption. Enabling SSL is a two-step process:

Enabling SSL on the Linux Agent System

To enable SSL encryption, complete the following steps on each agent system:

NOTE: Do not perform these steps on the monitoring station.

1. Ensure Stunnel is installed on the agent server. If you do not have access to a distribution, you can download it from Stunnel.org.
2. Edit the /etc/xinetd.d/uptmagnt file so that it includes the following configuration information:

   service uptmagnt\n{\n        disable         = no\n        flags           = REUSE\n        socket_type     = stream\n        wait            = no\n        user            = nobody\n        server          = /usr/sbin/stunnel\n        server_args     = /etc/stunnel/uptmagnt.conf\n}\n

3. Create the certificate that will be used by Stunnel. For example: 
   

   openssl req -new -x509 -days 365 -nodes -config stunnel.cnf -out stunnel.pem -keyout stunnel.pem\n

   The following is a sample stunnel.cnf for the openssl program:

   # create RSA certs - Server\n\nRANDFILE = stunnel.rnd\n\n[ req ]\ndefault_bits = 1024\nencrypt_key = yes\ndistinguished_name = req_dn\nx509_extensions = cert_type\n\n[ req_dn ]\ncountryName = Country Name (2 letter code)\ncountryName_default             = PL\ncountryName_min                 = 2\ncountryName_max                 = 2\n\nstateOrProvinceName             = State or Province Name (full name)\nstateOrProvinceName_default     = Some-State\n\nlocalityName                    = Locality Name (eg, city)\n\n0.organizationName              = Organization Name (eg, company)\n0.organizationName_default      = Stunnel Developers Ltd\n\norganizationalUnitName          = Organizational Unit Name (eg, section)\n#organizationalUnitName_default =\n\n0.commonName                    = Common Name (FQDN of your server)\n0.commonName_default            = localhost\n\n# To create a certificate for more than one name uncomment:\n# 1.commonName                  = DNS alias of your server\n# 2.commonName                  = DNS alias of your server\n# ...\n# See http://home.netscape.com/eng/security/ssl_2.0_certificate.html\n# to see how Netscape understands commonName.\n\n[ cert_type ]\nnsCertType = server\n

4. Copy stunnel.pem to /etc/stunnel/uptmagnt.pem.

• Create the /etc/stunnel/uptmagnt.conf file and add the following lines:

  cert=/etc/stunnel/uptmagnt.pem\nexec=/opt/uptime-agent/bin/uptmagnt\n

• Restart the xinetd service. After doing this, your agent should now be in SSL mode.

  You can verify that your agent is communicating securely by running the following command on your monitoring station:

  agentcmd +s -p 9998 <hostname> df-k\n 

  NOTE: You can change the port on which to enable SSL to any value. To change the default agent port to something other than 9998, edit the /etc/services file, and restart xinetd. You can also use the agent-configure.sh script (see Setting the agent port or permissions for more information).

Enabling SSL in the up.time UI

If the Linux agent has already been added to up.time, complete the following steps in the up.time Web interface for each agent system that you want to configure to use SSL.

1. Click My Enterprise.
2. Click the name of the agent system for which you want to enable SSL.
3. On the system information page, click the Edit Performance Monitor link in the System Profile section.
4. In the new Edit Service Monitor window that appears, select the Use SSL (HTTPS) option.
5. Click Save.
   
   Once saved, your monitoring station and agent system will be communicating via SSL.

If you have not yet added the agent system to up.time, follow the steps that are detailed in the up.time User Guide. When adding the agent system, ensure that the Agent Port Number option is set to 9998, and that the Use SSL (HTTPS) option is enabled.