This guide is for users of Supported Operating Systems without direct access to the Internet and is geared towards a base install.
Take a copy of our public Opsview Monitor repository and transfer it to a server on your target network, to create a repository mirror.
NoteThe 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 and RHEL, or apt-mirror for Debian and Ubuntu.
The base URLs for mirroring our repositories are:
# RHEL/CentOS https://downloads.opsview.com/opsview-commercial/6.6/yum/<OS>/<VERSION>/x86_64 # e.g. https://downloads.opsview.com/opsview-commercial/6.6/yum/rhel/7Server/x86_64 # Ubuntu/Debian https://downloads.opsview.com/opsview-commercial/6.6/apt
Additional OS packages may be installed during this process, so you may also need to provide access to mirrored or local OS repositories.
Set up offline repository
This is a simple example of setting up a local repository.
NoteThe setup of the repo assumes that the server pulling the repository files is on the same OS/Arch as the Opsview install target server.
Ensure you have the package to
yum install yum-utils createrepo
Setup Repo (same OS/Arch as the Opsview target server):
curl -sLo- https://deploy.opsview.com/6.6 | sudo bash -s -- -O repo
repoid(first line in the file), you will only need the information inside the square brackets:
head -n1 /etc/yum.repos.d/opsview.repo
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>
Inform the Package manager of the Opsview files.
createrepo -v /var/tmp/local_opsview_repo
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
Refresh the package manager cache.
yum clean all yum makecache fast
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
Ensure the returned string matches the following:
NoteAll of these steps should be run as the
Using the Opsview Monitor deploy script downloaded earlier, install the initial package set. Specify a suitable
<password>to use with the Opsview Monitor
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.
Amend the file
/opt/opsview/deploy/etc/opsview_deploy.ymland ensure all hostnames detected have the domain specified on them, for example, assuming the hostname is
orchestrator_hosts: opsmonitor.example.com: ip: 192.168.0.10
example.comto match your own domain.
Amend the file
/opt/opsview/deploy/etc/user_vars.ymland add in the following appropriate line for your OS to specify the URL to your local Opsview Monitor package repository mirror:
# CentOS/RHEL 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 ```
Continue the installation using the following command:
bash ./install_opsview -p <password> -O inst
NoteIf a more advanced setup is required then take a look the Advanced Automated Installation documentation first.
Once successfully installed, perform a manual activation by following the steps on Managing your Subscription.
After activation is successful, run:
This will check your newly activated license and ensure all appropriate modules are installed and configured for your use.
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.