Skip to end of metadata
Go to start of metadata

Introduction

So you've downloaded the latest version of the Opmantek Virtual Appliance from https://opmantek.com/network-tools-download/ and now you want to set it up and take it for a test drive to see how NMIS and the Opmantek networking modules can help you administer your network.  No problem.  Easy.

  1. Unzip the virtual appliance file
  2. Use the OVF (Open Virtualization Format) file (VMware and VirtualBox examples provided)
  3. Start up the new VM, optionally set a static IP address
  4. Access NMIS and the other Opmantek applications in your browser

Let's assume you've got step 1 under control (unzipping) and move to step 2.

Using the OVF file

After unzipping the file you should see a folder with a structure like this:

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

There are several options for VMware software.  Options 2 & 3 require the VMware OVF Tool, find the tool by doing a search on google or by visiting VMware's site, the other requires VMware Fusion (for Mac).  Options 2 & 3 assume you have it installed and know where it is.

1. VMware Fusion

Recent versions of VMware Fusion allow importing .ovf files directly from the application.  If this option does not exist or work you will need to use option # 2.  

To import: Select File->Import, then "Choose File", find NMIS8-OVF/NMIS8.ovf as the file to import, then select continue.  Fusion will import the file and then present you with the VM's default configuration.

1.  2. 3. 4.

 

2. Convert OVF to VMX

This option is for non-Fusion (or older) VMware products that do not support the OVF format directly; in this case you have to convert the appliance into VMware's native format VMX. As mentioned above this conversion requires the VMware ovftool.

You should now be able to import/load the vmx file with your VMware software and skip to step 3.

3. Transfer OVF to ESXi

Remember to set the name you like, the datastore you want, and point it at the server you want to deploy to.

4. Upgrade the Virtual machine hardware version (optional)

The Opmantek Virtual Appliance ships with the virtual machine hardware version set very low for maximum compatibility, but you may want to upgrade the hardware version to a higher level (to leverage performance benefits, remove memory limitations, etc.) as described on the VMware website.

VirtualBox

VirtualBox will import directly from an OVF file so you can just start up VirtualBox and select "Import Appliance..."

Browse to where you unzipped the file and select the ovf file

Select the file, you should see a screen something like this:

It should be safe to Import.  The import process may take a couple of minutes to complete, just enough time to grab a cup of coffee I'd say.

If you have any trouble the VirtualBox documentation is here: https://www.virtualbox.org/manual/ch01.html#ovf

Important Note regarding Ext4: if your virtualbox host is Linux and your VMs are stored on XFS or Ext4 file systems, then it is absolutely necessary that you enable the "Host I/O Cache" for all virtual disk controllers after importing the OVF file, or you run the risk of file system corruption in your guest. On one of our test systems (Linux kernel 3.14.23, Virtualbox 4.3.14) the VM wouldn't even fully get through the first boot before the virtual disks got corrupted - but with Host I/O Cache on everything is fine. Below is an example of how to enable Host I/O Cache using VirtualBox:

Other Hypervisors

To use OVF files with other virtualisation systems like KVM you may have to convert the OVF file to a native format; Two well-known tools for this purpose are virt-v2v (available in CentOS6/RHEL) and virt-convert (in Debian).

Hyper-V

The Windows Hyper-V technology does not fully support the OVF industry standard. Microsoft documents a complex and somewhat limited procedure on their page about converting OVF files to Hyper-V. There are third-party conversion tools available that simplify this deployment scenario, for example StarWind's free V2V Converter  which worked well in our tests.

Start up the VM and set a custom IP Address, DNS... (optional)

At this point the VM has DHCP enabled, and therefore it will receive a dynamic IP address suitable for your environment. The easiest way to access the VM at that point is from the virtualization software terminal. So go ahead and boot the VM. After the VM is finished booting you will be welcomed by a login prompt. First, log in using the default credentials.

