vSphere 5 – Storage pt.1 VMFS and Provisioning

VMFS:

VMware® vStorage Virtual Machine File System (VMFS) is a high-performance cluster file system that provides storage virtualization optimized for virtual machines. Each virtual machine is encapsulated in a small set of files and VMFS is the default storage system for these files on physical SCSI disks and partitions. This File system enables the use of VMware® cluster features of DRS, High-Availability, and other storage enhancements.
For more information please see the following document here and the following KB here.

Upgrading VMFS:

There are two ways to upgrade the VMFS to version 5 from previous 3.xx. An important for when upgrading VMFS-5 or provisioning new VMFS-5 is that legacy ESX host will not be able to see the new VMFS partitions. This is because of the enhancements made into ESX and the partitioning. Upgrading VMFS-5 is irreversible and consider always what you are doing. Lastly, there are many ways to provision VMFS-5 these are just two of the more common ways of doing it.

Method 1: Online Upgrade

Although an online upgrade does give you some of the new features in VMFS-5 it does not give you all of them. However, it is the least impacting and can be performed at anytime without an outage. Below are the features you will not gain by doing an in-place upgrade:

• VMFS-5 upgraded from VMFS-3 continues to use the previous file block size which may be larger than the unified 1MB file block size.
  
• VMFS-5 upgraded from VMFS-3 continues to use 64KB sub-blocks and not new 8K sub-blocks.
  
• VMFS-5 upgraded from VMFS-3 continues to have a file limit of 30720 rather than new file limit of > 100000 for newly created VMFS-5.
  
• VMFS-5 upgraded from VMFS-3 continues to use MBR (Master Boot Record) partition type; when the VMFS-5 volume is grown above 2TB, it automatically & seamlessly switches from MBR to GPT (GUID Partition Table) with no impact to the running VMs.
  
• VMFS-5 upgraded from VMFS-3 continue to have its partition starting on sector 128; newly created VMFS5 partitions will have their partition starting at sector 2048.
  

RDM – Raw Device Mappings

• There is now support for passthru RDMs to be ~ 60TB in size.
  
• Non-passthru RDMs are still limited to 2TB – 512 bytes.
  
• Both upgraded VMFS-5 & newly created VMFS-5 support the larger passthru RDM.
  

The end result in using the in place upgrade can be the following:

• Performance is not optimal
  
• non-standards can still be in place
  
• Disk Alignment will be a consistent issue with older environments
  
• File limit can be impacting in some cases
  

Method 1: How to perform an “Online” upgrade for VMFS-5

Upgrading a VMFS-3 to a VMFS-5 file system is a single-click operation. Once you have upgraded the host to VMware ESXi™ 5.0, go to the Configuration tab > Storage view. Select the VMFS-3 datastore, and above the Datastore Details window, an option Upgrade to VMFS-5 will be displayed:

Figure 3. Upgrade to VMFS-5

The upgrade process is online and non-disruptive. Virtual machines can continue to run on the VMFS-3 datastore while it is being upgraded. Upgrading the VMFS file system version is a one-way operation. There is no option to reverse the upgrade once it is executed. Additionally, once a file system has been upgraded, it will no longer be accessible by older ESX/ESXi 4.x hosts, so you need to ensure that all hosts accessing the datastore are running ESXi 5.0. In fact, there are checks built into vSphere which will prevent you from upgrading to VMFS-5 if any of the hosts accessing the datastore are running a version of ESX/ESXi that is older than 5.0.

As with any upgrade, VMware recommends that a backup of your file system is made prior to upgrading your VMFS-3 file system to VMFS-5.

Once the VMFS-5 volume is in place, the size can be extended to 64TB, even if it is a single extent, and ~2TB Virtual Machine Disks (VMDKs) can be created, no matter what the underlying file-block size is. These features are available ‘out of the box’ without any additional configuration steps.

NOTE: Some documentation are excerpts and provided and used from VMware Documentation and Sources..

Method 2: Provisioning New VMFS-5

This method explains how to update VMFS without performing an “online” upgrade. Essentially this would be the normal process of provisioning a VMFS LUN for ESXi 5 or older. Here are the listed benefits of VMFS-5 provisioning without doing an “online” upgrade.

• VMFS-5 has improved scalability and performance.
  
• VMFS-5 does not use SCSI-2 Reservations, but uses the ATS VAAI primitives.
  
• VMFS-5 uses GPT (GUID Partition Table) rather than MBR, which allows for pass-through RDM files greater than 2TB.
  
• Newly created VMFS-5 datastores use a single block size of 1MB.
  
• VMFS-5 has support for very small files (<1KB) by storing them in the metadata rather than in the file blocks.
  
