OracleVM Monitoring

Skip Prerequisites, Web and LPAR2RRD tabs in case of configuring Virtual Appliance, Docker or a Container

Follow installation procedure for your operating system platform

OracleVM monitoring schema

Implementation is agentless, all data is gathered from Oracle VM Manager.
Supported is OVM 3.3 and 3.4.

Oracle VM Manager host connectivity

    Allow access from the LPAR2RRD host to all Oracle VM Manager hosts ports 7002 (HTTPS)
    You might verify it manually like this for each host:
    $ perl /home/lpar2rrd/lpar2rrd/bin/conntest.pl 192.168.1.1 7002
      Connection to "192.168.1.1" on port "7002" is ok
    

Users access

You have to use the admin user, because Oracle VM does not support role based access You can create a different user if you wish (eg. 'lpar2rrd'), but it must have admin rights anyway.

Attach Oracle VM Manager hosts

  • LPAR2RRD UI ➡ Settings icon ➡ Oracle VM ➡ New :
    Oracle VM Manager configuration

    Make sure that connection test passes without errors or warnings.

  • Make sure cron jobs for Oracle VM Manager are in place (upgrade script might do it for you automatically)
    Skip this step if you install the Virtual Appliance - it is already taken care of.
    $ crontab -l | grep "load_oraclevm.sh"
    $
    
    Add following lines to crontab if necessary
    $ crontab -e
    
    # OracleVM support
    0,20,40 * * * *  /home/lpar2rrd/lpar2rrd/load_oraclevm.sh > /home/lpar2rrd/lpar2rrd/load_oraclevm.out 2>&1
    
  • Wait 30 minutes and then go to the web UI: http://<your web server>/lpar2rrd/
    Use Ctrl-F5 to refresh the web browser cache.


Install LPAR2RRD server

  • Download the latest LPAR2RRD server
    Upgrade your already running LPAR2RRD instance.

  • Install it:
    # su - lpar2rrd
    $ tar xvf lpar2rrd-6.XX.tar
    $ cd lpar2rrd-6.XX
    $ ./install.sh
    $ cd /home/lpar2rrd/lpar2rrd
    
  • Make sure all Perl modules are in place
    cd /home/lpar2rrd/lpar2rrd
    . etc/lpar2rrd.cfg; $PERL bin/perl_modules_check.pl
    
    If there is missing "LWP::Protocol::https" then check this docu to fix it

  • Enable Apache authorisation
    su - lpar2rrd
    umask 022
    cd /home/lpar2rrd/lpar2rrd
    cp html/.htaccess www
    cp html/.htaccess lpar2rrd-cgi
    
  • Schedule to run it from lpar2rrd crontab (it might already exist there)
    $ crontab -l | grep load.sh
    $
    
    Add if it does not exist as above
    $ crontab -e
    
    # LPAR2RRD UI
    0,30 * * * * /home/lpar2rrd/lpar2rrd/load.sh > /home/lpar2rrd/lpar2rrd/load.out 2>&1 
    
    Assure there is just one such entry in crontab.

  • You might need to add lpar2rrd user into /var/adm/cron/cron.allow if crontab command fails
    Allow it for lpar2rrd user as root user.
    # echo "lpar2rrd" >> /var/adm/cron/cron.allow
    
  • Assure you have a cron jobs for OracleVM in place (upgrade script might do it automatically) Skip it on the Virtual Appliance, it is already there.
    $ crontab -l | grep "load_oraclevm.sh"
    $
    
    Add it if it does not exist like above
    $ crontab -e
    
    # OracleVM support
    0,20,40 * * * *  /home/lpar2rrd/lpar2rrd/load_oraclevm.sh > /home/lpar2rrd/lpar2rrd/load_oraclevm.out 2>&1 
    
  • Initial start from cmd line:
    $ cd /home/lpar2rrd/lpar2rrd
    $ ./load.sh
    
  • Go to the web UI: http://<your web server>/lpar2rrd/
    Use Ctrl-F5 to refresh the web browser cache.

Troubleshooting

  • If you have any problems with the UI then check:
    (note that the path to Apache logs might be different, search apache logs in /var)
    tail /var/log/httpd/error_log             # Apache error log
    tail /var/log/httpd/access_log            # Apache access log
    tail /var/tmp/lpar2rrd-realt-error.log    # STOR2RRD CGI-BIN log
    tail /var/tmp/systemd-private*/tmp/lpar2rrd-realt-error.log # STOR2RRD CGI-BIN log when Linux has enabled private temp
    
  • Test of CGI-BIN setup
    umask 022
    cd /home/lpar2rrd/lpar2rrd/
    cp bin/test-healthcheck-cgi.sh lpar2rrd-cgi/
    
    go to the web browser: http://<your web server>/lpar2rrd/test.html
    You should see your Apache, LPAR2RRD, and Operating System variables, if not, then check Apache logs for connected errors