Wilk's Notes

This year I got invited to speak at Ireland VMUG on Friday February 2nd. I have to admit I was quite nervous about it as I always considered presenting at VMUG a great honor - especially for someone as me; not really known in the industry... yet ;)

Admit it. This can happen to all of us. Somebody was changing the root password while intoxicated, without a notepad at hand or had a sudden memory loss. Whatever's the reason, you're now locked out of your own host. What now?

Quickie (noun): 1.  a rapidly consumed alcoholic drink. 2.  a brief act of sexual intercourse . Today we're going to add a third definition to that list: 3. a low effort (but still informative) blog post.     Without dragging this (brief) introduction any further - let's get started.  

Essential network components are sometimes the hardest to configure without knowing the basics. When I first started working on a virtual environment, I didn't even know I had to setup networking! It took me weeks to understand fully how all the VMware "parts" speak to each other. The vKernels, vSwitches, vLANs versus VLANs... yeah, that's a story for another time.  For now, let's talk about the basics. In this post I'll quickly walk you through the process of setting up a virtual router (vRouter) - a Linux VM responsible for most of your internal virtual networking. Once we have that up and going, we can continue our journey through the exciting world of virtual networking inside both VMware vSphere and Hyper-V.