• VMFS-5 uses sub-blocks of 8K rather than 64K, which reduces the space used by small files.
  
• VMFS-5 uses SCSI_READ16 and SCSI_WRITE16 cmds for I/O (VMFS-3 used SCSI_READ10 and SCSI_WRITE10 cmds for I/O).
  

Other Enhancements:

• Disk Alignment for Guest OS’s become transparent and have less impact.
  
• Performance I/O and scalability become a greater value to running online vs. new.
  

As you can see the normal provisioning of VMFS-5 is a lot more robust in features and offers a great deal of improvement to just performing an “Online” upgrade. The online upgrade is easy and seamless but for normal considerations all benefits should be considered. In my case the chosen Method would be Method 2. The only instance in which an “Online” upgrade would be considered under normal circumstances would be if you were already at capacity on an existing array. In this type of scenario it could be viewed as a more beneficial way. Also, if you did not have Storage vMotion licensed through VMware further considerations on how to migrate to the new VMFS would have to be made. Migrating workloads to new VMFS-5 would be a bit more of a challenge in that case as well. However this is not an issue under most circumstances.

Method 2: How To provision new VMFS-5 for ESXi

1. Connect to vSphere vCenter with vSphere Client
2. Highlight a host and click the “Configuration” tab in the right pane.
3. Click on “Storage”
4. In the right pane click “Add Storage” (See image)
5. Select the LUN you wish to add
6. Expand the Name column to record the last four digits (this will be on the naa name) In this case it will be 0039. Click “Next”
7. Select to use “VMFS-5″ option
8. Current Disk Layout – Click “Next”
9. Name the datastore using abbreviations for the customers name with the type of storage followed by the LUN LDEV (Yes, a standard). This example would be “Cust-Name”=name “SAN”=type “01″= Datastore Number “LDEV” = 0038. (cus-nam-san-01-1234)
10. Select the radio button “Maximum available space” click > Next
11. Click Finish and watch for the “task” to complete on the bottom of vSphere client
    
12. After the task completes go to the Home > Inventory > Datastores
13. Make sure there is a Fiber Storage folder created. Under that folder create a tenant folder and relocate the datastores in the new tenant name folder.
    
14. After moving the folder you may need to provision this datastore for vCloud. Proceed to the optional method for this below.

Note: Some of the information contained in this blog post is provided by VMware Articles and on their website http://www.vmware.com

vSphere Networking 101 – Renaming VMnics – Backup and Restore

This is a super simple tutorial that I wanted to do on how to rename VMnics. This is great for network card replacement and is just a good thing to know in case something does go south on a hardware replacement. Let’s move on.

SSH to your host and try to keep in mind to use a DRAC or ILO just in case. There should be no need to do this if you are not touching the management or service console uplinks for ESX or ESXi.

1. run:
2. cp -p /etc/vmware/esx.conf /etc/vmware/esx.conf.backup (This will backup the current configuration seek kb here)
3. VI /etc/vmware/esx.conf
4. scroll down and locate the Dev/ids and these will be followed with a =vmnic#
5. Type i
6. go over to the VMnic you wish to modify
7. delete of backspace
8. Type in the right name
9. Hit “ESC”
10. Type “:wq” yes that is a colon wq.

You can either reboot or try cycling services but that is pretty much all that really to it. Enjoy and thinks for stopping by!

Youtube video:

VMware vSphere Labs – Infrastructure – Setting Up Active Directory on Windows 2008 R2

This Tutorial runs through a quick overview of installing Active Directory 2008 R2 on a Windows Virtual Machines running in VMware Workstation 8. It has a Video and general instructions to help you out. Enjoy!

1. Deploy from the template
2. Configure NICS Static
3. Disable Extra NIC
4. Gateway and DNS are the Gateway list in “Virtual machine Editor”
5. Keep DNS as the secondary DNS of the Domain Controller
6. Rename machine to appropriate Computer Name to reflect your Domain Controller (sysprep gives silly names)
7. Reboot
8. Add Role from server manager
9. Select Active Directory Domain Services
10. Yes, Install the .Net Stuff….
11. Run DCPRomo.exe from powershell or within the server manager under AD role
12. Install DNS (if not you must be doing something a bit more advanced )
13. Reboot and validate you can log into AD with a Domain Account.
14. Join another Virtual Machine to the Domain

VMware vSphere – Networking Best Practices – Networking 101 pt.2

Okay Experts take it easy on me…

