...
Because the file is in an open format it should be recognized by your virtualization software or by a conversion tool provided by your virtualization software.
VMware
I will cover two options for VMware software. Both of these options require the VMware OVF Tool, see here for some links or hit up google or vmware's site. From now on I'll assume you have it installed and know where it is
Convert OVF to VMX
Code Block |
---|
mkdir NMIS8 ovftool NMIS8-OVF/NMIS8.ovf NMIS8/NMIS8.vmx |
You should now be able to import/load the vmx file with your VMware software and skip to step 3.
Transfer OVF to ESXi
Code Block |
---|
ovftool --name="NMIS" -dm="thin" -ds=datastore_number ./NMIS8-OVF/NMIS8.ovf vi://user:password@host_ip_address |
Remember to set the name you like, the datastore you want and point it at the server you want to deploy to
VirtualBox
VirtualBox will import directly from an OVF file so you can just fire up VirtualBox and select "Import Appliance..."
...
Now set the IP, netmask, gateway, and DNS if you like ( to add DNS you can add two lines, one for each server: DNS1=ip , DNS2=ip)
Alternately
You could also install a text based UI to help you:
...
Code Block |
---|
opfixperms.pl Version 1.0 Copyright (C) 2012 Opmantek Limited (www.opmantek.com) This program comes with ABSOLUTELY NO WARRANTY; See www.opmantek.com or email contact@opmantek.com This script will fix the permissions for Opmantek based on the configuration /usr/local/opmantek/bin/../conf/opCommon.nmis The directory to be processed is: /usr/local/opmantek The user will be set to: nmis The group will be set to: nmis |
Now let's get started!
Opening a module
There are two ways to open the modules, by using the drop-down in the NMIS page (make sure you do not have pop-up's blocked for this page):
...
Code Block |
---|
http://vm_ip_address/cgi-omk/opFlow.pl |
Getting a trial license
opFlow, opMaps and opReports will present you with a page that looks like the following when not registered:
...
And you're Done! The next step is to make sure the configuration for the module you activated is correct & complete.
opFlow Configuration
Mongo
The first step to get opFlow working is to start the mongo database. The VM already has mongo installed and all the scripts are ready to go, first we will add the mongo script to the VM's startup routine, and then we will start the daemon.
...
Note: the first time you start mongo it may take a while to return to the command prompt, don't worry about it, just let mongo run and it will eventually come back, if it doesn't CTRL+C and start it again.
Flowd
flowd should be running, but to be sure we will take the same steps as we did with mongo.
...
Code Block |
---|
Starting flowd: bind: Address already in use Listener setup of [0.0.0.0]:12345 failed |
opFlowd
opflowd also needs the same treatment:
Code Block |
---|
chkconfig opflowd on service opflowd start |
Configure your Cisco Router
...
Code Block |
---|
ip flow-cache timeout active 1 |
Run setup script
./opflow_setup.pl setup=all
...