opConfig 4 is the NMIS 9 compatible version. In this guide, you will learn all you need to start using opConfig.
As a main differences between versions < 4.0.0:
- Nodes are saved in the same collection. As a consequence:
- Import from NMIS option is not available.
- IPs are not saved in opConfig database neither. They are part of the inventory collection. They cannot be edited, as modifying an IP has more implications that editing only the IP, there is a bunch of information related.
- os_info and connection info properties are part of the node configuration attribute. They should be accessed as follows:
Before you start
We recommend you:
- Be familiar with opConfig basic concepts
- The individual performing this installation has a small bit of Linux experience
- Root access is available
- Internet access is required for installing any missing but required software packages
- NMIS 9 must be installed on the same server that opConfig is being installed on. Here you can read the NMIS installation guide. NMIS 9 is not required to be running, but opConfig needs the NMIS dependencies to work.
- You will need a license for opConfig ( CONTACT US for an evaluation license )
Download the latest product version from opmantek.com.
opConfig is distributed in a self-extracting download format that simplifies the installation process quite a bit. More information on running the installer can be found HERE: The Opmantek Installer
Transfer the opConfig installer file onto the server in question, either by direct download from the Opmantek website, or from your desktop with
sftp or a similar file transfer tool.
Start the interactive installer and follow its instructions:
opConfig (4.0.0) Installation script
This installer will
a different installation location please rerun the
installer with the -t option.
- The installer will interactively guide you through the steps of installing opConfig. Please make sure to read the on-screen prompts carefully. Also, a preconfigured file can be used.
- When the installer finishes, opConfig is installed into
/usr/local/omk, and the default configuration files are in
/usr/local/omk/conf, ready for your initial config adjustments.
- A detailed log of the installation process is saved as
/usr/local/omk/install.log, and subsequent upgrades or installations of other Opmantek products will add to that logfile.
- For detailed information about the interactive installer please check the Opmantek Installer page.
If necessary the installer will offer to install MongoDB locally for you; if that is undesirable, or if you have a remote MongoDB installation that you want to use you'll need to adjust the MongoDB-related settings:
conf/opCommon.nmis in an editor, go to the database section and change the server, username and password to reflect your MongoDB installation.
The result should look similar to the following (but there might be extra settings related to other products):
Access the opConfig GUI and acquire, restore or enter your license.
The opConfig GUI is accessible at
http://<yourservername or ip address>/omk/opConfig/, and until you have entered a valid license neither the opConfig GUI nor the CLI tools will operate.
Configuration and Use
At this point opConfig should be ready for operation, but won't have any knowledge of which nodes to manage.
Your next step should be to consult the opConfig User Manual, which will tell you how to tell opConfig what commands to perform with which nodes, how to customize opConfig's behaviour to suit your needs and so on.
Please feel free to leave comments and suggestions below!
- Read the opConfig 4 User Manual to check all the actions you can perform with opConfig.
- Automating Configuration Changes with opConfig
- opConfig - Compliance Management
- opConfig Virtual Operator
- Plugins in opConfig
- Purging of old data in opConfig
- Adding a new device to be supported by opConfig
- opConfig CLI tool