Standing up the environment with the integrated Database is easy enough however if you want to add Active Directory into the mix it gets more fun.
During this I encountered the following issues:
Welcome to Part 2, this part will provide the background and current topology that is to be replaced, the real fun will start in Part 3. I know you are all impatient to get started configuring switches, routers and servers but I think that the design and the reasons behind the design are as important (if not more so) than the actual configuration. As always I know I am not perfect and all knowing so if from the background and the following tutorials you think I have missed something or could have done something better then please speak up, send me a message via the contact page or leave a comment.
NINet has grown since the last series and now has a floor of approximately 40 developers developing video solutions. The current solution was put together in bits and pieces and is resulting in poor performance and frequent outages. It must be stressed that this is a development network and as such cannot be locked down developers need to be able to connected unmanged switches (much to my irritation) and connect devices at will.
This series of tutorials will be similar to my posts on a wireless setup, where I take a real world requirement of mine and fit it to a tutorial about NINet.org.
This series will take an existing flat topology with mixed switches running in L2 and convert it to a Cisco Switch Topology mixing L3 and L2. Then we’ll take a bit of step into the sysadmin side of things where we setup infrastructure servers to support the end users. At the time of this writing, in the real world, this network is up and running however the supporting infrastructure is a lower priority than other work items so it may take a while to filter through to here.
This is just a quick gotcha that I found ages ago then forgot about and then had to figure out again. Before you convert the VM to a template.
rm /etc/udev/rules.d/70-persistent-net.rules
sed -i ‘/HWADDR*/d’ /etc/sysconfig/network-scripts/ifcfg-eth0
sed -i ‘/UUID*/d’ /etc/sysconfig/network-scripts/ifcfg-eth0
Update:
This also applies to SLES 11 SP2 (use /etc/sysconfig/network/ifcfg-eth0)
Bad news is that as of the 2011-12-31 I finished working for my Employer in order to move back to my home country, so I no longer have direct access to (and responsibility for) VMWare (and all the other really cool stuff we had, infini-band, HPC etc.) To top it off I was told before I left they intended to implement vblock (I suspect they just wanted to make me jealous ;) )
Good news is that from the 2012-01-09 I am starting my new job which will be mainly SCCM to start but moving into Citrix as well. So you will likely see no more VMWare posts, however I intend to make it up to you all by posting lots more
This is a function that allows you to clone a VM from a specified snapshot. The only way to do this in the UI would be to take a snapshot of the current state, revert to the one you wish to clone, clone, revert to latest snapshot and then delete latest snapshot. As you can see that is time consuming and takes numerous mouse clicks.
I recommend adding this function to your powershell profile so you always have access to it.
As always feel free to comment.
Deprecated – VMWare have release an official checker and there is a better script at http://virtu-al.net
This is a script I wrote to check vSphere 5 vRAM compliance.
Yet another role added to my Job description, Now I am managing our Virtual Servers. So true to form I’ve dived headfirst into powershell / powercli to see what I can do. Some of the posts coming up on this will likely be similar to others around the web as I reinvent the wheel while I learn. But you never know one of you might find me 1st or I might do it in a way that suits you better.
First up is a simple script to read data from an xml file and then update custom attributes on the vmhosts.
