Search Results for: kickstart

Quick Tip - vSphere MOB is disabled by default in ESXi 6.0

02.24.2015 by William Lam // 9 Comments

Yesterday, I noticed an interesting error when trying to connect directly to the vSphere MOB on an ESXi 6.0 host. The following error message was displayed on the browser:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x4bf02038] _serverNamespace = /mob _isRedirect = false _pipeName =/var/run/vmware/proxy-mob)

This was the first time I had noticed this as I normally use the vSphere MOB for debugging purposes or exploring the vSphere API. The vSphere MOB is also a quick an handy way to unregister vSphere Plugins when connecting to vCenter Server.

I did some further investigation and it turns out that in vSphere 6.0, the vSphere MOB will be disabled by default on an ESXi 6.0 host. The reason for this is to provide security hardening out of the box for ESXi versus having an administrator harden after the fact. If you are familiar with the vSphere Security Hardening Guides, you will recall one of the guidelines is to disable the vSphere MOB on an ESXi host and with vSphere 6.0, this is now done automatically for you. This information will also be documented as part of the vSphere 6.0 documentation when it GAs.

If you still need to access the vSphere MOB on an ESXi how, this of course can be re-enabled from the default. There is also a new ESXi Advanced Setting called Config.HostAgent.plugins.solo.enableMob which easily controls whether the vSphere MOB is enabled or disabled as seen in the screenshot below.

You have the option of using either the vSphere C# Client as shown in the screenshot above or the vSphere Web Client to configure the ESXi Advanced Setting:

You can also configure this property using the vim-cmd in the ESXi Shell.

Listing the ESXi Advanced Setting using vim-cmd:

vim-cmd hostsvc/advopt/view Config.HostAgent.plugins.solo.enableMob

Configuring the ESXi Advanced Setting to true:

vim-cmd hostsvc/advopt/update Config.HostAgent.plugins.solo.enableMob bool true

If you prefer to automate this using PowerCLI or vSphere API, this can also be done. Below are two examples using the Get-VmHostAdvancedConfiguration and Set-VMHostAdvancedConfiguration PowerCLI cmdlets.

Listing the ESXi Advanced Setting using PowerCLI:

Get-VMHost 192.168.1.200 | Get-VmHostAdvancedConfiguration -Name Config.HostAgent.plugins.solo.enableMob | Format-List

Configuring the ESXi Advanced Setting to true:

Get-VMHost 192.168.1.200 | Set-VMHostAdvancedConfiguration -Name Config.HostAgent.plugins.solo.enableMob -Value True

If you rely on using the vSphere MOB on ESXi and would like this to be your default, I would recommend you update either your ESXi Kickstart or Host Profile to include this additional configuration so that you do not get like I did 🙂 If you only need to use the vSphere MOB on occasion or do not have a use for it at all, then leaving the default is sufficient.

Fun end of the year facts on virtuallyGhetto

12.22.2014 by William Lam // Leave a Comment

I woke up at 6am this past Sunday for no apparent reason. Perhaps my body is preparing me for parenthood? In any case, I could not go back to sleep and started to think about some of the blogs I have written this past year on virtuallyGhetto (finishing its 5th year). With the year almost ending, I thought it would be cool to check out some of the statistics on virtuallyGhetto for this past year and share some of the fun facts with my readers. The data below is gathered by a WordPress plugin called Jetpack which is a must have for any bloggers using WordPress and the WP Statistics Plugin.

I would also like to take this moment and say thank you to all my sponsors for supporting virtuallyGhetto and most importantly I would like to say thank you to my readers. Thank you for your engagement whether that is a comment on my blog, a discussion on Twitter, an email describing a problem or just saying hi at a conference. Thank you to everyone who has shared interesting stories, challenges and unique use cases on how you use VMware products and continuing to help us improve our products. 2014 has been an amazing year and I look forward to all the exciting things coming in 2015 as well as continuing to share and contribute back to the community through my blog. If there are any topics that you would like to see me explore further or continue to explore next year, feel free to leave a comment or send me an email. I wish you a Happy Holidays tand have a fun and safe Happy New Years, see you all in 2015!

[Read more...]

Quick Tip - How to enable "remote" disk for Nested ESXi?

08.13.2014 by William Lam // Leave a Comment

I always love to hear about new tips and tricks from Internal VMware folks, especially ones that I can share with the community. The other day, my colleague Paudie O'Riordan had a pretty interesting problem that he was trying to solve pertaining to a re-production he was helping out with. After he found the solution, he thought I might find it interesting and he shared the details with me.

Paudie was looking for a quick way to force a disk to show up as "remote" versus "local" in a Nested ESXi VM during the installation process.

The disk type will depend on how the disk was presented to the ESXi host, but sometimes even local devices may show up as remote, especially if the disk controller is not in pass-through mode. Instead of having to setup a complex iSCSI setup, Paudie found that if you selected LSI Logic SAS as the virtual SCSI Disk Controller for your Nested ESXi VM instead of the default LSI Logic Parallel, that automatically any disks placed on that controller will automatically show up as remote.

This is definitely a handy tip you may want to bookmark, especially if you are looking to test any type of Kickstart configuration where you may be dealing with remote devices or practicing for your VCP/VCAP exams and playing with ESXCLI claim rules.