My Virtual Ramblings
Announcing VMware’s Developer Program: VMware {code} #vmwarecode
VMware {code} keeps developers up to date with emerging topics such as Microservices, Cloud-Native Applications and Agile Development & Deployment. Join us as we build, deploy and run!
VMware VSAN: When good enough more than passes muster (via The Register)
Last week I attended SFD9 and the last session of the week was with VMware about VSAN 6.2. This is not a review of the product or an analysis about single features; there are plenty of them already. Instead I’ll talk about what a product like VSAN 6.2 means for the entire SDS/HCI market.
VMware All Flash VSAN Implementation (Home Lab)
I’ve been waiting for a while to be able to implement an all flash VSAN in my lab and now that VSAN 6.2 has been announced, I thought it would be time to upgrade my capacity disks from HDD’s to SSD’s and get cracking..! (note: despite the announcement, VSAN 6.2 binaries are NOT YET available to download. I’m hearing it would be available in a week or two on My VMware though so until then, mine is based on VSAN 6.1 – ESXi 6.0U1 binaries)
Licensing Options for your vSphere Home Lab (via Wahl Network)
Looking to snag VMware licenses for your home lab adventures? Check out what I’m using, plus other options that don’t break the budget!
How vRealize Automation 7 builds on previous versions
VMware vRealize Automation 7 improves upon older versions with a simplified installation process and new tools to offer administrators greater control over automation.
Let’s go over how to disable the “This host currently has no management network redundancy” message. It’s annoying and we can get rid of the yellow triangles that show on the hosts due to this message. And I know, you “should” have redundancy on your management network but we’re just not worried about it. Our hosts are in our building and not at a co-lo so we have constant access to them in the event something happens and we need access.
Since we don’t care about this warning, I wanted to hide it. This way we can see if there are actual errors on the host and not some warning about network redundancy. The fix is done with an advanced option in the cluster properties. In the cluster properties, under vSphere HA, select Advanced Options. Then add an option named das.ignoreRedundantNetWarning and set the Value to true.
And that’s it! Once the option is in, go to each host and reconfigure for vSphere HA. The warning will then disappear and your vCenter will look clean again.
vExpert 2016 Award Announcement
First we would like to say thank you to everyone who applied for the 2016 vExpert program. I’m pleased to announce the list 2016 vExperts. Each of these vExperts have demonstrated significant contributions to the community and a willingness to share their expertise with others. Contributing is not always blogging or Twitter as there are many public speakers, book authors, script writers, VMUG leaders, VMTN community moderators and internal champions among this group.
CloudCredibility.com invites you to get ready for VMware’s upcoming Launch Events, February 9 & 11!
CloudCredibility.com invites you to get ready for VMware’s upcoming Launch Events, February 9 & 11! One lucky attendant and CloudCred player** who completes Task 3065 will be selected at random to win an event pass to VMworld 2016 !
VMware Integrated Containers critical to company’s #DevOps strategy (via @TechRepublic)
As DevOps adoption increases, VMware is attempting to drive interest in vSphere with VMware Integrated Containers.
I had an issue when using update manager to scan a host and it would fail with a “Check log for errors blah blah blah”. The errors are never useful. After investigating and checking the log, I found the following entry:
2015-06-02T20:57:30.312-07:00 [00504 info ‘VcIntegrity’] Error on logout (ignored): vim.fault.NotAuthenticated
When researching the issue, I came across a best practices guide that basically pointed out the error. So as a general best practice, verify on your hosts, on the configuration tab, under DNS and Routing, that you have filled in all the fields. I had missed the Search Domain field on that particular host which was causing the scan to fail.
The fields with the blue boxes will cause the Update Manager scan failure as well as cause other issues with DNS on the host. Just another one of things to check!
As always, leave questions or suggestions in the comments.
