Hey if you get a chance check out the blog below, Andres did a really nice write up about the Phoenix VMUG and their product..
I had a chance to watch the Nasuni presentation and they offer are really cool vm appliance that allows for “virtually” unlimited storage for a flat rate price…
When I heard the flat rate price it floored me how cost effective it was…
I currently have a need for some off site storage and we’ll be looking at Nasuni very soon…
I found this neat web tool today… it was a pretty quick way to do a Who-is and then do simple tests like SMTP, DNS, etc..
One feature I liked the Black list checker… real easy way to see if your domain or the domain your trying to send email to has been black listed.
VMware offers a free downloadable Exchange starter kit.
What you’ll get are 3 files (2PDF’s and one Video):
University of Plymouth – Video.mov
Here this link to register..
I found this information useful if your needing to do an “executive overview”.
If you need in-depth information and how-to’s for business critical apps then start here..
Tonight I got the pleasure to work on my home lab a bit..
Here is what I am currently running..
Antec Sonata Gen 1 Case
Antec 650 Earth Watts Power Supply
Gigabyte EP43-UD3L MB
Intel® Core™2 Quad Processor Q9400 2.66Ghz/1333FSB/6MB Cache
Cooler Master TX3
8GB of Patriot DIMM 2GB PC2-5300U CL4-4-4-12 (DDR2-667) (PEP22G5300LL)
500GB/300GB/160GB SATA 3.0 HD’s
Windows 7 – 64 Bit
VMWare Workstation 7
Installation of ESX 4.0 was easy… just follow the steps to create a new VM and choose ESX 4.0
Installation of ESX 3.5 was a bit tricky at first… I did the usually google for answers but everything was on Workstation 6.5 and how to modify the vmx config file…
I ended up doing the following and it seams to be working well..
Create a custom VM
Choose “I will install the OS Later”
Select “Red Hat Enterprise Linux 5 64-bit”
Defaults on the rest
When it completed set it to boot to your ESX3.5 Media, so that you can install the OS
Complete the OS install and your done..
Much easier then WS 6.5
Mine ran with out issue and it really moves..
In fact I installed it with my ESX 4.0 VM running in the background..
So far workstation 7 is seems to be a big improvement and it’s quite speedy for me..
I bought this book today… based on some blog posts I found (see below).
I must say it is one of the best.. It is a pocket reference so be aware the print is a bit small…
Download the Power-CLI Scripts from the book here…
Here are some notes about the book.. From this URL…
What a great way to kick off the new week – The highly anticipated book, vSphere 4.0 Quick Start Guide: Shortcuts down the path of Virtualization, has arrived at Amazon.com! I look at this new release as the 2nd edition or vSphere edition of RapidApp’s Quick Start Guide to ESX 3.0 which is still available and was a huge success.
The vSphere 4.0 Quick Start Guide was written by a lineup of new authors who are well known rock stars in the virtualization community: Bernie Baker, Thomas Bryant, Duncan Epping, Dave Mischenko, Stewart Radnidge, and Alan Renouf. I obtained a preview copy of this book at VMworld 2009 in San Francisco and I can tell you that this it is absolutely amazing. Nowhere else will you find as much information in such a small and convenient footprint. Its small size allows you to put it in your pocket and take it virtually anywhere: On the plane, on the bus, into a meeting, or into the datacenter. As with the first edition, there are several blank pages in this book which allow you space to write down notes, command line information, configuration maximum changes, information about your environment, helpful URLs, etc. The authors did a great job on this book and considering the cumulative years of experience and combined expertise packed into this book, you can’t beat the price. I don’t think a better value exists. My copy has been traveling with me daily in my laptop bag. I give it two thumbs up.
I found this switch that I believe will do VLAN’s and Tagging for only $340, not to bad for 24 port Gigabit and it seams like a deal for a ESX home lab..
I found this really cool article today… It’s not my work, but it is a great reference…
5 Critical VMware ESX CLI Network Troubleshooting Commands
by David Davis, vExpert, VCP, CCIE 9369 – December 23, 2008
Have you ever made a change to your VMware ESX Server Network configuration using the Virtual Infrastructure (VI) Client and then lost communications with the server? If you had to go to the ESX Service console to troubleshoot the virtual network configuration, would you know the commands to do it? In this article, you will learn the 5 most critical ESX CLI commands you need to know to troubleshoot networking issues.
#1) service network restart
The service X restart command is an excellent command that allows you to restart any service running on your ESX Server. In our case, we are using the network keyword to restart network services. This is the command you should run after making changes to your ESX networking configuration. You can also do network start or network stop. This brings down all network interfaces, then brings up the interfaces configured to start at boot.
The second command is ifconfig. Similar to the Windows command, ipconfig, this command is used to view the status of all network interfaces on the system. However, it can do a lot more than just view an interface, it can reconfigure interfaces, bring them down, or back up. You can change the IP address of your interfaces with ifconfig.
Next, we have the ESX command that allows you to view the status of or reconfigure the VMware Service console network interface. That SC network interface is called “vswif” and the first interface is always “vwsif0”. To view the status of it, you can use the -l (L for list)
The fourth command on the list is the esxcfg-vswitch command. This command is used to view the status of or reconfigure the VMware virtual switches (called vswitch). These vswitches are used to connect the physical NIC in the server (called vmnic) to the ESX port groups (such as the “Service Console” and the “VM Network” port groups). To view the status of your vswitches, you can use the -l (L for list) command, like this:
Lastly, we have the esxcfg-nics command. This command is used to view the status of or reconfigure the VMware Physical Network interface cards that are installed in the physical server. These physical NICs are called “vmnic” and they start with “vmnic0”. The vmnics are connected to vswitches to connect the physical network to the virtual networks.
To view the status of your vmnics, you can use the -l (L for list) command,
Believe me, there was a time that I was stuck at the ESX service console interface, trying to resolve a networking issues, and struggling to find the right commands to do it. I hope that you will save this URL or print this article to keep it handy the next time you are in a similar situation because that know that these 5 commands can help you get out of any VMware ESX Server networking configuration or troubleshooting issue.
From the command prompt enter
Netstat –nr — this Command will help you to id the actual gateway address
You now need to change your default gateway, you can do this by editing the network file located at /etc/sysconfig/network. To do this at the command prompt, follow the steps below.
Then while in vi, go to the location of the default gateway using the arrow keys.
Hit “i” which will perform an insert and change the default gateway to your liking.
Hit the escape key twice to exit insert mode.
type “:wq” to write (i.e save) and quit.
During the graphical installation of ESX 3.5 there is a single checkbox that states “Create Network for Virtual Machines” Usually I uncheck this box and create a new vSwitch for VM’s
However, if you don’t uncheck this box it will create the portgroup “VM Network” on the same vSwitch as the “Service Console” port group. If you run vCenter Server it’s easy enough to repair, however here is how it’s done from the console level…
Here is how you remove it from command line…
Esxcfg-vswtich –l –Show all the vSwitches and associated portgroups
Esxcfg-vswtich vSwitch0 –D “VM Network” – Actually Removes it
Here is the actual output…
I setup 4 ESX servers the other day and the wrong vlan tag was entered. MyLAN admin is out of the office, so I have two choices… One Bug him like crazy (Calls and Emails) or two wait till he returns to change the VLAN tag
I like Option 3 – Change the VLAN tag myself…
I found this here and it work perfectly…
Check which vSwitch the Service Console is on (and the name of the Service Console) with esxcfg-vswitch -l
To remove the vlan id completely, just set it to 0 (in case you have set it by accident on an access port)
esxcfg-vswitch vSwitch0 -v 0 -p “Service Console”
To set a vlan id on the service console (in case you forgot to define this during the installation)
esxcfg-vswitch vSwitch0 -v X -p “Service Console” (enter the vlan number where X is)
Here is my actual output (VLAN tags have been changed to protect the innocent!)