<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Cisco UCS Networking Best Practices (in HD)</title>
	<atom:link href="http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/</link>
	<description>Studies in Data Center Networking, Virtualization, Computing</description>
	<lastBuildDate>Sat, 04 Feb 2012 19:38:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: William Fleitz</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-8247</link>
		<dc:creator>William Fleitz</dc:creator>
		<pubDate>Thu, 20 Oct 2011 22:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-8247</guid>
		<description>Brad, Excellent presentation. I have a quick question perhaps you or someone else can answer. My server team wants to connect a VMotion switch to the UCS so that we can Vmotion legacy VM servers to the UCS ESX farm. I’m wondering what is the best practice to accomplish this? It would need to be accessible across both 6100s. Thanks!</description>
		<content:encoded><![CDATA[<p>Brad, Excellent presentation. I have a quick question perhaps you or someone else can answer. My server team wants to connect a VMotion switch to the UCS so that we can Vmotion legacy VM servers to the UCS ESX farm. I’m wondering what is the best practice to accomplish this? It would need to be accessible across both 6100s. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Praveen</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-6881</link>
		<dc:creator>Praveen</dc:creator>
		<pubDate>Mon, 16 May 2011 12:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-6881</guid>
		<description>Hi  ,

Awesome information!!!

I am designing a Network where we need to connect the 6120Xp Fabric extender to Catalyst 6509 . I found that we can connect the fabric Interconnect (FI) to 1G port of an uplink switch using   The first 8 fixed ports can be configured to operate in 1 Gigabit Ethernet mode with the transceiver options specified for use with SFP-compatible ports using 1000BASE-T SFP GLC- 

Since I have 2Nos 6509 Switches in the Datacentre I can connect only 4 Ports from 6120XP to each of 650. Can I configure channel from 6120Xp to 6509 between these 4 links?

Thanks and Regards
Praveen</description>
		<content:encoded><![CDATA[<p>Hi  ,</p>
<p>Awesome information!!!</p>
<p>I am designing a Network where we need to connect the 6120Xp Fabric extender to Catalyst 6509 . I found that we can connect the fabric Interconnect (FI) to 1G port of an uplink switch using   The first 8 fixed ports can be configured to operate in 1 Gigabit Ethernet mode with the transceiver options specified for use with SFP-compatible ports using 1000BASE-T SFP GLC- </p>
<p>Since I have 2Nos 6509 Switches in the Datacentre I can connect only 4 Ports from 6120XP to each of 650. Can I configure channel from 6120Xp to 6509 between these 4 links?</p>
<p>Thanks and Regards<br />
Praveen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Wilkinson</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-6458</link>
		<dc:creator>Alex Wilkinson</dc:creator>
		<pubDate>Fri, 15 Apr 2011 11:51:23 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-6458</guid>
		<description>Pure Gold! Thank you for providing this for the community!

    -Alex</description>
		<content:encoded><![CDATA[<p>Pure Gold! Thank you for providing this for the community!</p>
<p>    -Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Hedlund</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-5743</link>
		<dc:creator>Brad Hedlund</dc:creator>
		<pubDate>Tue, 01 Mar 2011 01:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-5743</guid>
		<description>Brad,
To partition BW for iSCSI, you can keep UCS in End Host mode, use a LAN Pin Group and call it &quot;iSCSI&quot; or something.  Pick the uplink you want dedicated for iSCSI traffic and put it in your iSCSI Pin Group.  Take the vNICs used for iSCSI and assign them to the &quot;iSCSI&quot; LAN Pin Group.

-Brad</description>
		<content:encoded><![CDATA[<p>Brad,<br />
To partition BW for iSCSI, you can keep UCS in End Host mode, use a LAN Pin Group and call it &#8220;iSCSI&#8221; or something.  Pick the uplink you want dedicated for iSCSI traffic and put it in your iSCSI Pin Group.  Take the vNICs used for iSCSI and assign them to the &#8220;iSCSI&#8221; LAN Pin Group.</p>
<p>-Brad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Hedlund</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-5739</link>
		<dc:creator>Brad Hedlund</dc:creator>
		<pubDate>Tue, 01 Mar 2011 00:43:12 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-5739</guid>
		<description>Leo,
No - static pinning will not work.  The FI will still only pick one uplink as the broadcast listener.  That&#039;s the case for UCSM version 1.4 or older.  

In the next release of UCSM, End Host Mode will be enhanced to support separate upstream L2 domains.  

Cheers,
Brad</description>
		<content:encoded><![CDATA[<p>Leo,<br />
No &#8211; static pinning will not work.  The FI will still only pick one uplink as the broadcast listener.  That&#8217;s the case for UCSM version 1.4 or older.  </p>
<p>In the next release of UCSM, End Host Mode will be enhanced to support separate upstream L2 domains.  </p>
<p>Cheers,<br />
Brad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leo</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-5735</link>
		<dc:creator>Leo</dc:creator>
		<pubDate>Mon, 28 Feb 2011 20:14:15 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-5735</guid>
		<description>Hello,

one question regarding connecting a UCS to two or more L2 domains: To avoid switching the fabric interconnects to switch mode, would it be feasible / recommended to build several vPC Channels and pin the vNICS manually to these channels?

__Leo</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>one question regarding connecting a UCS to two or more L2 domains: To avoid switching the fabric interconnects to switch mode, would it be feasible / recommended to build several vPC Channels and pin the vNICS manually to these channels?</p>
<p>__Leo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Hedlund</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-5560</link>
		<dc:creator>Brad Hedlund</dc:creator>
		<pubDate>Wed, 16 Feb 2011 03:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-5560</guid>
		<description>Vijay,
The unknown dest MAC received from the server will be forwarded on the pinned uplink only.  No flooding.
-Brad</description>
		<content:encoded><![CDATA[<p>Vijay,<br />
The unknown dest MAC received from the server will be forwarded on the pinned uplink only.  No flooding.<br />
-Brad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VIJAY SHEKHAR</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-5559</link>
		<dc:creator>VIJAY SHEKHAR</dc:creator>
		<pubDate>Wed, 16 Feb 2011 03:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-5559</guid>
		<description>Great work Brad!! really!

I have a question w.r.t Fabric Interconnect EHV Mode.
EHV mode does not learn MAC addresses on BI, It only learns MAC on SI.
now when server is sending a packet out of the POD to ethernet cloud, it will ARP and learn the MAC address of the nexy layer3 Hop, All good till here.
Now when the FI gets that Frame from server destined to L3 hop for that network it will be a Unlearnt MAC.
I also read that all Unlearnt MAC recieved on SI are Flooded to All other SI and Pinned BI.
If tha bove statement is true does FI flood traffic leaving the POD to ALL SI interfaces EVERYTIME?
It sounds too silly, but asking based on what I ave been reading.
Thanks!
Vijay Shekhar.</description>
		<content:encoded><![CDATA[<p>Great work Brad!! really!</p>
<p>I have a question w.r.t Fabric Interconnect EHV Mode.<br />
EHV mode does not learn MAC addresses on BI, It only learns MAC on SI.<br />
now when server is sending a packet out of the POD to ethernet cloud, it will ARP and learn the MAC address of the nexy layer3 Hop, All good till here.<br />
Now when the FI gets that Frame from server destined to L3 hop for that network it will be a Unlearnt MAC.<br />
I also read that all Unlearnt MAC recieved on SI are Flooded to All other SI and Pinned BI.<br />
If tha bove statement is true does FI flood traffic leaving the POD to ALL SI interfaces EVERYTIME?<br />
It sounds too silly, but asking based on what I ave been reading.<br />
Thanks!<br />
Vijay Shekhar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Morgan</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-5422</link>
		<dc:creator>Brad Morgan</dc:creator>
		<pubDate>Wed, 02 Feb 2011 06:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-5422</guid>
		<description>Brad,

What would the &quot;best practice&quot; recommendation be for a vmware deployment on UCS with redundant fiber interconnects connected to Nexus switches when the &quot;SAN&quot; connectivity is via iSCSI rather than FC. Would it be better to group the iSCSI vlan in with the other wan/lan traffic vlans so that it could share in the benefits present with vPC, or would it be best to set up the 6100s in switch mode to isolate the iSCSI vlan to protect it from broadcast storms or loops in the other vlans that might choke its bandwidth off. Is there a way to guarantee bandwidth to the iSCSI vlan to make sure that it won&#039;t be adversely affected if an issue arises in one of the other vlans?

Your posts are exceptinally helpful.

Thank you</description>
		<content:encoded><![CDATA[<p>Brad,</p>
<p>What would the &#8220;best practice&#8221; recommendation be for a vmware deployment on UCS with redundant fiber interconnects connected to Nexus switches when the &#8220;SAN&#8221; connectivity is via iSCSI rather than FC. Would it be better to group the iSCSI vlan in with the other wan/lan traffic vlans so that it could share in the benefits present with vPC, or would it be best to set up the 6100s in switch mode to isolate the iSCSI vlan to protect it from broadcast storms or loops in the other vlans that might choke its bandwidth off. Is there a way to guarantee bandwidth to the iSCSI vlan to make sure that it won&#8217;t be adversely affected if an issue arises in one of the other vlans?</p>
<p>Your posts are exceptinally helpful.</p>
<p>Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Hedlund</title>
		<link>http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/comment-page-1/#comment-5338</link>
		<dc:creator>Brad Hedlund</dc:creator>
		<pubDate>Mon, 24 Jan 2011 17:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://bradhedlund.com/?p=1421#comment-5338</guid>
		<description>aiwa,
Yes - you can connect UCS to any standard 1GE or 10GE switch.
Nexus is a good choice for the 10GE density, performance, high availability, and vPC - as discussed in one of the videos.</description>
		<content:encoded><![CDATA[<p>aiwa,<br />
Yes &#8211; you can connect UCS to any standard 1GE or 10GE switch.<br />
Nexus is a good choice for the 10GE density, performance, high availability, and vPC &#8211; as discussed in one of the videos.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

