DefinIT

Installing and configuring VMware Infrastructure Navigator 5.8

According to VMware, Infrastructure Navigator is

…a component of the VMware vCenter Operations Management Suite. It automatically discovers application services, visualizes relationships and maps dependencies of applications on virtualized compute, storage and network resources.

Effectively it takes a look at the network connections that are running between your VMs (and physical servers) and works out which applications and services are running on each, and the dependencies – both upstream and downstream – for each VM.

This is particularly useful in large enterprise environments where perhaps application developers have not (shock) documented the dependencies for a particular application. I can think of several times when I’ve been 100% confident that (according to all the documentation provided) I can decommission a server, or the service running on a server, only to have to turn it back on due to a production outage – because an un-documented dependency exists.

Effectively, Infrastructure Navigator leverages VMware Tools to run a netstat command on each VM and work out what connections are being used. It comes with a library of already classified services – e.g. MSSQL running on port 1433 is a pretty obvious service. Non-classified services (or services configured for running on a non-standard port) can be easily added to the library to build up a detailed picture of which VMs depend on each other (as well as “unmanaged” servers/services that are out of the scope of vCenter). (more…)

vMA 5: Cannot initialize property ‘ vami.DNS0.vSphere_Management_Assistant_(vMA)’

| 23/08/2012 | Tags: , , , ,

Just a quick post regarding the vSphere Management Assistant 5 – when deploying the vMA with a static IP address, you might see the following error:

vMA Error

Power On virtual machine <VM name> Cannot initialize property ‘ vami.DNS0.vSphere_Man- agement_Assistant_(vMA)’ , since network ‘<network name>’ has no associated IP pool configuration.

Edit the vMA virtual machine’s properties and go to Options, vApp Options and select disable. Acknowledge the warning and click OK to close the VM properties.

Disable vApp Options

The vMA booted fine after that – the solution comes from this vmware communities post.