Configuring vMA 4.1

In my previous post I showed you how to deploy vMA 4.1 into your Virtual Infrastructure Environment.  In this post I’m going to show you how to configure vMA and integrate it into your existing network.  If you followed my previous post you should have a powered off VM deployed from the vMA .ovf file:

Power on the VM, open a console session to the VM and wait for it to boot up:

Once the VM has booted you will be asked if you want to assign an IP address to the VM using DHCP.  Select your required option.  In this example I will be setting a static IP address up for the VM so I will be selecting No:

You will then be asked to enter the IP address for the server:

You will then be asked to enter the Subnet Mask for the server:

You will then have to enter the Gateway address:

You will then be asked for the Primary DNS address for the server:

You will then be asked for the Secondary DNS address (Leave blank if you don’t have one):

You will then be asked for the VM’s host name.  I personally try to keep this the same the VM name within the inventory:

You will finally be prompted to confirm that all the settings are correct:

The VM will then restart the eth0 interface and should now be pingable on it’s IP address.  You will be prompted to set a password for the vi-admin account (more on this later):

The vMA will finish it’s configuration and show the default logon screen:

You should also be able to SSH into the box by using something like putty.  Putty allows you to create an SSH session to the VM and run commands remotely rather than having to log onto the console:

In my next post I’ll go into using the vMA to connect to ESXi hosts and run commands on the hosts remotely.