<?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; FCoE</title>
	<atom:link href="http://malaysiavm.com/blog/tag/fcoe/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Thu, 26 Apr 2012 15:54:26 +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>UCS Firmware 1.4 support FCoE Direct Attach SAN</title>
		<link>http://malaysiavm.com/blog/ucs-firmware-1-4-support-fcoe-direct-attach-san/</link>
		<comments>http://malaysiavm.com/blog/ucs-firmware-1-4-support-fcoe-direct-attach-san/#comments</comments>
		<pubDate>Sun, 13 Mar 2011 15:00:42 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[EMC]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[Netapp]]></category>
		<category><![CDATA[SAN]]></category>
		<category><![CDATA[ucs]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=2218</guid>
		<description><![CDATA[If you are following Cisco Unified computing solution, here is some good news. The latest firmware version 1.4 is officially support direct attach FCoE Storage protocol without require the additional SAN switch as previous version. Both Netapp and EMC are officially supported and certified to direct attach with the Cisco UCS without a SAN switch [...]]]></description>
			<content:encoded><![CDATA[<p>If you are following Cisco Unified computing solution, here is some good news. The latest firmware version 1.4 is officially support direct attach FCoE Storage protocol without require the additional SAN switch as previous version. Both Netapp and EMC are officially supported and certified to direct attach with the Cisco UCS without a SAN switch require. This will reduce the complex layer it require to deploy especially for those environment who are not FC users previously.</p>
<p>I found some very good post over the internet, you can refer the URL below for more information about the new update provided in Firmware 1.4</p>
<p><a href="http://www.unifiedcomputingblog.com/?p=187">Unified Computing Blog</a><br />
<a href="http://www.mseanmcgee.com/2010/12/cisco%E2%80%99s-stocking-stuffer-for-ucs-customers-firmware-release-1-41/"><br />
M. Sean McGee</a></p>
<p><span id="more-2218"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/ucs-firmware-1-4-support-fcoe-direct-attach-san/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FCoE VLAN and FC Uplinks in Cisco UCS Architecture</title>
		<link>http://malaysiavm.com/blog/fcoe-vlan-and-fc-uplinks-in-cisco-ucs-architecture/</link>
		<comments>http://malaysiavm.com/blog/fcoe-vlan-and-fc-uplinks-in-cisco-ucs-architecture/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 14:18:08 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Cisco UCS]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[Fiber Channel]]></category>
		<category><![CDATA[MDS]]></category>
		<category><![CDATA[Nexus 5000]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1821</guid>
		<description><![CDATA[Today I found some interesting technical details during my installation of Cisco UCS for the client. FCoE architecture are slightly different when you decide to uplink the FCoE traffic end to end to the Cisco Nexus 5000 unified fabric, or you are doing the FC uplink directly from the UCS 6120 to the MDS or [...]]]></description>
			<content:encoded><![CDATA[<p>Today I found some interesting technical details during my installation of Cisco UCS for the client. FCoE architecture are slightly different when you decide to uplink the FCoE traffic end to end to the Cisco Nexus 5000 unified fabric, or you are doing the FC uplink directly from the UCS 6120 to the MDS or SAN fabric switches. I went through the documentation and my previous round of installation, we were actually configure the LAN &amp; SAN uplink from UCS 6120 to Nexus 5k. Therefore, in our configuration, we required to have specified FCoE VLAN which carry the FCoE traffic to reach the storage through Nexus 5000. Today, I implemented the similar configuration, but the different was the uplink configuration.</p>
<p>This new setup are included with 10 G Ethernet uplink from UCS 6120 to Catalyst 6509 through Fiber, and utilizing FC Uplinks from UCS 6120 to MDS 9124. In my test, I removed the VLAN that I created purposely for FCoE, and found that there are no impact to the configuration.  I had confirmed with the support guys that if you are doing an uplink with FC from UCS 6100 to MDS, you will not require to tag the specified VLAN that created for the VSAN in the configuration.</p>
<p><span id="more-1821"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/fcoe-vlan-and-fc-uplinks-in-cisco-ucs-architecture/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Unified Computing System with Unified Storage</title>
		<link>http://malaysiavm.com/blog/unified-computing-system-with-unified-storage/</link>
		<comments>http://malaysiavm.com/blog/unified-computing-system-with-unified-storage/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 17:03:37 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[EMC]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[Netapp]]></category>
		<category><![CDATA[ucs]]></category>
		<category><![CDATA[Unified]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1775</guid>
		<description><![CDATA[Unified had become a key word today, and what does it really meant for everyone? It is similar as the phenomenal Cloud Computing 2 years ago.  We had seen the storage vendor are moving from FC SAN, ISCSI SAN, NAS to a unified storage today. What a unified storage does today are providing all the [...]]]></description>
			<content:encoded><![CDATA[<p>Unified had become a key word today, and what does it really meant for everyone? It is similar as the phenomenal Cloud Computing 2 years ago.  We had seen the storage vendor are moving from FC SAN, ISCSI <a href="http://malaysiavm.com/blog/tag/san">SAN</a>, NAS to a unified storage today. What a unified storage does today are providing all the storage protocol standard in the market in a single box. Vendor such as EMC and Netapp had their Unified storage to support this today and proven to be performing and user are happy with it.</p>
<p>Beside unified storage, we are looking forward for unified computing system for the server compute platform too. <a href="http://malaysiavm.com/blog/tag/cisco">Cisco</a> had moved ahead of their competitor to bring this to the world and it is 1 fo the great platform that get attraction and adoption worldwide. Cisco UCS or Nexus 5000 both provide the unified I/O capabilities and allow us to transform the data center architecture today. Beside consolidating LAN and SAN into 1 with FCoE, the more interesting capabilities that get attention by us are the switching capacity.</p>
<p><span id="more-1775"></span>The Nexus 5000 or <a href="http://malaysiavm.com/blog/tag/ucs">UCS</a> 6140 switches supported up to 1.14 Tbits/s and this number are more than enough to consolidate all the necessary traffic it need to be delivered by the LAN &amp; SAN. If you have this solution in place today and well integrated with the unified storage as well as the core networking environment, you can easily choose to run NAS, ISCSI or <a href="http://malaysiavm.com/blog/tag/fc">FC</a> through the same Unified frabics and Unified Storage you have. As everyone know, there are no perfect solution or protocol for every scenario, but now, you will able to choose the right protocol for every different computing system, application and database requirement without implementing separate ISCSI, NFS or FC physical infrastructure.</p>
<p><a href="http://malaysiavm.com/blog/wp-content/uploads/2010/01/unified-300x225.jpg" rel="shadowbox[sbpost-1775];player=img;"><img src="http://malaysiavm.com/blog/wp-content/uploads/2010/01/unified-300x225.jpg" alt="UCS" /></a></p>
<p>This is a nice picture to summarize the description about Unified Platform which I get it from http://viewyonder.com</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/unified-computing-system-with-unified-storage/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Simplify Setup and Configuration for Cisco UCS vs Traditional Blade</title>
		<link>http://malaysiavm.com/blog/simplify-setup-and-configuration-for-cisco-ucs-vs-traditional-blade/</link>
		<comments>http://malaysiavm.com/blog/simplify-setup-and-configuration-for-cisco-ucs-vs-traditional-blade/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 16:51:44 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Blade]]></category>
		<category><![CDATA[Cisco UCS]]></category>
		<category><![CDATA[FCoE]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1765</guid>
		<description><![CDATA[I was tighted up with the cloud computing event we run in KL and Penang last week. It also the 1st time that the Cisco UCS showcase to the public in our event. Of course the demo and staging unit were setup by myself with my close buddy from Cisco Malaysia. The 1st time I [...]]]></description>
			<content:encoded><![CDATA[<p>I was tighted up with the cloud computing event we run in KL and Penang last week. It also the 1st time that the Cisco UCS showcase to the public in our event. Of course the demo and staging unit were setup by myself with my close buddy from Cisco Malaysia. The 1st time I unpacked and setup the box, it really surprised myself because it does not require special skillsets to understand too much about the architecture. Of course, I did went for a 4 days boot camp previously for Cisco UCS, but they did not show us step by step to setup and configure the UCS box from scratch. Anyway, to setup the UCS 6120 HA cluster, it take me less than 8 mins from the console CLI. I will suggest anyone of you who are preparing to setup this Cisco UCS, to have the Serial to USB converter ready as most of the business laptop today will not support serial ports. It require console connection to both unit of UCS 6120 for the 1st time to enable the UCS Switching cluster. Once is done, you can access the UCS Manager with the right virtual IP you had enabled in the UCS switch cluster.</p>
<p><span id="more-1765"></span>Once I unpacked the UCS Chassis from the box, it took me  less than 10 mins to slot in 5 units of the B200M1 with 48GB Memory , 2x Intel 5540 and 2 x 146 SAS Local HDD each. At the same time, I did try to open up the casing for 1 of the blade,. it took me less than 1 min to do so. Came to the cabling part, usually we spent a lot of effort for cable management on Gigabits Ethernet and FC cabling, for Cisco UCS, maximum 8 cables per chassis for IO uplink. Of course, I do not require to over provision in this case, I managed to connect 4 FCoE connections from the chassis to the UCS 6120 Cluster for demo purpose and it is more than enough to handle the IO requirement for the showcase.</p>
<p>Well, when I move the box from my office to 2 different location in my country for event, it take me less than 1 hour to re-setup everything and boot up all the physical and virtual machine within the Cisco UCS.  It is really a great design to simplify a hardware setup and configuration. Guess what, I do have different engineer who are non server background that help me to re-setup and they were impressed with the design and took less than 5 mins to understand the architecture after my explanation.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/simplify-setup-and-configuration-for-cisco-ucs-vs-traditional-blade/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FCoE End to End Solution with Cisco Nexus 5000 and Netapp Storage</title>
		<link>http://malaysiavm.com/blog/fcoe-end-to-end-solution-with-cisco-nexus-5000-and-netapp-storage/</link>
		<comments>http://malaysiavm.com/blog/fcoe-end-to-end-solution-with-cisco-nexus-5000-and-netapp-storage/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 16:21:11 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[FAS3140]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[Netapp]]></category>
		<category><![CDATA[Nexus 5000]]></category>
		<category><![CDATA[ucs]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1585</guid>
		<description><![CDATA[FCoE will be the next trend for most users to be adopted. Previous post I had explain about the high level architecture from Cisco UCS. Here I will describe the FCoE end to end solution which is slightly different with the UCS architecture. Please note that both architecture is similar but it does not same [...]]]></description>
			<content:encoded><![CDATA[<p>FCoE will be the next trend for most users to be adopted. Previous post I had explain about the high level architecture from Cisco UCS. Here I will describe the FCoE end to end solution which is slightly different with the UCS architecture. Please note that both architecture is similar but it does not same to each others.</p>
<p><img class="aligncenter size-medium wp-image-1587" title="fcoe2" src="http://malaysiavm.com/blog/wp-content/uploads/2009/10/fcoe2-254x300.jpg" alt="fcoe2" width="441" height="520" /></p>
<p><span id="more-1585"></span></p>
<p>Each server above will be connected to Nexus 5000 through CNA (Converge Network Adaptor) which provide FCoE and 10GE at the single connection. The Netapp FAS 3140 are connected to Nexus 5000 with FCoE interfaces which provide end to end solution from servers to switches, switches to storage. FC switch are not required to be in placed to allow servers communication to storage in this architecture. You can choose either NFS, FCoE or ISCSI in this configuration. The above picture is for reference and do not meant in very details as I am rush up the drawing about this post. EMC will soon officially launch the storage to support FCoE. I believe this will be the future strategy for Data Center &amp; Storage solution. In Cisco UCS, you will still require FC switch in place as the UCS 6100 interconnect does not meant the full capable FCoE switch as Nexus 5000 did. I think the new architecture are suitable for new and clean deployment and large scale virtualization. It help to reduce the massive cabling, and achieve the throughput requirements needed by the virtualization.</p>
<p><img class="aligncenter size-medium wp-image-1590" title="fcoe3" src="http://malaysiavm.com/blog/wp-content/uploads/2009/10/fcoe3-300x106.jpg" alt="fcoe3" width="519" height="182" /></p>
<p>Picture above is Traditional Network and SAN environment VS FCoE for reference purpose</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/fcoe-end-to-end-solution-with-cisco-nexus-5000-and-netapp-storage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>High Level Cisco UCS architecture</title>
		<link>http://malaysiavm.com/blog/high-level-cisco-ucs-architecture/</link>
		<comments>http://malaysiavm.com/blog/high-level-cisco-ucs-architecture/#comments</comments>
		<pubDate>Mon, 28 Sep 2009 12:45:39 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[ucs]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1579</guid>
		<description><![CDATA[As the picture show above, it is the high level architecture which requires to run the entire UCS solution from Cisco. Not necessary every environment will require Nexus 7000, it is meant for large scale networking environment. You may go with various different switches to replace the Nexus 7000 in the picture depend on your [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-medium wp-image-1580" title="UCS1" src="http://malaysiavm.com/blog/wp-content/uploads/2009/09/UCS1-300x206.jpg" alt="UCS1" width="451" height="308" /></p>
<p>As the picture show above, it is the high level architecture which requires to run the entire UCS solution from Cisco. Not necessary every environment will require Nexus 7000, it is meant for large scale networking environment. You may go with various different switches to replace the Nexus 7000 in the picture depend on your requirement. In the current UCS release, the UCS 6100 interconnect fabric will integrate with the MDS 9000 series Fiber Channel environment or others compatible FC switches. This allow UCS blade I/O to be consolidated with CNA with 10Gbps per connection as FCoE.  This had significant reduce the physical cabling requirement per blade chassis.</p>
<p><span id="more-1579"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/high-level-cisco-ucs-architecture/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Server Virtualization &amp; Cloud Computing Model</title>
		<link>http://malaysiavm.com/blog/server-virtualization-cloud-computing/</link>
		<comments>http://malaysiavm.com/blog/server-virtualization-cloud-computing/#comments</comments>
		<pubDate>Sat, 26 Sep 2009 15:00:08 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[cloud computing]]></category>
		<category><![CDATA[FCoE]]></category>
		<category><![CDATA[Infiniband]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Xsigo]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1571</guid>
		<description><![CDATA[What will be the next after the server virtualization with any hypervisor in the market today? Everyone may has a different thought about it when they went through the journey with different experiences. VMware are very focus on the future of cloud and we also notice there are more cloud providers in the market to [...]]]></description>
			<content:encoded><![CDATA[<p>What will be the next after the server virtualization with any hypervisor in the market today? Everyone may has a different thought about it when they went through the journey with different experiences. VMware are very focus on the future of cloud and we also notice there are more cloud providers in the market to provide the cloud services to everyone around the world. But it does not convince enough for the enterprise environment to go for public or hybrid cloud at the moment. Private cloud are always considerable for most enterprise environment.</p>
<p>Is virtualization meant everything? Virtualization is not, but it had played the important role in the entire journey. Everyone may had faced different challenges during or after the server virtualization in the data center. The next thing which prompt up after server virtualization will often be I/O virtualization and utility computing model. I/O had become real challenges as server virtualization had increased the total bandwidth require to be allocated per physical servers which may easily contains 30 virtual machines in 1 single server. At the mean time, we often see the FC, ISCSI and NAS are seperated with the Ethernet LAN in data center.  Can we do it better? my answer is Definitely. Plenty of solutions today such as Xsigo or Cisco Nexus are really ready to address the challenges that everyone is facing today through Infiniband or FCoE.</p>
<p><span id="more-1571"></span></p>
<p>FCoE had become an open standard as Qlogic, Emulex, Brocade and Cisco are officially supported today. Do we require to have multiple SAN cablings and Ethernet gigabits connected to each physical server? I will say Yes or No. For 90% of the environment, it should be the right thing to combine both FC and Ethernet into 1. I/O consolidation allowed everyone to simplify the data center environment and improve the bandwidth per connection from 1Gbps to 10Gbps for Ethernet and FC both. It help us to virtualize and simplify the I/O management within the data center.</p>
<p>Leave the technology away now, and look at the operation structure. How do we benefit from virtualization or private cloud computing? Virtualization had made a big move for many environments to go for the private cloud computing model. As my personal experience and the proven success in the past, the biggest benefit I had experienced was the way it transform the IT Services delivery. It had allowed everyone to work closely and demonstrated a better team work and understanding to delivery the right infrastructure for the business needs. Back to the traditional situation, the virtualization implementation team will have to deal with storage team, server team, application team, DBA, Network folks and others IT personnel within the organization, which require a long journey to kick off the virtualization project. We always noticed that for each individual functional team will have different standards, opinions and road maps for specified technology. We understood that standardization is always important, but it will require to further fine tune when it come to the virtualization, cloud computing and data center transformation era.</p>
<p>The collabration within each IT functional team had been improved due to the virtualization and cloud computing.  Everyone started to learn or understand about both virtualization and cloud computing. Infrastructures and solutions build today are always collaborate and align within different functional team to achieve the company goal. Is there a threat for server, network and storage guys due to virtualization and cloud computing? I will say NO, but it does help to improve the relation within the team and allow them to learn from each others. A pure networking background IT folk had known more about storage and servers technology because virtualization.</p>
<p><img class="aligncenter size-medium wp-image-1572" title="example" src="http://malaysiavm.com/blog/wp-content/uploads/2009/09/example-300x238.jpg" alt="example" width="300" height="238" /></p>
<p>This picture had explained the relationship within the IT solutions. With the changes happen today, it allow IT to do more with less. It does simplify the IT infrastructure  and improve the services delivery.</p>
<p><img class="aligncenter size-medium wp-image-1573" title="example1" src="http://malaysiavm.com/blog/wp-content/uploads/2009/09/example1-300x187.jpg" alt="example1" width="300" height="187" /></p>
<p>This picture is a good reference which allow us to understand where are we now.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/server-virtualization-cloud-computing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>
	</channel>
</rss>

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

