Opsview 6.8.x End of Support

With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.

The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.

Offline installation

This guide is for users of Supported Operating Systems without direct access to the Internet and is geared towards a base install.

Planning Copied

Take a copy of our public Opsview Monitor repository and transfer it to a server on your target network, to create a repository mirror.

Note

The repository is not browsable; a mirroring process is the best way to download all of the packages.

Setting up the mirror is outside the scope of this documentation, but we suggest using a tool to achieve this such as reposync for CentOS, RHEL, and OL, or apt-mirror for Debian and Ubuntu.

The base URLs for mirroring our repositories are:

# CentOS/RHEL/OL
https://downloads.opsview.com/opsview-commercial/6.8/yum/<OS>/<VERSION>/x86_64
# e.g.
https://downloads.opsview.com/opsview-commercial/6.8/yum/rhel/7Server/x86_64

# Ubuntu/Debian
https://downloads.opsview.com/opsview-commercial/6.8/apt

Additional OS packages may be installed during this process, so you may also need to provide access to mirrored or local OS repositories.

For RHEL 7/8/9 systems, ensure the subscription manager is configured to allow system repositories. Verify that the disable_system_repos option is set to 0 in the /etc/dnf/plugins/subscription-manager.conf file on each system.

The root user must be able to run sudo without a password on all servers in the Opsview deployment.

Make sure you check the software requirements, particularly the hostname requirements.

Set up offline repository Copied

This is a simple example of setting up a local repository.

Note

The setup of the repo assumes that the server pulling the repository files is on the same OS or Arch as the Opsview install target server.

1. Ensure you have the package to createrepo installed:

   yum install yum-utils createrepo
   

2. Setup Repo (same OS/Arch as the Opsview target server):

   curl -sLo- https://deploy.opsview.com/6.8 | sudo bash -s -- -O repo
   

3. Obtain the repoid (first line in the file), you will only need the information inside the square brackets:

   head -n1 /etc/yum.repos.d/opsview.repo
   

4. Create local area to store Opsview packages.

   reposync  -l  --repoid=<repoid-from-head> --download_path=/var/tmp/local_opsview_repo
   
   RHEL 8 you will need to run:
   reposync -p /var/tmp/local_opsview_repo --download-metadata --repo=<repoid-from-head>
   

5. Inform the Package manager of the Opsview files.

   createrepo -v /var/tmp/local_opsview_repo
   

6. Add a repo source file.

   vim /etc/yum.repos.d/localrepo.repo
   
   [localrepo]
   name=Opsview Local Repository
   baseurl=file:///var/tmp/local_opsview_repo
   gpgcheck=0
   enabled=1
   

7. Refresh the package manager cache.

   yum clean all
   yum makecache fast
   

8. You will also need to take a copy of the installation script (and verify its checksum) before transferring this to the target server:

   curl -sLo- https://deploy.opsview.com/6 > install_opsview
   sha256sum install_opsview
   

9. Ensure the returned string matches the following:

   a3ecab0424b50e9cde7d3a3b83bfcdfc9ee83b5caad073f5cd7145eaeaf4985a
   

Installation Copied

Note

All of these steps should be run as the root user.

1. Using the Opsview Monitor deploy script downloaded earlier, install the initial package set. Specify a suitable <password> to use with the Opsview Monitor admin account here.

   bash ./install_opsview -p <password> -O fire,boot
   

   This will make use of both the mirrored OS repository and the mirrored Opsview repository you have previously set up and configured.

2. Amend the file /opt/opsview/deploy/etc/opsview_deploy.yml and ensure all hostnames detected have the domain specified on them, for example, assuming the hostname is opsmonitor:

   orchestrator_hosts:
   opsmonitor.example.com:
       ip: 192.168.0.10
   

Note

Change example.com to match your own domain.

3. Amend the file /opt/opsview/deploy/etc/user_vars.yml and add in the following appropriate line for your OS to specify the URL to your local Opsview Monitor package repository mirror:

   # CentOS/RHEL/OL
   opsview_repository_str_yum: 'http://my.repo/$basearch/'
   # Debian/Ubuntu
   opsview_repository_str_apt: 'deb http://my.repo/ trusty main'
   # Pre-flight check for the repository
   check_uri_opsview_repository: 'http://my.repo/'
   

   If you intend to use optional modules, you can enable them by adding lines as follows (note: these will still need an appropriate license to enable them) in the same file:

   opsview_module_netaudit: True
   opsview_module_netflow: True
   opsview_module_servicedesk_connector: True
   opsview_module_reporting: True
   opsview_module_snmp_traps: True
   

4. Continue the installation using the following command:

   bash ./install_opsview -p <password> -O inst
   

Note

If a more advanced setup is required then take a look the Advanced Automated Installation documentation first.

5. Run the post-install configuration step:

   /opt/opsview/deploy/bin/opsview-deploy lib/playbooks/setup-monitoring.yml
   

Activation Copied

Once successfully installed, perform a manual activation by following the steps on Managing your Subscription.

After activation is successful, run:

/opt/opsview/deploy/bin/opsview-deploy lib/playbooks/setup-opsview.yml

This will check your newly activated license and ensure all appropriate modules are installed and configured for your use.

Logging in Copied

During the installation, a single administrative user will have been created. The credentials for this user are:

username: admin
password: <password supplied during installation>

After the system is activated, carry out a reload by navigating to Configuration > [System] > Apply Changes and pressing the Apply Changes button.