<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Malaysia VMware Communities &#187; ISCSI</title>
	<atom:link href="http://malaysiavm.com/blog/tag/iscsi/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2011 15:50:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>FCoE in the Data Center</title>
		<link>http://malaysiavm.com/blog/fcoe-in-the-data-center/</link>
		<comments>http://malaysiavm.com/blog/fcoe-in-the-data-center/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 12:55:44 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[Nexus]]></category>
		<category><![CDATA[nfs]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1515</guid>
		<description><![CDATA[FCoE is new today for data center environment, but it will be very soon adopt by most of the users in 2 years time. If we look at the current environment in most data center today, there will be isolated environment of FC connection for Storage and Ethernet connection for networking purpose in every single [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.malaysiavm.com/blog/tag/fcoe">FCoE</a> is new today for data center environment, but it will be very soon adopt by most of the users in 2 years time. If we look at the current environment in most data center today, there will be isolated environment of FC connection for Storage and Ethernet connection for networking purpose in every single data center. Cabling management and knowledge require to keep the environment running and organize is becoming more challenging from time to time. Well, with the FCoE technology from <a href="http://www.malaysiavm.com/blog/tag/cisco">Cisco</a>, it will definitely simplify everything for us.<br />
<span id="more-1515"></span><br />
FCoE reduce the number of cabling require to be managed in the data center by replacing the traditional FC and Ethernet cable with <a href="http://www.malaysiavm.com/blog/tag/cna">CNA</a> cards and nexus switches. In additional to that, <a href="http://www.malaysiavm.com/blog/tag/iscsi">ISCSI</a> and <a href="http://www.malaysiavm.com/blog/tag/nfs">NFS</a> had become better and we have seen the storage vendor like <a href="http://www.malaysiavm.com/blog/tag/netapp">Netapp</a> which deliver the promises of performance over the IP base environment. FCoE will bring a lot of benefits to the virtualization host, especially when you plan to have <a href="http://www.malaysiavm.com/blog/tag/iscsi">ISCSI</a>, NFS and FC SAN to be connected to the same <a href="http://www.malaysiavm.com/blog/tag/esx">ESX</a> host.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/fcoe-in-the-data-center/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NFS ISCSI and FC Storage on vSphere</title>
		<link>http://malaysiavm.com/blog/nfs-iscsi-and-fc-storage-on-vsphere/</link>
		<comments>http://malaysiavm.com/blog/nfs-iscsi-and-fc-storage-on-vsphere/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 16:39:10 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Storage]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[FC Storage]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[nfs]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1510</guid>
		<description><![CDATA[NFS, ISCSI and FC storage are all supported in VMware vSphere today. As some of the benchmark been done recently showed the performance of ISCSI and NFS had been improved versus ESX version 3.5.  In the benchmark report it show that the overhead on NFS and ISCSI were higher VS FC storage. With the latest [...]]]></description>
			<content:encoded><![CDATA[<p>NFS, <a href="http://www.malaysiavm.com/blog/tag/iscsi">ISCSI</a> and FC storage are all supported in VMware vSphere today. As some of the benchmark been done recently showed the performance of ISCSI and <a href="http://www.malaysiavm.com/blog/tag/nfs">NFS</a> had been improved versus ESX version 3.5.  In the benchmark report it show that the overhead on NFS and ISCSI were higher VS FC storage. With the latest processors chip from <a href="http://www.malaysiavm.com/blog/tag/Intel">Intel</a> and <a href="http://www.malaysiavm.com/blog/tag/AMD">AMD</a>, I believe the overhead on the CPU will not be the major concern as users are always considering to maximize the usage of the CPU power they have in the physical server.</p>
<p><span id="more-1510"></span></p>
<p>We had been running Vmware in our environment for more than 2 years now in production mode and found that 80% of our production virtual machine should easily could be handled on either NFS and ISCSI. I will suggest to have <a href="http://www.malaysiavm.com/blog/tag/fc">FC</a> and IP <a href="http://www.malaysiavm.com/blog/tag/san">SAN</a> in place within the virtual infrastructure. This will allow the administrator to select the right storage option to support the IO requirement for each system been hosted in VMware. The mission critical and high <a href="http://www.malaysiavm.com/blog/tag/io">IO</a> requirements systems will be deployed on  the FC SAN, but the low IO requirement virtual machines will be migrated to IP SAN. With the storage vMotion option in vSphere 4, this will able to be done with zero down time. At cost perspective, it will make the hosting package to be more competitive to support the customer need.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/nfs-iscsi-and-fc-storage-on-vsphere/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Performance tuning on Virtual Infrastructure with MD3000i</title>
		<link>http://malaysiavm.com/blog/performance-tuning-on-virtual-infrastructure-with-md3000i/</link>
		<comments>http://malaysiavm.com/blog/performance-tuning-on-virtual-infrastructure-with-md3000i/#comments</comments>
		<pubDate>Mon, 25 May 2009 07:07:56 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Server]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[Dell]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[Jumbo Frame]]></category>
		<category><![CDATA[MD3000i]]></category>
		<category><![CDATA[R710]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vsphere 4]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1314</guid>
		<description><![CDATA[With the recent experience I had on the deployment with vSphere 4 and PowerVault MD3000i, I found there are plenty of room you may able to further fine tune to improve the performance of the storage and virtual infrastructure. Before this, the initial deployment was done by default configuration without any fine tune yet, and [...]]]></description>
			<content:encoded><![CDATA[<p>With the recent experience I had on the deployment with <a href="http://www.malaysiavm.com/blog/tag/vsphere">vSphere</a> 4 and PowerVault <a href="http://www.malaysiavm.com/blog/tag/md3000i">MD3000i</a>, I found there are plenty of room you may able to further fine tune to improve the performance of the storage and virtual infrastructure. Before this, the initial deployment was done by default configuration without any fine tune yet, and I found that the storage performance looks  little bit slow. Therefore, I had decided to further research and fine tune everything we had to improve the <a href="http://www.malaysiavm.com/blog/tag/performance">performance</a>.</p>
<p>Equipment List</p>
<ol>
<li>2 x <a href="http://www.malaysiavm.com/blog/tag/r710">R710</a> with Intel 5530</li>
<li>2 x <a href="http://www.malaysiavm.com/blog/tag/powerconnect">PowerConnect</a> 5424</li>
<li>MD3000i with 15 <a href="http://www.malaysiavm.com/blog/tag/sata">SATA</a> Disks</li>
<li>Software <a href="http://www.malaysiavm.com/blog/tag/iscsi">ISCSI</a> initiator from vSphere 4</li>
</ol>
<p><span id="more-1314"></span>I was impressed with the functionality of the <a href="http://www.malaysiavm.com/blog/tag/dell">Dell</a> PowerConnect switch which provide the important features as link aggregation, jumbo frames, ISCSI optimization and etc. Here is what I did. I had enable the <a href="http://www.malaysiavm.com/blog/tag/jumboframe">jumbo frame</a> on the specify port that connected for the storage and ISCSI connectiones. At the same time, I had also turned on the <a href="http://www.malaysiavm.com/blog/tag/mtu">MTU</a> configuration and jumbo frame setting from the MD3000i management console. You may need to repeat the same action for every data ports that provided by the storage controller on MD3000i. Enable the Jumbo frame and configure the MTU value of 9000 on it. On the PowerConnect switch,I had configured the specify ports on ISCSI optimization and jumbo frames enable. Now it come to the vSphere level, which I had to manually enable the ISCSI vswitch to support the jumbo frame and put in the right value for the MTU.</p>
<p>Command for reference</p>
<p>#esxcfg-vswitch -l    <br />
This will allow you to list all the virtual switch you have on the ESX server</p>
<p>#esxcfg-vswitch -m 9000 vswitch1  <br />
this command is to enable the mtu value of 9000 for every nics that connected to the same virtual <a href="http://www.malaysiavm.com/blog/tag/switch">switch</a> which provide the storage access to ISCSI</p>
<p>#vmkping -s 9000 192.x.x.x   <br />
test the jumbo frame setting</p>
<p>The outcome of the jumbo frame enable, I had able to achieve higher throughput on the <a href="http://www.malaysiavm.com/blog/tag/md3000i">MD3000i</a> I had and I am happy with the performance of the storage.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/performance-tuning-on-virtual-infrastructure-with-md3000i/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>FC NFS ISCSI</title>
		<link>http://malaysiavm.com/blog/fc-nfs-iscsi/</link>
		<comments>http://malaysiavm.com/blog/fc-nfs-iscsi/#comments</comments>
		<pubDate>Mon, 05 Jan 2009 03:29:26 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[FC]]></category>
		<category><![CDATA[Fiber Channel]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[netapps]]></category>
		<category><![CDATA[nfs]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=752</guid>
		<description><![CDATA[There had been numbers of review and discussion regarding the choices of storage for us to run on Virtual Environment today. I believed that the hot discussion is always moving talk about the right storage with right design and implementation to the VM farm always. The most hottest topic are still regarding the NFS, ISCSI [...]]]></description>
			<content:encoded><![CDATA[<p>There had been numbers of review and discussion regarding the choices of storage for us to run on Virtual Environment today. I believed that the hot discussion is always moving talk about the right storage with right design and implementation to the VM farm always. The most hottest topic are still regarding the <a href="http://malaysiavm.com/blog/tag/nfs">NFS</a>, <a href="http://malaysiavm.com/blog/tag/iscsi">ISCSI</a> and <a href="http://malaysiavm.com/blog/tag/fc">FC</a> implementation which provide better features, performance and reliability.</p>
<p>Personally, I had 3 of it running in my environment now and of course, I had spent a huge number of times to really test out all the solution and compare apple to apple to further study of my requirement. Here are some reading I get from my test for 3 solution above.</p>
<p><span id="more-752"></span></p>
<p>For I/O performance, I am using the <a href="http://malaysiavm.com/blog/tag/io">IO</a> meter as to generate the max output to the storage. I manage to get 190MB/s for my FC storage on 100 % read, and I only managed to get the output of 170MB/s on ISCSI, but on NFS, I only managed to get at 125MB/s. If we look at the number here, and compare to my high load <a href="http://www.malaysiavm.com/blog/tag/r900">R900</a> ESX host, actually it is more than enough to handle the number of <a href="http://www.malaysiavm.com/blog/tag/vm">VM</a> I have in the ESX host. There are a lot of article introduce NFS, and the features of Netapps, but remember, <a href="http://www.malaysiavm.com/blog/tag/esx">ESX</a> itself had improved from time to time. Thin Provisioning is no longer new thing, as you may get it with many vendor today by free as well as volume snap. But Dedupe will still be an interesting technology in netapps. If we look at FC, you will mostly lose all this technology, but it provide a stable performance as you need to virtualize some heavy environment moving forward. I am currently still test out the storage solution before I decide to go with a final choice. I will suggest to keep an eye on the technology trend as we may also remember that the <a href="http://www.malaysiavm.com/blog/tag/vmware">VMware</a> <a href="http://www.malaysiavm.com/blog/tag/esx4">ESX 4</a> is on the way, which may change the game of storage strategy significantly.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/fc-nfs-iscsi/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>DELL Equallogic PS5500E Auto Snapshot Manager</title>
		<link>http://malaysiavm.com/blog/dell-equallogic-ps5500e-provide-auto-snapshot-manager-for-vmware/</link>
		<comments>http://malaysiavm.com/blog/dell-equallogic-ps5500e-provide-auto-snapshot-manager-for-vmware/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 16:30:13 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[10Ge]]></category>
		<category><![CDATA[array]]></category>
		<category><![CDATA[Dell]]></category>
		<category><![CDATA[Equallogic]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[PS5500E]]></category>
		<category><![CDATA[SAN]]></category>
		<category><![CDATA[sata]]></category>
		<category><![CDATA[Snapshot Manager]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=563</guid>
		<description><![CDATA[The latest version of ISCSI SAN Equallogic PS 5500E which launched recently had provide better capacity, performance, extra functionalities and more spindles in arrays. It could be support both 500GB and 1TB SATA II spindles up to 48 drives in a single array of 4U. A very impress usable storage space in single array which [...]]]></description>
			<content:encoded><![CDATA[<p>The latest version of ISCSI SAN Equallogic PS 5500E which launched recently had provide better capacity, performance, extra functionalities and more spindles in arrays. It could be support both 500GB and 1TB <a href="http://malaysiavm.com/blog/tag/sata">SATA</a> II spindles up to 48 drives in a single array of 4U. A very impress usable storage space in single array which up to 48TB in <a href="http://malaysiavm.com/blog/tag/raw">raw</a>. If we compare to the capacity, it is hardly found that a single array would provide a huge capacity at 48TB in Raw today. In additional to that, <a href="http://malaysiavm.com/blog/tag/dell">DELL</a> had provide all the necessary features as for storage management as free which integrated as part of the storage purchase for Dell Equallogic <a href="http://malaysiavm.com/blog/tag/iscsi">ISCSI</a> <a href="http://malaysiavm.com/blog/tag/san">SAN</a>. The latest features is regarding the Snapshot Manager for VMware. Previous version is only supported on Microsoft environment, but now, it had also supported on <a href="http://malaysiavm.com/blog/tag/vmware">VMWare</a> environment.</p>
<p><span id="more-563"></span></p>
<p>This features provide more option which will allow the users to snapshot, backup, and restore the files, volume, VM or even a single file that you need. Many of us may think about using the VCB for our VM backup today, the Dell <a href="http://malaysiavm.com/blog/tag/equalogic">Equallogic</a> had provide some interesting package which allow us to avoid of <a href="http://malaysiavm.com/blog/tag/vcb">VCB</a> in our environment, and provide better backup and restoration process.</p>
<p>If we talk about disk base backup, which is VTL, it always cost involve in term of disk space and software licenses. With the latest features from <a href="http://malaysiavm.com/blog/tag/equallogic">Equallogic</a>, we will able to avoid the extra investment require on VTL, but provide the similar functionalities on disk base backup, and from disk to tape backup. If I bought the equallogic previously and sign up with the maintenance, I entitle the upgrade of the new features today. It will be a excellent surprise for my investment. As economy crisis, <a href="http://malaysiavm.com/blog/tag/it">IT</a> budget is been tight and require to work smarter, this should be a great news for the consumers. Personally, I will still say that the 10Gbe will be my option as to get rid of the fiber channel storage that we current use for <a href="http://malaysiavm.com/blog/tag/vmware">VMware</a>. As 48 spindles in a single array, we may need the bigger through put from the array to reach the client always.</p>
<p>According to <a href="http://malaysiavm.com/blog/tag/dell">DELL</a>, we should able to see the official launch on 10Gbe on 1st quater of 2009.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/dell-equallogic-ps5500e-provide-auto-snapshot-manager-for-vmware/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Storage Planning &#8211; Virtualization</title>
		<link>http://malaysiavm.com/blog/storage-planning-virtualization/</link>
		<comments>http://malaysiavm.com/blog/storage-planning-virtualization/#comments</comments>
		<pubDate>Wed, 10 Sep 2008 05:35:47 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[datacenter]]></category>
		<category><![CDATA[EMC]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[ISCSI]]></category>
		<category><![CDATA[netapps]]></category>
		<category><![CDATA[nfs]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=246</guid>
		<description><![CDATA[Storage is always the important piece to be run in Data center as well as any solutions we put into the production environment. It will also impact the capacity planning, performance as well as the sustainable period of the specify solution. Here I would like to specify talk about ESX storage planning. As many of [...]]]></description>
			<content:encoded><![CDATA[<p>Storage is always the important piece to be run in <a href="http://malaysiavm.com/blog/tag/datacenter">Data center</a> as well as any solutions we put into the production environment. It will also impact the capacity planning, performance as well as the sustainable period of the specify solution.</p>
<p>Here I would like to specify talk about <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> storage planning. As many of the cases I read and experience before, more and more users are really heading to the stage of choosing specify storage for specify solutions. Example you may think off for using <a href="http://malaysiavm.com/blog/tag/netapps">Netapps</a> on <a href="http://malaysiavm.com/blog/tag/nfs">NFS</a> for ESX, which claim better performance, dedupe and protocol different. Somehow, the users had forgotten that they had not run any of netapps storage in their existing environment. When we look at the management perspective, the operation management for IT support is not SIMPLIFY. Everyone know how important to standardize our environment as well as simplify out IT environment. The more complex you have, the more pain you will feel.</p>
<p><span id="more-246"></span><br />
<a href="http://malaysiavm.com/blog/tag/esx">ESX</a> had been design to run on multiple different range, different brand, as well as different type of protocol of storage in the market today. The reason of this is able to provide users a number of choices to be choose for deployment which may really fit the existing environment. Most users are now been looking at the storage specifically for Virtualization, that was really due to the marketing strategy or brochure been always claim the specify products will gain better performance. If you are the storage guys in your IT department, maybe you should consider what will be the best fit for your environment VS what is the coolest technology in the world for VMware.</p>
<p>Let talk about 1 scenario here, a user who had existing running with cx3-80 <a href="http://malaysiavm.com/blog/tag/emc">EMC</a> SAN storage with all fiber switches ready. The storage is only 50% populated. The storage guys had raised the request to bring in the latest ISCSI technology from netapps and Equal logic. When it does the price comparison, the TCO and implementation cost of ISCSI become too huge different VS extending the enclosure on cx3-80. Back to real world, I am really curious that if <a href="http://malaysiavm.com/blog/tag/san">SAN</a> Fiber storage will be poor perform and inconsistent compare to ISCSI if you have everything setup and configure correctly in your fiber SAN. Most of the case is NO. As in my POC test, I can see that the performances on the Fiber are still better and stable.</p>
<p><a href="http://malaysiavm.com/blog/tag/iscsi">ISCSI</a> is really simple and easier manage, but somehow, there are many technical details that require redeploying the entire environment to gain the peak performance you expected. That is definitely an advice at the end you will get from the vendor. Therefore, a best fit storage for your own environment is more important always. You should look at CAPEX vs OPEX when you plan the storage for virtualization.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/storage-planning-virtualization/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.428 seconds -->

