Author Archives: Iwan Rahabok

About Iwan Rahabok

A father of 2 little girls, my pride and joy. The youngest one quickly said “I’m the joy!”

Operationalize Your World: import steps

My apology for a long overdue post. Finally managed to put an updated video on how import the dashboards, views, super metrics, XML into your environment.

The video is now based on vR Ops 6.6. It complements the import steps here.

If you’re not familiar with Operationalize Your World, read this.

VMworld 2017 presentations

As promised during my sessions at VMworld 2017, you can find the materials here.

I did 10 sessions/workshops covering 2 topics:

  • Achieve Troubleshooting Mastery with vRealize.
  • Operationalize Your World

The deck contains additional material that didn’t fit in the time given.

I made the presentations available in powerpoint, not PDF. Can you guess why?

Operations differ to Architecture. We can have 1000 VMware customers with identical architecture (e.g. they all use Validated Design), and you will see 1000 unique operations. Operations is like fingerprint. It’s personalized to each customer. That’s why Sunny Dua and I share in editable format. Feel free to change the 2 ugly photos with yours! 🙂

So go ahead to personalize it. Throw away the irrelevant ones, add your custom content, and make it yours. We would be honored to see your version, and how you improve our deck. I shared many times that the reason why customers find the solution resonating because it comes from you all. What we have done is simply collect the experience and wisdom from customers globally. Your war stories, your idea, your feedback, have become an integral part of the deck.

Operationalize Your World 

We provided 2 decks as we were asked to deliver in 1 hour and 2 hour format. If you need to see the full 1-day workshop, you can download it here.

A number of you have asked for a more details explanation on the billing model. I’m working on a deck that will cover that. Allow me to test the deck in VMworld at Barcelona first, as it’s just 1 week away.

Keeping VMware Tools current

Keeping VMware Tools current is one of the best practices of vSphere operations. VMware Tools interfaces with both ESXi and VM (the virtual motherboard or virtual machine). Hence, there are 2 comparisons to consider:

  1. VM Hardware version
  2. ESXi version

From the vSphere API, here is what you get when you query it:

  • Guest Tools Current
  • Guest Tools Not Installed
  • Guest Tools Supported New
  • Guest Tools Supported Old
  • Guest Tools Too Old
  • Guest Tools Unmanaged

What do they mean?

  • Guest Tools Not Installed:
    • Tools are not installed on the VM. You should install it as you get both drivers and visibility.
  • Current
    • Tools version matches with the Tools available with ESXi. Each ESXi has a version of Tools that comes with it. See this for the list. This is the ideal scenario.
  • Supported New
    • Newer than the ESXi VMware tools version, but it is supported.
  • Supported Old
    • The opposite of New. It is also supported. Even it is older by 0.0.1 is considered old. It does not have to far behind.
  • Too Old
    • Tools version is older than the minimum supported version of Tools across all ESXi versions. Minimum supported version is the oldest version of Tools we support. Basically, guest is running unsupported Tools. You should upgrade. As of now for Linux and Windows guests. minimum supported version is the Tools version bundled with ESXi 4.0 which is 8.0.1. Supporting such old versions is challenging. We are planning to change this in future to something newer. In the meantime, you should upgrade as might not work as expected
  • Unmanaged
    • Tools installed in the guest did not come from ESXi, so Tools is not being managed by ESXi host. It may be supported or maybe not, depends on what type of Tools is running in the guest. We support open-vm-tools packaged by Linux vendors and OSPs, which both show up as unmanaged.
    • If a customer builds their own open-vm-tools from source code, we may not support that because we will not know if they have done it correctly or not.

Operationalize Your World has a dashboard that highlights the VMs not running the current or supported new. You should expect the number to be minimal, or ideally none.