VMware vCenter Infrastructure Navigator (VIN)

Contributor(s): Tom Walat

VMware vCenter Infrastructure Navigator (VIN) is a virtual appliance that finds and maps application dependencies to assist with troubleshooting and operational management in a vSphere environment.

VIN automatically uncovers application services, describes the relationships between applications, and shows what virtual network, storage and compute resources the application uses. For example, VIN shows how a Web server communicates with a database server that speaks to a mail server.

VIN is only available from the vSphere Web client.

VIN comes from a company called nLayers that EMC acquired in 2006. EMC then incorporated it into its Smarts product line. VMware acquired the technology as part of the February 2010 purchase of EMC’s Ionix portfolio. VIN 1.0 was released in January 2012, and version 1.1 was introduced in April 2012 alongside vCenter Operations Management 5.0.1.

VIN was renamed the product to vRealize Infrastructure Navigator in late 2014 and included in the vRealize Operations -- formerly vCenter Operations Management -- bundle.

This was last updated in February 2015

Continue Reading About VMware vCenter Infrastructure Navigator (VIN)

Dig Deeper on Using monitoring and performance tools with VMware

Join the conversation


Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

How do you manage your multi-tiered application vSphere environment?
My organization uses policy based governance to manage our multi-tiered vSphere environment. We prefer this method because it allows us to control the requests of our service users, the type and amount of resources that they are allowed to consume. policy based governance also gives us a range of  actions to take across workload or service life cycle. we are also considering incorporating intelligent resource management for resource allocation based on service level requirements.


File Extensions and File Formats

Powered by: