WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Alternative Way of Extracting VIN (vSphere Infrastructure Navigator) Information

Alternative Way of Extracting VIN (vSphere Infrastructure Navigator) Information

11.20.2012 by William Lam // 2 Comments

Here is an alternative method of extracting the super useful information from VIN (vSphere Infrastructure Navigator) which I stumbled across while troubleshooting an earlier VIN 1.2 deployment. This method is much simpler from a data extraction point of view and has less prerequisites compared to the first method documented here and here, but it does require a bit more data processing.

Once VIN is up running, there are a set of zip files that are created in /var/log/vadm/results which are name with the virtual machines MoRef ID. We can quickly view the contents of one of these files (without needing to extract the zip file) by using zcat, here is the command to view one of the zip files: zcat /var/logs/vadm/vm-238.zip

From the screenshots above, we can see it contains the same set of information as displayed in the VIN UI. The information is broken down into several section including high level summary of the VM, individual processes running in the virtual machine, application/services known by VIN as well as a netstat table.

Instead of operating on these files directly, you should make a separate copy of the directory for further processing. Since the file name contains the VM's MoRef ID instead of the human readable VM display name, I wrote a quick script called extractVINData.sh which creates a copy of data and rename the files to VM display name.

To use the script, you just need to download it and upload it to your VIN appliance (make sure you set the execute permission on the script). Then just run the script and it will automatically copy the directory to /root/vin-results and translate the VM MoRef ID by correlating with the /var/log/vadm/engine.log file.

Here is a screenshot of the script output:

So if you do not mind some parsing, you can easily extract the data VIN is collecting by simply SSHing to the VIN appliance and periodically copying out /var/log/vadm/results directory. From my quick test, this directory is automatically updated as new VMs are brought online and inventoried by VIN.

More from my site

  • Extracting VIN (vSphere Infrastructure Navigator) information using PowerCLI & vROps REST API
  • Configuring vSphere Infrastructure Navigator (VIN) To Manage An Alternate vCenter Server
  • How To Configure vCenter Server 5.0 To Work With VIN 2.0?
  • How to Update vSphere Infrastructure Navigator (VIN) After Changing vCenter Server IP Address
  • VIN 2.0 Supports New Export to CSV & Maps Feature

Categories // Uncategorized Tags // infrastructure navigator, vIN

Comments

  1. *protectedLeon Scheltema says

    10/20/2014 at 1:43 pm

    Thanks for the script, I was looking for a way to create such a export as the GUI lacks of this. But when I run the script on a VIN version 5.8.3.140 Build 2170967 the script does not create / rename all the files. I only get a .zip file with one vm-MoRef ID XML file of a random VM. Is there still a way to export the dependencies for all VM's within a vCenter with the latest VIN build?

    Reply
    • *protectedLeon Scheltema says

      10/21/2014 at 9:07 am

      It looks like you need to make a small change to the script as there is a change in the engine.log file in the recent build of VIN. the script look for: VM_NAME=$(grep "Creating discovery task for ${VM_MOREF}" but in the latest build has to be changed to: VM_NAME=$(grep "Creating task for ${VM_MOREF}"
      After the change the script runs perfectly, giving me all the data I need for mapping application / server dependencies !

      Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025