You now have three options to configure custom networking options:

  • manual configuration
    The VM appliance is a normal CentOS 6 system, hence all the mechanisms for network configuration in CentOS are available.
    Most specifically you'll be interested in the  files /etc/hosts, /etc/sysconfig/network, /etc/sysconfig/iptables and /etc/sysconfig/network-scripts/ifcfg-eth0.
  • use our example network configuration files

    Root's home directory contains 2 example network configurations, one for static IP's and one for DHCP.  Copy the one you require to /etc/sysconfig/network-scripts/ and edit it to suit:

    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); finally, run service network restart to activate.

  • use the menu-based tool system-network-config
    Simply type  in system-config-network and follow the prompts.
    Please note: in Opmantek VM appliances before 8.5.12G the  tool is not preinstalled and you have to run yum install system-config-network-tui first.

Set Up Firewall (optional)

Please note that by default the Opmantek VM Appliance does NOT have a firewall active. If you would like local firewalling on your VM, you can easily enable that:

The standard iptables tools are installed, and all you would have to do, is enter your desired rules in /etc/sysconfig/iptables, followed by service iptables restart AND a final one-off run of chkconfig iptables on.  The service call enables your firewall rules, while the chkconfig call enables activation of the firewall rules on boot. Until and unless the chkconfig step is taken, your firewall rules won't persist when the VM is rebooted. Besides this, somewhat low-level, method of configuring an iptables firewall there are also various user-friendly frontends available for installation with yum.

Troubleshooting Network Problems

The most common problem is with how CentOS 6 handles interface discovery, it wants to hang onto MAC addresses which of course in a virtual environment you want managed by the Hypervisor.

Run the command "ifconfig -a", the result should look like this:

If you do not see an interface called eth0 then run this command and reboot your VM.

Accessing the Application Modules on the VM

By default the VM boots with DHCP enabled, and once you determine the hostname or IP address of the VM you can access it a web browser using a URL like:

http://nmis.domain.com/ or http://192.168.1.8/

You will be presented with a menu of the installed tools, similar to the following screenshot:

You can either use this menu, or navigate directly to NMIS, Open-AudIT or any of the Opmantek applications.

Simply open your favourite web browser and navigate to:

  • http://<vm ip address>/nmis8 for NMIS,
  • http://<vm ip address>/open-audit for Open-AudIT Community,
  • or http://<vm ip address>/omk for the list of all Opmantek applications.

The default access credentials are username "nmis8", password "nm1888" (more info regarding credentials can be found on this page).

Once you've got either the NMIS dashboard or one of the Opmantek application dashboards open, you can also navigate between modules using the "Modules" and "NMIS Modules" menus, respectively.

Secure Access with https

The VM ships with support for secure https access enabled, and you can use https instead of http in any of the URLs mentioned above.

However, the included certificate-key pair is the same for all VM downloads, and it is a self-signed certificate (for "opmantek.local"): this will cause your browser to display security warnings.

If you want to use https access operationally it is highly recommended that you replace this shared default key-certificate pair with your own (or use an automated certification authority like https://letsencrypt.org/ for example).

Application Module Licensing

The first step to using a module is knowing how to open it, the next is to get a license for it. This process is simple and painless: all products on the appliance (except opFlow) now support free licenses (which are not time-limited but limited to 20 nodes). For these applications the initial dialog offers the generation of such a free license; for opFlow the licensing dialog offers guidance for obtaining a trial or a full license.

You can also use the "opLicensing" module (reachable at http://<vm ip address>/omk/opLicense or from the Modules menu) to manage your licenses comfortably (including the ability to download previously purchased licenses from the Opmantek website). More info about opLicensing can be found here.

Exploring and Configuring Application Modules

All modules on the Virtual Appliance come with their configuration set to very minimal but safe defaults; to explore the full functionality available you will very likely have to make config modifications to suit your environment. These configuration options are all documented on this site, the Opmantek Community Wiki, in the per-application section (or "Application Space"); certain common, shared aspects are discussed in the "opCommon" space.

For all recent Opmantek applications you'll find links to the respective sections of Wiki in the "Help" menu (usually under "Online Documentation"); there's also an online version check on the "About" page which helps with keeping your modules up to date.

build.opmantek.com_2016-06-08_13-32-03.pngUse Host I:O Cache.png

  • No labels