As you know I have been writing various post around building your VMware Workstation Lab. One of the key points that I am trying to drive during this lab build is how to get your environment as closely matching a production environment as you can. Obviously networking is a very broad subject especially when it comes to implementing a production vSphere environment. I am going to attempt to do this topic justice by sharing some key points that should help you understand more of how you should design your network. I am not going to attempt to do what Kendrick Coleman does (because his designs are solid). I am only going to provide talking points and recommendations about traffic separation, why it should be separated, and details. Also, keep in mind that the most important factor of networking is using N+1 or not to use N+1. I will say that it is highly recommended from VMware to have your physical networking N+1 so you can benefit further from High-Availability. So let’s get started with the traffic types.

Traffic Types:

1. Management (High Availability)
2. vMotion
3. Fault Tolerance (Not in all cases)
4. VM Networks
5. Backup (Not in all cases)
6. Storage/NAS (Depends on the type)

Note: backup and Storage say depends because in some cases you may or may not have iSCSI/NAS storage or be running backups for your virtual machines, Especially if you use a product like Veeam or CommVault. Fault tolerance isn’t really used and I believe that even when it does get better it still may not be worth it, considering all the bigger workloads and cost in licensing as well. Here are my recommendations and best practices I follow for dedicating traffic:

1. Management: If possible: VLAN it, Separate the traffic (to a different switch), Use teaming or a single Nic (if you set up a MGMT kernel on another port group), You can run/share traffic with vMotion, Fault Tolerance, Backup, and Storage NAS. If you do share traffic use some sort of QOS or Network I/O control. BE mindful that running management with all this traffic isn’t recommended but this would provide you a way to run all this traffic over a separate switch a part from production VM traffic. If you have plenty of NICs then you can run it over the VM production network (but you don’t want to expose it to that network) but you must somehow separate it with a different subnet or VLAN. Most cases I see vMotion and MGMT being shared with Fault Tolerance (FT with big 10GB networks). Your NIC teaming should use explicit failover and over-ride so your vMotion/FT traffic will go over a seperate interface then your management traffic.
2. vMotion-FT-Backup-Storage-NAS: L2 traffic, hopefully doesn’t have to be routed, in most cases I see this and management traffic being shared, especially with 10GB. vMotion+FT+Backup+NAS if you don’t have a ton of connections. On this particular set up it would be good to setup Jumbo Frames. This traffic you wouldn’t want running over production if possible so a dedicated switch would be really good, also VMware recommends using a dedicated storage switch anyways.
3. VM Networks: I usually dedicate two NICs for VM production traffic and usually create separate port groups for each type of VM related traffic. In some cases you may have a customer who requires separating this out over different NICs. Again this is just one of those you have to look at based on requirements at that time. Normally the ladder is good enough.
4. Storage/NAS and Backup: In most cases businesses may have their own backup network. You could run storage and backup traffic over those switches if you choose. In that case, you mines of well also run vMotion and FT.
   

The Switches and considerations:

You usually want 2 types of switches if that is all you can do. In some cases if you go 4 that would be even better because then you can look at N+1. Where you can try to separate the big traffic from the little traffic (Management). If you cannot separate it by using dedicated switches then use QOS or NIOC to control the traffic. Managed switches can be expensive, just remember in vSphere 5 support for LLDP came into being so you don’t have to worry about buying CISCO stuff to get that CDP information. If you do not plan on using a Converged Network Architecture (FCoE) then be sure to buy enough 1GB Nics. These things are cheap you can load them up even if you may not use them. Things like migrations and stuff come up and if you only buy what you need you’ll end up robbing Peter and paying Paul.

This is really just a quick overview and recommendations. Unfortunately we only have what we are given in most cases. We also work off budgets.  I am going to cover some lab exercies that break this down even further.  General Stuff… I hope you enjoy it and I am sure I am going to be updating it as well.

Cheers,
Cwjking

[Resolved] VMware Workstation 8 – Windows XP VM Hang Issue

This video explains how I solved my own issue after I upgraded to VMware Workstation 8. It seems going throught he process of removing and adding virtual devices narrowed mine down the A: drive or aka Floppy Disk. I just simply disconnected it through VMware Workstation and I would recommend removing it entirely if you do not need it. To this you would need to power down the VM. Just for the record I did an upgrade for VMware workstation, however it completely uninstalls and reinstalls the new version.

1. Power Down the VM

2. Right Click and go to “Settings”

3. Click on the Floppy Drive

4. Click Remove

5. Click Ok

*NOTE* You can also just uncheck the connect at power on option as well. I hope this fixes your issue as well.

VMware vSphere Labs – Foundations – Installing VMware Workstation 8 Custom

This video simply depicts how to install VMware workstation 8. It’s nothing really advanced it just covers a more thoughtful way of install VMware workstation 8.

