Recently (18th of April 2017) I covered Objective 2.7 from the VCAP6-DCV Design (VMware Certified Advanced Professional – Data Center Virtualization) certification blueprint on vBrownbag EMEA.
The objective had the ominous title of “Build Security Requirements into a vSphere 6.X Logical Design“. Among other things it covers the security aspects of a vSphere design and what needs to be kept in mind when addressing topics such as regulation compliance, Role Based Access Control and analyzing security requirements and how they can map to various design characteristics and IT processes.
Here is the slide deck:
I hope this helps someone on their path to achieving the VCAP-DCV Design exam (and than the VCDX of course).
Here is a link to all the other Objectives covered by vBrownbag
I’ll add the Youtube video as soon as it is published.
Recently I had the privilege to be selected as a contributor for the new vSphere Design Pocketbook v3, published by Pernixdata, where IOs are eaten for breakfast.
As the name implies this is the third edition of the book, each one with a different format.
First one had many tweet sized recommendations, the second on included longer posts on design and technical components while this third one is a mix of both.
The social edition, or the online edition only with more fancier name, can be downloaded right here. A physical copy will probably be available at various trade shows where Pernixdata has a presence.
Even as biased as I am I recommend picking up a copy for you and all your closest relatives, cause they will love you forever when you send them a copy. (results may vary).
And as a PernixPrime I also recommend you to check out Pernixdata based on their slogan: “Keep you CPU and memory close, but your IOs even closer”. (this is not their slogan and should be regarded as nonsense).
A short post, even though its been ages since my last post. But I promise I will fix that next week. 🙂 This one is more of a personal reminder cause the VMware KB had nothing on this, only this which didn’t work at all.
I was trying to vMotion a VM today (actually Redeploy VMs in vCloud but still) and I got this error:
A general system error occured: Failed to start migration pre-copy Error 0xbad010d. The Esx host failed connect over the VMotion network.
All host were using vDS and different VLANs for Managment and vMotion vKernels.
First thing to check is vmkping vMotion IPs on the hosts, everything checked out fine.
Then I glanced over the event log on the host and I saw that the vMotion vKernel was trying to contact the mangement IP on another host, not its vMotion vKernel (which were not on the same VLAN, as they should).
Just before I had to remove the receiving host from the vDS by unassigning all pNics from its vDS, restore vSS and re-add the host to the cluster.
So the easy way to fix that is to deselect vMotion on the management vKernel on the receiving host.
Took me at least good 20 min to finally check for that small line in the event log 🙂 I hope this helps someone in the future so they can use the 20 min to get more coffee and bacon.