Welcome to docs.opsview.com

Upgrading

Opsview 4.6.1 and Opsview Rancid 2.1 require each other due to the migration from IP based storage of monitored host to Host Title based one. If you are going to upgrade those packages make sure to update all of them on every server.

This document is split, based on the function of the server.

From the architecture pages:

  • Master - This is the central Netaudit repository, which holds the configuration information (stored using Subversion). This also includes some integration code with Opsview. This is installed on the Opsview Master
  • Collectors - These run the Netaudit application to collect the router configuration information. These would usually be installed on the Opsview Master and the Opsview Slaves.

Follow the section below based on whether you are upgrading the Opsview Master or a Collector.

Master

Upgrade to Opsview 4.6.1 and Rancid 2.1.0 from Opsview 4.x and Rancid 2.0.x

Opsview 4.6.1 will generate new Rancid configuration using host titles that is incompatible with Rancid 2.0 and below, so the upgrade of both is required.

APT for Debian/Ubuntu

Run as root:

for p in opsview-activemq opsview-activemq-consumers opsview-file2activemq; do /etc/init.d/$p stop; done
apt-get install opsview opsview-core opsview-web opsview-base libapache2-mod-auth-tkt-prefork-opsview
# if collector was installed on the server
apt-get install opsview-rancid opsview-rancid-master opsview-rancid-collector
# else
apt-get install opsview-rancid opsview-rancid-master
# fi
for p in opsview-activemq opsview-file2activemq; do /etc/init.d/$p start; done

YUM for CentOS/RHEL

As packages have been reorganised, you will need to remove the previous software before installing the newer software:

for p in opsview-activemq opsview-activemq-consumers opsview-file2activemq; do /etc/init.d/$p stop; done
yum install opsview opsview-core opsview-base opsview-perl opsview-web mod_auth_tkt_opsview
# if collector was installed on the server
yum remove opsview-rancid opsview-rancid-master opsview-rancid-collector
yum install opsview-rancid opsview-rancid-master  opsview-rancid-collector
# else
yum remove opsview-rancid opsview-rancid-master
yum install opsview-rancid opsview-rancid-master
# fi
for p in opsview-activemq opsview-file2activemq; do /etc/init.d/$p start; done

YUM for SLES

for p in opsview-activemq opsview-activemq-consumers opsview-file2activemq; do /etc/init.d/$p stop; done
zypper update opsview opsview-core opsview-base opsview-perl opsview-web mod_auth_tkt_opsview
# if collector was installed on the server
zypper remove opsview-rancid opsview-rancid-master opsview-rancid-collector
zypper install opsview-rancid opsview-rancid-master  opsview-rancid-collector
# else
zypper remove opsview-rancid opsview-rancid-master
zypper install opsview-rancid opsview-rancid-master
# fi
for p in opsview-activemq opsview-file2activemq; do /etc/init.d/$p start; done

Confirm at Opsview 4

Confirm that you have upgraded to Opsview 4 first, as this will setup the appropriate repositories.

Ensure you have the feature for Netaudit enabled before upgrading.

Upgrade Steps

This is based on your OS.

You may need to refresh your browser to clear its old cache as new CSS files are provided

APT for Debian/Ubuntu

Run as root:

apt-get update
apt-get install opsview-rancid opsview-rancid-master

YUM for CentOS/RHEL

As packages have been reorganised, you will need to remove the previous software before installing the newer software:

yum remove opsview-rancid opsview-rancid-master opsview-rancid-perl opsview-repository opsview-repository-perl
yum install opsview-rancid opsview-rancid-master

YUM for SLES

zypper remove opsview-rancid opsview-rancid-master opsview-repository
zypper install opsview-rancid opsview-rancid-master

Collectors

Collectors will need some changes to repositories to pick up the new software.

APT for Debian/Ubuntu

Remove Previous Repository Locations

Check /etc/apt/sources.list and all files in /etc/apt/sources.list.d. If there are any links to downloads.opsview.com, these need to be commented out.

Add the New Repository Location

Create a new file, /etc/apt/sources.list.d/opsview.list, and add the following line to it:

# Opsview packages
deb https://USERNAME:PASSWORD@downloads.opsview.com/opsview-commercial/latest/apt <OS> main

Where:

  • OS is your distribution name, such as squeeze, lucid or hardy
  • USERNAME and PASSWORD is your Opsview.com credentials

For example:

deb https://username:password@downloads.opsview.com/opsview-commercial/latest/apt squeeze main

Upgrade

Run as root:

apt-get update
apt-get install opsview-rancid-collector

YUM for CentOS/RHEL

Due to package reorganising, you have to remove the old software before installing the new software:

yum remove opsview-rancid-collector opsview-rancid-perl
yum install opsview-rancid-collector

Post Upgrade

Version 2.0 with Single Sign On

If you are upgrading to 2.0, you will need to re-configure Apache to allow Single Sign On.

Your Apache files could be in /etc/httpd/conf.d or /etc/apache2/sites-enabled, depending on how you have configured it.

You need to make these changes to the Apache configuration. You must comment out lines that used to exist before. This must go before the ProxyPass for Opsview.

Alias /websvn /opt/opsview/repository
ProxyPass /websvn !
<Location /websvn>
   AuthType None
   TKTAuthLoginURL /login?app=websvn
   TKTAuthTimeout 86400s
   #TKTAuthIgnoreIP on   # This may need to be enabled if AuthTkT is set to ignore IP address
   require valid-user
</Location>
#<Location /websvn>
#  AuthType Basic
#  AuthName "Opsview"
#  AuthUserFile /usr/local/nagios/etc/htpasswd.users
#  require valid-user
#</Location>

Restart Apache.

Changes

This provides information about changes between releases.

Network Analyzer 2.1

  • Switched to host title based configuration

Network Auditing 2.0

  • Removed opsview-repository-perl and opsview-rancid-perl, and using opsview-perl instead
  • Merged opsview-repository into opsview-rancid-master
Navigation
Print/export
Toolbox