<?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>Blades Made Simple™ &#187; UCS 6100</title>
	<atom:link href="http://bladesmadesimple.com/tag/ucs-6100/feed/" rel="self" type="application/rss+xml" />
	<link>http://bladesmadesimple.com</link>
	<description>Making blade servers simple</description>
	<lastBuildDate>Tue, 15 May 2012 11:18:05 +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>Cisco&#039;s UCS Software</title>
		<link>http://bladesmadesimple.com/2009/10/ciscos-ucs-software/</link>
		<comments>http://bladesmadesimple.com/2009/10/ciscos-ucs-software/#comments</comments>
		<pubDate>Fri, 09 Oct 2009 18:38:17 +0000</pubDate>
		<dc:creator>Kevin Houston</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[eWeek]]></category>
		<category><![CDATA[UCS]]></category>
		<category><![CDATA[UCS 5108]]></category>
		<category><![CDATA[UCS 6100]]></category>
		<category><![CDATA[Unified Computing System]]></category>

		<guid isPermaLink="false">http://kevinbladeguy.wordpress.com/?p=62</guid>
		<description><![CDATA[eWeek recently posted snapshots of Cisco&#8217;s Unified Computing System (UCS) Software on their site: http://www.eweek.com/c/a/IT-Infrastructure/LABS-GALLERY-Cisco-UCS-Unified-Computing-System-Software-199462/?kc=rss Take a good look at the software because the software is the reason this blade system will be successful because they are treating the physical blades as a resource &#8211; just CPUs, memory and I/O.  &#8220;What&#8221; the server should be [...]]]></description>
			<content:encoded><![CDATA[
<div class="topsy_widget_data topsy_theme_blue" style="float: right;margin-left: 0.75em; background: url(data:,%7B%20%22url%22%3A%20%22http%253A%252F%252Fbladesmadesimple.com%252F2009%252F10%252Fciscos-ucs-software%252F%22%2C%20%22style%22%3A%20%22big%22%2C%20%22title%22%3A%20%22Cisco%26%23039%3Bs%20UCS%20Software%20%23Cisco%20%23eWeek%20%23UCS%20%23UCS%205108%20%23UCS%206100%20%23Unified%20Computing%20System%22%20%7D);"></div>
<p>eWeek recently posted snapshots of Cisco&#8217;s Unified Computing System (UCS) Software on their site: <a href="http://www.eweek.com/c/a/IT-Infrastructure/LABS-GALLERY-Cisco-UCS-Unified-Computing-System-Software-199462/?kc=rss" target="_blank">http://www.eweek.com/c/a/IT-Infrastructure/LABS-GALLERY-Cisco-UCS-Unified-Computing-System-Software-199462/?kc=rss</a></p>
<p>Take a good look at the software because the software <strong>is the reason this blade system will be successful</strong> because they are treating the physical blades as a resource &#8211; just CPUs, memory and I/O.  &#8220;What&#8221; the server should be and &#8220;How&#8221; the server should act is a feature of the UCS Management software.  It will show you the physical layout of the blades to the <a href="http://kevinbladeguy.wordpress.com/2009/09/23/cisco-ucs-vs-ibm-bladecenter-h/" target="_blank">UCS 6100 Interconnect</a>, it can show you the configurations of the blades in the attached UCS 5108 chassis, it can set the boot order of the blades, etc.  Quite frankly there are too many features to mention and I don&#8217;t want to steal their fire, so take a few minutes to go to:  <a href="http://www.eweek.com/c/a/IT-Infrastructure/LABS-GALLERY-Cisco-UCS-Unified-Computing-System-Software-199462/?kc=rss" target="_blank">http://www.eweek.com/c/a/IT-Infrastructure/LABS-GALLERY-Cisco-UCS-Unified-Computing-System-Software-199462/?kc=rss</a>.</p>

]]></content:encoded>
			<wfw:commentRss>http://bladesmadesimple.com/2009/10/ciscos-ucs-software/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

