This guide is for users of [Supported Operating Systems](🔗) without direct access to the internet and is geared towards a base install.
Please read through the [Simple Automated Installation](🔗) guide for prerequisites and general information before embarking on this guide.
You will need to either:
set up a network proxy to enable access to the public repositories, or
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 and RHEL, or [apt-mirror](🔗) for Debian and Ubuntu.
The base URLs for mirroring our repositories are:
Please note, additional OS packages may be installed during this process, so you may also need to provide access to mirrored or local OS repositories, too.
### Offline Repo Setup Example
This is a simple example of setting up a local repository
The setup of the repo assumes that the server pulling the repository files is on the same OS/Arch as the Opsview install target server.
Create local area to store Opsview packages
Inform the Package manager of the Opsview files
Add a repo source file
Refresh the package manager cache
You will also need to take a copy of the installation script (and verify its checksum) before transferring this to the target server:
Ensure the returned string matches the following:
Note: All 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 `
admin` account here.
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.yml` and ensure all hostnames detected have the domain specified on them, for example, assuming the hostname is `
Note: change `
example.com` to match your own domain
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:
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:
Continue the installation using the following command:
Note: If a more advanced setup is required then take a look the [Advanced Automated Installation](🔗) documentation first.
Run the post-install configuration step:
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.
## Logging in
During the installation, a single administrative user will have been created. The credentials for this user are:
After the system is activated, carry out a reload by navigating to 'Configuration => [System] => Apply Changes' and pressing the `
Apply Changes` button.