WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / Automation / VSAN Managed Object Browser (MOB) in vSphere 6.7 & vSphere 6.7 Update 1

VSAN Managed Object Browser (MOB) in vSphere 6.7 & vSphere 6.7 Update 1

09.10.2018 by William Lam // 1 Comment

If you have ever spent any time using the vSphere API, you probably have heard of or have used the vSphere Managed Objected Browser (MOB) which is an extremely useful learning and debugging tool when working with the vSphere API. The vSphere MOB is accessed through a web browser connecting to either vCenter Server or ESXi and provides a graphical interface, allowing you to discovery/explore the underlying vSphere API and its data in a very intuitive manner.

As an avid user of the VSAN Management API since its release, I have always wanted something similar, especially when I first got started. I was quite happy when I found out in vSphere 6.7 and VSAN 6.7, the VSAN team has added a VSAN MOB interface directly on ESXi, for the VSAN specific APIs that are available only on an ESXi host. Just like the vSphere MOB which is also available on ESXi host, it is disabled by default and must be enabled.

The following ESXCLI commands can be used to enable/disable the VSAN MOB on ESXi 6.7:

esxcli vsan debug mob start
esxcli vsan debug mob stop

However, when I tried to enable the VSAN MOB, I ran into the following error message:

hostname 'localhost.localdomain' doesn't match '192.168.30.10'


It turns out there is an issue where it fails to match the IP Address of the ESXi host to the default localhost.localdomain and hence it fails to start the VSAN MOB. This issue is fixed in the upcoming vSphere & VSAN 6.7 Update 1, but in the mean time, there is a workaround.

To enable/disable VSAN MOB, simply run the following command in the ESXi Shell (specify the IP Address of your ESXi host):

python /usr/lib/vmware/vsan/perfsvc/VsanMgmtCli.pyc -H 192.168.30.10 mob --start
python /usr/lib/vmware/vsan/perfsvc/VsanMgmtCli.pyc -H 192.168.30.10 mob --stop


You should see similar output as above stating that the VSAN MOB has been started. To access the VSAN MOB on ESXi, simply open a browser to following URL: https://<ESXi>/vsan/mob


In addition to the VSAN MOB fix for ESXi, the upcoming vSphere & VSAN 6.7 Update 1 release will also include the VSAN MOB for vCenter Server, which will give customers access to the rest of the VSAN Management API. Just like the VSAN MOB on ESXi, it will be disabled by default and you will be able to enable it using RVC.

The following RVC command can be used to enable/disable the VSAN MOB on VCSA 6.7:

vsan.debug.mob --start localhost
vsan.debug.mob --stop localhost

Lastly, you can programmatically enable the VSAN MOB on both vCenter Server and ESXi using the VSAN Management API by using the vanDebugSystem managed object which provides the following three methods:

  • VsanQueryMobStatus()
  • VsanStartMobService()
  • VsanStopMobService()

For more VSAN Automation goodness, Alan Renouf and I recently presented at HCI2522BU Getting Started with vSAN Automation at VMworld US 2018. You can find the online recording here in case you missed it or was not able to attend VMworld. Happy Automating!

More from my site

  • Unable to apply VSAN VM Storage Policy on NSX Controller/Edge VMs?
  • How to check if your vCenter Server is using vSphere+ / vSAN+ Subscription?
  • Automating subscription and usage retrieval for vSphere+ and vSAN+ Cloud Service
  • Quick Tip - Inventory core count for vSphere+, vSAN+ & VCF+ Cloud Service
  • How to bootstrap ESXi compute only node and connect to vSAN HCI Mesh?

Categories // Automation, ESXi, VSAN, vSphere 6.7 Tags // mob, VSAN, VSAN 6.7 Update 1, vSphere 6.7 Update 1

Comments

  1. Christopher says

    09/11/2018 at 2:17 am

    Is there any performance penalties by enabling this? If not, is there a reason why I wouldn't I like to always have it enabled?

    Reply

Thanks for the comment! Cancel reply

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

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • Self-Contained & Automated VMware Cloud Foundation (VCF) deployment using new VLC Holodeck Toolkit 03/29/2023
  • ESXi configstorecli enhancement in vSphere 8.0 Update 1 03/28/2023
  • ESXi on Intel NUC 13 Pro (Arena Canyon) 03/27/2023
  • Quick Tip - Enabling ESXi Coredumps to be stored on USB 03/26/2023
  • How to disable the Efficiency Cores (E-cores) on an Intel NUC? 03/24/2023

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 © 2023

 

Loading Comments...