I recently updated my Ubuntu install from 17.04 to 17.10, which meant the kernel was updated to 4.13. As a result, I was no longer able to run VMs with VMware Workstation. I found some posts regarding the error and that it was due to a change in the way the Linux kernel handles paging. To resolve the issue I needed to replace the vmmon modules. I didn’;t take down the entire error message, but this post references the same error.

Today I came across the need to use PowerCLI on a computer without internet access. Thankfully I found this blog post detailing the steps that I needed to perform, however not all was rainbows and unicorns. I quickly ran aground when attempting to import the modules. After a bit of research, I learnt that Microsoft had changed the module directory structure in PowerShell v5. This new structure is not compatible with previous versions.

vRA uses Custom properties to help define parameters and the behaviour of requests. In the previous post CHEF: vRA Integration, Property Groups and Blueprints we used custom properties to define the properties of our Chef deployment. In this post, we look at using custom properties to assign the node environment. The Chef default client deployment workflows form the basis of the examples. A brief on custom properties We use custom properties to manipulate many aspects of workflow execution.

The Chef plugin provides some workflows to help with getting the vRA integration up and running with minimal effort. I would suggest treating them as samples to build functionality on top of. There are some limitations from the default state which might not provide sufficient flexibility for production usage. Setting up the Property Groups: Launch the vRO Client and navigate to the Chef workflow ‘Create Property Group for Chef EBS Workflows’.

Chef Integration with vRA: Part1 In the previous Chef integration with vRA post, we covered how to install the Chef plugin for vRO. In this post, we will look at provided workflows used to install the Chef Client on Windows and Linux VMs. The workflows are called by the Event Broker Servers (EBS) after a VM is provisioned. The Client Provision Workflow To begin launch the vRO client and navigate to the Chef workflow folder.

The Chef agent is installed on a VM after the VM has been deployed and completed the ‘Machine Building’ stage of deployment. This is achieved by creating an event subscription through vRAs Event Broker Service (EBS). When an event triggers an EBS subscription, vRA communicates with vRO causing a workflow to run. This means the first step of configuring Chef integration with vRA is to configure the Chef vRO plugin.

In October 2016, I took the VCP6-NV exam and failed. While this was not the first exam I have failed, it was eye opening. After seeing the question set, I realized my understanding of the exam was incorrect. I wrote a post In February, I went to retake the exam but due to an issue with the Pearson systems I couldn’;t sit on the day. On the 31st of March I sat the exam for the second time and passed.

I primarily use this PowerCLI script after performing VM migrations. The script output focuses on what changed during the migration. Specifically moving to hosts running a newer version of ESXi. The script is simple to modify and adapt to fit your specific needs. Using the Script To make use of the script, all that you need to do is set the $ClusterName and $Path values at the beginning. However, think of this not as a ‘run as it is’; script.

Layer2 Invisibility L2 traffic is a major blind spot for many companies. Most security filtering only happens when traffic traverses a Layer3 boundary. If traffic does not cross this boundary, it is not scanned and not seen. Attackers can move unseen within a L2 network, due to this lack of visibility. Physical firewalls work well for North-South traffic. They do not perform as well for east-west. Creating a shell, that offers no internal protection.

QoS is a method of providing a minimal Quality of Service to network traffic. This is done through adding values to the Ethernet or packet headers. By adding these values, priority can be assigned to network traffic types. Some services do not a significant amount of bandwidth but are sensitive to latency. These services can benefit from QoS. Networks use QoS as a way to give priority where needed. A service provider often provides a level of service for their clients.

Last night Sydney VMUG hosted a VCDX Workshop, with Travis Wood presenting. This is the first workshop that I have attended and thought that I would share some thoughts on my impressions. Travis holds two VCDX certifications for Data Center Virtualization and Desktop and is a VCDX panelist. Being a VCDX panelist means that Travis reviews design submissions and sits on the examinor panel, grading defences. What is the VCDX Certification VCDX is VMwares top level certification and validates a mastery of VMware technologies and design methodologies.

RDM High-Level Cover VMware vSphere RDM or Raw Device Mapping is the method to remove levels of abstraction from the storage presented to vSphere VMs. RDMs are used to meet use cases and could be considered a deviation from the ‘normal’;. When creating an RDM, there are two options; Virtual and Physical. A Virtual RDM provides some level of storage abstraction. Physical does not, the full capabilities are visible by the VM.

I’;ve been having some issues with the conversion of a VMDK to a Physical RDM. This is a request from a client, as the storage and backup vendor has stated that there are advantages to doing this. Not something I have done before, but nothing wrong with that. I found the KB article with ease: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=3443266 Steps looked straight forward, get the identifier and power down the server, run the commands.