The only thing really important to note is that VMware Workstation 8 installs windows services as part of the installation. What this means is that if you do install it on a separate drive it will need to be a part of a back up in order to do a full system restore. Meaning that you will have to do an image of that other drive. When using windows 7 of course. Remember this is a simple approach and may not cover as deep as you may want it too.

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere Labs – Foundations – First Series

Well, I have decided to dub my basic intro into VMware workstation labs as “Foundations” . I, like many others, enjoy discussing and learning about everything. Storage, networking, what I want to achieve, what I am designing for, name a few things you will have to consider in your lab. Sure, there is the easy stand up a lab slap some storage on it, run ESXi, Build vCenter, but for the few, the proud, and the pros… we like to cover it all. This series is pretty much going to go through every bit of that. Yeah, every bit… even the crumbs from the table. So here is the outline and obviously post videos and notes on each. Duly note, that at any time I may add a few dozen more post to foundations as I embark on this journey. I am looking forward to it and I hope you do as well! (Perhaps when I get to it I will do some CommVault vs. Veeam videos when I get a chance – OH, the drama!)

1. The different kinds
2. The Downloads and what you need to know
3. VMware Workstation Storage Considerations
4. Networking Considerations and Design
5. Installing Custom VMware Workstation 8
6. Creating you windows 2008 R2 template VM in VMware Workstation 7 and 8

Yeah, I know who would’ve ever thought a lab took this much thought. It’s just good stuff to think about and if people are board well you got something to do or watch. By the way, some videos have some music others don’t. Again feedback always appreciated!

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere Labs – Foundations – VMware Workstation Storage Considerations

This video informs you of what you may or may not know about the different types of storage you can use for your VMware vSphere lab set up. Things like physical iSCSI and NFS and Virtual Storage Appliances (VSA) are important to know about and some are MIUCH cheaper than the other.

Links Show in the video:

http://www.techhead.co.uk/how-to-configure-openfiler-v23-iscsi-storage-for-use-with-vmware-esx
http://go.iomega.com/en-us/products/network-storage-desktop/storcenter-network-storage-solution/network-hard-drive-ix4-200d-cloud/?partner=4760
http://nickapedia.com/2010/05/01/celerra-vsa-uber-smaller-faster-easier-geekier/
http://thehyperadvisor.com/?p=934
http://www.vmware.com/products/datacenter-virtualization/vsphere/vsphere-storage-appliance/overview.html

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere Labs – Foundations – The Template on Workstation 7 and 8 – Windows 2008 R2

This videos covers the template we will be setting up for deploying windows server 2008 r2 from. On this template we will be installing Active Directory, DNS, vCenter Server, and a lot more stuff. At the bottom of the blog will be references for ensuring your template is supremely prepped for space and performance!

Here are both the videos one for doing it:
VMware workstation 7:

On this video I made a few mistakes… but this wouldn’t be VirtualNoob if I didn’t make a few of those.
VMware workstation 8:

Really great resource:

http://www.happysysadm.com/2010/11/vmware-windows-2008-r2-template.html

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere Labs – Foundations – Networking Considerations and Design

This how to will go into some detail of the Networking consideration for your VMware Lab. It’s all in what you want to do.

This video addresses those considerations and provides some details on how you may want to do that. If you want some resources for particular lab setup head on to the bottom.

Another Lovely Video

Networking (As seen in the video if you want to reproduce

1. Management Stack for vCloud :
2. Production stack for tenants:
3. VMnet1  192.168.240.xxx – ESXi Management Host-Only (isolated for security )
4. VMNET2 192.168.238.xxx – iSCSI (vmkernal port group and NFS will be shared)
5. VMNET3 192.168.237.xxx – vMotion
6. VMNET4 192.168.5.xxx – VM Networks for ESXi host
7. VMnet8 192.168.4.xxx – Production-MGMT

   .10 = Domain Controllers

   .20 = vCenter Servers (2 interfaces one for ESXi MGMT and Production)

   .30 = All Other systems

8. VMNET5 192.168.120.xxx – vCloud Mgmt

Other Wonderful Links on vSphere Labs and Networking Design included are SRM and vCloud Director Setups:
http://nickapedia.com/2010/10/07/lights-camera-replication-uber-srm-video-guide/
http://www.hypervizor.com/2010/09/video-guide-taking-vmware-vcloud-director-for-a-spin-and-on-the-go/
http://www.yellow-bricks.com/2010/09/13/creating-a-vcd-lab-on-your-maclaptop/
http://blog.tsugliani.fr/featured/create-your-own-virtual-vcloud-lab-part-1/
http://www.chriscolotti.us/vmware/vsphere/vmware-vcloud-in-a-box-for-your-home-lab/

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~