Installation Steps
- Copy the opFlow tarball to the server (a tarball is a GZIP'd tar file, e.g. opConfig-Linux-x86_64-1.0.tar.gz)
- You may need to use SCP or FTP to get the file onto the server.
- The file will now likely be in the users home directory.
- If the installation directory does not already exist
- Change into the directory where the tarball was copied
- Untar the file
cd /usr/local tar xvf ~/opConfig-Linux-x86_64-<version>.tar.gz cd opmantek/ cp install/opCommon.nmis conf/ cp install/credential_sets.nmis conf/ cp install/command_sets.nmis conf/ cp install/connections.nmis conf/ cp -r install/phrasebooks conf/ bin/opfixperms.pl cp install/01opmantek.conf /etc/httpd/conf.d/ service httpd restar
Configure MongoDB
The standard Opmantek configuration MongoDB will suite here
Create the database indexes required:
bin/opConfig-cli.pl act=create_indexes
Configure opConfig
Credentials
conf/credential_sets.nmis holds the credential sets that are used when connecting to a device. Even if auto discovery is not use the credentials still need to live in this file
Setup credentials, edit conf/credential_sets.nmis
#add/remove/change the lines with default username/password info to match credentials for the devices you want to discover %hash = ( 'empty' => { username => '', password => '' }, 'YourSetHere' => { username => 'YourUsername', password => 'YourPassword' } );
Make very sure this file is only readable by you / root (opfixperms.pl will do this for you)
chmod 600 conf/credential_sets.nmis
Connections
Connections tell opConfig how to connect to the devices you would like to gather configuration data from. Connections can be auto-discovered if opConfig is attached to an NMIS configuration.
NB: opConfig will only attempt to discover devices from NMIS that are active and are currently being collected.
Here is a sample connections.nmis file